Everywhere I’ve worked, you have a Windows/Mac for emails, and then either use WSL, develop on console in Mac since it’s Linux, or most commonly have a dedicated Linux box or workstation.
I’m starting to see people using VSCode more these days though.
I think someone else said what it actually is in another comment. It’s functionally identical 90℅ of the time for me anyway,and I use CLI and vim on it.
They’re both UNIX-like, i.e. they both implement the POSIX specification and are therefore in many ways compatible.
But yeah, modern macOS is more directly derived from the original UNIX operating system.
Linux was instead implemented from scratch to be compatible with UNIX.
The entire IT ecosystem is built around Linux, because it’s so prevalent in servers, containers, budget hardware and the open-source community.
Yes, many companies don’t understand that and expect their devs to be productive on Windows. But in my experience, that’s an uphill battle.
In my company, we get very little IT support, if we decide to order a Linux laptop and we still have significantly less trouble with getting things set up to start coding.
Not to mention the productivity boost from having all the relevant technologies natively available + being able to script whatever you want.
But because everyone is working off a 6TB Nas shared over the LAN at the office. No one really knows who changed the code. So we decided to fire 51% of the team figuring we got em.
@nifty I have nothing against Ruby and think it’s a nice flexible language. At the peak of RoR though, all the asshats were all over Ruby.
My problem with Ruby wasn’t even RoR, it was with the way the asshats valued creativity “cleverness” which seemed to mean writing code in the most cryptic ways possible. These folks took what should be an expressive language and wrote scripts that rivaled Perl’s worst “read once and never again” scripts.
This wasn’t “creativity over code” so much as it was the tail end of y2k and all the greybeards were canned so none could teach the shiny whiz kid how to code like an adult.
Without the linus-like code review sessions, they never learned why and how to improve.
Now their kludge-bro mentality has raised a whole new generation.
And that’s why people don’t know not to flatpak or npm themselves into a solarwinds sploit.
Apparently UK universities need to teach how directories work to first year Computer Science students. They’ve grown up with polished, closed devices and many only know apps and the basics of using the internet.
Theres a sweet spot before like 2010 where computer skills are still prevalent enough to be taught en masse, but the upcoming generation seem to be learning touchscreen keyboards and app stores long before they ever use a mouse or try to download off a website. The older generation has had time to adjust but a lot still struggle with tech.
I bought a keyboard kit recently and to my horror discovered all the “documentation” to build it is on Discord. The creator’s last message was that he was working on other things after losing interest, and was not monitoring it anymore. So all the channels are full of messages asking where he is, what the status is, is he coming back, etc. I had to scroll back through dozens of pages just to find the docs.
Maybe put up a wiki on GitHub or something? Especially if you don’t want to run a forum or plan on dipping. It’s not that hard.
Just rewrite it with 80% functionality and force migrations on the users. Once the remaining 20% “edge cases” that require serious effort hop to the next job - where you where hired to “maintain” such a system and “just add a small feature here and there”. Ooops.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.