Same here, and he was the CIO for a global investment bank. He also dictated his replies for his secretary to type up and send.

It's a telescope, so it's a receiver. Why - and, indeed, what - was it transmitting?

There are five AI-related stories on the front page of Slashdot just below this one.

It's not hard to see a cause/effect between massive deployment of new AI-related hardware in data centres, and the increased carbon emissions of power generation required to run them.

And no, the "we're running our new DC on green energy" argument doesn't hold water unless equivalent new green generating capacity has also been constructed.

Oh, it might also have a bit to do with the increased demand for electricity to power the increasing number of EVs.

Did I miss the memo that mentioned that power delivery from orbit was now a thing?

Or did someone actually design a terrestrial power network that depends on telecoms provided by a single-point-of-failure that cannot be reached to repair?

And most will have valid reasons for not having made the switch, whether they be financial or practical. After their house, a car is typically the most expensive item someone will buy (and if they rent, it's the most expensive), so they want it to be right, and they don't change on a whim. In the ICE world you can pick exactly the vehicle type you want/need - roadster, coupe, sedan, station wagon, mini-van, SUV - and then decide between gas, diesel or, increasingly, hybrid for the powertrain, but if you want full EV your choices are still limited and compromised.

One other thing: in some parts of the demographic, I suspect an aversion to the "iPad-on-wheels" approach to driver controls might play no small part - I still have to remind my mother how to copy/paste or forward email every few weeks, but not how to turn on the heated seats or tune the radio in her ICE car...

I'm likewise a city dweller without the possibility of home charging. However, my city has perhaps a total 30 public charging points, spread across the carparks of the out-of-town retail parks, only a handful of which could be called "fast". Even better, most of the carparks use ANPR to limit your stay to 2 hours, so even if you can get a working bay, you'd get barely enough juice to cover the journey.

They did dig up one corner of one of the carparks last year, did a load of cabling and groundwork, and I thought "Great, they're putting in dozens of EV chargers!"

It was a new Burger King.

Most, if not all, current EV owners can charge at home, as part of the decision-making process in buying an EV is having the ability to install a home charger.

However, huge numbers of ICE owners do not have that luxury - dedicated off-street parking for urban car owners is very much the exception, irrespective of the dwelling type. For many, it's pot luck whether you can even park outside your own house, and running a cable across the sidewalk/pavement is very much frowned upon.

EV adoption has plateaued because pretty much everyone for whom they are a practical option - the low-hanging fruit, if you will - has already bought one. The hard yards are making them fit the use-case(s) for everyone else, which includes both ubiquity of charging and a viable second-hand market... and, perhaps not telling people to change their use-case(s) to fit the advantages - and limitations - of an EV.

Good call - resource forks were indeed a first for Apple as part of MFS, with the release of the original Mac in 1984.

Fuck me - that was FORTY years ago. Damn but I feel old now...

Anyway, I've always been in two minds about resource forks. It's elegant, but not portable across different file-systems until quite recently, compared to the resource tables compiled into Windows binaries. I suppose it was a very early step on their "walled-garden," "we know best" path.

I'm not sure that's entirely the case - Qualcomm has had an FP16 block in their SoCs for a while.

I will agree that Jony Ive's designs look very good, but the underlying tech took a back seat.

For example, I remember that early iPhones didn't support MMS or even copy/paste, when smartphones that predated the iPhone did.

And then there's the "you're holding it wrong" iPhone 4, the "don't put it in your back pocket and sit down" iPhone 6, and the "don't type too hard" butterfly keyboards, to name but a few...

Sorry, but no.

The Corvus Concept was earlier. Obscure, certainly, but before Apple.

Sony started making the first 3.5" drives in, IIRC, '81, and several vendors - including HP - were putting them in their kit before the first Mac came along in '84.

De nada :)

...that Apple haven't been first in anything.

This is not to say that many of their products have not been successful, just that none have been original - with the possible exception of iTunes.

Yeah, this'll probably get modded down, but it is nonetheless objectively true.

Except ARM is currently owned by SoftBank, which is Japanese. Not currently an problem but, IIRC, they tried a while ago to sell it and might try again, so who knows?

Until the accountants and marketers are subordinate to the engineers in the org chart, nothing will change in either company.

Well, from my real-world support experience, I've had to downgrade many a 64-bit Windows installation to 32-bit to support either drivers for niche hardware (and that the users won't change - scanner drivers were a notorious culprit), or ancient 16-bit Windows apps that the user can't live without (and the user is insufficiently sophisticated to deal with a VM).

Remember, there are many people running Windows 10 on the Windows 7 hardware they bought early last decade and, with maxed RAM and an SSD, is working just fine for them for everything they need to do. These are the same people that use a smartphone until it breaks or won't hold a charge, rather than buy a new one every 18 months. There are really quite a lot of these people.

And before you ask "Why would anyone use a 10 year-old computer?" consider the car analogy - "Why would anyone drive a 10 year-old car?" - and the answer is the same: "It does what I need it to do and it runs fine."

Now you tell the guy with a 10 year-old car "Well, you gotta buy a new car, because someone decided the annual safety inspections won't certify anything older than 6 years." "Why?" "So that you have to buy a new car."

Well, that's kind of my point - when people are forced to buy new hardware when Win10 goes EoL, that's when sales volumes take a leap upwards, and that's when we'll see a repeat of the "Why doesn't [blah] work on this new machine when it worked fine on my old one!" conversations at the returns desk.