As a ML/DL practitioner: it’s never my fucking fault; it’s always TensorFuck and PuTorch, fucking piece of shit softwares fail to converge my ass writes better fucking code in a backwoods truck stop toilet stall than this piece of shit; oh fuck right I need to just reduce the learning rate and yes I’m a fucking genius.
I saw the writing on the wall a few years back, it was so painfully obvious. I started switching to KiCAD early, and feel so bad for ever recommending Eagle to people who will now have to learn yet another new tool in order to find something usable.
Fusion360 is so bad, I had to explain why SolidWorks was different earlier today and they were shocked by things like "if I move the case the board I say is attached to the case moves to" and "I don't have to align it by eye, it's a computer".
And I'm definitely not starting VMWare to run Fusion360 with nonsense online components that slow it down to uselessness and integrate it into a tool that doesn't need to be on at all... it's just not possible. It was obvious once they stopped updating the version. It's pathetic nonetheless that they cannot think beyond the one-true-way of integrating a dozen mediocre tools into one extra-mediocre product.
This is a perfect rant in that it is so specific it loops back around to universality. I have no experience with any of the programs you mentioned - I'm only in the comments because I thought my husband, who uses SolidWorks sometimes in his day job, might find this thread entertaining - and yet I totally related to everything in your comment. I have felt all those same frustrations, just with different software; stuff that was perfectly fine getting "improved" to the point of uselessness for my situation.
You're a great writer! It takes skill to rant so well about niche stuff that anybody can relate.
Any recommendations on what to use beside Fusion? I hate that the files created in it are only stored in the cloud while I would like to use git for version management.
After switching to onshape, I have had the true revelation that it was actually solidworks fault the whole time for doing multibody modelling in a bad way.
This just isn't true any more. Is SolidWorks buggy? Sometimes, yeah. But with the right machine and knowing how to model things correctly, crashes are rare. Maybe once every couple of weeks - and I'm using it 6+ hours per day.
The reason SolidWorks gets a bad rap (mostly from Reddit) is because the majority of posters are students with shitty computers.
I had highend Dell workstation running NX, I thought I'd try SolidWorks. The SW installer crashed repeatedly, I called the local reseller support....they were like yeah sometimes it's just like that. lol. SW is OK but it is a mid level CAD product, and starts to breakdown when building in lots of automation. Solid Edge is a more robust mid level CAD tool.