By this I mean, a beginner to NetBSD is already a far more competent user than a beginner in many other contexts of OS users.
12,518 karma · joined May 13, 2015
Author of murex (https://github.com/lmorg/murex, alt DevOps $SHELL). Contributor to open source. Also works on a few proprietary projects too.
By this I mean, a beginner to NetBSD is already a far more competent user than a beginner in many other contexts of OS users.
Depends on specific instance of malnutrition. If it’s lack of calories, then yes you’d be right. But that’s not what most people in the west suffer from.
> I think addition of some E coli or whatnot from screen prints makes a McD meal much worse but sure YMMV.
To be honest it was a flippant remark. I was expecting to get downvoted for elitism. Wasn’t expecting a genuine discussion about hygiene and nutrition.
But fair play, you’ve made some interesting points.
But the point I was making clearly wasn’t about restaurants being healthy. It was about fast food joints being especially unhealthy.
So far I can only think of 1: term vulnerabilities due to ANSI escape sequence parser bugs. And that’s exactly the reason I’m suggesting OSC8 should be off by default.
It doesn’t prove that they don’t want a better solution should it have the right UX. And, as I said in my original comment, the current UX for version control in documents both sucks and is often hidden away where people might not even be aware it exists.
Yet there is a demand for version control for nontechnical people. And I know this because I’ve seen enough files called “copy of important thing” or “important thing 2”.
I wouldn’t mind OSC8 so much if it had proper security auditing but it doesn’t. The whole thing was pushed by one guy on a GitHub gist who blocked anyone who dared discuss security issues.
At least with browsers, you have masses of people testing these things. But there’s no rigour to any of the tests that happen with terminal emulation. Let alone independent security audits.
And at this rate, it’ll only be a matter of time until we see “don’t cat untrusted READMEs” advice because they might contain boobytrapped escape codes. Which is an absurdly bad place to end up.
Someone? Almost certainly
If people want it enabled, they can enable it. It shouldn’t be the default.
That is, in my opinion, the correct default.
Maybe this is me being naive?
I mean, everyone has their own workflow preferences so I wouldn’t criticise you for wanting to use AI in your own personal set up. But it feels like your two statements there should be moral opposites of each other.
Beyond that, the distinction is purely arbitrary. Same tech stacks, same delivery methods, and the same client-side display tools.
So I don’t think there’s much merit arguing about what doesn’t exist any longer.
1. It’s not cross platform.
2. Non-native but mature cross platform toolkits (eg Qt) have spotty support in many of the more recent and popular languages like Rust and Go.
3. The proliferation of the web has lead to application design becoming part of the branding. Which often works against using the sterile native widgets
4. Even before that happened, many companies still reimplemented their own spin on native widgets. Including the OS vendors themselves (Apple and Microsoft are notoriously bad at filling their own style guidelines).
5. A surprising amount of times, native widgets simple don’t exist for precise problem you need solving. For IDE example, you’d have to build your own text area anyway. Likewise for terminal emulation.
6. Web developers are cheaper
I honestly do think VB6 was peak GUI development for desktop systems. But times have moved on.
The vast majority of the stuff that was downvoted was factually incorrect content.
it’s been pretty similar for the last ~decade though.
That’s why I’ve been running my own $SHELL for ~10 years. Even had my own Linux WM in development for a brief period.
But you’re right that it’s never been easier.
As you can tell, I chose the latter.
Browsers are surprisingly efficient renderers. So I can use a lean AOT language for most of the heavy lifting and then just use the webview for the final painting to screen.
The final runtime isn’t actually any more CPU nor memory hungry than when I was having to store images and font atlases in GPU memory and writing to the frame buffer directly via SDL. And as a benefit of the switch, I get a richer library of widgets to draw, far fewer rendering glitches due to edge cases in fonts, graphics drivers, and a plethora of other hard-to-debug problems.
The original plan was to support both WebKit and SDL frontends (like how libghostty works) but the webview was such an accelerant on productivity and with so few drawbacks that i quickly dropped SDL support and went all in with webviews.
It was a nice API to target and I got some really good performance vs memory and CPU usage out of it. But I also don’t regret moving off it.
Interestingly, they’re using graphics libraries like OpenGL/Vulkan in Go. Like I originally was. But after a year of edge cases, I gave up and switched to Wails (using OS-native webviews). And I found that a good balance between avoiding the slowness and bloat of Electron, while not having to reimplement font atlases, Unicode rendering, and a million other things people take for granted these days.
> You can download it for macOS and Linux
Also 2 of those 3 companies were famously NOT broken up.
The loss of your purchase is insignificant compared to the money Apple and Google make from their walled gardens.
Plus what other viable options are there in this duopoly?
Apparently there’s a popular 3rd option in Asia but is there any support for western apps? And how are you going to convince a million other people to switch?