I prefer tui's for two reasons.
1. Very used to vi keybindings
2. I like low resources software. I love the ability to open the software in less than a second in a second do what I needed using vi motions. And close it less than a second.
Some people will be like you save two seconds trying to do something simple. You lose more time building the tool than you will use it in your life.
It's not about saving time. It's about eliminating the mental toll from having to context switch(i know it sounds ai, reading so much ai text has gotten to me)
That’s an excellent way to explain it. I’m already in the shell doing stuff. Whenever I can stay there without sacrificing usability, it’s a big boost.
The history here is more complex than that… originally Irish was not an EU language because Ireland just used English… then as part of one the cycles of EU treaty renegotiation, Ireland successfully pushed for it to be made a secondary EU language… and then later successfully pushed for it to be upgraded to full status… so Ireland actually has two EU languages, their original one (English) and their newer one (Irish). Because the practical reality is everyone in Ireland is fluent in English-around 60% of Irish people can’t even speak basic Irish, and fluent Irish speakers is <10% of the population
Also, English remains one of the main working languages of the EU bureaucracy, because for many EU states (especially in Eastern Europe) it is a more popular foreign language than the other two (French and German)-when Czech diplomats need to talk to Spanish diplomats, English is the language they choose.
This idea people have here that “each country gets to nominate a language” isn’t how it actually works. The treaties just contain a list of languages, and which languages are in the list is down to diplomatic negotiations not any coherent principle.
So if someone says "I do know German and the translations were all wrong", parent should feel free to say "Actually, I just meant the English grammar of the subtitles, not the accuracy of the subtitles itself" and you'd be just fine with that?
How would you go about it. Let's say I want to learn how to do x in library y. How am I gonna find x. When library y has it's own idiosyncraties. In the library the concept is named differently so searching through the documentation yields nothing. Let's say you find what you are looking for. You read the documentation. And it makes no sense like if I was learning haskell and I searched for a monad and got "a monad is a monoid in the category of endofunctors". It's a ineficient process.
Documentation is the most helpful when you already know something and want to learn the specifics. Or when you are already using something and have an issue and want to figure out why.
EDIT: Another issue I just came up. Structure is very important. It's good to know how to sum before how to multiply. It's so important having a hand crafted pathway leads to rapid success like MathAcademy does.
To be clear, that is not the way I'd recommend for someone with zero knowledge in software development. The assumption is that you understand something, just not this language/library. I don't think following a tutorial is a good way to learn anything besides doing this very specific thing in a tutorial. You won't learn things like how to consume documentation and evaluate libraries, which is IMO required to develop anything there isn't a tutorial for.
Maybe use libraries (and language) with better docs? I don't know much about Haskell beyond fixing other people outdated software, but I was able to do these fixes without watching any tutorials and reading books, just by reading docs.
If I were to build web service in rust, Google would lead me to axum, and https://docs.rs/axum/latest/axum/ pretty much gives me everything I need to know to get started.
Then I will want to add some sort of CLI to start that service, clap.rs docs are pretty clear. Then I will want some configuration management, I will search crates.io for crates providing such functionality and evaluate how they work (by reading the documentation), pick one and implement.
When I wanted to build an android tv app, I've read android docs and built it. If I were in tutorial hell, I'd google for "building android tv reddit client" and not found any.
Decided to build a small macOS tray app for myself? A few minutes reading the official docs, and I'm ready to start.
BS. Everything I learned from college was me anki and youtube. Lectures were wasting me time from actually studying. Most people I talked to they said. They didn't follow the lecturer at all just sat there like me for the attendence. There is no reason why we should continue to have mandatory lectures when you can just record them like Gilbert Strang did.
I remember pasting a lot of text in vim. And waiting for all of it to be rendered. In helix it's instant. Things could have changed since then. I am talking about no later than 2023
In Neovim at least one reason for why it might be slow is that the particular treesitter implementation for the syntax you're using isn't very optimized?
But it depends a lot on what kind of type you're pasting exactly and your setup.
I actually do this. I put urls and files in a text file. Which I parse with rofi. The reason why I do this is so I can just open rofi with a shortcut and type out the name of the file or url and instantly open it.
park chess players gamble.
Going to a chess tournament with a prize pool and paying an entry fee is gambling.
In germany magic the gathering tournaments are banned since they are deemed as gambling.
Some people will be like you save two seconds trying to do something simple. You lose more time building the tool than you will use it in your life.
It's not about saving time. It's about eliminating the mental toll from having to context switch(i know it sounds ai, reading so much ai text has gotten to me)
reply