this post was submitted on 16 Aug 2024
173 points (93.0% liked)
Open Source
30302 readers
831 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I can tell you for a fact, in 1999, we were running Windows3.11 and MSDOS 5.x on a brand-new Pentium II ? or something like that, because the DSP-board and daughter-card system didn't like Win2k. We were all on the network. Everyone ran Win2k Pro while loading the test codes via network / SMB/CIFs share to that machine.
Same could be done using Linux on all those systems except for the test rig.
NO YOU DO NOT have to use Windows on your desktop just for your toolchain. Put that shit on a separate test-rig and isolate it.
Best Practices and Good Standard procedures makes it possible to use Linux on the Desktop.
It is a matter of ability and talent to do things properly using the best tools at any given time.