I find it amusing that the paper doesn't include any screenshots. Those were the days!

I also expected screenshots there, especially given the word "interface". Turns out, it's not about user interface (UI), it's about programming interface (kinda API). It allows calling window-related functions on Macintosh, X Window System, and Atari. So the resulting windows were looking like a native UI, I assume.

The readers' natural question is 'does this look reasonable on multiple platforms?'. A two-second glance at two or three screenshots goes a long way to answering that.

In hindsight, this sounds more reasonable in 2026 where graphical documentation is taken for granted. In those days I think anyone would have spooled the .ps to their nearest laser printer and begin building something quickly with it just to check the looks.

I remember following a "build your own text windowing system" tutorial printed in a hcontinous paper back then

The document looks to be nicely rendered, likely from Postscript. Maybe generated by roff, since it doesn't look like TeX. Screen cap bitmaps could be converted to EPS and inserted into the Postscript.

If it was a PS document, you would have to spool it to a printer or screen renderer to read it anyway. The X Window System debuted in 1984, so on-screen renders would have been not too hard to find in a CS department in 1989.

> . i learned alot from this project, from how to solder,

This part is simply amazing, the "nothing is impossible" drive!

Back in the day, in Operating System Design class I dared to suggest the teacher that for some obscure inode related problem the system should ask the user what to do.

His answer was "We are designing an operating system, not a messaging solution".

This was circa 30 years ago of course, and the essence and complexity of what an OS is today is different, but the idea still resonates in my head every time macOS deploys one of these prompts at me.

Somewhere in early MacOS design guidelines I remember it saying that settings/prompts were a design failure that put a burden on users. Something really has been lost on the design team.

I know the landscape is different – more liability , regulation etc. But Lawyers will always overreach on compliance and notice. Even to the point of making the app useless.

They are expecting the product team to be forceful.

A positive example is that I noticed most EVs have a lot of consent prompts and warnings (e.g. a warning to look at the backup camera, and a consent prompt to comply to never using the nav/infotainment while driving) – but Tesla’s do not. I imagine Elon being very demanding that the experience take precedence.

That's why I'm rocking a Scribe. Do not really care much about note taking but my poor eyesight welcomes the bigger font size.

Light from the sun that is reaching us now escaped the surface of the sun 8 minutes ago, yes.

But photons are generated in the core through nuclear reactions, where they take their sweet amount of thousands of years bouncing around until they get out.

I think this is right in a certain sense, but not precisely. From what I understand no visible light photons are created in the core from nuclear fusion, it's mostly a bunch of gamma rays that get almost immediately absorbed. The energy, but not the photons from fusion, gets transfered up through the layers of the sun, through radiation and convection, eventually heating the photosphere. It is then the photosphere, white hot, which ultimately radiates the visible light we see as sunlight.

Thanks for your answer, I understand you're correct. Also, as another counterargument, if a photon is scattered... is it the same photon or a different one? Your perspective on energy instead of particles is better.

And thats a fact you don't need to learn in high school, at least you didn't in my time.

When we got notifications through Growl.

Have to love the tone of the article.

Builtwith reports this website is built with Framer, is this an official EU asset? If that's the case it's also a declaration of intentions.

the FAQ clearly states that it isn't an official EU website, it was used for petitioning the EU to consider this proposal.

Thanks for poiting this out

... but it seems most casualties in this accident are the passengers in the first carriages of the second train.

You never know.

Adobe could have benefited from doing this acquisition but they can be somewhat forgiven as they are already pushing Edge Delivery Services which is based in NextJS although it's a different approach. Combined with the Universal Editor they have a solid headless authoring setup for enterprise CMS.

But I really feel like Akamai is who dropped the ball here, this was a low hanging fruit for them and they're lacking offering this capability to offer their corporate clients as they transition to full headless. Now it's going to be their competition (Cloudflare, even Fastly through Adobe & the EDS push) who will try to take a portion of their cake.