It’s generally conspicuous consumption, where the main point is to flaunt wealth.
Functional aspects like how well an engine runs or a clock displays time are part of that, as poorly functioning but expensive-looking stuff is generally derided, but you also can get great-working stuff that doesn’t look flashy.
The O is for the kind of whooshing sound
Yeah, and Android has had some 16 years of “optimize later”. I have some very very limited experience with writing mobile apps and while I found it to be a PITA, there is clearly a lot of thought given to how to not eat all the battery and die in the ecosystem there. I would expect that kind of work to also be done at the JVM level.
If Windows Mobile had succeeded, C# likely would’ve been lower as well, just because there’d be more incentive to make a battery charge last longer.
Is there a lot of computation-intensive code being written in pure Python? My impression was that the numpy/pandas/polars etc kind of stuff was powered by languages like fortran, rust and c++.
And it powers a lot of phones. People generally don’t like it when their phone needs to charge all the freaking time.
And battery costs, including charging time, for a lot of devices. Users generally aren’t happy with devices that run out of juice all the time.
Yeah, none of that with bat:
λ bat $(type -P bat)
───────┬──────────────────────────────────────────────────────────────────────────
│ File: /usr/bin/bat <BINARY>
───────┴──────────────────────────────────────────────────────────────────────────
λ bat < $(type -P bat)
───────┬──────────────────────────────────────────────────────────────────────────
│ STDIN <BINARY>
───────┴──────────────────────────────────────────────────────────────────────────
λ
Or bat, which will just print <binary> in those cases
Oliven, Norwegian. For some reason it’s an uncountable noun.
Ah yes, traditional urban cores, historically entirely without any good food options, either delivered, on the go, or even sit-down at odd hours
As if anyone cared if they had to wait a total of 3 seconds in a workday.
That depends on when it appears. Some tasks kind of have to feel instantaneous, and there might be a pretty slim margin between okay and frustrating.
But yeah, that’s the kind of savings that mostly matter on the scale of regional or national grid planning.
Most engineers already write bloated, abstracted, glacial code that burns CPU cycles like a California wildfire. Clean code? Ha! You’re writing for other programmers’ academic circlejerk, not the hardware.
It’s interesting that everybody else preaches ‘Write for the human first, for the machine second’.
Yeah, the author seems to lean too hard into the “programming is electronics” model, where the opposing end is “programming is math and formal logic”; most of us take some mixed view. And most of us have higher correctness requirements than what a reasonable effort in memory unsafe languages like C and C++ gives us, so we trade away some machine efficiency. In the authors parlance, most of us aren’t interested in the demoscene circlejerk; we need to make tradeoffs between maintainability and everything else. Write-once code isn’t good enough.
There have been attempts at establishing a third pole of “promptgramming is natural language” or whatever ever since COBOL promised programming in plain English, but the ambiguity of natural language when used to encode a business logic machine means that a “sufficiently advanced compiler” will have to be extremely advanced, on the order of including the manager and the entire engineering methodology.
I think some of the stuff you worry about as a kid will just arise naturally. Ideas like not stepping on cracks, or imagining monsters in dark places are likely produced spontaneously and naturally by an underdeveloped ape brain.
But it’d be nice if we didn’t tell kids about old superstitions, yeah. Wait until they’re old enough to react with dismissal about the stupid stuff people used to believe.
Yep. The colour theory stuff in there makes MBTI and horoscopes look detailed and well-documented in comparison
I’ve been using neovim for years (and the vim family for decades), and I guess with LSP it’s pretty much an IDE these days.
You’ll likely also want to check out ruff for linting and formatting, by the same company that makes uv. It doesn’t enable a lot of lints by default, but there’s a long list of checks to enable.
They also have a typechecker, ty, which is still in early alpha. If it’s as good as their other tools I expect it to become the standard for typechecking Python. Currently you’ll likely want to go with pyright for that.
Yeah, it’s the kind of thing that in utopia would actually help search engines and users find relevant pages, but under capitalism becomes “hey, listen! look at me my ads!”
I think it’s far more likely that the article that doesn’t know what “sweep under the rug” means also got other stuff wrong.
Yeah, but there’s also no way anyone in the Nordics would be fine with a nine-hour workday. There’s something clearly wrong here.
I’d rather guess that they’re working a five-day workweek but have cut the hours per day from 8 to 7.2, or 8 hours Mon-Thu and 4 hours on Friday or the like. The article just comes off as weird.
Yeh. Ubuntu also discussed it back in 2019, and wound up keeping some of it so Steam would keep working.
I expect the willingness to bend over backwards for one proprietary and very profitable app doesn’t last forever, and given how involved gaming often is with pushing technology, it’s frankly weird that Steam is still shackled to 32bit like that.