7,124 karma · joined May 3, 2010
make menuconfigNobody wants this Copilot everywhere, but they sure are pushing it anyway. It's like they completely forgot how to make a product and only know how to push their agenda using whatever monopoly is left.
The developer makes a highly optimized native app that is a hit with the user. Now that it's a hit, the developer is now big company. And big company needs telemetry, A/B experiments, fast iteration. They can't just sit around waiting for the original developer to spend more years crafting another masterpiece. Due to tech, sign-ins, or what have you the app is also a kind of monopoly. Since it's a monopoly, quality doesn't matter. It can be a bloated electron thing and nobody can do anything about it other than suck it.
The main issue with EF is ultimately there is an expression builder that maps linq expressions to sql. This mostly works, until it doesn't, or it does but has strange generated sql and performance. If all you are doing is CRUD or CRUD adjacent then it's fine. But for some complex stuff you spend a lot of time learning the innards of EF, logging generated statements, etc. It is time better spent writing good sql, which something like Dapper allows.
What valid JSON would be invalid MAML?
All of that is trivial when you consider the Lua reference implementation. It is beautiful.
This is untrue and actually uncommon. Not every instrument is a guitar. Left handed cello players don't string their instrument upside-down. They play it right handed.
Why use Photoshop when Gimp is available? Fusion360 when there is FreeCAD? etc.