To say nothing of the truly excellent battery life Macs these days get.
That's the only reason to avoid Linux on a laptop these days, IMO.
2,117 karma · joined March 13, 2013
To say nothing of the truly excellent battery life Macs these days get.
That's the only reason to avoid Linux on a laptop these days, IMO.
It's also .NET if you're itching to contribute :)
We attempted a move to mono for backend web services maybe 3 years before .NET Core released, and it was a complete no-go. 10x reduction in performance on the same hardware.
This wasn't specific to our workload either. I was big into the game Terraria at the time, and I saw similarly poor performance when running it's game server under mono vs .NET 4.x
While some of the mono toolchain was integrated into .NET Core, CoreCLR was a rewrite and immediately solved this problem.
Sounds like you're just in a part of the ecosystem that doesn't touch C#. Aside from gamedev, C# is mostly a back-end web language, and almost all new builds are going to deploy to some Linux based serverless offering or something like Kubernetes. At my work, we're a mix of Python/Typescript/C# deploying to Google Kubernetes Engine and Cloud Run.
As for the language, your parallels to Java are accurate but outdated. Older versions of C# were very very similar to Java, but C# progressed when Java didn't. For better or worse (depending on your tastes), C# is more comparable to Kotlin or Swift these days than Java.
That's to say nothing of C#'s contributions to other programming languages; async/await and unsafe{} blocks were both first seen in C# before being adopted elsewhere.
I recently discovered they're local to me but seem to only do custom items now.
This one is more subjective, but I also think C# has a more mature and painless web stack.
I love both languages but for me they each fill a different role.
As a Linux user and fan of good GUI apps, it always bums me out I'm stuck with the CLI-only options for apps like Tailscale. Even for a simple tray icon I have to resort to buggy GNOME extensions.
I understand the fragmented ecosystem and small user-base on the desktop Linux side make it hard to justify, but I hope that changes one day!
I know multiple people that have had to upgrade the main electrical panel in their home to support an EV charger, because their older building did not have enough capacity.
They have three full EV's, in rough order of size: CH-R, BZ (previously called BZ4x), and BZ Woodland (basically a long station wagon version of the former).
Subaru is also selling a tweaked and rebadged version of each. I believe these are all made in Subaru factories with Toyota power-train components.
They're also priced pretty competitively.
I go back and forth between Fedora and Ubuntu a lot, and once you get past the snap/flatpak and the apt/dnf differences everything feels the same.
I usually format my Fedora disk ext4, add flatpak to my Ubuntu installs, manually override the fonts, add dash-to-panel.. the resulting experience ends up identical.
MS even had a prototype version of Windows where the entire OS from the kernel up was managed code (a little excessive, IMO).
Dotnet GUI apps failed on Windows mostly because their UI toolkits are a mess and Electron won the cross platform war. I avoid this stack like the plague, but I write a lot of web backends in C#/ASP.NET (on Linux deploying to k8s) and it's great!
I'm running a Framework 13 and other than the physical click requiring more effort than the haptic "click" on a Mac, it's pretty dang similar.
My understanding is that they had a mostly in-house architecture (that predated Kubernetes' rise) and by moving to this new platform, they are now much more closely aligned with standard Kubernetes. They can now utilize EKS for their control plane, and leverage the many community provided features previously unavailable to them.
It's called a layer because each layer on top depends on the layers below.
If you change the package defined in the bottom most layer, all 49 above it are invalid and need re-pulled or re-built.