4 ms·
As discussed on another thread, the outcome is poorly tools glued together, due to lack of roadmap and polish that commercial software usually supports, instead
by pjmlp 1y ago
As discussed on another thread, the outcome is poorly tools glued together, due to lack of roadmap and polish that commercial software usually supports, instead of volunteers coming and going, only caring for their little ich.
- wasmainiac 1y agoI’m not sure about that. I used to use LabView and its various libraries often. The whole thing felt scattered and ossified. I’d take a python standard library any day.
- pjmlp 1y agoYet most EE engineers rather use a graphical tool like LabView or Simulink. Not everyone is keen doing scripting from command line with vi.
- sallveburrpi 1y agoMaybe it’s different for those actually working in the profession and n=1 but in my (many) years of studying EE I never used these tools even once.
- amluto 1y agoI once interned at a lab that used a piece of surely overpriced hardware that integrated with Simulink. You would make a Simulink model, and you’d click something and the computer would (IIRC) compile it to C and upload it to the hardware. On the bright side, you didn’t waste time bikeshedding about how to structure things. On the other hand, actually implementing any sort of nontrivial logic was incredibly unpleasant.
- wasmainiac 1y agoHahaha yep, so much clicking after One day my finger was actually sore.
- wasmainiac 1y agoNo not really, depending on the application Cpp or python has been the language of choice in the lab. Labview was used because it was seen as easy to make UIs for operators in production facilities, but even that was a regrettable decision. We ended up rewriting LV business logic in c# and importing it as a lib into a LV front end.
- scotty79 1y agoCommercial software polish is lipstick on a pig. A pig that will never be anything else and will eventually die as a pig. Ugly os software at least has potential to grow internally. Long lived commercial software is a totting carcass with fresh coat of paint every now and then.
- pjmlp 1y agoYet, the Year of XYZ software seldom comes, the usual cheering of tools like Blender, often forgets its origin as commercial product and existing userbase. Someone has to pay the bills for development effort, and when it based on volunteer work, it is mostly followers and not innovators.
- scotty79 1y agoThere's nothing wrong with commercial software being the origin. What's a crime is that it can stay commercial. Source code should enter public domain in a decade at most.
- aleph_minus_one 1y ago> What's a crime is that it can stay commercial. Source code should enter public domain in a decade at most. In many cases, people are free to write their own implementation. Your claim "Source code should enter public domain in a decade at most." means that every software vendor shall be obliged after some time to hand out their source code, which is something very strong to ask for. What is the true crime are the laws that in some cases make such an own implementation illegal (software patents, probitions of reverse-engineering, ...).
- scotty79 1y ago> every software vendor shall be obliged after some time to hand out their source code, Obviously. Since software is as much vital to the modern world as water, making people who deal with it disclose implementation details is a very small ask. Access to the market is not a right but a privilege. If you want to sell things we can demand things of you.
- zozbot234 1y agoTo be fair, "sundry tools poorly glued together" describes CAS and symbolic computation software in general, including Maple or Mathematica. It's surprisingly difficult to put a proper formal foundation (guaranteeing the absence of "wrong" or even outright meaningless results) even on very basic symbolic manipulations.