Linux doesn't always work. We know that. But it looks like you're misconstruing your specific issue with some broader argument for Linux being mainstream. The fact that you connected it to a switch tells me that youre already more advanced than the average user. I get you're annoyed, but you can also just ask about your specific issue.
The article made a few good points, but a good amount of it was conjecture. I liked the part about comparing the two functions and showing that exceptions are faster but I think a big thing he's not getting is readability. Even in the functions he showed, you can directly see that the one using std::expected has the happy path and error path directly in the function signature, whereas the exception one doesn't.
As for the "error kind" trap he was talking about, that definitely exists, but ignores the fact that you can also get this same kind of error from exceptions. I've definitely gotten exceptions that I didn't understand from Python or Java libraries, but it's not a problem with exceptions but a problem with how they're shown. If there's nothing to tell me that I should have thought of that error, it shouldn't be an expectation for a dev to have thought of it.
I use vim bindings in vscode, but I'm trying to switch to neovim.
It's hard to talk about efficiencies without use cases but here's some that I like:
Compared to using mouse, text selection is just much easier in vim. Instead of accidentally highlighting an extra space and clicking somewhere on accident which gets rid of my selection, vim lets me go directly to the end of the word and be precise about where I'm selecting.
I remember before I used vim, I would count the number of times I hit the backspace or delete when I had heavily nested parentheses. With vim I just type the exact number I want, and if I were to undo that operation I also know exactly what was changed, whereas when counting there's always the possibility of miscounting or pressing delete without counting.
I don't have to scroll. I can jump 100 lines in less than a second. Instead of searching through long files to find where I left off, I just generally remember what line number I was at, then I can simply just jump back.
Forces me to type better. Before vim I had really shitty typing form(I don't know what it's actually called) but switching to vim shone a light on exactly how I was typing wrong, and now I type faster.
Using the % operator you can jump between brackets or parentheses. This comes in handy especially when you want to highlight the inside of a function call, or just jump to the end of a pair of brackets
Before scraping I would verify that there is no HTTP API that you can use to craft requests instead of scraping from the website. These might be higher quality than what you can scrape. If there is no easy to use http API, go to scraping then. I would generally consider scraping the last option, unless it's a ridiculously easy website to scrape.
I'm not exactly sure what to think about it, but I do like how there's specific things that have their implementation in code right there. I did only look at the site for like a minute, so take that with a grain of salt.
This looks like a really cool library, but I don't have any experience in color. Are there any resources you'd recommend to learn before/while using this library?
Why do the tech heads show why it won't be adopted mainstream any time soon?