"BASIC was never thought in university as far as I know, maybe in kindergarten schools."

I was taught BASIC in a 100-level course at the University of Massachusetts, Boston - via teletype interface (that's 'typing on physical paper and the computer types back on the same roll' for you kids) to a mainframe that was actually somewhere on the UMass Amherst campus).

Of course, this was in 1977.

This has been out for a while... here you go: https://www.youtube.com/watch?...

I appreciate the sentiment (it's a running theme through the comments here), but as a (very) senior software guy with health issues and approaching Medicare eligibility (that's 65 years old for the non-USians reading), I wouldn't be able to even shadow a driver all day, let alone do deliveries. No, I don't work for DoorDash, but if I did I'd not be physically capable of complying with such a 'mandatory' policy.

I think quite a few folks here are making assumptions about the physical capabilities of folks who design/code vs folks who are physically active as a part of their regular workday... there seems to be an assumption that the DoorDash software devs are all young enough that 'some fresh air and real work' (dogfooding) would suit them right... and that might well be the case, given the ageism in the industry.

But I don't think enough consideration is being made for the possibility that employees who make a living sitting on their backsides and crafting code may not be physically and/or otherwise suited for a 'down in the trenches' role of any given enterprise.

I initially read this as: "Ransomware Attack Disrupts Massachusetts Furries"

On re-reading, I am much less concerned.

Massachusetts residents, furry or not, will simply drink-beer-in-place until things are resolved.

I received an iPhone 5c from <company> as an award in lieu of a raise back in 2011... it was my first 'smartphone'.

I'm still using it.

Had to replace the battery a few years ago (iFixit kit) and iOS no longer updates, but it's still my operational phone and works well.

Eh? Speak up!

If it was a C library... well, you couldn't really take advantage of all of the advantages C++ has vs C especially when implementing a windowing UI / application framework - inheritance, polymorphism, etc. really make a difference. If you did that in raw C you'd have, well - pretty much what we had to use for programming to the Win16 (now Win32) API before Borland's OWL (Object Windows Library) made the scene (this is before MS ever came up with MFC) - opaque handles to this and that, breaking down and handling Windows messages, etc. It was very low-level stuff, tedious and prone to error.

If you're happy with a CURSES-like library, that's fine (I've done my share of that also with C on DEC platforms, back in the VT-100 days) - but for anything this side of Y2K, application frameworks and OOP are the way to go. wxWidgets is definitely a valid way to get a cross-platform (and cross-language... look at wxPython) GUI app out there and still keep what's left of your hair.

Disclaimer: I've been using wxWidgets (was wxWindows) creating apps for a Fortune 500 international since the early 2.0 days (mid-90's).