Facebook told to rename their Threads app in UK or face legal challenge

I just love it when 800 pound gorillas don't do their homework.

A software company in the UK trademarked a package that they sell called Threads. It's an enterprise messaging platform that does all sorts of marvelous things, from the first link: "The British company trademarked Threads in 2012 for its intelligent messaging hub, which can store a company's emails, tweets, and voice over internet protocol phone calls in a cloud database."

A DECADE AGO. Facebook's parent company Meta approached them four times to buy their domain name, threads.app, and were rebuffed each time. Threads were kicked off of Facebook when Meta's Threads went live. And now they've been given 30 days before the UK Threads people are going to take them to court! Threads, of course, is Meta's 'Twitter' app.

I can see them being forced to change their name in the UK, which will cause a bit of consternation.

There's a very good comment in Slashdot about Meta's choice in a product name: "We use the word threads to talk about email, forums and chat. FB intentionally chose this name in order to throw a wrench (or spanner) into popular vernacular. It's quite manipulative and deeply troubling behavior that is all too common with tech companies." At least Twitter and Tweets were unique when it started up.

https://www.businessinsider.com/meta-told-stop-using-threads-name-company-owns-uk-trademark-2023-10

https://www.businesswire.com/news/home/20231030082004/en/Threads-Software-Limited-Gives-Meta%E2%80%99s-Instagram-30-Days-to-Desist-from-Using-the-Service-Name-Threads

https://yro.slashdot.org/story/23/10/30/2045231/meta-told-to-stop-using-threads-name-by-company-that-owns-uk-trademark

A couple of tech news items

First up, Western Digital is splitting off its flash memory business.

In 2016, WD - traditionally a hard disk drive maker - purchased flash memory maker SanDisk. SD is known for making USB flash drives and compact flash cards for cameras, smart phones, and other devices. If you look back at 2016, the purchase makes sense: solid state drives were booming, and WD wanted to grow in that direction. But the pandemic utterly disrupted the hard drive and SSD industries and the flash memory side of the business has been suffering.

Now here's the interesting bit. An activist investor started pressuring WD to split off the business, and now they are! Their fortunes will rise and fall as they may, independent from one another. And, I guess, investors will be able to gobble up more stock from each of them?

https://www.reuters.com/technology/western-digital-separate-into-two-companies-2023-10-30/


Apple released their new CPU architecture, the M3 chip. And it has an interesting memory characteristic: it has 25% less memory bandwidth!

There's some curious things going on here, and it's a little too early to know exactly what's up. The chip was just announced yesterday, and the computers are not yet available though they can be ordered now. This is the third ARM M-series chip that Apple has developed in-house and they are screamers. I bought an M2 MacBook Pro earlier this year and am quite happy with it. This M3 chip? It's a bit puzzling. They are comparing the specs of the M3 against the M1, not the M2. And gee whiz, Batman, it's faster than the M1! The numbers would not be nearly as dramatic against the M2.

But the memory numbers are pretty firm: if you have processes that require LOTS of memory access, you may not get the performance out of an M3 system that you would out of an M2. The reason why this limit is in place is unclear, it may have to do with chip limitations or yield. Things will be revealed when actual units ship and are subjected to rigorous testing and labs outside of Apple's purview can get to the bottom of this strangeness.

It's going to be interesting to see what's going on here.

https://www.macrumors.com/2023/10/31/apple-m3-pro-less-memory-bandwidth/

I admit I'm an Apple fan - to a degree. They do a great job of integrating their products, and that is very useful to me. Their hardware is very high-end, but you do pay a direct price for that. They have excellent customer support. And you pay a price for that. And I'm willing to pay that, because I'm sick and tired of having to fix lousy products myself! I've been doing it for too long.

But I also don't like a direction that Apple has taken. They've bound themselves onto this treadmill that ALL of their iPhones have to be refreshed EVERY year. Which means a new iOS EVERY year. They introduce new iPads every year, though that's not a complete line refresh annually. And they introduce new laptops every year, but again, not a top-down refresh. And they do a new MacOS every year.

And in my ever so humble opinion, this is sometimes forcing them to release things before they're truly ready for prime time. The iPhone 15 released a few months ago? Has overheating problems. And if you use wireless induction charging in a BMW or maybe a Toyota, it can zap the NFC chip - Apple says a fix coming later this year. When they released iOS 11 a few years ago, they completely screwed over hearing aid users for pretty much the entire duration of that product release.

The problem is, a lot of the tech industry is ruled by people who live by the mantra 'Move fast and break things' and go back and maybe fix it in the next iteration. I hate seeing products released that haven't been properly tested and have major flaws, just to meet a marketing deadline! Marching to this constant beat of a one year release cycle to match hardware of ever-increasing complexity is a recipe for utter doom.

My iPhone, a 13 Mini, is two hardware generations from the current version. I bought a pair for my wife and I two years ago this coming Christmas. It's running iOS 17, the latest version. But I now believe that it is not truly iOS 17. You see, they time the new iOS release with the new iPhone release, and the new iPhone will ONLY run the latest iOS, can't run the previous generation. I have a feeling that iOS 17.0 is actually iOS 16.9. I think that they're continuing to build on the previous iOS, putting on new shinies and bells and whistles, plus the stuff needed to support the new hardware in the latest generation phone, and then changing the version number to the next increment. At some point they have to fork the operating system (make a copy so maintenance engineers can make patches (fixes) for problems in the aging code base) so that the engineers working on next year's phone can get the operating system working for the newer hardware, which is software-disabled for the old phones since that hardware doesn't exist on an iPhone 13 even though iOS 18 will need to run on it.

Software development for things like this must really suck be really challenging, and I am so glad that I was never involved in it! I wrote business systems for government agencies to support populations in need, and I'm proud of what I did because it helped people. This stuff? Far beyond my ability, that's for sure. Completely different type of programming.