Having used versions on both for years, I'd say there was a "dark" time around 2011 when the macOS versions were lagging badly feature-wise, but they're pretty much on-par today.

My biggest complaint is that you can't turn off the ridiculous animations in macOS versions (e.g. moving between cells in Excel). That makes the entire suite "feel" slower when in reality, the macOS version could easily be just as responsive as the Windows suite.

The more I spoke with, the more I realized that they were there entirely by choice. Most were given packages to "retire", but they were still in their 50s and their spouses hadn't retired yet, hence the job. All of them loved the physical work, interaction, and especially leaving work at work at the end of the day. They seemed relaxed and genuinely happy.

If you end up at Home Depot, chances are you'll really enjoy the work, plus I think they were still using an AS/400 the last time I peeked at their displays!

I have in my hand (I guess I like using that phase today), my father's original receipt for the HP-45 (it's with the box and manual). $299.00 in 1975, which is $1,850 today(!!!).

Relatively speaking, electronics are very, very cheap today compared to what they used to be. Still appreciate that my $30 CASIO does 90% of that the NumWorks can do, but I'm happy to support upstarts such as NumWorks.

I'm holding in my hand a 4-bit Von Neumann Mostek MK50310N that my father and I used to use to build calculators long ago. Although Mostek made chips for HP (such as the HP-35), they weren't commercially available, but the 50310 was. We could only dream of a project such as yours. I was happy when the "open source" NumWorks was released, but this project aligns more with my interests.

Will definitely install the Qt simulator - would be even better to build one IRL!

Edmonton is as far west from the geographical centre of Canada as Toronto is east. I think it's a a bit of a stretch to call the GTA "geographically central". Economically and demographically, definitely.

The Weather Network, which really should consider geographic markers only, calls the GTA "central Canada". I think there would be an outcry if they started saying "eastern Canada".

This is part of the issue; the GTA is solidly in the east (the centre of Canada is in Manitoba), but when someone says, "eastern Canada", one automatically thinks "Nova Scotia", but Toronto is a relatively short drive from New York City. That being said, I understand that in most cases, "central" is referring to population, industry, finance (not fashion - that's Montrėal).

Regarding the site, the exhibit's producer, Zbigniew Stachniak, wrote an excellent book [0] on the world's first truly portable computer: the MCM/70 - which ran APL (yay!).

[0] https://www.mqup.ca/Books/I/Inventing-the-PC2

"The thing I always love is when there's an intellectual challenge that when you master it gives you practical abilities."

Tangential capabilities from mentally challenging tasks are your personal differentiator - regardless of what tools you use or what you're working on. Running 5 miles puts you way ahead of the person who rode their e-bike for 20. Performing the hard work pays off - not always monetarily, but like exercise, it's uplifting and healthy, and provides long-term advantages.

Corporations need differentiators as well - hopefully they rely on their creative and innovative employees to stand out, regardless of tooling.

Also, for sale: BMW E60/61 Bentley 2-volume set. Barely used.

Most of the team has since passed away, and their code has been long replaced by modern systems, but what stuck with me is that great code is a form of art - where your individual style, insights and personality can be reflected in code for the better. The systems were efficient, responsive, extensible, and a joy to work on, since the team took a great deal of pride in their work. It really is akin to being affected by a clever and insightful work of art. A decade later, and programming became something to "make money" at, which flooded the market with many people who never really had a deep love of programming, and I guess that's ok, but something has definitely been lost along the way.

To your point, it may not be such a bad thing if people started boycotting computer science and it again became more of a calling than purely an avenue to employment.

When I have other sweeteners such as taking a swig of a stevia-laden diet iced tea, I have a reaction. I used to be able to drink the exact same iced tea when they used Aspartame with no effect. I don't think your body is "fooled" by sweet tastes - it only reacts when there is actually something to process.

The fact sucralose is being added into all kinds of products has removed many choices for me, which is unfortunate as the selection was quite small to begin with.

Prepared food is pretty much a no-go; there's only a single energy bar I purchase that uses stevia only, but I make my bars from whey protein isolate, cocoa powder, and peanut butter powder, plus roasted flax, almond flour, almond milk, and sweeteners. I did skip sweeteners completely for some time, thinking that I'd "get used to it", but I really didn't - we're programmed for something sweet!

We already know from glycemic index charts that almost all sugar substitutes impact blood glucose to a certain degree, and there are only a few that have no impact. When sucralose became widely available, I bought some to try to bake with, but the carrier was maltodextrin - a starch, which prevented me from using it. Undeterred, I purchased pure sucralose drops in a neutral liquid. The sickly-sweet mouth feel after consuming sucralose is a bit tough to take [0], but that wasn't the worst of it. It actually impacted my blood glucose, and when I read more of the research, sucralose actually did cause an insulin reaction in many people who consumed it ("Several studies have shown that sucralose is not physiologically innocuous").[1]

Then I read how sucralose is produced; literally thousands of pounds of sugar is used and converted to produce a few pounds of sucralose. It's being pushed hard by the industry, and I can only think of the 'vilification' of cheaper sweeteners such as Aspartame by industry, much in the same way that saccharin was vilified by flawed [2] studies in the 1970s - just as Aspartame was being developed as a commercial product.

Alcohol is a class 1 carcinogen, and sugar causes irreparable damage to millions of people around the world. I find it somewhat odd how people react to what appears to be a flawed and dubious Aspartame study, when there are much larger elephants in the room.

[0] https://nationalpost.com/news/world/after-sales-plummet-diet...

[1] https://pmc.ncbi.nlm.nih.gov/articles/PMC7155288/

[2] https://pmc.ncbi.nlm.nih.gov/articles/PMC3185898/

Indeed, when someone changes lanes in front of me, I gently let off the accelerator, but as someone else noticed, that can enrage drivers behind me (I don't take it personally), and I'm definitely traveling fast enough to remain in the middle lanes.

Unfortunately, sometimes over a 45 minute freeway commute, dropping back repeatedly means arriving 15 minutes or more later. Again, no big deal now, but it was somehow unacceptable when I was younger.

Incredibly frustrating, and I've driven all over North America - there's practically no major city where this doesn't happen. If you're not maintaining a safe following distance on city/residential streets, that's a different matter.

I think the Internet made 'waiting' for a response completely normalized for many applications. Before then, users flew through screens using muscle memory. Now, when I see how much mouse clicking goes on at service counters, I always think back to those ultra-fast response time standards. I still see a few AS/400 or mainframe terminal windows running 'in the wild' and wonder what new employees think about those systems.

This is sage advice. I spent the better part of a day trying to steer Gemini into correcting an inconsistency when I likely could have solved it in under an hour. I think persevering with Gemini was due to a number of factors, including novelty, stubbornness, and (unfortunately) not knowing in detail what Gemini had written up to that point.

I eventually studied the resulting code, which ended up having a number of nested 'hacks' and required refactoring - more time wasted, but still much faster overall.