Way cool project, but why are folks so allergic to putting screenshots of their work in the readme? There's a graph of how the internals work instead of a screenshot of the desktop running.
The youtube video covering it has an interesting run through of the desktop environment in the final section https://www.youtube.com/watch?v=eGS9su_inBY&t=2418s. But I agree a screenshot or two wouldn't hurt.
Tinfoil Hat Take: Avoiding screenshots on the project page drives eyeballs to YouTube, which the provides ad revenue, which then feeds back into the project.
This is one person's hobby project that presumably less than 100 people will actually install. Of course no one cares that it was made with AI and won't be maintained.
We had WiiMac a month ago: https://news.ycombinator.com/item?id=47691730
Are we seeing a resurgence of interest in porting stuff to old consoles? AI is helping with these hobbies I guess.
WinCE had a load of weird issues (and looked consistently awful), but moving onto PDAs and even phones running it from a world of Psion and Palm was like stepping forward a century. This might be rose tinted recollections - and helps that it coincided with with the consumerisation of WiFi and Bluetooth - but fond memories. I still can't believe how Microsoft had a surprisingly capable mobile OS years before Android or Apple and yet managed to fail so badly.
CE 6 doesn't get enough love. It was an amazing OS that had a tiny runtime and a tiny on device foot print (it could get under 16MB iirc).
Too bad the tooling around it was so bad. I should do a writeup of why, it is an interesting case study in how poor extendability of tooling can hurt an entire company.
Way cool project, but why are folks so allergic to putting screenshots of their work in the readme? There's a graph of how the internals work instead of a screenshot of the desktop running.
The youtube video covering it has an interesting run through of the desktop environment in the final section https://www.youtube.com/watch?v=eGS9su_inBY&t=2418s. But I agree a screenshot or two wouldn't hurt.
Tinfoil Hat Take: Avoiding screenshots on the project page drives eyeballs to YouTube, which the provides ad revenue, which then feeds back into the project.
Or it might just be a sign of the times. Many folks seem to prefer video as a way to convey and use information.
+1
I support this. Make Screenshots of your work and put it in the README.md
This is written entirely by claude right? I can tell just by the comments in the source code.
Weird how HN upvotes projects like these but seemed to hate the Bun Rust swap done with Claude.
This is one person's hobby project that presumably less than 100 people will actually install. Of course no one cares that it was made with AI and won't be maintained.
New ground-up projects get a softer reaction than 100% rewrites to tools that people are already depending on.
We had WiiMac a month ago: https://news.ycombinator.com/item?id=47691730 Are we seeing a resurgence of interest in porting stuff to old consoles? AI is helping with these hobbies I guess.
WinCE was so weird. Didn't it have pretty insane limits, like maximum 32 processes?
WinCE had a load of weird issues (and looked consistently awful), but moving onto PDAs and even phones running it from a world of Psion and Palm was like stepping forward a century. This might be rose tinted recollections - and helps that it coincided with with the consumerisation of WiFi and Bluetooth - but fond memories. I still can't believe how Microsoft had a surprisingly capable mobile OS years before Android or Apple and yet managed to fail so badly.
Windows CE late in its lifetime (CE 6.0) had that go away with per-process address spaces.
CE 6 doesn't get enough love. It was an amazing OS that had a tiny runtime and a tiny on device foot print (it could get under 16MB iirc).
Too bad the tooling around it was so bad. I should do a writeup of why, it is an interesting case study in how poor extendability of tooling can hurt an entire company.