Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Platform-Independent SIMD in Go (go.dev)
    38comments
  2. Allow Carriers on Planes (jefftk.com)
    80comments
  3. Git-bug: Distributed, offline-first bug tracker embedded in Git (github.com/git-bug)
    30comments
  4. First Principles Thinking (sunilsadasivan.com)
    2comments
  5. Pentium II at 600Mhz with Voodoo 3 Emulated on 86Box with M6 Mac Mini (nyaa.sh)
    74comments
  6. Ink and Switch Interactive Homepage (inkandswitch.com)
    17comments
  7. Dutch governments builds alternative for Microsoft based on NixOS (dawo.community)
    412comments
  8. F-Droid 2.0 (f-droid.org)
    391comments
  9. Boards of Casio (ambionix.com)
    17comments
  10. Show HN: Make cursed fonts like Times New Bastard (mitpit.com)
    105comments
  11. Amiga Screens: A Primer (datagubbe.se)
    10comments
  12. CVE-2025-13032: Entering and Breaking the Avast Antivirus Sandbox Part 2 (safateam.com)
    22comments
  13. Special Projects (2016) (openai.com)
    31comments
  14. Show HN: Whiteboard (YC W26) – An open-source IDE for thoughtful software design (github.com/devdotfast)
    126comments
  15. The Test (tante.cc)
    17comments
  16. Factorio that you can touch (factorio.com)
    1comments
  17. Why is the liver so weirdly regenerative? (dynomight.substack.com)
    250comments
  18. 2DWillNeverDie (2dwillneverdie.com)
    72comments
  19. Topcoat is pushing the boundary of server applications with Rust (tokio.rs)
    66comments
  20. Rails World 2026 Opening Keynote [video] (youtube.com)
    418comments
  21. Fearless SIMD v1.0 (linebender.org)
    47comments
  22. Opus 5.5 is good at explainer videos (launchvideo.io)
    183comments
  23. Toyota is taking the Corolla electric (electrek.co)
    693comments
  24. Oracle on the hook to pay data centre investors even if site has no electricity (ft.com)
    105comments
  25. My weird new hobby: Wandering around Tokyo on Google Maps (ahmedhossamdev.com)
    165comments
  26. Microsoft Abandons Personal AI Chatbot Race with Copilot Reboot (bloomberg.com)
    3comments
  27. The Mafia may be keeping fentanyl out of Italy (economist.com)
    209comments
  28. What About Rails? (jardo.dev)
    112comments
  29. Two-tier encryption in the UK (macanorak.com)
    436comments
  30. Using LLMs to trace alchemical knowledge and decode 17th century letters (resobscura.substack.com)
    34comments

Amiga Screens: A Primer

67 pointsby 8h agodatagubbe.se
10 comments
4h 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.

4h 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.

3h 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.

3h 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?

2h agoHN ↗

It’s basically just an SD TV signal, the vertical height in lines doesn’t change, it largely just swaps if each line outputs 320 or 640 pixels during its assigned time period.

Having interlaced and non interlaced modes at once seems a bit funky though, but I assume it just forces everything into interlaced with the non interlaced mode sections having the same line sent on both fields?

2h agoHN ↗

In the context of the Amiga you didn’t need to change the signal frequency, the underlying video signal stayed the same.

For wider pixels, the hardware just drew each pixel for longer, and for taller pixels each pixel spanned more lines.

Pixels weren’t real in the CRT days :)

1h agoHN ↗

In a sense pixels arent even real today right? It's an abstraction

33m agoHN ↗

Kinda, but a CRT literally doesn’t have precise pixel targeting in the way an LCD does. Instead, you’re telling the electron gun to draw red for a little while, and it paints what it paints.

1h agoHN ↗

Analog monitors don't care about the dot clock. They draw lines, but you can put whatever signal you want in the lines so long as the dot clock doesn't exceed the available bandwidth. So horizontal resolution is effectively a range you can change at any time and the monitor won't even notice.

Vertical resolution is very much part of the spec, but even then CRTs will sync to hilariously out-of-spec signals that gain or lose lines per frame. Sanely-designed graphics hardware like the Amiga wouldn't do this, but the Atari 2600 wasn't sanely designed and had plenty of games that played fast and loose with NTSC. Atari graphics hardware only generated a single line of graphics and relied on H-Blank effects for literally everything else. Even the vertical retrace signal was controlled by the game. So it was very common to see badly programmed games send too many lines, and a different wrong number of lines each frame, which nobody noticed until people started writing 2600 emulators.

2h agoHN ↗

I don’t know much about Amiga, but from this article I recognize the Atari 8 bit / ANTIC DLI heritage at play!