Honestly, Manjaro community differs from place to place as well.
Russian Manjaro community didn’t go much far from Arch one. English, though, is very decent.
Honestly, Manjaro community differs from place to place as well.
Russian Manjaro community didn’t go much far from Arch one. English, though, is very decent.
The contrast is very strong with the Arch Wiki, which does a genuinely good job - for a set of short articles - at explaining how that whole machinery works. Yet, if you don’t understand something from there - good luck finding a person to explain what to do.
Written in a typical rude condescending hacker speak.
Let’s call it for what it is - it’s more of a frustration vent than a guide. And this approach will certainly not make these people read through.
There are always way more polite ways to put it, like:
“Most of the questions you face about software are replied to by unpaid volunteers taking spare time to help you - thereby, the more effort you’ll put into properly filing the issue, the quicker you’ll get a response. Here are main points that we may need in order to help with your problem, and a way to obtain all information required”
The most reasonable approach, I guess.
The terminal commands have same idea and structure and apply to the entirety of your system. While it is still sometimes annoying to learn CLI commands of third-party apps (yes, I know of man, but it can be useless without examples at times), commands are generally the same for Linux systems and they cover everything.
Learning vim is like learning Linux terminal again, but for just one task of word processing in one specific application. Why?
With that being said, I’d rather solve most of my problems with GUI applications rather than go into a terminal. I can do stuff through terminal - I know basics of Linux/Unix commands - but just why? For most routine tasks, it is simply faster and easier to go with GUI, unless you are over SSH or just have a terminal-only instance, or unless you’re a sysadmin that does it 20 times each day and have muscle memory running in front of thinking what you wanna do.
I know how to update packages through terminal - the thing you demonstrate. But I can also press two buttons in app store and it will all be done for me, so why bother? (Also, you call it three steps, but it’s kinda two steps on Debian or other apt-based distros followed by one step in Arch and other pacman-enabled ones? I’m confused)
I’m certainly not gonna use terminal for word processing unless I absolutely have to. And for that, I’ll pick nano.
Linux has to get more user-friendly - and it does. Most people are not die-hard terminal fanatics and want to get their stuff done with minimal headache - and that’s where it goes and should go. Being vim elitist doubles down on that terminal philosophy that is alien to an average user. And we should not discourage any type of user to try Linux for as long as they are willing to figure truly necessary stuff out.
Fair enough.
I guess someone can make use of this all, just not regular users. Besides, the controls are very legacy and it would make sense to make an updated version just to keep it more in line with tools people are used to and generally enhance user experience.
You just kindly described why no one ever should use Vim :D
Using xyzbdvefsisgshs to copy-paste a line is not the level of convenience someone expects from a modern tool
There is a demand, and there is a supply. Decentralization trends lead more and more people to self-host, and you can’t get around it any other way.
But also self-hosted (the central server, i.e. “lighthouse”) and open-source
Sadly, not really - didn’t go deep into various options.
But maybe someone else can help?
RISC-V should be fine, if price, performance, software support, and form-factors are all okay for you.
For most, it isn’t, but if you wanna go such great lenghts, I’d say you have a chance.
You might be right on that - you know, everyone faced the challenge to find the right Debian installer :D
Wow, good luck with your project!
Well, it’s obviously dictated by hardware and the software that manufacturers release for it. I’m not calling enthusiasts to reverse engineer every single driver, that’s impossible.
The point is, there is a lot of proprietary blobs in everyone’s systems, and it’s not cool. If you ask me, we should obviously shift policies to force manufacturers to open source drivers and management systems.
Answered to another comment. In short: it’s very hard to make your PC run fully libre software, and no consumer-grade solution can do that.
Debian uses its own version of the Linux kernel with proprietary parts removed; however, if you want to install it on a machine that does have hardware for which there are no free drivers (which is to say almost any machine out there in the market), you’ll have to install proprietary parts; in the last version, Debian 12, system does that by default.
Intel Management Engine is a CPU-level microprogram that runs with highest priority and does not have open code, so essentially every PC with Intel CPU runs some arbitrary code we cannot verify. Same for AMD Platform Security Processor by the way, so there is no simple escape.
Oh and BIOS is proprietary too, and only a few select machines can have a fully libre BIOS successfully installed on them.
Thereby even if you go to essentially libre version of Linux, there will, almost universally, be pieces of obfuscated code with no disclosure on what they’re doing there.
Cool promising future that failed to currently deliver for most
Some could not be happier, though.