Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Dutch governments builds alternative for Microsoft based on NixOS (dawo.community)
    173comments
  2. Ink and Switch Interactive Homepage (inkandswitch.com)
    11comments
  3. Pentium II at 600Mhz with Voodoo 3 Emulated on 86Box with M6 Mac Mini (nyaa.sh)
    39comments
  4. Platform-Independent SIMD in Go (go.dev)
    1comments
  5. F-Droid 2.0 (f-droid.org)
    372comments
  6. CVE-2025-13032: Entering and Breaking the Avast Antivirus Sandbox Part 2 (safateam.com)
    16comments
  7. Show HN: Agentic CUDA Kernel Optimizer (github.com/bertaye)
    —discuss
  8. Special Projects (2016) (openai.com)
    16comments
  9. Show HN: Make cursed fonts like Times New Bastard (mitpit.com)
    101comments
  10. Oracle on the hook to pay data centre investors even if site has no electricity (ft.com)
    35comments
  11. Git-bug: Distributed, offline-first bug tracker embedded in Git (github.com/git-bug)
    —discuss
  12. Show HN: Whiteboard (YC W26) – An open-source IDE for thoughtful software design (github.com/devdotfast)
    120comments
  13. Why is the liver so weirdly regenerative? (dynomight.substack.com)
    227comments
  14. The Mafia may be keeping fentanyl out of Italy (economist.com)
    97comments
  15. Topcoat is pushing the boundary of server applications with Rust (tokio.rs)
    5comments
  16. 2DWillNeverDie (2dwillneverdie.com)
    61comments
  17. Amiga Screens: A Primer (datagubbe.se)
    4comments
  18. What About Rails? (jardo.dev)
    53comments
  19. Fearless SIMD v1.0 (linebender.org)
    41comments
  20. Rails World 2026 Opening Keynote [video] (youtube.com)
    387comments
  21. Boards of Casio (ambionix.com)
    —discuss
  22. Toyota is taking the Corolla electric (electrek.co)
    627comments
  23. My weird new hobby: Wandering around Tokyo on Google Maps (ahmedhossamdev.com)
    162comments
  24. Opus 5.5 is good at explainer videos (launchvideo.io)
    154comments
  25. Using LLMs to trace alchemical knowledge and decode 17th century letters (resobscura.substack.com)
    31comments
  26. Two-tier encryption in the UK (macanorak.com)
    417comments
  27. Google’s Project Suncatcher to put ML infrastructure in space (blog.google)
    403comments
  28. Writing Parquet files using Haskell (datahaskell.org)
    18comments
  29. Book review: Is parallel programming hard, and, if so, what can you do about it? (ahelwer.ca)
    57comments
  30. Sourcehut account takeover via build logs (XSS in ansi2html) (blog.arusekk.pl)
    27comments

Amiga Screens: A Primer

21 pointsby 4h agodatagubbe.se
4 comments
1h agoHN ↗

Maybe its me, but i believe the primary or secondary reason for screen is different screens had different resolutions and color depths, both of which dont really exist these days on any major OS.

1h agoHN ↗

I've been thinking a lot about this. Virtual desktops gets us somewhat close, but not quite. You're right the difference in resolution and colour depth isn't really relevant any more.

What I think made screens feel different was as a grouping mechanism, usually driven by a single application (though in more recent versions of AmigaOS you could open "public screens") that would manage the layout for that screen. You can do that with virtual desktops, but it takes some effort to simulate the behaviour.

I'm slowly iterating on something like that for my wm. I now snapshot the (by default tiling) layout and restore it, letting me "open" and "close" screens/virtual desktops, and re-open the applications on them, so instead of opening a single application that opens a screen, I will open a "project" and it will open a desktop and multiple applications on it whose windows will snap into place. I'm not happy with it yet, but it feels somewhat closer to me to how it felt to use Amiga screens.

24m agoHN ↗

It feels like the concept faded with the advent of large VRAM and fast fill rate graphics accelerators. I remember old X Window System workstations supporting multiple concurrent windows with different color depths and modes. The hardware would compose windows from memory during display scan-out, all to save VRAM.

10m agoHN ↗

How do different resolutions (pixel sizes) work? I get that everything memory related (including color mode and depth) could be switched on a raster line.

In theory it should be possible to change the frequency of the video signal mid screen as well, but I have a hard time to imagine switching repeatedly every frame wouldn't have driven the monitors of the time crazy. Even multi-sync monitors needed probably a couple of frames to sync, right?