I'm sorry, but that's just not practical.

There's also two other excellent floss electronics CAD tools - LibrePCB and Horizon, which are also worth trying. They are built by people who felt they could do a different workflow to KiCAD, and have succeeded at that. I personally still feel more comfortable with KiCAD, but it's always nice to see alternatives.

One thing I've been seeing with the FLOSS tools that just doesn't exist at all in the commercial world is cross-pollination of both code and features. KiCAD now has footprint DRC built in, which is something that originated in LibrePCB. And Horizon uses the KiCAD routing engine internally, while having a completely different everything else. Developers of all three hang out with each other and exchange ideas. This is something where the commercial closed stuff simply cannot compete.

It's not quite forced, but you can't explicitly ignore. In practice I'm one accidental click away from an unwanted update now. (Each time need to remember to go one menu level deeper before updating)

    nocatalina() {
      sudo softwareupdate --ignore "macOS Catalina"
      defaults write com.apple.systempreferences AttentionPrefBundleIDs 0
      killall Dock
    }

You can go crazy and spec everything, in fact that can help, but:

- In practise, nobody does it

- Specs come with no guarantees. They could even be wrong.

- The official implementation stubbornly insists on not checking return types, so half of your annotation may just be glorified documentation (although you can use third party libs like orchestra)

Just imagine: Add a new required field to a spec, and get a convenient list of source code locations that you need to review. That's the promise of a statically checked system. It's not a silver bullet, but not having this leads to what I like calling "refactor anxiety" (i.e.: did I handle all cases?)

I still love clojure no matter what. I think in practise you can express so much, so elegantly, and with far less code, that your project size is always sorta manageable.

So you're not forced, except when you are... I think the GP meant people is forced to use their store to play certain games. Games not developed by Epic, which were meant to be released in other stores and operating systems. You can choose not to play those games. Many people do in fact just that. But that was not the point.

Of course Tim Sweeney does not force random people at gunpoint to use their store. That's never going to be the case because there's laws forbidding him!

A great example of why macros in Lisp are powerful, and how they empower you as a user even if you never write one.

Currently, web-based development is unsuitable for video streaming or native GUIs which operate on local filesystem files. I don't think video streaming over networks is easy. If development shifts such that people stop wanting local filesystems and native GUIs, I'll be sad...

has a hacker ever hurt themselves by hacking and sued the company whose computer they were using?

Anyway I guess people can also buy their own computers if they want to play outside the sandbox.

> Anyway I guess people can also buy their own computers if they want to play outside the sandbox.

My point was, precisely, that we might get to some point where this is no longer possible. Imagine they stopped selling what we today call "PC", and instead everything is closer to smartphones or tablets. There would be no way to setup a development environment on the machine. There's no sudo access, no compiler toolchain...

Also, what matters isn't whether someone actually sued as much as if some executive somewhere thinks that someone might.