mrighele

European cars are expensive not just because the manufacturers are greedy, but also because we want them to pay their employees a proper living wage, human working hours, sick leave, a few weeks of vacation every year, healthcare... Those don't come for free.

Also you have to add that cars sold in Europe (regardless of manufacturer) require by law much more expensive extras compared to other countries.

It's like Intel i3/i5/i7/i9, or nvidia 50/60/70/80.

It is meant to give a rating inside a generation. Different generations are not necessarily comparable. an i7 is better than an i5, but not if you compare an i7 7xxx with an i5 14xxx.

A nvidia xx80 card is better than a xx60 card, but not if you compare a 1080 to a 5060.

The only difference for OpenAI is that not every generation has every model.

> While employed, you’re using corporate accounts and can’t be banned.

Google/openai/etc detect that you are using your corporate account from the same home where you use your banned account, corporate account get banned for trying to circumvent the ban.

Can you be sure this will never happen ?

I like Bun too, I think its ergonomics are much better. If you are writing a front end you can produce the final output without an external bundled. Similarly if you are working on a backend TS project (less of a problem these days but transpiling TS used to be full of gotchas depending on your dependencies) . You can even just build a single binary to deploy in your container. Useful for command line tools to (they come out a bit big, but for personal use is not an issue)

> scaling problems due to the influx of LLM assisted coding

You mean people pushing LLM assisted coding, or github's own coders pushing LLM assisted code to production ? :-).

I am more inclined to think that it is the second, but if the reason is the first, what is particular hard to scale ? It's not like everybody is vide-coding into a single repository, so I would expect that most of the load would naturally be scalable by increasing the resources. If for some reason that is not possible, I would expect a corporation as big as Github to keep the paying customers working by gracefully denying service to the free tier, not to collapse like an house of cards.

I guess there is a certain amount of luck in this, probably related to the provider, or the range that your IP reside into. (I guess google and microsoft keep their own blacklists, regardless of what public blacklists say). I wonder if the best course of action in that case is to just spin up a new server on a different provider and try again.

FWIW, in my case, I am running the server on Hetzner, even though is supposed to have a bad reputation, but I have been using its IP for more than 10 years for other things (web server, personal services etc) so I guess that helps

Last year I started self hosting my email. I found that once you setup the “usual suspects” (DMARC, DKIM, SPF…) outgoing mail works without issues. In fact it works now better than the (small) provider I was using before.

And setting them up properly is not even that difficult nowadays

Not all non-trivial workloads are web-scale. There are plenty of on-premise applications out there that have at most hundreds or thousands of concurrent users, and the connections come from a bunch of fat spring boot servers that handle most of the pooling by themselves.

> (Optimized by you through testing. Not that AI)

Why not optimized by AI through testing ? Give it a test set to work on and let it loose.

# Prompt Cache Misses

> It globs your filesystem and re-reads AGENTS.md (injected in turn-0 system prompt) on every SSE turn. If you put a quick note in AGENTS.md to be read in the next session, you immediately force a full re-evaluation.

> Personal favourite: it puts the current date in the turn-0 system prompt and re-evaluates every SSE turn. If you’re using OpenCode at midnight you get a full prompt cache miss.

I used opencode with deepseek v4 via openrouter during the weekend. Openrouter claims a cache hit rate of about 95%. Maybe it can be improved, but it doesn't seem broken.

I agree that it is bloated, and uses a lot of memory and cpu. But I don't remember seeing any bug during its usage, or at least not big enough to notice

> So if that were the case then why isn't there some sore of daemon or system software service that tracks the expected life of the hardware?

Some linux distribution will regularly check SMART data from disk and warn you if some threshold has passed (like number of corrected errors, spin up/down, total hours etc).

That said, if we talk about consumer hardware in a home lab or the like, of the disks that I bought in the past 15 years, only one broke down, and it did fairly quickly so my suggestion is to use redundant storage, make backup and change the disk when it breaks down. (Enterprise disk and usage is another can of worms of course).