I have been very happy with github for _years_. Lately, not so much. Now I want to try a self-hosting alternative again. I tried gitlab years ago (pre-pandemic, IIRC), and it wasn't for me (they had _serious_ security issues as well, which of course didn't affect my self-hosting thing, but still...).
So - where do we stand in August 2026?
*EDIT:* No, I don't want anything related to Felon Musk.
It's the other way around for me: as 99% of the stuff I develop is .NET (and I use EF Core for database stuff), I can get away with SQLite for local development, prototyping (and even staging), and then just "flip a switch" for it to run on production PostgreSQL.
I can't recommend this "switch". If you are not testing locally with the same relational database as in production, you can miss mistakes and bugs. This is not just theoretical. One example where I thought I will be fine using SQLite was with a small Django project. But time and time again I ran into limitations of either SQLite or Django's database adapter for SQLite, when it came to dealing with many to many relationships in the model and through tables, requiring me to work around the limitations. There is no guarantee, that these workarounds in turn will work the same in PostgreSQL in production.
Anyway, it is a basic practice of keeping test and dev environment as close as feasible to production, to avoid missing issues and wrong assumptions.
> Anyway, it is a basic practice of keeping test and dev environment as close as feasible to production, to avoid missing issues and wrong assumptions.
Containers are great for this during development.
Testcontainers are great for tests in particular when you don't want to use some mocked in-memory DB because those have the same issues as using a different DB during development: https://testcontainers.com/
Agreed, and it is easy to have a Postgres container for local tests or in CI as well. I don't really see much need to avoid Postgres in testing. Also if production runs in containers, testing can and probably should just run in containers as well. Also makes for a cleaner test setup usually.
That's kind of risky considering the radical differences between types in SQLite and Postgres. There are plenty of situations where EF will need to be configured differently in order to map your .Net types correctly to each DB. Or subtle differences in behavior due to storage differences (particularly SQLite's predilection for storing things as strings). It's so trivially easy to run Postgres in Docker that I don't really see the advantage of using SQLite for local dev.
Yeah this really isn't so true anymore. I was a diehard Dapper fan for a long time, but the performance of EF Core is comparable to Dapper now. Dropping down to SQL in EF Core is super easy and parameterized. I just don't even bother with Dapper anymore. I have an app with ~200k users with the slowest query being ~6ms and of 1000s of queries only 3 are hand rolled complicated SQL written for perf executed via EF Core.
if you knew how to cook it, you could use make older EF Core (and original EF) go brrr. you sound like you do know. my problem is that it is hard to find out what exactly is the best without dropping down several abstraction layers, sometimes, as you noted, to raw SQL.
why not just construct SQL queries in a type-safe DSL, like, say, JetBrains Exposed does? you are writing what's basically SQL that your compiler understands and your existing tooling checks for free. (granted, C# may need an additional Roslyn analyzer, but it's still simpler than either guessing what transaction LINQ will make or writing SQL in strings.)
On July 9, 2026, the Bundestag passed Germany's new electricity-capacity law, which subsidizes reserve/dispatchable power capacity as coal is phased out. SPD and CDU/CSU voted for it; the Greens and Die Linke voted against it.
The Greens specifically argued against a long-term fossil-fuel lock-in, while Die Linke argued for renewables and batteries instead of subsidizing new fossil gas plants.
The law itself is primarily about new hydrogen-ready/gas-capable reserve plants, not coal plants.
I've never seen one here, which makes sense because we don't use much coal. I suppose if they were 200m high and scattered across half the state I'd have a similar opinion.
Coal mines are often associated with massive slag heaps and they can be over 200m in height.
They are not pretty but what they lack in beauty they make up for with danger to the local community from leached chemicals, underground fires and landslides.
Europe? The entire continent? The continent that includes large swaths of Russia?
I give up, I don't even know what you're trying to imply here. That somehow Texas (a state, in a country, in a continent) burns less coal than an entire continent? And...?
> If you continue to use our services after the billing adjustment, you will be deemed to have accepted the adjusted billing terms. If you do not agree, you may choose to cancel your service and apply for a refund.
Is it just me, or does this sound like the pricing change is somehow retroactive, i.e. I have to pay extra for already used (and paid for) tokens?
> You can't just raise minimum wage and expect people to make more money since businesses need to fire everyone who aren't worth the new minimum wage [...]
This way of thinking is what's wrong with USA (among many other things).
You don't (or at least shouldn't) hire lots of people because it's cheap.
It's a voluntary agreement between people. It's not immoral to pay minimum wage to someone when they both agree. I find it to be immoral for the government to force themselves into the agreement.
Only ~1% of people in the US make federal minimum wage. ~58% of that 1% are serving related occupations who collect tips that are not counted in BLS wage data.
You need to use median wage - which is ~$24 for all occupations.
If that way of thinking is wrong, why not just make the minimum wage a million an hour and let everyone be mega wealthy? What do you think would happen if we passed that?
Edit: to the down voters, what is your answer to the question?
You didn't answer the question. I suspect that is because basic economics kicks in and you quickly realize that you can't just raise the minimum wage as high as you want and expect it to work. It is a complicated and complex and highly nuanced thing.
Your water example actually reinforces my point. If GP ignores the reality around drinking too much water, they will poison themselves, just like ignoring the reality around minimum wage would destroy things.
Because the question is stupid on its face. If thing X is good, 1000x X must be good too is such a stupid fucking mentality. It doesn't apply to literally anything. Vitamin C is good. Too much is toxic. Sun exposure is good. Too much is toxic. Drinking water is good. Too much is toxic. Such a basic fucking concept that exists across basically everything in our society.
Yet here you are stating that because a higher minimum wage is good, it must be more good to make the minimum wage "a million an hour" too right? Which doesn't follow at all based on literally any other example of things that are "good". It's mind-numbingly stupid. It's a ridiculous straw-man made by someone either disingenuous or ignorant.
Whatever is the darker shade of blue in the bottom-right graph had a bump at the same time cost did. Perhaps that's output tokens (which include reasoning)?
I'll add many have remote access that is like a serial port. Digital Ocean has a "recovery console" that appears to work in a similar way. It runs in your browser. It works when other stuff breaks.
Now, for Linux, they have a SSH client in the browser enabled by default. I use it to manage a pile of $5/mo droplets, like the author.
