throwawayish

joined 2 years ago
 

cross-posted from: https://lemmy.ml/post/9648279

I would like to premise this with the following:

  • The best approach is probably just testing out each and every editor that interests me until I've found what works best for me.
    • However, I wonder to what degree a test as such would be representative when the likes of Emacs and (Neo)Vim are considered; both of which are known for being a life time learning process.
  • I don't literally expect Emacs or (Neo)Vim to be drop-in replacements for any IDE. Some of the most basic IDE-functions are absent by default and some (perhaps more advanced) functionality might simply not be attainable at all.
  • I am not interested in anything that remotely resembles a flame war. The community at Lemmy has so far been very kind to me; let's keep it that way ๐Ÿ˜œ.

Motivation

I've had experiences with Atom, VS Code and some of Jetbrains' IDEs like Pycharm and Rider. While I've been generally content with all of them, it leaves a bad taste in my mouth whenever I'm forced to switch IDEs because their lifetimes and/or lack of extensibility doesn't allow me to responsibly continue using them. As such, I'm interested in a long time investment that will grow as I will. Both Emacs and (Neo)Vim have passed the test of time and I honestly don't think they'll cease to exist in the upcoming decades, that's why I would love to start using either one of them.

Furthermore, Vi(m) keybindings seem to be somewhat ubiquitous and almost any IDE offers some support. As such, improving my Vi(m)-game should only net-positive my productivity (at least eventually). Also, fluency will benefit me whenever I'm remote accessing any random server as they will always have Vi(m) installed. Thankfully, this doesn't force me to use Vi(m) (or Neovim) just yet, because Emacs offers with Evil perhaps the single best Vi(m) implementation; outside of native Vi(m)*.

My setup:

  • I'm on a custom image of uBlue using their startingpoint as template. For those unaware; an oversimplification would be that it is Fedora Silverblue with some extras.
  • As such, I would like to have my developer environments local and have used Distrobox to that extent using steps similar to the ones outlined over here. But I'm not married to that specific way of utilizing local containers. So please feel free to recommend me something that's at least as good.
  • If I go for Emacs, then I will definitely rely on Evil.
  • If possible, I would like to use it for C#, Python and Rust. Furthermore, I engage in editing Bash scripts, Dockerfiles, Linux config files, texts written in Latex and/or Markdown and other files written in Nix or JSON. As both are very extensible, I don't expect any issues, but I might be wrong.

Questions:

  • First of all, does it make sense for me to only consider these two?
  • Can the split between Vim and Neovim be interpreted as the first schism and as such be a forebode for what's yet to come?
  • Google Trends suggests that Neo(Vim) is ever-popular. On the other hand; not only is Emacs relatively less popular, but its popularity seems to be slightly declining. Should this worry me regarding their long-time future? Especially considering that a thriving community is literally the lifeline for both of them.
  • For those that have used both extensively, which one do you prefer (if any) and why?
  • While I understand that the power of both of them lies primarily in how one can literally make them behave however suits their workflow best. Therefore, the use of premade configs and/or starter kits/distributions should (ideally) only be used either temporary or as a starting point. However, at this point, they provide a decent showcase of what each 'platform' has to offer. So:
[โ€“] throwawayish@lemmy.ml 0 points 2 years ago (1 children)

Aight, I actually don't know a lot about it, but I guess something that looks like an answer is better than none. So without further a due.

First of all, Nitrux is quite unique, so I won't be able to do it justice regardless. However, I'd say that it being an 'immutable' distro with OpenRC and focusing on AppImage (over Flatpak/Snap) is the primary one. It's important to note that Nitrux' model doesn't allow you to install .deb packages natively at all. So in that regard, it's one of the less flexible among its 'immutable' siblings. It does offer great support for Distrobox, so you can install your debs, rpms and from the AUR etc if you so desire within a container instead; you can even install other desktop environments with this. Waydroid works. AppArmor is configured. KDE Plasma looks fantastic on Nitrux, but they offer even more spice through their Maui Shell.

[โ€“] throwawayish@lemmy.ml 1 points 2 years ago* (last edited 2 years ago)

(Manjaro keeps breaking itself for a laugth)

Are you perhaps using the AUR more than you should on a Manjaro installation? Just for your information; because Manjaro holds back packages for a couple of weeks, any package from the AUR might conflict with those 'outdated' packages and thus cause some breakage. If you really need those packages, then you should consider container solutions like Distrobox to resolve this. Note that trying things like installing a custom kernel won't work through Distrobox.

So the main options probably consist of:

  • Just plain Arch; archinstall has made it a lot easier to install. Furthermore, after everything is set and done, it can literally be Manjaro without outdated packages and less bugs etc, or actually whatever you would like your Linux installation to be. Setting up is the most daunting part though. Fortunately, the Arch Wiki does an excellent job in providing a resource at every set of the journey. Recommended if you're not scared of setting up your system from a blank slate.

  • Any other Arch-based distro, really. There are a ton of recommendations found in the other comments and there's even more if you check out Distrowatch for Arch-based distros. If you kinda know what you'd want from a future system, but can't be bothered with setting it up directly from Arch, then this might be recommended based on the specifics of your demands and to what degree existing distros align to that. For whatever it's worth, I think Garuda Linux is an interesting option for those that want to move on from Manjaro. Similary to Manjaro, it's opinionated on how your system is/should be configured. That's why it's also one of the few Arch-based distros (like Manjaro) that offers -out of the box- the means to rollback to a working system whenever anything unfortunate befalls your system, Garuda achieves this through coming pre-configured with Btrfs+Snapper. It should be noted, though, that Garuda is considered bloated by some. However only you can decide for yourself if their offering is bloated to you or not. So check out its Xfce edition -or any that sound interesting to you- for yourself, if you're interested. If you think it's interesting, but are still too much bothered by the bloat, then perhaps their Lite versions are more to your liking.

There are a lot of options beyond Arch-based distros. However, as I don't know what made you gravitate towards Manjaro in the first place and what you've come to (dis)like since, it's hard to pinpoint what exactly you'd like. If the AUR has been your main reason for using Manjaro in the first place, then it's important to note that Distrobox also grants access to the AUR from any of the other popular distros out there. So you're not confined to just using Arch(-based distros) unless you really need some custom kernel that is somehow only available in the AUR.

  • If you checked out Manjaro for its unsuccessful attempt at providing a stable rolling release, then you should check out the most successful attempt with openSUSE Tumbleweed. It has a respectable amount of packages and enables users through OBS (OpenSUSE Build Service) to extend this significantly. Its installer offers the option to go for a minimal installation.
  • If rolling release has scarred you, but you still want up-to-date packages, then consider Fedora. Huge community, AUR-like repo in COPR and once again a very respectable amount of packages make it definitely worth a mention. It offers the so-called Fedora Everything ISO (Network Installer) that acts as the installer for minimal systems.