US views on AI are interesting. There is actually some nuance in the answers people give :
"50% say they’re more concerned than excited about the increased use of AI in daily life, up from 37% in 2021.
10% are more excited than concerned.
38% say they’re equally excited and concerned."
For people who are interested in modern literature reading the Booker Prize winners from 1969 forward and skipping any book that you find dull after 100 pages or whatever is well worth it.
Then people can stop as they get to the latest things that are driven by identity politics when they choose.
Are you sure about that? The page you link says that "The 100,000-word spelling checker lets you check a range of text, look up a single word, check continuously, and add words to the user dictionary", but doesn't mention underlining words. I also couldn't find a screenshot of that feature. Actually, with the AmigaOS 1.x color scheme, the squiggly lines would have probably been orange, because the standard color scheme was black/white/blue/orange (in AmigaOS 2 and above it was black/white/grey/blue to enable a 3D effect on the controls, so the highlight color would have had to be blue?!).
It does have a real time spell checker. But it doesn't seem to have the squiggly line. The screen blinks at you when you type a word it can't find.
I've just run Prowrite 2 and 3.1.1 via FS-UAE.
So my memory is wrong about that feature have a red squiggly line.
It did have realtime checking. Also Prowrite was WYSIWYG. The realtime checking is neat, but it's actually a bit annoying with the blink. The red squiggly line is a better way to show that there is an unrecognised word.
"Among the many new features was a spell checker with a 40,000 word dictionary, although lacking many American English terms,[11] a mail merge program, footnotes and semi-automated hyphenation.[12] The spell checker included the relatively rare, for the time, option to check on-the-fly. It also added document statistics display, including the number of characters, pages, etc"
Honestly I'd guess it's one of those things that possibly originated at Xerox Parc and then got added to consumer products from the 1980s onwards.
Personally, I remember it because I remember seeing Word 6 and thinking 'at last they have caught up to Prowrite'.
1st Word on the Atari ST 520+ with monochrome monitor: that
was how the far future felt like in 1986.
With the exception of the somewhat wobbly cheap keyboard, that was the best and most distraction-free setup I have ever seen for WYSIWYG word processing (sadly never tried the Xerox workstations).
Sorry, but as a former Amiga user I have to jump on the opportunity to disrespect the Atari ST: wasn't the same thing (WYSIWYG text editing or even desktop publishing on a monochrome monitor) already possible years before with the Apple Mac? I mean, it was nicknamed the "Jackintosh" for a reason. Ok, it was only one year (the Mac being famously released in 1984, and the Atari ST in 1985). And of course the Atari ST was more affordable, it had that going for it.
I can't find screenshots or descriptions of that either (but it doesn't really say much either way - I couldn't find much about the spellchecking at all). But re: colors, a lot of applications would open their own screens and set their own palette, so the Workbench palette isn't necessarily relevant.
Indeed, no relevance at all. Sorry rob74, that's a misunderstanding of how large applications most often tended to work on the Amiga. They didn't generally open a window on the Workbench screen, they opened their own screen. The keyboard shortcut <Amiga key>-<M> cycled between them. A word processor's screen could then have 16+ colours.
No problem! My recollection is a bit hazy, and I'm not active enough in retrocomputing to refresh it. I was aware that applications could use their own graphics modes, but I wasn't aware anymore just how often "productivity" software did that too. But of course, it made sense, since the Workbench screen was limited to 4 colors (in order to save memory, I guess, especially the precious "chip memory" that was accessible to the custom chips), and on their own screen they could use a whopping 16 colors :)
That's a really interesting/informative link you have.
Some highlights are:
- Energy use per capita has been declining since 2000
- Overall energy use has been basically flat since 2000
- Essentially, coal is being replaced by gas, almost 1:1. Lump both together and their relative share of the market is pretty stable.
- Solar went from 0.3 to 2.8% in the last 10 years, wind from 0.3% to 4.2% in the last 20 years. 7% wind/solar isn't world-leading but getting from basically 0 to 7% in 20 years is significant movement.
Check out 'Coding for Beginners Using Python' by Osborne.
Also have a look at 'Coding Projects in Python' by DK books.
Both these books are excellent and would enable a smart and determined 11 year old to learn to code.
To be honest these books teach coding in a way that is much easier than it was in your day. You can also jump on many, many websites and teach yourself how to code.
You're also an exception. Many, many kids read those old Osborne books and only a very tiny fraction like yourself became coders and an even smaller fraction became as successful as yourself.
Right place, right time, right level of curiosity. Back then, I didn't really have a choice: there weren't any other books in my school library, I didn't want to spend lunchtimes in the playground (I was being bullied), I knew programming would be potentially useful (my Dad had switched from being an accountant to something I heard was called a "systems analyst", which I knew had something to do with computers, and had allowed him to emigrate with his new family), and well, I was a bit of a mess.
I have seen some of the newer projects, and like I say, the Raspberry Pi stuff makes programmable computing accessible to a kid without much, I just don't think the bar overall is as low as it was for me.
And yeah, survivorship bias, and a weird population skew with me: I was literally the only kid in that computer room determined to learn how to code.
A windows laptop from today is vastly easier to code on that a C64 or whatever. Most houses would have an internet connection as well so they can get to all sorts of things.
A Raspberry Pi is probably something richer kids get to play with.
Primary School kids today in Australia often get a Chromebook and have some tutoring in Scratch. Again, it gets you the ideas of coding in a way that more kids will get.
You mention the lack of alternatives that got you and other kids into coding. That's probably a thing. There is so much more entertainment available today that most kids probably don't get bored like kids did in the past and sat down and learnt to code. It has to be more intentional.
When I was a kid my mum was a teacher and brought home a computer over the school holidays which had no games. I taught myself databases and spreadsheets because there was a good tutorial on that.
There is also probably something in that until, say, the 2010s computers were not quite ubiquitous enough that they were a constant part of kids lives. Certainly in the 1980s and 1990s there was something almost magical about the devices. A kid today who grows up in a household with smartphones, tablets, laptops and multiple smart TVs probably won't get the same thrill about moving an object around a screen as someone did 30+ years ago.
