I have used vim/neovim for years and cannot go back to a non-modal editor. But TBH I got sick of its configuration. You need far too many plugins and config to get things into a sane working order to be usable on a day to day bases for any type of development. It takes ages to learn and become as productive as you were before and a lifetime to refine.
For the past year or so I have switched to helix and don’t plan on going back to vim/neovim as my main editor ever again. It is a modal editor that is a mix between Neovim and Kakoune editors. It comes with batteries included, and supports an IDE like experience out the box with treesitter syntax highlighting and LSP language integrations out the box. My whole config is like 6 lines long yet it works far better then my old neovim setup with a multitude of plugins and hundreds of lines of config. It is like what AstroNvim, LazyVim, LunarVim and NvChad etc are trying to do to vim/neovim but instead has built in support for all the things they rely on plugins for. Which means there is no need to constantly keep them up to date nor weird edge cases where one plugin does quite integrate with another smoothly. It is all built in so things are designed to work well together.
But it currently does lack any plugin support. So if something is not built in that you want you have to make due without it (well, except language support, adding new LSPs is not too hard). And plugin support is being worked on so even this will be a non-issue hopefully in a year or two.
I have used vim/neovim for years and cannot go back to a non-modal editor. But TBH I got sick of its configuration. You need far too many plugins and config to get things into a sane working order to be usable on a day to day bases for any type of development. It takes ages to learn and become as productive as you were before and a lifetime to refine.
Interesting. Though I can definitely see where you’re coming from. Uhmm…, have you used any of the Neovim distributions to make maintenance easier?
For the past year or so I have switched to helix and don’t plan on going back to vim/neovim as my main editor ever again.
Both Helix and Lapce have certainly piqued my interest as FOSS alternatives to VS Code. However, both have issues related to how well their current Vi(m) implementation is. As you’ve touched upon it; Helix’ keybindings and ‘sentence-structures’ are different to those found on Vi(m).
Furthermore, neither of the two have existed long enough to be able to profess any statement regarding their longevity. Like, there’s no guarantee that I can keep using either of the two 20 years into the future. While no program is able to 100% guarantee that, undoubtedly, the track records for both Emacs and Vi(m) testify that -if anything- they would be the most likely ones to survive 20 years down the line; like how they’ve done for the last couple of decades.
I appreciate the input, but I simply don’t want to invest in a program whose future is very unclear to me at this point in time.
Interesting. Though I can definitely see where you’re coming from. Uhmm…, have you used any of the Neovim distributions to make maintenance easier?
I have, but dont like them. They all have weird install processes and need to manage their own set of configs on top of vim in your home dir. This makes them very hard to properly package or integrate with config management tools and require a different flow to keep them up to date from the rest of your system. They combine sometimes hundreds of plugins, of which only a few are designed to work together and while a lot don’t try to step on each others toes that many I often find issues in niche use cases. And when you do find an issue, or something you want to tweak you have 100s of plugin configurations that you need to learn about to figure out just what is doing what and which options you need to tweak.
It is all just far more hassle then I want out of my editor these days. Helix just works out the box and has basically everything I want from a editor nicely integrated into it.
As you’ve touched upon it; Helix’ keybindings and ‘sentence-structures’ are different to those found on Vi(m).
They are a little different and take a bit to get used to. But IMO I find them far nicer way to work. It is very nice being able to see what your action is going to effect before you do it - unlike in vim when you just hope you have hit the right movement keys. And it also pops up a small window for leader keys (like space) which show you what you can do with it making it far more discoverable then vim/neovim without needing to pour though hundreds of pages of manuals to even get a glimpse of what it can do or needing to go back to them to remember something that you dont use very often. It is not trying to be a 100% vim compatible layer, it is trying to give you the best experience it can out the box. And I think it does that quite well (at least once you get used to the new way of working - which does not take that long).
Furthermore, neither of the two have existed long enough to be able to profess any statement regarding their longevity. Like, there’s no guarantee that I can keep using either of the two 20 years into the future.
20 years is a long time. I can see it existing for the next 5 years at least, and looks to be on the trajectory to be a long lasting product. Though no one can say for sure. But, the more people using it the more likely it is to stick around for the long term. Just about everyone that I have seen use it over vim have highly praised it and it has quite a few contributors already (700+ on github), which is very impressive compared to vim (about 300), and neovim (more then 1100).
And keep in mind that vim has been around so long thanks to a single maintainer, Bram Moolenaar, who passed away this year. Which is not a great sign for vims future for the next 20 years.
I appreciate the input, but I simply don’t want to invest in a program whose future is very unclear to me at this point in time.
The investment in helix is far less then that you need to put into vim/neovim due to all the configuration you need for them. Well worth it for how active it currently is and how many people are putting effort into it.
Wow! Excellent and thorough response. Thank you so much for taking your time 😊!
It is very nice being able to see what your action is going to effect before you do it - unlike in vim when you just hope you have hit the right movement keys.
That’s awesome! Which does beg the question why the others haven’t implemented such functionality (yet)?
And it also pops up a small window for leader keys (like space) which show you what you can do with it making it far more discoverable then vim/neovim without needing to pour though hundreds of pages of manuals to even get a glimpse of what it can do or needing to go back to them to remember something that you dont use very often.
Interesting. If I’m not mistaken, both Spacemacs and Doom Emacs offer similar functionality through the emacs-which-key package. I would think that Neovim should have some plugin that does something similar, but perhaps not.
Just about everyone that I have seen use it over vim have highly praised it and it has quite a few contributors already (700+ on github), which is very impressive compared to vim (about 300), and neovim (more then 1100).
I didn’t expect for them to be so many 😜. Hmm…, food for thought; thanks for pointing that out!
And keep in mind that vim has been around so long thanks to a single maintainer, Bram Moolenaar, who passed away this year. Which is not a great sign for vims future for the next 20 years.
I definitely understand that Vim’s future is lot less certain compared to two years ago due to the passing of Bram Moolenaar. However, and I might be wrong on this, but I feel as if Vim has reached a critical mass of following such that it’ll probably continue to exist in some healthy form regardless.
In general I think you make a excellent case for Helix. I’m actually considering if I should reconsider it (if that makes sense). Uhmm…, but two questions remain:
I shouldn’t expect remote accessing some random server will allow me to use Helix, right? Is there any other way to make this work? Or…, should I just learn both Vim and Helix’ Vim + Kakoune amalgamation?
Vim is literally ubiquitous and plugins that enable its features can be found on almost any ‘platform’. It’s unrealistic to expect Helix’ adoption to be at that rate (yet). However, would you happen to know if at least the likes of VS Code and/or Jetbrains’ IDEs support it? And if so, how good their support/implementation is?
I shouldn’t expect remote accessing some random server will allow me to use Helix, right? Is there any other way to make this work? Or…, should I just learn both Vim and Helix’ Vim + Kakoune amalgamation?
That all depends on the server in question and if you can install things onto it or not. Some points to consider though:
If the server is restrictive on what you can install then you likely are stuck with basic vim or worst only vi - and without all your configs it is a very different beast of an editor anyway and something you will need to get used to everytime you jump on the server.
If you can install stuff to your home drive then it is quite easy to get helix running - it is a single binary with some language assets (requires one env var to point to them). So is trivial to get working from your home dir without a package manager.
IMO you should not be editing things on a server often enough to worry too much about what editors it has on it. Ideally with things like ansible you should not need an editor on it at all.
Vim is literally ubiquitous and plugins that enable its features can be found on almost any ‘platform’. It’s unrealistic to expect Helix’ adoption to be at that rate (yet). However, would you happen to know if at least the likes of VS Code and/or Jetbrains’ IDEs support it? And if so, how good their support/implementation is?
Do you mean vi input mode in other editors? That is one downside - you wont find it anywhere yet. Though since learning it I have not needed to go back to other IDEs like VS Code or Jetbrains, WIth inbuilt LSP support its language integration is just as good as VS Codes as it is working off the same essential language servers. Though it does seem that at least vscode has a plugin for kakoune keybindings which are more similar to helixs.
Though what you will find is a lot of the keys are very similar between vi and helix, so apart from the big action > movement vs selection > action and a few other things they dont feel too dissimilar from each other (things like basic movement, ie w for word, e for end of word, or text objects are essentially the same).
and without all your configs it is a very different beast of an editor anyway and something you will need to get used to everytime you jump on the server.
Good point.
If you can install stuff to your home drive then it is quite easy to get helix running - it is a single binary with some language assets (requires one env var to point to them). So is trivial to get working from your home dir without a package manager.
I’m impressed. Thank you for pointing this out.
Ideally with things like ansible you should not need an editor on it at all.
Hmm…, honestly, I haven’t yet done a lot of things with Ansible yet. Perhaps it’s time to go explore that rabbit hole as well 🤣. Thank you (once more) for pointing this out!
Which does beg the question why the others haven’t implemented such functionality (yet)?
Helix continues the work previously done by Kakoune (some people prefer Kakoune over Helix anyway). As to why - because it, like any other computer science topic, is a topic of active research, and Kakoune is the next generation of research into modal editing. Disclaimer: I use Neovim because it works well enough for me (it does offer more configurability, but I doubt I use it that much) and I don’t want to learn another set of hotkeys (which is similar enough, but still different).
I shouldn’t expect remote accessing some random server will allow me to use Helix, right?
That’s right, but as a Neovim user, it’s hard for me to use Vi, because it lacks many features, and I don’t know which ones. When you start going from basic to advanced knowledge, it sadly doesn’t translate. Of course, I would still pick Vi over Nano any day.
There’s a similar problem with many shells (fish, readline (bash)) that don’t fully implement Vim’s features, so their Vi mode sucks, but I still use it.
As to why - because it, like any other computer science topic, is a topic of active research, and Kakoune is the next generation of research into modal editing.
Interesting. First time I’m hearing this, but I’m very interested to learn about it. Thank you for mentioning this!
That’s right, but as a Neovim user, it’s hard for me to use Vi, because it lacks many features, and I don’t know which ones.
Very interesting. Did you first start with Vim or Neovim?
As you’ve touched upon it; Helix’ keybindings and ‘sentence-structures’ are different to those found on Vi(m).
Unless you really want vim bindings, try them out. At least Helix is based on the Kakoune editing model which is the editor I use, and I much prefer the way Kakoune works over vim, while still being close enough so that you can pick it up quickly if you already know vim and the other way around.
I kinda do for how ubiquitous Vim keybindings are.
try them out.
Regardless, I think I will try it out after I’m at least somewhat productive with Vim.
I much prefer the way Kakoune works over vim
I think preference is generally subjective. So you’re completely in your right to prefer Kakoune over Vim (and vice versa). Though, if possible, would you mind elaborating what you prefer exactly and why?
while still being close enough so that you can pick it up quickly if you already know vim and the other way around.
I kinda do for how ubiquitous Vim keybindings are.
Yeah, that’s a great reason to stick with it. It’s unfortunate that nothing really has Kakoune bindings other than Kakoune.
I think preference is generally subjective.
Of course, I know preference is subjective. That’s why I didn’t say “it’s better” :P Could very well be that vim works better for you.
The big reason I like them more is the concept of selections. Basically instead of a cursor you have a set of selections with start and end position (which could be the same position for a normal cursor), instead of having the object to delete as a parameter. For example, to delete two words it’s ‘d2w’ in vim, while it’s ’2wd’ in Kakoune. And after you type the ‘2w’, the selection shows what you’re about to delete, because it’s a separate command. It’s more useful when you’re operating on larger blocks of text, of course, or chain multiple commands together to create the selection you want. Sure, you can use visual mode in vim but it feels like an afterthought in a lot of ways.
I’ve already mentioned it but you can also have multiple selections at the same time, which I don’t think vim really does (I could be wrong though). This makes bulk operations really easy since they work exactly the same as operations on a single selection. For example, if you want to prepend let’s say “foo” to the next 10 lines, in Kakoune it would be ‘9CIfoo<esc>’ where C creates a selection one line under the current one, and I works the same as in vim. I believe you’d have to use macros for that in vim, something like ‘qqIfoo<esc>jq9@q’.
Those two are I think the main reasons I like Kakoune.
Doesn’t that disrupt muscle memory?
I haven’t really had problems with it, at least. Maybe because I’ve used vim for a long time before Kakoune. TBH I also don’t really use vim a lot anymore except on one remote machine that isn’t mine.
It’s unfortunate that nothing really has Kakoune bindings other than Kakoune.
That’s indeed very unfortunate…
And after you type the ‘2w’, the selection shows what you’re about to delete, because it’s a separate command.
That genuinely seems like very useful functionality. Thanks for pointing that out!
Sure, you can use visual mode in vim but it feels like an afterthought in a lot of ways.
Could you perhaps give some examples so that I can better understand/grasp why you feel that’s the case?
Those two are I think the main reasons I like Kakoune.
I haven’t really had problems with it, at least. Maybe because I’ve used vim for a long time before Kakoune. TBH I also don’t really use vim a lot anymore except on one remote machine that isn’t mine.
I am very grateful to you for sharing your experiences as a long time Vim user that currently prefers Kakoune over it. It has definitely impressed me and made me a lot more curious towards it. And I genuinely feel like I should think this over properly before I rashly commit to Vi(m). Thank you for raising such awareness!
Could you perhaps give some examples so that I can better understand/grasp why you feel that’s the case?
Hmm, one I guess is that it is not “permanent” and deactivates after one command (in Kakoune, you have to explicitly do ‘;’ to collapse the selection to its end (which you can flip with the start using ‘alt+;’) or move around without extending the selection). That’s really the only thing I can think of at the moment and I feel like often it really doesn’t matter tbh, so maybe I was just talking out of my ass there a bit lmao.
Apparently you can quickly reselect it in vim with ‘gv’ though, which I never checked until now. That’s useful to know.
One thing I’m really missing from vim though is that it can list directories, has a hex editor, and can read a bunch of other file formats. I think it can even edit remote files over sftp, but maybe I’m confusing that with Emacs. Kakoune just does local text files (though you can of course do stuff like ‘%|xxd’ to pipe the file through xxd to get a hex view, edit and then ‘%|xxd -r’ and save but that feels very very sketchy).
Hmm, one I guess is that it is not “permanent” and deactivates after one command (in Kakoune, you have to explicitly do ‘;’ to collapse the selection to its end (which you can flip with the start using ‘alt+;’) or move around without extending the selection). That’s really the only thing I can think of at the moment and I feel like often it really doesn’t matter tbh, so maybe I was just talking out of my ass there a bit lmao.
Regardless; thank you for mentioning this!
Apparently you can quickly reselect it in vim with ‘gv’ though, which I never checked until now. That’s useful to know.
Hehe, thanks for sharing that; might become useful soon 😅.
One thing I’m really missing from vim though is that it can list directories, has a hex editor, and can read a bunch of other file formats. I think it can even edit remote files over sftp, but maybe I’m confusing that with Emacs. Kakoune just does local text files (though you can of course do stuff like ‘%|xxd’ to pipe the file through xxd to get a hex view, edit and then ‘%|xxd -r’ and save but that feels very very sketchy).
Until yesterday I knew almost nothing about Kakoune. But I’ve since tried to do some reading; while there’s still a lot to uncover and/or explore, I feel as if it tries to offer a more focused experience (for better or worse).
Use the nbd system (network block devices) and qemu to create a qcow2 image with your defective device as the base device. Serve this qcow2 image with qemu-nbd and attach it as a NBD device locally. Then run fsck or testdisk on the NBD device. This will let you repair the filesystem Linux sees without writing to the disk. Testdisk can scan for any filesystems left on the device if the partitions no longer match filesystems.
Also, if all else fails use photorec to slice the file types you need.
Also, ddrescue can try to read any actually failing sectors and work out what they contain, but puts a lot of stress on the device.
Beware, any method that puts more wear on the disk should not be used unless you’re willing to accept the risk that the drive could get worse.
I don’t know how to do any of that first part. All of the data on the drive is replaceable, it’s just going to be very tedious and time consuming. I’m currently trying one other method and I think after I’m done with that, that I’m just going to skip trying to recover the data. I had some other plans for what I wanted to do with this device and I think trying to recover the data isn’t worth it at this point.
With the amount of different distros you’ve tried (though mostly derivatives of Arch/Debian), I’m actually surprised to see that you haven’t used any derivative of Fedora. Is there any reason in particular?
I forgot to mention Fedora Silverblue. I’ve used it after Micro os and it was a better experience. Fedora seems to have a better out of box experience and had no issues.
I’m not surprised to hear that you preferred Fedora Silverblue over openSUSE MicroOS. Don’t get me wrong, I think that openSUSE Aeon/Kalpa (current names for openSUSE MicroOS Desktop) have a lot of potential. However, as it stands, Fedora’s Atomic Desktops are just more mature.
I’ve tried both LMDE and Debian itself, but I think I just ended up frustrated at the age of software in the repos and how much stuff relies on Ubuntu specific stuff.
Way back in the day I was an Ubuntu user, but then everyone simultaneously decided that gnome 2 was too old and that touch interfaces were the priority. So I now use Mint and Cinnamon.
Wow, I worded that poorly. I meant that a lot of software not in the repos (usually proprietary apps) provide a .deb download tailered for Ubuntu rather than base Debian.
If you know how to use git, you will know how to use docker (provided you know what you want to do). They are completely different programs, yet you can quickly grasp the other instinctively.
Now, Photoshop and Blender - they are also different programs, but if you know Photoshop, you still need to relearn Blender’s interface completely.
This is why I prefer terminal programs in general. Unless it’s more convenient to use GUi, i.e. Drag&Drop file manager, some git tools etc.
Because GUIs on linux don’t do everything that the CLI can. I use my computer for more than just browsing and editing documents, so the GUIs that do just that, don’t cut it.
Also, I’m on NixOS. There’s simply no way around the terminal - sadly.
I’m not saying it as a source of pride. It’s incredibly annoying to me that I need to edit a file in order to manage my system instead of having a GUI like KDE’s to manage all the settings. On NixOS, there’s just no way around that at the moment.
Unfortunately, I don’t know another somewhat sane declarative distro. Do you? (No, not GUIX. That’s just NixOS with a ton more brackets and less packages).
pop!_os That’s what I run for desktop I like flatpak better than snap and it has some other nice enhancement over Ubuntu. For my servers I still use Ubuntu.
Run “journalctl --lines 200” and send photos of output.
NOTE: This is all of the logging of the computer, and it’s long (that command select the last 200 entries), so you might have to scroll down using the PageDown key (or arrow down) in order make the photos of everything
The RAID1 seems to be failing according to that screenshot. That breaks the "Local File Systems" task and since quite a lot of things tend to depend on that, many things usually end up failing in an annoying cascade failure. It's also failing with a timeout instead of a strict error, which is odd.
Either way, I'd try commenting that line for /mnt/raid in /etc/fstab for now and seeing if that makes the system boot. It's possible that journalctl -u dev-md0.service or systemctl status dev-md0.service might tell you more, but it's 50/50 if it'll be anything useful.
You're most likely booted, otherwise you might need a live USB. Hopefully, the system isn't in read-only mode. What I'd recommend doing is:
cp /etc/fstab /etc/fstab.backup
To make a copy once. Then, nano /etc/fstab to run nano, a basic CLI editor. You can use the arrow keys to navigate and type freely in it. The hints like ^O shown on the bottom mean ctrl+o.
You'd use the arrow keys to go down to the line that probably says /dev/md0 /mnt/raid morecrap, put a # in front of it, press ctrl+w then enter to save. If that worked, ctrl+x to exit and try a reboot again.
Obviously can't promise this is "the" error preventing the system from booting, but it's generally a good idea to disable broken stuff like this to get the system working again, then fix it from there. Hopefully, this does the trick. Your RAID setup will not be activated on reboot after you do this but it's not going to permanently delete data or anything.
Looks like you need to look for messages about /dev/md0 and why it may be timing out. Also maybe add nofail to the raid entry in fstab so you can still boot if the root fs is not on it and it fails ( is root on NTFS possible or good?)
I don’t think the edid message is a problem, just an artifact of your monitor not talking to your video card?
Maybe NTFS is the problem, I think it needs special options to automatically remove the dirty bit and replay the journal
As another commenter mentioned, it’s rather silly to use a USB stick to transfer files from one HDD partition to another. However, there’s absolutely no need to use a Live USB session, and their description of how to access files on block devices was … wrong.
There are programs you can find for Windows to access Linux filesystems, but those tend to be flaky; NTFS support for Linux is mature enough to accomplish what you need. You should be able to install NTFS support with apt and access the Windows partition like any other drive - I’ve done this. Googling “Linux Mint NTFS” should find you what you need.
Install stuff, try and make it better but end up breaking it horribly, and then spend time fixing it. This is how I’ve learned everything over the years.
I distro hopped for a few years but eventually settled on Arch over a decade ago. It was a lot more difficult to install back then, but it will still get you comfortable with the CLI if you’re not comfortable with it already. Also, if you don’t know already, Arch pretty much has the best Wiki available and it works with almost all distros since most only differ in package management.
I actually got heavy into Linux during my freshman year of college (2004) back when Linux wasn’t supported for most things, so I wiped Windows off of my PC, and forced myself to use Ubuntu for 2 months, which required me to figure out how to install WINE and Microsoft Office. It was a pain, and after two months I put Windows back on it for dual-boot and ease of use purposes but largely used Linux once I got over the learning hump.
I’d suggest setting up a Level 1 hypervisor like VMware or Proxmox so that you can have multiple things running at once independent of each other, but a Level 2 hypervisor like KVM works just as well, but you have to make sure that you don’t break the host OS somehow hahaha
I’ve never seen an error that just says “bad platform”.
Fixing computer problems is essentially just being good at searching for stuff related to your problem. For example in your problem it would just be googling “Linux bad platform ≤name of game>” and guaranteed someone else has had the same problem and either them or someone else has figured out a fix for it. You then apply that fix, if that doesn’t work, try the next result. If it gives you a new problem, rinse and repeat.
Look up the XKCD comic about fixing a computer, that’s literally how we do it. My dad asked me a similar question to yours, I literally printed out the comic and taped it next to the computer and said “this is what I do”.
About 2 years ago (I’ve been working from home for the past 3 years, a week here or there was spent at my parents), years after I had printed out that comic, he said “I just realized that your job is essentially knowing how to look for the information you need and how to apply it when you find it”. He’s an electrician, so not really the same set of skills haha.
yeah, you’re right. The magic for me is when you dealt so much with this that you just know common errors (like reading java errors). And the bad part is when the google it part doesn’t work.
like recently I figured out that my mouse sends different packets wired and wireless. long story short wireless works bad. And I only found one source, that led to another([1], [2], [3]) but got to lazy caz I just plug my mouse in and the problem is gone, lol
Yeah, you run into common (or uncommon but repeatable) errors often that you’re either like “I know exactly how to handle this” or “I remember running into this before but just need to jog my memory real quick…”
I had a similar odd issue with my HDDs. I had 20 HDDs in my system of various ages, and they would seemingly randomly throw shit tons of R/W checksum errors and drop out of its assigned zpool. It was almost never the same drive. SMART said the drive was perfectly fine. It would happen on brand new drives I got a week ago and drives that were years old. I swapped power cables, SATA/SAS controllers (three different HBAs and 3 onboard controllers) and cables, bought a UPS, etc… and nothing seemed to work. I didn’t think it was a PSU issue since I had a 1.5 KW PSU and my Kill-A-Watt meter was only showing about 600w at full load. This took literal months of troubleshooting. Someone on Reddit finally suggested trying another PSU or limiting the amount of drives attached to the PSU. I bought a cheap 400w PSU and connected about 8 drives to that… and all the errors stopped.
It turns out that there wasn’t enough power supplied on the 5v rails to write the data without errors 100% of the time, but it had enough power supplied on the 12v rail to spin all the motors. First time in 25 years I’d ever seen that, but that was also the first time I’ve ever had like 20 drives connected to one PSU. I was literally about to throw in the towel because drives dropped out on a daily basis, but after like 2 or 3 total dropped no more usually failed.
Oh wow, I feel for you. I bet when u did solve it it felt wonderful. That’s the high I’m chasing with software at least.
also side note, as I feel like this thread is over: DANG I love this platform. I’m not even alive for 20 years and your not the first guy on here who gives me free advice from 20+ years of experience. This shit is pure gold for someone who wants to learn. And it’s not even like I’m here to use people, I stayed because how kind and helpful everyone is.
Anyone who reads this in the future, you’re the good side of the internet. I’m showing some threads to my friends from time to time and if it’s more then 3 sentences they’re like “ah, wall of text, I ain readin allat”.
Yeah it was a massive relief! I’m always willing to help and share all of the knowledge I’ve gained over the years, gotta make use of it somehow! Back when I was your age I felt the same way, I was part of a private hacking/security community and dudes would spout out stuff about Linux, Windows, and network tech that I had no idea about and I was always thinking “I aim to be like you some day” 😊
Yeah actually somewhat of a related experience I been using Linux for 3 years, 2-3 months on Ubuntu then manjaro one week and skipped next to arch till now ( hopped into nix and artix for a while too ).
The experience I have i gained through installing arch from scratch fixing things playing with Wayland and pipewire from the early days.
I am bit scared is of the edge cases, I have a software engineering background, or actually I still into it and was looking for some sources fro the most common problems and how to diagnosi edge case ones.
Yeah, I really only started to learn, when I started resisting the urge to reinstall everything if something goes wrong and instead start trying to properly fix it.
I would always crawl back to Windows, so that’s why I forced myself to just use Linux and force myself to fix everything that popped up, that was the key moment.
Hardly. I self-host a bunch of VMs on a home server. It would be a waste of resources having window managers running them just so I can click around once in a while. Also, it takes way more time to set up a container in Docker Desktop compared to just copying across a command to the terminal from a setup guide.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.