alex_smart

How is this not a trademark infringement?

If a trend can be established by one data point, surely it can be countered by four?

I am surprised not enough people are talking about the philosophical implications of these inventions. AI is the biggest attack on religion/human-centralism since Newton and Darwin.

For intellectual property, copying without permission is theft.

Because simplicity is hard and often the result of careful thought. Anybody can keep piling pile of shit on top of pile of shit which is why that sort of code is so common in our industry.

You could just let the driver support something like “LOAD DATA INFILE LOCAL <>” for the same effect.

Why would you need this over just using the jdbc driver?

Pretty sure that is entirely an unfair comparison. You don't need a connection per thread either. It is common to have web servers handles thousands of requests per second with a connection pool size of 20. As long as the handler threads borrow a connection for only a little time and block waiting for a connection while other threads are doing their thing, it works out fine.

There is absolutely no logical reason why database pool sizing could be a reason for preferring fibers over threads.

The /wordpress/ part of url suggests otherwise

The problem only arises when you have to worry about persistent state. As soon as you have to worry about that, you have to think about backups, replicas, disaster recovery drills and so on. It is much easier to solve for that can of worms for one system than three.

Sorry my brain somehow missed the literal first three words of the oc.

Less installed things means smaller security surface area, fewer things to patch when CVEs get discovered etc.

Thanks to `kubectl debug`, you don't need to install debugging utilities into your production image.

Isn't that the whole point of TCP? Creating a pair of two streams you can read out of and write to out of less reliable network primitives?

I am not sure why this is a revelation. Any college level networking course would cover this?!

Who uses JWT like this anyway?

Typical production architecture would look like - frontend only ever sees an opaque session cookie - bff stores the access token against session and attaches it when calling backend services

Yes, storing JWTs directly in the frontend client is a bad idea but surely there is a better way of communicating that than "JWT is a scam and your app doesn't need it".

> RS256 verification is in the same order of magnitude as a Redis lookup

But the point is that the verification is CPU bound and local to the service - which means that it is horizontally scalable.

> If I’m understanding this correctly

You're not.

> it starts by raising this question, then argues that it’s kind of a cheap and meaningless punch-down.

The cheap and meaningless punch-down in the article is the vibecoding accusation. The question in the title is actually their main line of attack against that accusation, all the way to the end.

>> QED So. Where are the vibecoded Photoshops? WHERE IS THE THREAT YOU MADE UP TO ATTACK ME?

>>I'm waiting.

I find it hilarious that so many people are finding it so difficult to grasp even the general line of argument of the article despite trying earnestly.