It's crazy that an emulated version of a famously-buggy alpha OS running in a browser is more responsive than the host OS, but there you go. These Copland windows open at lightning speed in comparison to Golden Gate.
What does it tell you? It gives me much more confidence in their output tbh. Reading generated text is unpleasant; feels like mediated and averaged-out humanity.
> AmigaOS 2.x layed out a vision of the desktop UI as a malleable and personalizable toolbox (or one might say "workbench" heh) like no other operating system since then
Can you say more? I had (and loved) an A1200 and appreciated what things like ARexx could do, but I don't know what you're alluding to here that things like the Mac didn't ultimately implement as well (though sometimes less well; I miss multiple screens to this day)
Back on the Amiga 3000 we had built our asset creation tools for a game that eventually ended up as Urban Assault on the PC. This was a wild mix of custom-made and standard tools wired together via AREXX and controlled with a little macOS dock like icon toolbar, and all integrated with the workbench file manager.
E.g. one such custom workflow would be to "pipe" an image file created in DPaint into some standard image processing tool (forgot the name, basically like ImageMagick, but as a UI tool) to change the pixel format, scale and filter, then piping the resulting output image into a custom tool to convert into an engine specific texture format, all the while updating some asset database files, and IIRC also creating an icon file in the process.
Most of this can also be achieved with a pure cmdline workflow today via Python or Node (by glueing together tools like ImageMagick, ffmpeg, various asset pipeline tools), but the special sauce on the Amiga was that most 'modern' UI tools adhered to standards defined by the Amiga team for cmdline usage and scripting.
The 'plugin architecture' was mostly about datatypes (globally available file format encoders/decoders), BOOPSI UI components and 'Commodities' (IIRC small background tools that could intercept and manipulate system events).
> most 'modern' UI tools adhered to standards defined by the Amiga team for cmdline usage and scripting.
One minor example of the usability was that the ReadArgs() call was fairly extensively used within a year or two after it was introduced and meant that the "?" command line option for help worked "everywhere" and would give a machine parseable, semi-typed options list (annotations like "/T" for toggle, "/N" for number etc.)
Many newspapers in the 90's had their whole classified sections automated using custom AppleScript workflows, it was one of the big things that kept publishers on the Mac instead of Windows, since Microsoft didn't have anything to compete (OLE/VBA was a joke for these things)
Yep the whole AppleScript and (Quark Xpress) Xtension mechanism was remarkably sticky. Apple were treading dangerously during the OSX transition when it became clear much of that would never port over, but Quark was losing their grip by then.
MS were trying a huge NT push into the DTP industry that basically hit that wall and aborted.
I recall the A500 series as being thought of as 16-bit in the UK -- the 32-bit marketing started with the A1200, and devices based on it, like the CD32 (hence the name).
That was because the A1200 was the first Amiga to have a 68020 as the native CPU on the motherboard. The 68020 had 32-bit data registers and 32-bit address registers. Earlier Amiga's were designed around the 68000 CPU which was instruction set compatible with later 680x0 CPUs (which featured backward-compatible super sets). In the 68000's data registers only had 16 data lines connected externally, requiring two cycles to read or write 32-bits and the 32-bit address registers didn't have their upper 8 bits connected to external pins, limiting the directly addressable RAM to 16MB (24-bits). These compromises allowed the CPU to fit in a 64 pin DIP package while the standard 68020 came in a 114 pin PGA package and was fully 32-bit internally and externally.
However, it's confusing because the A1200 had a lower cost version of the 68020, the 68EC020, which also didn't have the top 8 bits connected and came in a smaller 100 pin QFP package. So technically, it had the same addressable RAM limit as the 68000 (although it had other instruction set and clock speed improvements).
Prior the the A1200 (1992) here was an earlier Amiga model, the A2500 (1989), which came with a full 68020 CPU but it was a 68000-based A2000 with Commodore's A2620 add-on accelerator card pre-installed, so it had both CPUs (although the 68000 was unused when the accelerator was added).
This team really have been thinking about weather a lot, and it makes me very curious about what they’ve created this time.
It’s that depth of thought and expertise that feels missing from most of the vibe-coded launches we’ve seen recently. I actually wouldn’t mind if Acme had vibe coded parts, but I bet they didn’t.
> it makes me very curious about what they’ve created this time
The rainbow and sunset alerts are really cool ideas. I'm now realising that a simple tie-in to astronomical phenomena could prompt a useful notificationa around it e.g. being worth going stargazing that night. I ski–learning that the near-term forecasts just changed would help me change my schedule the day before versus trying and failing the morning of.
I'm almost shocked we don't have a large weather model instead of a language model. Seems right up the alley.
Also I don't get what happened but I think it was AccuWeather or weather underground in the early 2000s where it was to the minute accurate and it seems like it's gotten worse since everywhere.
Re-read what you just linked. In the response from the JIMU:
"A 51-year-old man from Aldershot was arrested on suspicion of sending by public communication network an offensive, indecent, obscene, menacing message or matter."
This is the legal basis for the arrest. Without the retweet, police would not have had authority to turn up to his place of residence - twice - and demand entry. No doubt they preferred Brady voluntarily submit himself for interview at the station, but he refused, which I hope we can all agree is the morally correct position. No one should have police turn up outside their house - TWICE - because of a parody retweet.
The law might be a bad one (and probably is) but on balance better that police investigate suspected illegality than don’t. Overall I’d rather be somewhere where even a former royal can be arrested than somewhere the rule of law is optional.
This doesn't feel like good-faith. There are leagues of difference between "what you typed out" when that's in a highly structured compiler-specific codified syntax *expressly designed* as the input to a compiler that produces computer programs, and "what you typed out" when that's an English-language prompt, sometimes vague and extremely high-level
That difference - and the assumed delta in difficulty, training and therefore cost involved - is why the latter case is newsworthy.
When has a semantic "argument" ever felt like good faith? All it can ever be is someone choosing what a term means to them and try to beat down others until they adopt the same meaning. Which will never happen because nobody really cares.
They are hilarious, but pointless. You know that going into it.
Fastmail is the way. These are people for whom email is their job and focus and you get everything that comes with that, including good and responsive customer service.
So are the email servers used by the recipients of your emails, no? Almost everybody uses gmail, so even of you don't most of your email correspondence is going to end up, or originate from, on gmail servers anyway.
reply