I like browser-based UI, as they offer similar advantages to TUIs: You can use the UI on a different machine than the application itself is running. Arguably, modern Web standards also lend themselves to some elegant code design for UI. However, the "waste" is a valid point, but then again your TUI (and many GUIs) will fail on those things that cause the "bloat" of a browser: support for the weirdest encodings, dealing with the most absurd edge cases, supporting the largest amount of devices in a uniform manner. Shipping a whole electron for your crappy app is not what I mean. This should stop, as it trades all advantages for almost only disadvantages.
Can you compare with what used to be, to the best of my knowlege, by far the fastest implementation, https://www.cs.cmu.edu/~quake/triangle.html ? It's not int specific though, but I would still be curious
The article only mentioned he asked for a different problem, not that he was quickly explaining the solution and then asked for a different one. So this were exactly my thoughts, it's a bit like getting asked to find the roots of a polynom and replying "oh I already know how to do it, can you ask me something different?"
A post-apocalyptic desert landscape. The hero descends into the ruins, now a temple. Crude drawings of times before, people riding dinosaurs and mobile phones with arms and legs swinging a whip at the oppressed. He reaches the altar, a old MacBook, bottlecaps and fidgit spinners glued as a mosaic onto it. In the corner three starved men, riding on power generating bicycles providing some artificial light and supplying the machine with divine electricity. He proceeds and types: "we are starving. How can we get food?". Everybody waits in silence. Hours pass. Days. Slowly, letters emerge on the cracked screen: "you are absolutely right —" the screen flickers and fades. Panic. The link to God severed cynically. The hero has to seek out a new device, into distant lands. Maybe this time it will save them
Worse than OpenGL though? Haven't had the time to really look into it, probably native Metal is better, yes, but either way it might be easier to port/adapt from Vulkan than from OpenGL (due to similar concepts, no global state, etc)
OpenGL is limited to 4.1 on Apple platforms if I am not mistaken, and will not get updated ever. So you will run into missing features eventually on some platforms, e.g. SSBOs are really nice but you can't them use on Apple devices.
For me, a much stronger argument against OpenGL is that is requires a global state. This often leads to bad design, is miserable to multi-thread, and is rather tedious to port to Vulkan. I have spent several years fighting with multi-threading applications doing all sort of things in OpenGL and it is not great. Yes, Vulkan is extremely painful to set-up and you have to think about a million things you might not really care about directly, but honestly, I would also recommend against starting anything serious in OpenGL. To get your hands wet maybe, as with a couple lines you can get something running..
I also do not like the Rust culture. I think the core problem is that it is so centered around identity, and this leaks into how the arguments are presented and how "outsiders" are judged. Which your example illustrates.
I like zig a lot, I share its core philosophy, and I generally agree with Andrew's views. I found this article interesting, and I think it is understandable in all of this to be a bit bitter towards Bun and Jarred - in some sense, it had turned into a big "If you don't use Rust in 2026 you are stupid" which directly hurts the Zig project.
Personally, I prefer zig over most other languages. I find "memory-safety" is bought at the price of code that is not straightforward to reason about and requiring a steep learning curve. The reader's working memory is filled up quickly with language constructs and crutches rather than with the actual logic of the code at hand. I have used C++ for a large part of my professional career and eventually got so annoyed by always having to cross-reference multiple files to check which behavior might be used by which constructor and things like that. I have written a big and critical system in pure C once, just to try, and while I would not do it again, diligence and testing resulted in virtually zero runtime failures across its lifespan - while it was always possible to quickly reason about all the logic that tied low-level hardware access and near-realtime requirements together in a way much more visible than hidden behind layers of "safe" abstraction. Zig is, for me, the sweet spot: It solves the terrible issues that plain C has, and adds a lot of convenience on top that does not obscure the logic, while encouraging but not enforcing safe patterns.
>3D in 2D in 3D. OpenGL clients can use GLX rendering over X11. Compatibility varies, as it did in the 2000s.
Made me chuckle. I think at one point in my life I actually knew which exact GL versions and features were working on which servers. Also it's pretty cool.
Why do you think a government should compete on a market segment? I find it slightly irritating.
Let me get a cup of the good EU coffee! I like the "privacy" blend the most!
Now let me turn on my EU computer and log-in with my EU id
Check my messages on EU social media and then I have to leave for work
Oh that's a cute girl that messaged me on EU dating
I hope she also likes privacy and democracy
Now into my EU car, let me quickly stop at my EU charging station
Power is cheap, no middleman, all EU for our democracy
And then I'm on my way to my EU employer!
When there are two options that describe exactly the opposite of each other, it will be one of them. Reduced a bit the fun - but then again, for some words I understood what they are dealing with, but not whether positively or negatively.
The way verification works requires sharing unique identifiers that a government can always trace back to the real identity. It is not clear whether these identifiers are retained, but I believe it is partially necessary to allow for "decentralization"
But please note that the bridge will be available without the guard rail / fence, parts of the concrete might be missing, and the rust proofing needs a refresh!
I can't use "Claude Max" subscription and the likes with my own software, can I? Using OpenCode instead of ClaudeCode violates the ToS, doesn't it? How would I go about permissions and integrating with my other services I already run on AWS? IAM roles for Bedrock are pretty nice. You appear very confident and concerned about my spending, so please help me here!
I agree, the original article is rather questionable. I do not write code like the article advocates for. I would probably go for overloads for each data type I have considered and tested, or maybe something fully templated, or std::span/boost::span (hash function is, interesting enough, the very example boost docs give to illustrate boost::span).