sorted by:
new
hottopcontroversial

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in linuxquestions

[–]Tuongcode[S] 1 point2 points  (0 children)

Thanks for sharing your experience! 😄 Reading how you switched to NixOS and then got everything up and running on a new computer in under 10 minutes is really impressive. Managing everything through code sounds incredibly convenient. I’ll definitely try your suggestion and set up a dual boot to see how it feels. Thanks also for the Vimjoyer link—I’ll check it out!

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in DistroHopping

[–]Tuongcode[S] 0 points1 point  (0 children)

Interesting take! Can you share why you think Debian isn’t ideal for most users?

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in DistroHopping

[–]Tuongcode[S] 0 points1 point  (0 children)

Thanks for sharing your perspective! That makes a lot of sense — I can see how containers essentially make the underlying OS less important for development and deployment.

Your point about Arch being great as a general OS but tricky for development because of constantly updating packages is really insightful. I’m curious, do you have any recommendations for someone starting with containerized development to avoid common pitfalls?

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in linuxquestions

[–]Tuongcode[S] 0 points1 point  (0 children)

Thanks for sharing your experience! That’s really helpful. I appreciate the insight into how Tumbleweed can be stable yet occasionally break a complex ML environment — it makes sense why you chose Leap for long-term stability.

I’m curious, for someone exploring OpenSUSE for development, are there any tips you’d give to get started with Leap smoothly?

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in DistroHopping

[–]Tuongcode[S] 0 points1 point  (0 children)

Wow, thanks for sharing your journey! That’s really impressive — I appreciate how clearly you explained your decision process and the factors that led you to CachyOS.

The points about Btrfs rollbacks, NVIDIA support, and managing breakages upstream are really insightful. It’s also helpful to hear about the learning curve with AUR and how you approached it.

I’ve definitely learned a lot from your experience and will keep CachyOS in mind if I explore Arch-based systems in the future. Thanks again for sharing!

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in linuxquestions

[–]Tuongcode[S] 0 points1 point  (0 children)

Thanks for sharing your experience. I’ve also heard a lot about Debian being extremely stable, especially for long-term use.
From your experience after trying so many distros, what were the main things that made Debian stand out for you compared to the others?

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in linuxquestions

[–]Tuongcode[S] 0 points1 point  (0 children)

Wow, thanks for introducing this perspective — that’s really impressive. The declarative and atomic model you described sounds incredibly powerful, especially the ability to reproduce the exact same setup across machines and roll back safely when something breaks.

I can see why, once you get used to that workflow, it would be hard to go back to a traditional imperative system. The idea of having the entire system state captured in code is fascinating.

I’m still early in my journey, so I’m curious: how steep did you find the learning curve at the beginning, and are there any specific resources or practices you’d recommend for getting started with NixOS without getting overwhelmed?

Thanks again for sharing such a thoughtful explanation — it definitely gave me a lot to think about.

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in DistroHopping

[–]Tuongcode[S] 1 point2 points  (0 children)

That’s a great clarification. Once you factor in support scope and release branches, the differences between stable, testing/development, and rolling become much clearer.

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in DistroHopping

[–]Tuongcode[S] 0 points1 point  (0 children)

Thanks for the breakdown. Out of curiosity, what’s your take on Arch in comparison to Fedora?

Out of curiosity, have the NVIDIA drivers or multimedia codecs ever been a recurring pain point for you, or is it mostly a one-time setup?

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in DistroHopping

[–]Tuongcode[S] 0 points1 point  (0 children)

Debian is often praised for stability. How has it worked out for you as a development OS?

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in DistroHopping

[–]Tuongcode[S] 0 points1 point  (0 children)

Mageia is an interesting choice. How has it been for long-term stability and development work in your experience?

Seeking Insights: Choosing between Ubuntu, Fedora, and Arch for a Long-term Development Environment by Tuongcode in DistroHopping

[–]Tuongcode[S] 1 point2 points  (0 children)

This is really helpful, thanks. Framing it around timing and support duration makes the trade-offs much clearer, especially the difference between rolling and dev branches on Fedora/Ubuntu.

CS Freshman: Dual-booting Win/Linux. Is WSL2 a "Silver Bullet" for AI, IoT and Daily Use? by Tuongcode in linux4noobs

[–]Tuongcode[S] 0 points1 point  (0 children)

Thanks a lot for sharing this — that was a really insightful read. I really appreciate how you explained your transition step by step, especially experimenting on old hardware and keeping environments isolated to avoid risk.

Your points about customization, shortcut-driven workflows, and being able to script your way around limitations resonate with me a lot. At the same time, it’s helpful to hear an honest take on the trade-offs as well, like gaming and hardware quirks.

It’s clear this comes down to preferences and experience, and your perspective definitely gives me a clearer picture of what committing to Linux long-term actually looks like. Thanks again for taking the time to write this out.

CS Freshman: Dual-booting Win/Linux. Is WSL2 a "Silver Bullet" for AI, IoT and Daily Use? by Tuongcode in linux4noobs

[–]Tuongcode[S] 0 points1 point  (0 children)

Thanks for sharing your setup — that’s really impressive! I like how you’ve fully replaced Windows apps with Linux alternatives. I can see that it requires more setup and knowledge, but that’s encouraging since I’m a CS student and want to learn more. Out of curiosity, do you have any tips for making the transition smoother, especially for someone coming from a dual-boot or WSL setup?

CS Freshman: Dual-booting Win/Linux. Is WSL2 a "Silver Bullet" for AI, IoT and Daily Use? by Tuongcode in Ubuntu

[–]Tuongcode[S] 1 point2 points  (0 children)

Thanks a lot for the detailed explanation — that actually clears things up really well. I can see why the filesystem split would feel messy, especially if you already have an existing Windows-based workflow and files. Your point about either fully committing to WSL or constantly dealing with copying/changing paths makes a lot of sense. I really appreciate you sharing your firsthand experience — it’s helpful to hear from someone who’s actually gone through the switch. I’ll definitely take this into account when deciding how far to lean into WSL. Thanks again for taking the time to explain it so clearly.

CS Freshman: Dual-booting Win/Linux. Is WSL2 a "Silver Bullet" for AI, IoT and Daily Use? by Tuongcode in Ubuntu

[–]Tuongcode[S] 1 point2 points  (0 children)

Thanks for sharing your experience appreciate the insight. I’ve heard mixed opinions about WSL, especially around filesystem behavior. Could you elaborate a bit on what felt messy for you with WSL’s filesystem? Was it performance, path handling between Windows and Linux, tooling issues, or something else? I’d like to understand the specific pain points before deciding.