It gets funner when it’s a value that actually is a complex number with an “imaginary” component, but gets represented by NaN because the real value doesn’t make sense by itself. In reality, imaginary components are extremely critical for some equations and are totally valid.

I wish I remembered my math well enough to have one off the top of my head, but I don’t use it often enough… IIRC, it’s even important for magnetics, let alone more complex physics, so it does come up in practice quite often. I think there’s even a fundamental part related to derivatives, but yea, don’t exercise math enough. Might be misremembering.

Keep defending the bahavior.

Oh, so it’s OK if Google does it… Fuck you defending these tech giants stealing data. Seriously. Fuck defending any part of this shit.

I just never set up my voicemail. Then people who actually have a chance of successfully contacting me know not to even try the phone.

The funny thing is, as much as people shit on Java, that’s exactly what its Java EE container arch was for. Truly tiny microservices in wars, an entire app in an ear. All managed by a parent container that can dedup dependencies with a global class loader if done well, and automatically scale wars horizontally, too.

No idea how to get that level of sharing with OS-level containers.

That might just be the typical “business speak”, but I feel you on it. It takes a certain kind of child robot to accept that sort of crap without at least internally cringing pretty hard.

Though remember: They have to sell this stuff to moron managers and execs who think on that level.

Simplicity is literally part of the point? Who wants to look at a flow chart when it just needs to be a few lists of tasks? The general design is still heavily inspired by physical cards or sticky notes, but it’s always been just a list of lists.

Aren’t some of the scenarios for needing a semicolon logical-domain problems and not syntax issues? I wouldn’t trust autoformatting to spot a logical problem, though I also hope no one is writing code that flippantly. (as if honest mistakes aren’t common enough!)

Yup! I love TypeScript, and I love the flexibility of JavaScript. With all of the type templates and generics and other black magic TypeScript has, it’s pretty easy to even support the crazy stuff like mixins and contextual parameters (if I’m not speaking too loosely while avoiding proper terms!).

A lot of the crazy stuff won’t optimize, but at least it goes to show how it’s not really tying JavaScript’s hands even when requiring TS everywhere.

You need to remember that a lot of those best practices are to cover for the performance issues from misusing loosely typed variables.

The JavaScript engine can compile clean, type-safe code down to be almost as fast as properly compiled code. When you use various features like the loose equals or various object mutations and the like, the engine cannot optimize it, leaving your code much, much slower.

The irony of you being upvoted when reality is the exact opposite…

Model collapse IS NOT from them consuming more human-based knowledge. It is from them consuming AI-generated content it thinks is human.

This has been all over the news. How can you utterly fail to understand a basic phenominon? Because you like using the AIs?

Stop lying about reality if you want them to continue giving you any truth.