edit: Someone also brings this up on the OP: https://community.frame.work/t/introducing-the-new-and-upgra...
I happened to use this last week because we needed test data for a community tree in an app we're building. There are nine communities, and we needed test cases with 0, 1, and many subcommunities. This not only provided ready test cases, but the team is learning celestial facts while working on the feature!
* Lack of AppleScript support (my main complaint, every other was lifted from other comments).
* Lack of other basic features such as pinch-to-zoom.
* Poor Keychain support.
* Slow.
* Resource-hungry.
And this article comes out just after reports of a 0-day exploit of Firefox on macOS[1].
If you want people to give Firefox a chance, make it good. For many of us it isn’t, and shouting over and over that it’s good doesn’t make it so. Fine if it works for you, but it doesn’t for many.
[1]: https://arstechnica.com/information-technology/2019/06/poten...
Are you arguing that Firefox is not even "good," or just not perfect?
(I use Firefox on a Mac all day and the only kind of "resource hunger" I've observed can be pinned to the web pages that it's running.)
https://hn.algolia.com/?query=Capstone,+a+Tablet+for+Thinkin...
[1] https://wordenenglishiv.weebly.com/uploads/2/3/6/5/23650430/...
https://books.google.com/books?id=KJQRAwAAQBAJ&pg=PA36&lpg=P...
Which leads to this link: https://groups.google.com/g/clojure/c/OnagUrQZ1NE/m/Uwm8fvak...
Where Rich comments on the thinking behind this.
Also see https://clojure.org/reference/lisps , which compares Clojure with other Lisp dialects on this and other points