▲WinCE64 – Windows CE 2.11 for N64(github.com)
69 points by xyru 1 hour ago | 5 comments
▲realjame 1 hour ago
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.
▲acmiyaguchi 53 minutes ago
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.
▲drum55 0 minutes ago
That video is very annoying and doesn't in any way replace just having a screenshot of it running.
▲xattt 44 minutes ago
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.
▲ssl-3 26 minutes ago
Or it might just be a sign of the times. Many folks seem to prefer video as a way to convey and use information.
▲alpenbazi 1 hour ago
+1

I support this. Make Screenshots of your work and put it in the README.md

▲ 1 hour ago
▲darksim905 9 minutes ago
The video that skipped to the actual content was neat, but the author saying "they don't know what they're doing" is very evident by the time you get to the end of the video watching them fumble to find architecture-specific MIPS binaries. Good grief.
▲ieie3366 56 minutes ago
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.

▲zamadatix 0 minutes ago
Leisure vs business.
▲smith7018 29 minutes ago
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.
▲rspeele 42 minutes ago
New ground-up projects get a softer reaction than 100% rewrites to tools that people are already depending on.
▲oliver66677 44 minutes ago
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.
▲queenkjuul 11 minutes ago
We definitely are. Somebody is trying to build a PS2 exporter for Unity. Someone else ported Portal to the N64 before Nintendo slapped em with a C&D. There's been a lot of work on Dreamcast development, too
▲vardump 59 minutes ago
WinCE was so weird. Didn't it have pretty insane limits, like maximum 32 processes?
▲BuildTheRobots 36 minutes ago
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.
▲xp84 0 minutes ago
I certainly thought the c. 2001 PDAs under the PocketPC brand were absolutely sick. My hot take is that if the US telecom industry had by that year built out a network of good 3G coverage, those PocketPC devices would have of course had cellular capability, and would have sold like hotcakes, and would have become the basis, the ‘trope originator’ if you will, for Mobile computing. What iPhone was in our timeline.

I think what really held them back was that Wi-Fi was only starting to roll out, and outside a hotspot area, the universe of things you might do with one was necessarily quite self-contained. It limited what “killer apps” could be developed, as anything designed for the platform probably needs to be fully offline most of the time.

▲my123 32 minutes ago
Windows CE late in its lifetime (CE 6.0) had that go away with per-process address spaces.
▲com2kid 14 minutes ago
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.