Liam Proven
liam-on-linux.dreamwidth.org · Personal blog · on HN since 2022
Liam Proven writes about operating systems, lean software, Linux and BSD history, desktop environments and old computers.
What HN saysHN links it for retro computing and OS history, and a commenter cites his lean software views against bloated, over-designed systems.
17HN people shared it
2linked it in comments
35stories submitted
1.2Kstory points
3 months agolast shared
2022people per year2026
Most-shared posts
- 1A Plea for Lean Software (1995)5 people · 157 points · first shared 2022 · 133 comments on HN
- 2What's the point of lightweight code with modern computers?3 people · 11 points · first shared 2025 · 1 comments on HN
- 3Everyone seems to forget why GNOME and GNOME 3 and Unity happened2 people · 562 points · first shared 2022 · 397 comments on HN
- 4The pivotal importance of IBM's PS/2 range on computers, even today2 people · 63 points · first shared 2022 · 84 comments on HN
- 5Plan 9 Is a Bicycle2 people · 12 points · first shared 2024 · 2 comments on HN
- 6A Fresh Look at FreeBSD2 people · 6 points · first shared 2022 · discussion on HN
- 7How the Linux-vs-BSD culture clash looked in the 1980s/1990s2 people · 3 points · first shared 2025 · discussion on HN
- 8On the strange joys of mainframe OSes that have survived into modern times1 people · 111 points · first shared 2022 · 122 comments on HN
- 9I think the GNOME designers are incompetent1 people · 94 points · first shared 2022 · 147 comments on HN
- 10How to tell a mainframe from a minicomputer from a micro1 people · 62 points · first shared 2022 · 27 comments on HN
- 11The reason that the first version of Windows NT was called 3.11 people · 43 points · first shared 2022 · 14 comments on HN
- 12DOS live USB image with tools for writers1 people · 30 points · first shared 2025 · 9 comments on HN
- 13MS-DOS was *not* an illegal clone of CP/M1 people · 19 points · first shared 2022 · 9 comments on HN
- 14Reviewing a Dell Linux PC 23 years ago (by me in PCW magazine, Sep 2000)1 people · 8 points · first shared 2023 · discussion on HN
- 15Why MS Word jumped from version 2 to version 61 people · 3 points · first shared 2022 · discussion on HN
What HN people wrote when they linked it
lproven · 2026-05-13
> One interesting turn on the ST side was the creation of from-scratch GEM implementations.
Oh yes indeed. I was on the edge of the FreeGEM project: I did some bug-fixing, documentation, translation, and stuff like that. I ended up learning a lot about the history of ST GEM, and one aspect was how its cleanly-layered design let people just re-implement bits and plug them back into the original.
Which is what led to FreeMINT and TOS 4, and the desire for a FOSS distro of that is what led to AFROS.
> You can even run MagiC on Linux now
Oh! I knew he'd open-sourced it. I did mention MagiC in passing in my follow-up to Nemanja's history:
https://liam-on-linux.dreamwidth.org/96552.html
I didn't realise there had been recent activity. I must try it. Thank you!
camgunz · 2024-02-19
I'm a Vim user and I've made this point when I rail against IDEs; it's even on the front page today [0]: "5. The belief that complex systems require armies of designers and programmers is wrong. A system that is not understood in its entirety, or at least to significant degree of detail by a single individual, should probably not be built."
I think I agree, but I think there are a lot of things you could say about this. What if you're just starting out and you don't know how to efficiently design systems? What if you work in an industry of people under 40 (under 30?) who by definition can't have the kind of experience that would let you design small systems? What if you work for a company that doesn't want to give you the time to figure it out? What if you have a competitor that's just shipping trash and forcing you out of the market with a "we'll clean up the tech debt later" mentality? How do we make tools that are powerful enough to enable us to do hard things, but wise enough to keep us from doing foolish things? Should we rely on our tools to do this? Is this an argument against centralization? Isn't that deeply inefficient?
Honestly I struggle with this all the time. I've got the outlines of some ideas and there are some tech communities grappling with the same issues, but I think we're just at the very beginning of a rethink about how we do software.
[0]: https://liam-on-linux.dreamwidth.org/88032.html