I've been using xterm, urxvt, and st. Also tested alacrity, kitty, and wezterm. Your shell also plays a critical role in your terminal usage (but I won't deviate here).
For my use-case, the latter are overkill so I stayed with st. The only missing feature for me was image support even though I use it sporadically. To cover that I use a script that relies on ueberzug or ucollage if I need to browse folders.
I've wrote a small post about ucollage if you're interested.
The general idea is that a desktop environment provides you with common graphical user interface elements such as icons, toolbars, wallpaper, and desktop widgets. In other terms it's purely an aesthetic question. You can also decide which of these features will be useful to you and install the appropriate package(s) if you don't want to grab the bundle that comes with any DE.
As far of timing is concerned, you can always experiment and install what you need as you go. The only downside to wait will depend on how good your distro is in managing packages dependencies.
Personaly, my Linux journey made me realize that the features offer by a DE were actually negatively impacting my productivity and a windows manager (a tiling one for me) was all I needed. But this decision - like a lot of others - comes down to personal tastes. Note that not using a DE doesn't mean relying on the terminal only.
Any more details to share?
Yes, using coreboot would just have been nice to support open-source from all aspects.
Thanks for a nice feedback. One more vote for Framework ;)
I don't use a DE, so this would not make me go with them. Also, I'll use Arch anyway, not PopOS.
Have you looked at KISS? Extremely lightweight and customizable. You can go from the most minimalist approach with text only and selection of apps to show to crash things like visual effects and icons for every single installed app.
I can see that from a server maintenance point of view. After having read so many great things about NixOS, I may have exaggerated my expectation and I may be the problem for being a user with too limited needs to get the full benefits of NixOS.
For me this single config file doesn't save that much additional files and most of them would be files you configure only once during installation. Nonetheless I can see how "easier" it would be to save one file instead of 3 to reproduce your system and I can only imagine how much better it is from a server point of view.
I will not reiterate the great things others have said but I've used old windows to create an enclosure for my printer and it definitely helps with the prints. Also since you're a new user and have an Ender 3, I would recommend you to take a look at thingiverse.com and printables.com - if not already done - for great tweaks to protect your printer but also to find great things to print.
For your printer, you may be interested in cable guides, filament guide, spool roller, fan duct, bed lock (they will keep your bed in place so you will not have to deal with bed tramming anymore before your bed leveling sessions)...
Finally, although a little bit off topic, if you get bored to walk to your printer to watch the prints and would like to add some level of safety in case anything goes wrong I would highly recommend considering octoprint.
It's always difficult to find a good starting point but remember that you're not married to your apps so you can easily switch from one to another and maybe come back later. Over the years, I've seen most of Linux users going that route because 1) it's fun and you learn a little bit from each experience, 2) Linux users are generally curious, 3) some apps may be more suitable to your workflow at a given time but your workflow may change over time, 4) Linux offers us so many options so it's like unleashing kids in a toys store, you want to try everything :)
I've often heard Emacs users pose the argument that Emacs as an Elisp interpreter does just one thing. It's just that this single thing allows the myriad of functionality it offers. So in that sense comparing it to a terminal/console seems more apt than comparing it to a text editor. I wonder what you think of that argument.
I only used emacs for a year so I may be wrong but speaking only about how I used it and my current workflow I don't see a difference. Looking at the usage (and not the code), my very first impression of emacs was that it's acting as a terminal multiplexer which I was used to and so I liked this aspect. Anytime you need to do something that goes beyond the tasks of an IDE (calendar, email...) you switch window/panel (I've always been confused with the specific emacs terminology). That's exactly what I'm doing with Tmux where I run neovim and call other apps with a single keybinding. Then I can freely switch from one to another, close one, recall it in the state I've closed it...
Again, this is related to the philosophies of emacs and neovim (i.e. do-it-all or do one thing). While neovim is "only" an IDE, emacs goes beyond, and for me this is not a negative criticism of either app. You build a tool with the coding language you need to implement some functionalities. In that sense, to compare apple to apple, emacs has to be compared to neovim coupled to a terminal multiplexer.
Hehe, that's cool! Currently I'm really happy with Thunderbird so I don't expect to move away anytime soon, but I'll keep it in mind.
I used Thunderbird as well and did the switch mainly to allow me to achieve the workflow described above. I do most of my tasks in the terminal. Neomutt would certainly be one additional layer of complexity in your transition to an IDE, unless you chose to use emacs for your emails. Actually configuring emacs as an email client or going with neomutt is pretty similar. But at the end - and this is an example of the higher level of granularity I mentioned earlier - neomutt is more customizable.
Talking about the level of customization of the IDE functionality only, the plugins I use offer more configuration options in neovim as well.
Orgmode is also one (the?) big star player in emacs and neovim is trying to attract some users by developing a similar thing here or there but this is not something that would benefit to my workflow. This is maybe one of the reason why people choose emacs vs neovim and why I could quit emacs easily. Going back to the coding language, you can see that the use of lua opens new doors to the original vim. What I appreciate though is that you don't have to implement any features if you don't use them in neovim so I can keep my system limited to my needs. This is also seen as a bad thing by some when you start because emacs is capable of quite a lot with a fresh installation while neovim can barely open itself ;)
Overall we're all sharing personal experience so no generalization should be extrapolated from single visions and I'm aware of my own bias and preference for singl- task, lightweight, fast tool.
Dive in beyond the basic "hjkl:q" though.
This is a video I can't recommend enough: https://www.youtube.com/watch?v=d8XtNXutVto It's long (>1h) but it's very well made.
It's a long tutor go through with some bonus advanced tweak, and the explanations clearly helps remembering everything easily. If I knew it when I've started that would have saved me so much time and helped me from getting into bad habits I then had to fight against.
Looking for something else I ended up on MusicPlayerPlus which may check lots of the boxes, especially those not covered by ncmpcpp which is my favorite mpd frontend.
https://rybczak.net/ncmpcpp/ https://github.com/doctorfree/MusicPlayerPlus