Quality will be just around 90v phase degrees behind.

The knowledgeable senior did his job and left. Juniors need to pick the slack and become seniors. That's the phase disparity, and in the middle, spaghetti happens.

Easy. Look at the curve of IT engineer salaries. That pretty much reflects the distribution of quality code.

Good engineers aren't paid for trade secrets. They'll mostly push for divulgation, because that leaves their mark (and possible portfolio), and have the luxury to push, argue and/or ignore.

So they'll always be in demand, but they are expensive, and thus, companies pressure their mid devs (because they don't wanna pay a senior) to take responsibility without compensation.

@12bitfloat
@Lensflare

I said this before. Will say again. We all can read code. We can not read intent. Comment intent, not just blindly repeating what code evidently does.

Sure, if you use some obscure technique like quake fast sqrt by all means comment.

In the end, it's all about being able to put yourself in the shoes of anyone new to your project.

In nVidia, it's enforced that anything that is pushed must build, and our AI assistant can actually tell (because it analyzes frequency of use and such) whether what you implemented is easy enough to maintain.

It only flags when it doesn't understand what we try to do, and forces us to comment (again, intent) the AI has a compiler, and therefore knows better than us what code is trivial and what is doing esoteric shit

After all, rust may not have this problem (or so he claims), but, it shit hits the fan, and unsafe is used, and an unexpected object is created, C++ can just call sigab(o)rt, but Rust's garbage collector doesn't know what to do with it... So it lives. To adulthood.

So yeah. Rust wants to be NSFW, but its overly strict upbringing by parents who forgot they were also children holds it back.

That's it. In my head it's a spectacular meta-joke. I'll be fine if just one person finds it funny. XD

Noobs.

C++ is the kinkiest of them all. Accepts all sorts of deviations C would object (bad um tshh) to,
requires esoteric codewords for safety, and can interface with pretty much anything you want, if you don't mind the ocasional mangling... (Liberal full-gcc, ocassional-clang or prude MSVC).

Rust is like, "I wanna play, but don't want to get any STD- sorry, L-, so I'll try to play and preach safe, despite that ohh so much limiting my fun."

And of course, when it comes to the kinky compilation time, C++ will carefully foreplay its includes and macros, ensuring they are part of the fun by literal inclusion.

Rust may call the same partner twice, or thrice, but the pimpmo(du|bi)le only rides once.

Booooring.

And then again, Rust will complain that he wants to play safe, and that's fine, but it's no fun.

The theme should be like my room, and like my soul. Abyss dark.

@glowFX

Not that I want to defend php, but the situation you described is exactly what php-fpm was made for.

Rust vs C++ is like Ubuntu vs debian.

They are the fucking same. Just different philosophies.

Ubuntu is essentially debian unstable. Debian based, but not wanting to conform to the rigidity of debian release cycles.

Rust is one (of many) attempts to re-do C++ without adhering to it's two core principles... Keep already written code working (C++ is oh so much held back by this) and having zero cost abstractions.

Rust breaks the first by existing. It's new, doesn't have the baggage. The second one it breaks by forcing you to adopt what they say is secure.

Sure, there are a lot of things you, as a developer, can mess up, but it shouldn't be enforced by the language. Because in doing so, it's no longer zero cost. Bounds checking, for example, *does* have a runtime cost. (As do many other "security" measures.)

Contrary to popular belief, C++ *does* have these mechanisms. They are called debug layers, and, following the core principle, are opt-in. Don't pay for what you don't use.

Know JavaScript since it was the thing it should never have tried to outgrow. A DOM manipulating language.

I started dealing with node at around 2014 or so.

Of course, it helped that I know what asynchrony is from way before Promise was a thing, and that I'm way too familiar with V8 and libuv.

I dare say I know all the inner black magics of JavaScript and typescript, and have used them to pull crazy stuff.

Yet still the decisions the ecmascript committee makes will forever keep js as a clown language.

So, all in all, considering that previous to node there wasn't any depth to really explore, I'd say 4 years or so.

Dead element detection is simple enough. Log your tasks. Create a meta object when stuff is supposed to happen.

Upon completion, delete original video and meta object.

Your cleaner can periodically check for videos without meta object and flag then or delete them outright

Why do you control shit from the *client*?

S3 has hooks for successful uploads. Don't rely on client code. (A malicious user could probably replay your "process video" message and DoS your app)

If you are worried about the webhook, s3 uploads can trigger lambdas. Use those.

Also, in your stated case you can use redis TTL and key space notifications to do what you want without relying on polling.

I don't think the developers of Xcode use Xcode to develop Xcode.

I'd gladly welcome them here if they could have free speech.

If they are just gonna spew the same curated bullshit corporate apple stuff, they can keep it to themselves.

Well, definitely beats still paying for a domain for a project you never even started. XD

Uh, this, you know, was a friend of mine...

