There's also plenty of accounts from the early days of Cortez' invasion where the Spaniards had a very hard time against the indigenous warriors even when the Spaniards were not largely outnumbered.
23,650 karma · joined October 15, 2013
There's also plenty of accounts from the early days of Cortez' invasion where the Spaniards had a very hard time against the indigenous warriors even when the Spaniards were not largely outnumbered.
In the end the defeat of the Aztecs was decided just as much by politics as by violence.
Also it's not like Cortez won every battle, they were even catastrophically defeated in the "night of tears". Coming back from that defeat wouldn't have been possible without indigenous allies and their thousands of skilled and well-equipped warriors fighting on Cortez' side against the Aztecs even after Cortez was driven out of Tenochtitlan (and not to mention logistic support which was probably even more important).
The pixel shader is indeed quite complex compared to SDF:
https://github.com/floooh/sokol-samples/blob/8afa83928ce1870...
https://terathon.com/blog/decade-slug.html
The timeline basically checks out, maybe it simply took the patent office over a year to process the patent application?
via WebGPU backend: https://floooh.github.io/sokol-webgpu/slug-sapp.html
via WebGL2 backend: https://floooh.github.io/sokol-html5/slug-sapp.html
There's quite a bit of helper code plus stb_truetype.h and stb_ds.h under the hood to parse TTF files and crunch the TTF curve data into the runtime format expected by the Slug shader (this stuff should better go into an offline asset pipeline tool):
https://github.com/floooh/sokol-samples/blob/master/libs/slu...
...the actual text rendering code is also taking a couple of shortcuts, e.g. no kerning, no right-to-left, and also no text shaping.
There's also a new and complete text rendering stack by Mikko Mononen called Skribidi (AFAIK not based on Slug though):
https://github.com/memononen/Skribidi
...the list of external dependencies is a bit scary for a small self-contained sample though (Harfbuzz, SheenBidi, libunibreak, etc...), but that basically shows that proper international text rendering is really damn hard, even when trying to simplify the code as much as possible.
Ticket: https://github.com/gpuweb/gpuweb/issues/4973
Caniuse: https://caniuse.com/?search=uniform_buffer_standard_layout
The std140-style layout restrictions are basically a leftover when GPUs used vec4 "register tables" for uniform data.
It's such an obvious issue that I'm wondering whether I'm the only one experiencing it or whether Apple users just don't use Spotify or whether Spotify simply doesn't test on macOS (and as such I have no idea where even to write a ticket, the macOS Feedback app doesn't even have a category for problems in non-Apple applications).
For instance in Germany, the specific words "Bundesregierung" (Federal Government, or just short "government") and "Landesregierungen" (State Governments) explicitly describe the "executive part" of the "political system".
The Federal and State Parliaments are the "legislative part" and the courts are the "judiciary part" (with the "Federal Constitutional Court" at the top). This whole idea of strict separation of power is the most important foundation of the German political system.
When talking about "the government" in Germany, people mean the institutions of the executive (mainly the chancellor and ministries, sometimes also including the president, but never the parliaments and courts).
And tbh, I would also have a hard time describing the US Democratic Party as the "current US government" just because they're sitting in the Congress.
https://youtu.be/yjrbcLm78I8?si=GMIqDdL31hq4ik72&t=87
Although tbf apparently that's done via the AY sound chip of the 128k, which is a lot easier than through the on/off beeper of the 48k since the AY can do digitized audio via CPU-driven volume modulation.
It would be good if you did at least a minimal amount of due diligence before spreading misinformation (but I guess spreading misinformation is the whole point).
1. the AfD thing was the decision of individual banks, not of the German government. Basically, in a free world companies can decide who they want to do business with.
2. the Canadian trucker "debanking" was quickly resolved because the Canadian justice system did their job and overruled the unlawful "emergency" government order
I think that really depends on whether they use PCs at all, and what for. I wouldn't dare to generalize people's habits based on age (the American "Gen*" labels never made much sense, and is usually downright discriminatory in both directions).
E.g. one result of the downward spiral of desktop UIs is that at least a lot of devs seem to have moved back to the command line, and the most hilarious thing of all is that the most modern tools (e.g. LLM frontends like Claude Code) are 1980s style TUIs. e.g. that's how bad the modern graphical user interfaces are failing us, we have to bring back half a century old UI technologies ;)
...which tbh is a good thing, because the Windows desktop of that time was pretty much the peak of the desktop UI paradigm, with actual research going into the UX instead of 'whims and vibes' like today (I would pick Win2k though since it had a much more solid technological foundation than Win95/98).
KDE has found its own way since it was a mere Windows desktop copy though (e.g. it's much better now - even more visually consistent - than both modern Windows and macOS). But unlike GNOME, KDE never abandondend what made it great.
I was there, Gandalf ;)
(and note how I specifically wrote "dominant high level language", not "dominant language", since assembly coding was indeed very relevant on those machines, for UI apps 100% assembly was quite rare though, and hybrid C/ASM seems to have been more common).