The writing style is similar to the other articles by the same author. He has been doing this for years. I have no idea what your problem with the actual content is.
how not? All of this is "soft" control, if tomorrow 75% of the people in any country decided "this can't keep on going on", all relevant public buildings would be occupied everywhere and the relevant government imprisoned promptly.
On a more positive note, the fact that this doesn't happen indicates things aren't that bad right now. No amount of KYC or age verification can stop large amounts of angry people who want one thing.
People sometimes bring up China - which isn't relevant because people still remember being extremely poor, thus being grateful to the Party - or one of those dictatorships as counterexamples for this, but see the Arab Spring (food got more expensive -> revolutions), Nepal recently... etc.
>if tomorrow 75% of the people in any country decided
No kings protests was a very respectable effort....peaked at 2.3%.
Even the current administration inept as it is is basically home free on this one. Senate neutered, Courts sidelined, Treasury subjugated, loyalist in charge of military, JAG core silenced, secondary personal goons squad established and lavishly funded, Social media captured, Stats department dismantled, Cult of personality created, common enemy created (immigrants), distractions for the masses arranged (culture wars, UFC on whitehouse lawn), truth undermined (prez spouting nonstop lies & AI), oligarch class established, surveillance normalized, norm of kiss the ring & pay tribute established.
Dunno about you but to me that looks like US democracy is so cooked the kitchen smoke alarm has gone off & everyone was too busy doomscrolling to notice.
Hope I'm wrong but that list looks pretty fuckin comprehensive to me. Hell they even somehow managed to throw in a roman salute...
Marching on a street holding placards with permission from the police is a very different thing than an angry mob marching into the town hall searching for officials.
Can't say I entirely buy it in this case, but interesting rule of thumb anyway. It sure didn't feel like regime change was imminent if it were a little bigger.
The cipher wishes Charles II was the king again. The Stuart Restoration did happen in 1660 in fact, restoring Charles II to the throne. Legend has it he died of laughter, which checks out with the cipher because he was laughing how his wish got fulfilled yet he could tell no one about it yet :P
I suspect this happens due to optimising for reasoning... if you insert a few words, it will suddenly start to make more sense.
"If the crashes stop, (that means) the factory overclock is marginal; (so) run a small negative offset. (to confirm this hypothesis)"
The core thought is basically avoid crashes -> caused by marginal overclock -> apply small -offset to test.
Which is exactly the order the sentence is in :P
1. If you have debug symbols on, it's obvious - the type names, layouts and whatnot are embedded in the binary. Bigger names = bigger executable. Of course, this doesn't apply here because on micros you usually don't even have an ELF executable, you upload raw executable code.
2. Even without debug symbols, think about how generics work in statically compiled languages. For each N<T> you need to instantiate the code for all T. The more nested types you have, the more code you instantiate. Usually, these are folded away by the linker, but with deeply nested generics, it's very easy to cause "non-local" effects, for example if you store T in a struct, access its fields or do anything other than treating it as opaque, then the code won't be identical for each T, because the offsets of each field will change depending on the `size_of`.
Of course, this assumes LTO because without LTO, crate boundaries are "hard" and you can't optimise/inline across them.
that would only be true with a perfectly expressive language with both high-level and low-level features, perfect support for any kind of metaprogramming and a godly optimiser.
ofc we don't have that, so code is compressible, and compressible a lot. You can say what you need in English much shorter than in in any programming language
No, rapid development is essential when you're making games. It's not a "solved science", sure you can code something up and slap some programmer art on it then ship it but you very well know that won't be usable. You need to iterate on the gameplay and gamefeel a lot if you want something more than slop.
One way is sure the native language + embedded scripting language combo but that's got the trap of impedance mismatch i.e. you spend all your time making engine not game then it overruns. But in any case having a way to iterate fast is a hidden productivity superpower, look at how many game studios have Live++ licences on their webpage;)
Sadly it still feels like it's one of the languages where the language doesn't trust you, it tries to force you to do things "the right way". I do love quite a few of its design like how traits are, not forcing every method into the declaration, and the standard library is much less crazy than the C++ version.
Sadly, other things a bit less so - the story for the thin battery-less stdlib + npm-style churn encourages bloat, and the semantics are obsessed with safety at a heavy cost to productivity unless you spam clone() and reference-counting - but then your program becomes slow, kind of negating the advantages, you might as well have written it in C# or something...
Yeah it doesn’t trust you, and for good reason the decades of developers making the same mistakes over and over again. If everyone was perfect you wouldn’t need Rust, but no one is perfect and that’s why Rust exists.
the technical parts are fresh as ever but the writing style is awful, man
reply