All my keyboards have insane amounts of rundown. I type. Furiously. Probably is a reflex from when I learned mechanography in old mechanical typewriters. But yeah, I do love the tactile feedback and the mechanical aspect of it all.

In fact, keyboards should implement a mechanism where when you smash enter or escape, it automatically opens your current app's help or documentation or whatever, just like in mobile phones when they detect shaking.

Now for real. That's not usual behavior from trying to json.parse something too big.

You have a memory leak somewhere. As @Lensflare said, profile.

But it's most likely some unbounded cache behaving faulty.

Sounds like go SAX or get (butt)SEX'd

@D-4got10-01 murican hotdogs are made of plastic so of course they are bad.

If you go to a real brauerei (spelling, I know, don't have German keyboard and ICBA), it's real bread, real sausage, real condiments, and I refuse to believe it's bad for you.

Now for real, everything in excess is bad, but I just don't buy the narrative that just because once in a while you want to pork pork food you are doomed.

Just don't overdo it, and fucking enjoy it, ffs.

Makes me remember all these "vegans" crying in joy when they are fooled into eating meat...

@Lensflare

I admit I'm also one of those people that make agile fail.

I've always been kind of the fireman dev, putting out fires here and there, and when you are constantly shifting your attention everywhere, the scrum master is delusional if he expects me to *also* pull whatever was in the usually already bloated sprint.

@BordedDev

Agile is the biggest lie of the dev world.

It would be useful if the only involved parties were devs, but since bosses and salesmen tend to allow client reps in planning, it turns out to be "do whatever shit client asks for, but more agile!"

In short, a shortcut to bothering you in ways they couldn't before.

Right now I was doing a side project involving some audio socket tunnels.

Every junior said it couldn't be done because it had too much latency.

Enter setsockopt (and having to do it in C or python) to save the day.

No vibe programmer will ever learn that shit if left to their own devices.

Good thing I don't have to attend those dreaded stand-ups.

@D-4got10-01

Being able to publish with minimal (if any) QA, and hardly any moderation from stores leads to that, yes .
In the end, both the store and the dev hurt themselves, because erasing (gommaging, fucking GotY)
Is something stores won't do, and it drives down interest in others.

And it's especially egregious (and confirms my take) when all people do is complain about games not coming to gamepass day one, and their response was locking day one releases under the higher tier subscriptions.

@TeachMeCode

The idea is that for a "play any game for a fixed subscription price", having games day one is actually a big deal.

Gamepass subscriptions would tank if people had to wait, say, 1 year to play.

Yeah, dads probably wouldn't mind, but a lot of the public of gamepass, are, as I said, young adults or fathers that like videogames, would.

They could easily just buy the 3/4 vidya a year they want, and it would come out cheaper than gamepass.

Let's be real, outside of day ones, or big titles that come later, no one gives a fuck about the filler shit they include, just like in steam.

@Lensflare

Well, most games are priced similarly on PC. Unless they are indies, but indies (hate me as much as you want, hardly ever meet my standards). They are the equivalent nowadays of shovelware, with some hidden gems in the midst.

All things aside, I could buy pretty much any videogame I wanted, but taking into account the whole world, let's say, and I'm being optimistic, people can buy 4 games a year. That's, at least, 280 euro.

Gamepass at 30/mo, is 360. No longer worth it.

I mean, if I really want to play day one, I can buy the fucking game. And, especially for people with kids and such, which is obviously their target audience (male adults with disposable income), it's a ruinous deal, because for them, one of the four games a year can easily last more than three months...

I guess I'll stick to my model. Since companies lie, I'll lie. I'll keep pirating every game I can, and if it's worth the buck, I'll pay for it even if I already beat it.

And so no one can complain, in the last 2 years I did it with BG3, ghost of Tsushima, black myth Wukong, soul reaver remaster, expedition 33, hades, and triangle strategy.

Slow API double posted

Microsoft got drunk on power. They really have no competition, so the suits on top thought "hey, monopoly, let's milk"

Newsflash, it backfired.

And for all the doubters, C++ actually has the best of both worlds.

Because you can choose to link against a debug runtime or a release runtime, meaning again (zero cost) you don't pay for what you don't use.

Yes, I'm aware it's harder because you can't mix main program and libraries with different runtimes, but alas, then again, you can fucking static link...

So yeah, by all means, try. C and CPP will not go anywhere, because, as captain Yamamoto said, no stronger shinigami has been born in over a thousand years...

Don't care about the off topic discussion.

So long python is still implemented in C, python will close the gap more and more to C++.

CPP is screwed in stubbornly maintaining backwards compatibility.

Being utterly verbose is a byproduct of that.

Rust may become a worthy successor... Maybe. Definitely not with the choices the steering committee is doing.

In the end. You can never prevent all footguns while enabling uncontested top notch performance.

Every language that tries to do so will inevitably fall behind C and CPP. At least while they don't adopt the zero cost abstraction model, which is the cause of the CPP cruft.

If anyone has the solution, I'm all ears. I'll happily vote them for the Nobel prize.