My recommendation? No. Don’t.
I’m an ex Windows user, current Linux and Mac user. Keyboard shortcuts on Linux are much closer to Windows conventions compared to macOS. I wouldn’t recommend using a Mac keyboard with Linux. I’d only recommend it if you want to use both Linux and macOS with the same keyboard (you will be happier in this case, because using macOS with a Windows keyboard sucks, vice versa).
If you don’t like the Windows key design, get a keyboard with a custom one.
Too often, you won’t be given time to make your software understandable. Probably almost never. So you have to incorporate a way of programming that leaves your code more understandable after you fixed your bug or added your feature.
I don’t know if understandability is the most important thing. However I certainly agree with the author that it’s curcial, if you ever want to do more than merley a script or a proof of concept.
“We’re going to clean up that code later.”
That’s a long list of changes, wow.
Personally, I’m not considering Vanilla OS just yet. It does too many things in a custom way. I am however keeping an eye on the project, since they have interesting ideas and they’re making progress in the area of immutable distributions (which will be the future I figure).
I second the recommendation to use NTFS. I don’t have the same use cases as OP, but in my experience it works really well. Back in the days when I was using Windows, I had a system and a data partition (i.e. personal files, pictures, videos… you get it). When I switched to Linux, I kept my data partition and just mounted it on my Linux system. I started with dual boot and didn’t have any issues. No need to manually install a NTFS driver these days.
That’s a couple of years ago and my secondary SSD’s still that same old NTFS partition. Thought about moving to a Linux native filesystem, since I don’t use Windows anymore, but never had an actual reason to do it.
Oh, yeah you should. I mean I’d advice against it, but since you already know the pain of switching layouts… sure, go ahead! :D
I prefer Bone over Neo, Neo has quite broad software support though. I’m using Bone on Linux and macOS without any issues.
I use a variant of the Neo-Layout called Bone. It’s an ergonomic layout optimized for German and English text. The base layer is already different (see the linked page), but I also really like it for programming, since there’s an entire layer with easily accessible symbols:
Should I approach the team about this?
Yes, certainly. It sounds like some/most members of the team don’t understand the stylesheet architecture of your project and it’s vital to sort that out ASAP. The more time passes, the harder it will get to get everything back on track.
Try to avoid finger-pointing and this shouldn’t be a very hard conversation (assuming they aren’t super stubborn).
As a side note, the fact that you first address this issue on the Fediverse and not in your team makes me think that maybe there are some underlying issues regarding trust and open communication. You might want to further look into that. Take it with a large grain of salt though. I don’t really know anything about your team so it’s likely that I overdramatize the situation.
Personally, I’m not interested in the type of posts you mention. However, I don’t mind it. In general I think it’s great to tell the world if you ditch Windows for Linux, because it shows other (Windows) users that they can do it, too.
Though I have to agree that for a dedicated Linux community, it doesn’t add too much value. If I think a post is a bad fit for the community, I vote it down.
(dead thread I know, but whatever)
It’s very similar, more like an evolution from Neo than a revolution. They switched a few keys and if you’re starting fresh I think I’d recommend Bone, but if you already know Neo I’m not sure switching is worth it. It could be fun though (if you consider learning a new layout fun ^^).