kyruzic

I agree its what they are being used for and their primary revenue source.

My point is mainly that was never the pitch that got ai the hype it did and imo doesn't justify the valuations even if we all lose our jobs to ai. Because it no longer seems like they even think its making other jobs go away.

So at this point new models seem to only care about one task, software development. This really was not the original pitch of ai and I do not see how it justifies the insane spend or valuations it has produced.

The funds in USD were recovered because bitcoins value is 5x higher than it was when he got arrested.

He even started his comment like it had been approved by lawyer first lol

2025 is 6 months away. There is absolutely no way a majority of applications will use it.

And OpenAPI is spending more than $20 to provide you that service...

The type any exists. The type unknown exists. The types actually have no meaning at runtime.

I do agree with this, but I'd argue the developer experience of nodejs with Typescript is far worse than that of rust/go

Nodejs backends are not "as performant as you build them" nodejs is slow! This is an undeniable fact. If you ever have to do anything computationally intensive, which every backend at some point will nodejs will become the bottleneck.

That's why you shouldn't use slow backend technologies in the first place because you get to the point where you need preformance and it's impossible because your limited by extremely slow runtime you chose initially because it was flashy (not even easier to developer for) when you could have just chosen something better from the start.

Simple crud apps can get by fine with those technologies, but in the future I'd still never use it because you're leaving huge amounts of performance gains on the table for virtually no benefit. I don't buy the argument that javascript is just easier to develop for because it's simply not. The js ecosystem is a disaster.

Go is perhaps the simplest language to learn there is. It's almost impossible to not get it to work because it has so few things you can actually do.

And nodejs only preforms well in hello world benchmarks, real world applications are nothing like that. Once you start having to manipulate large arrays or do any large amount of math nodejs preformance goes into the dumpster.

Typescript (nodejs) backends are not performant, and your ultra modern stack is going to just cause you issues going forward if you need to scale. Prisma is really bad too, slow queries and no flexibility. If you ever need to do any sort of complex query you will just have to write sql anyway. And typescript is only sort of static typing.

These technologies are great for prototyping and building a v1 release to see if what you're trying to achieve is actually possible, but you will regret it later on.

The reason I know this, I work at a startup where we literally had the same backend stack and its been nothing but preformance issue after preformance issue. And it all needs to be replaced. We would have been better off building everything with go/rust in the first place. Or even java.

I didn't say they were individually selected and yes they can just throw out a certain number of potential jurors without any reason.

Maybe I worded my comment poorly but the point still stands.

There's two possible decisions the jury could make, and the jury is composed of a group of people who are chosen by both sides to prevent it from being a biased decision. Obviously not perfect but a lot better than you describe.