1·
1 year agoI mean, largely to me this is fine and great as long as the reverse is also true. It’s fabulous to have two totally independent systems that are fully interoperable to such an extent.
I don’t think there’s a meaningful competition in growth or anything, that’s just a number. The main downside is reduced development focus…
But – If Lemmy is like a frontend for kbin and vice versa, isn’t that fine? The Lemmy apps will load kbin posts and kbin apps will load lemmy posts.
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.