The engineers wouldn't have made world changing products without his guidance. There are many books about this, even by the employees themselves such as Creative Selection and Insanely Simple, which talk about how Jobs' product vision simplified much of the UI and UX and therefore product for regular users when engineers instead wanted to add more features and complexify the product. Steve was not just a salesman handed a product and asked to sell it.
Steve Jobs said no. No to 'stupid' ideas and no to 'cannot be done'. That leads to some products being bad (eg mac cube) and other to be interesting to build on (iphone with no app SDK).
The Mooncrash DLC specifically is one of the best pieces of gaming available. It turns the base game mechanics into a Rogue-like where the world resets but some things in the world still stay persistent.
While I like that DLC, I think it loses what makes these games so great to play: the feeling of exploration and slowly uncovering a story. Moon crashes repetition and time limits don't quite do it for me (although I still really recommend it to anyone).
GPUI is quite a strange choice because there are so many forks of it, because Zed which made it is not interested in PRs that don't serve their use case of text editors, thus lots of common sense PRs for general desktop development were rejected.
The fragmentation around GPUI really is unfortunate. It seems to be the only framework that is complete enough for serious products. E.g. you can pair it with accesskit and have accessibility, it has a good number of components including difficult to write ones like text editors with highlighting.
I'm looking forward to Blitz personally. And I don't think it's true that it's the only complete enough solution as there are many in Rust like slint, iced, egui etc.
Slint yes but it’s commercial. Iced didn’t have a real accessibility story when I looked a few months ago. Ditto for egui. Also egui is immediate mode only which limits its general applicability.
Slint is under multiple license, including the open-source GPL and a royalty free license. What specifically bothers you about the licensing? (I work on Slint, genuinely curious)
Correct. This is a class of products that I really would rather not go commercial for. It's extremely difficult to change after the fact so from a business standpoint it puts us in a place where if the vendor decides to start cranking prices or they sell their business and the new owner does, then we are in a really difficult position.
It's not actually about paying money or not, I've signed up for many a patreon or what not to support open source projects I use. I fully believe in paying people for software. But for core things like this I do prefer MIT/APACHE.
You know what they meant. This is the same argument that artists used when AI image generation came out, it's not very helpful. Being able to do something and actually doing it are different and we all benefit when web app makers rewrite their apps into native languages.
Maybe that was true in the past but it has definitely not been the case for the past 15 or 20 years for web developers who actually don't know anything about native development.
Well if you put it that way, some of them don't even know anything about the browser technology that powers their JavaScript framework used to generate static content.
reply