this post was submitted on 10 Jan 2024
767 points (95.9% liked)
linuxmemes
25762 readers
685 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. ๐ฌ๐ง Language/ัะทัะบ/Sprache
- This is primarily an English-speaking community. ๐ฌ๐ง๐ฆ๐บ๐บ๐ธ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
- Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed.
ย
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
While I'm not exactly an expert user of AutoCAD (my background is architecture, industrial design and full stack development), I know enough about the software where I can tell it's based on a lot of legacy spaghetti code.
It's the same for Solidworks, which I know through and through, including the shitty VBA scripting environment. My CAD teachers always used to say the software is built like a wooden playhouse, which has been extended over the years to include a second story, a slide, a swingset and a roof extension. But underneath it all, it is still the same "don't fix it if it aint broke" codebase that Dassault has taken their chances on since the '90s.
The second someone invests any kind of money into an open source alternative, the way Blender has done for the mesh modeling industries, both Autodesk and Dassault systemes stand to lose their respective monopolies on 2D and 3D CAD.
But the trend is not limited to CAD software only, it is also highly prevalent in software providers for governmental tasks. Most of which sell the same products for years without iteration on their codebase. The result is that government organisations have to deal with shitty software that requires their individual users to connect to the database (yes, you heard that right, every user has to manually input database credentials that include all grants on all of the relevant datasets). Most of these cronies are reselling badly thought out software, where they've outsourced the development to third-world shitholes. Is is a goddamn miracle that there aren't more major incidents with government organisations.
The only solution for this kind of bullshit is open standards that encourage an open source approach to these kinds of critical applications. Where more parties are actually encouraged to build their own software and where the businessmodel is built around being a service provider and not a magical black box salesman.
If you're able to stop worrying about generating revenue based on your intellectual property and focus on generating revenue from the service you provide, surrounding your product... you'll automatically build a better product.
I completely agree, but there is a problem with that approach. It means you have to work hard... which is not what most of these software companies are ready to do.