What this shows is how terrible raw JS is, when all of this crap is required to fix all of the edge cases and make things actually work the way it’s supposed to.
Your own rock, in this economy?
The damage was not the actual pricing (which was cheaper than Unreal), the reason people are going to leave for Unreal/Godot and never come back is the loss of trust. Nobody wants to be chained down to a company that’s willing to pull the rug out like this.
If you think they had impenetrable security before this, I’ve got some bad news for you…
It’s the API that ALLOWED the misuse in the first place, so the developers are the ones to hold accountable.
Git was specifically CREATED to facilitate this exact mailing list workflow.
These are not "mistakes", these are willfully evil acts.
I'm just going to quote another comment here:
Billet Labs sent their best prototype (as in, the only one they had) to LMG for review. Linus proceeded to strap it to a video card where it didn’t fit, so bad that there was a 1mm gap (which might as well be a million miles when you’re talking about cooling). Of course the performance sucked due to it being strapped to a card it wasn’t designed to fit, linus trashed the block and the company. And here’s the part that just fucks me off. Billet Labs SENT THEM THE CORRECT CARD WITH THE BLOCK! There is literally no valid excuse for putting it on the wrong card, Billet Labs sent them the correct one!!!
Combine that with the image in the OP, and there's just no excuse. These are not the actions of someone that "intends no malice". This is not an "accident". This is not a "learning opportunity". This is not a "mistake". This is a person doing everything in their power to selfishly extract every dime they can from both their viewers and this startup.
They intentionally lied to the viewers because trashing a product gets more views. They intentionally lied to the startup because they got more money from selling the prototype.
They do not deserve any sympathy.
So you’re saying it’s about as robust as a typical Linux application then?
I don’t think that last part is entirely accurate. The reason the weak gravity causes tides is actually because it’s acting over the entire ocean all at once.
It turns out that the ocean is a bit heavy… when you add up the entire mass of all of the water, this imparts quite a substantial bit of potential energy. This can be seen as a “bulge” outward in the moon’s direction, making the planet look a little “squished”.
If the planet were perfectly smooth, this probably would be fairly stable as the bulge wrapped around the planet… however, because we have continents and the sea floor, this movement of water crashes into the land and causes ripple effects with a huge amount of kinetic energy.
I don’t think it would take more that a few years for this process to ramp up to our current level of tides, if there were some way of doing such a ramp up in a controlled way.
The problem is that almost all electronics available online (not just on Amazon) are rebranded Chinese bargain bin garbage marked up by 10x and people think "it must be good because it's expensive".
Really your only option is to either accept that everything is disposable and will need to be replaced frequently, or to find the "good" brands and stick to them.
That last part is by design... it's why a lot of this shit is perpetuated by the same parent company under a different name, to create a "hostile environment" to make it so you can't shop around for cheaper prices.
The worst part is they're also removing all of the existing gold awards from old posts as well.
If you’re branching logic due to the existence or non-existence of a field rather than the value of a field (or treating undefined different from null), I’m going to say you’re the one doing something wrong, not the Java dev.
These two things SHOULD be treated the same by anybody in most cases, with the possible exception of rejecting the later due to schema mismatch (i.e. when a “name” field should never be defined, regardless of the value).