gornius

It's just as crazy as saying "We don't need math, because every problem can be described using human language".

In other words, that might be true as long as your problem is not complex enough to be able to be understood using human language.

You want to solve a real problem? It's way more complex with so many moving parts you can't just take LLM to solve it, because that takes an actual understanding of a problem.

It's funny, I buy Apple Car specifically so that that I can't decide where I want to go. At work we MDM and Apple's approach isn't for everyone, but forcing something like choosing their destination simply isn't the right choice for all types of users.

I'm all for encouraging them to be on the right side of Right-to-Repair, labor laws, and environmental best practices. But I left the world of thinking where I want to go and choice for the Apple Car's tight lockdowns. At first I still couldn't help myself but to try to go around wherever I wanted with my first Apple Car or two, then I stoped that also.

Apple Car's filtered possible destinations are all I need, so I don't see why anyone would ever want to go any other place.

All of these functionalities can be provided by a simple WebSocket + REST server. The car connects to the WebSocket, and you can access these functionalities from your phone either with WebSockets or regular HTTP requests.

Cheapest servers with backend written in JS can easily handle thousands of WebSocket connections, and written in Go tens of thousands WebSocket connections. They would not ever need like over 100 of these servers GLOBALLY, which would cost them around $3000 monthly.

That's the price of 60 subscriptions, which is freaking ridiculous.

You realize that maintaining a server that would allow that costs pennies?

You wouldn't pay $150 for a lollipop, but somehow people think this is ok.

This problem exists exactly because of people like you, thinking it's OK to pay for the features you already paid for.

Ah yes, perfect data format, where markup takes more space than the actual data.

Mainly GTG response time and latency. For watching movies it's generally not a problem, but when it comes to playing games with a mouse, latency can be a huge issue, and bad GTG response time leads to smearing.

But yeah, 4x the price is ridiculous.

And as always, DRMs fuck only legitimate customers, and pirates can watch anywhere at full quality.

That's one of the reasons I don't feel bad about pirating any more. Not even the cost, but the fact that if you pay you're going to have a worse experience.

Am I too 1Gb/s fiber connected to understand that?

At least the performance gap somewhat justified the price. The other cards, mainly 4060 got little to no performance upgrade, yet cost more.

Learn it first.

I almost exclusively use it with my own Dockerfiles, which gives me the same flexibility I would have by just using VM, with all the benefits of being containerized and reproducible. The exceptions are images of utility stuff, like databases, reverse proxy (I use caddy btw) etc.

Without docker, hosting everything was a mess. After a month I would forget about important things I did, and if I had to do that again, I would need to basically relearn what I found out then.

If you write a Dockerfile, every configuration you did is either reflected by the bash command or adding files from the project directory to the image. You can just look at the Dockerfile and see all the configurations made to base Debian image.

Additionally with docker-compose you can use multiple containers per project with proper networking and DNS resolution between containers by their service names. Quite useful if your project sets up a few different services that communicate with each other.

Thanks to that it's trivial to host multiple projects using for example different PHP versions for each of them.

And I haven't even mentioned yet the best thing about docker - if you're a developer, you can be sure that the app will run exactly the same on your machine and on the server. You can have development versions of images that extend the production image by using Dockerfile stages. You can develop a dev version with full debug/tooling support and then use a clean prod image on the server.

Then again, cookie auth is vulnerable to CSRF. Pick your poison.

Although CSRF protection just adds a minor inconvenience, while there is never a guarantee your code is XSS vulnerability free.

Framework has multiple config files, allowing you to customize almost every aspect of it.

Nooo, this is too much config files, they take up too much space in my project tree.

Framework is a monolith with a single file to configure it.

Nooo, the file is unreadable and developing extensions for it is annoying.

Framework is minimal

Nooo, it doesn't have any useful built-in features.

Framework is a complete solution without too many things to configure.

Nooo, it doesn't allow me to do what I want.