this post was submitted on 18 Mar 2024
1131 points (96.5% liked)
linuxmemes
21428 readers
715 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Are they fanboys, though? I used to be one of those guys back when I used to help debug Windows permissions issues (it was always permissions issues) when getting .NET code to run on Windows 7. If anything, I think a lot of Windows people know that everything on Linux is far better supported and had more developer oversight, but ultimately these were the tools you had to use to use your language of choice.
If anything, it led to such a deep imposter syndrome that I ended up moving away from C#. While I could be just as productive in Windows as I was in Linux (even today), having to use "different" tools or run "special" commands to get something as basic as Ruby running on your OS constantly made you feel that you were running against the current.
Many of them are, yes.
Not all of them, but many.
Not sure how long ago you used C#, but these days the entire .NET Framework and C# compiler are open-source and cross-platform, and the latest versions of .NET have native ahead-of-time compilation ("Native AoT") which lets you compile C# apps into a single executable file that can run on a system that doesn't have the framework installed.
Visual Studio is still Windows-only, but VS Code is available everywhere and has good C# support, and JetBrains Rider is great too.
You can get PowerShell on Linux too. PowerShell is really nice once you get a feel for it. You pipe objects rather than strings, so there's a lot you can do easily without needing to use grep/cut/sed to manipulate string streams.
I stopped around 2016, so it's been a while, but it's something I still really miss. I remember .NET Core being a thing, but didn't see enough movement in places looking to transition away, so I jumped over to a different stack.
.NET Core was renamed to .NET in 2020 to signal that it's the main framework now. It had mostly reached feature parity with the old .NET Framework by then. .NET Framework is still on version 4.6.x and isn't receiving updates other than bug fixes, so a lot of people have migrated to .NET.
C# keeps evolving and there's a bunch of useful language features that have been added even just in the last few years.