I very much doubt it. Really we need the regulator to have a look at it, and do the science needed.

You are right about Japanese sentence order, although it's typically not as wordy as Yoda is.

I figured that Lucas just did it to make him sound profound, which was mocked by the movie Mystery Men. In reality Yoda didn't say much in the original movies, and most of what he did say was either obvious bollocks or terrible advice. The prequels only confirmed that, with Yoda basically handing a vulnerable Anakin to the Emperor by telling him to bury his quite legitimate feelings.

I wonder how much of the Windows licence cost is handed back to the consumer, and how much Linux tax they add on.

By "Linux tax" I mean the extra margin to cover a higher return rate and greater amount of technical support. Maybe it's zero, but certainly back in the day it used to be quite considerable because returns were high and Linux users tended to pose a lot of relatively time consuming questions.

IIRC game developers found the same thing when they released Linux versions, which is why many of them only unofficially support play under WINE and derivatives.

That's how many professional unions work in Europe too. They are there to provide support in employment disputes and lobbying for legal changes, not to negotiate blanket salaries.

A better question is what de-orbiting thousands of satellites a year is going to do to the atmosphere. We don't really know, but it's probably nothing good.

That is indeed the problem. Unicode took the problems with ASCII and made them worse in many ways. It's become a very difficult problem to fix.

I think the new encoding would have to have a robust set of conversion tools, but that might be the best way to get it adopted. If it could solve developer's issues with Unicode it might gain popularity.

For case insensitive comparisons specifically I would suggest creating a character coding system where a certain number of bits are allocated to that specifically. Say the top 4 bits, so you can have a maximum of 16 characters that are all comparable when case is not considered. You would probably standardize on a 32 bit per character encoding, because the whole UC8/16 mess just leads to issues and these days we can afford to spend 4x as many bits as we did in the 1960s.

Then comparing characters is as simple and fast as masking off those bits, and deal with some related issues in non-Latin languages. It would be fully backward and forward compatible, so no need to care about the version of the encoding in use.

Yeah, and that's why we need an official support library that handles that kind of thing and tells you when it doesn't make sense.

Well that's why I mentioned that Unicode is deficient because it lacks any concept of languages, only characters.

The use case is that most files are stored on case insensitive filesystems, at least on personal computers, because of NTFS and FAT.

Moderators had email addresses leaked in the hack. Many of them contained their real names.

Most people seem to agree that to make a living from YouTube you need other revenue streams, like affiliate links and merchandise. That's one of the reasons why the Honey browser extension caused so much harm - it stole affiliate link revenue on a massive scale.

I don't think it was ever about the real danger posed. You could take up to 1 litre of liquid on board, it just had to be in 10 x 100ml bottles.

I don't think you could make a very effective bomb out of an iPad. There isn't much room in there for the explosive, and the shape doesn't lend itself to directing the blast to cause maximum damage. It has to get through the x-ray machine as well.

Ideally Unicode would come with a nice library that handles all that stuff for you. Unfortunately Unicode is kinda broken so it's not nearly as easy to do as it should be, but it's not impossible.

I'd implement it as language metadata, which is where the current implementation of Unicode is lacking because it is focused entirely on characters, and wrongly merged some of them too. Anyway, language metadata, which is then used to generate libraries for different languages and operating systems, so for the developer it's largely transparent. Make it so that developers don't need to understand languages, but can still write code that works for all of them.

Part of it is because Unicode is broken and doesn't provide adequate support to developers. Part of it is because major operating systems like Windows are case insensitive and developers are really looking for how best to support NTFS and FAT, not how to avoid security issues on Linux.

Replacing Unicode would do a lot to help with this. Most of the rest is down to less than ideal operating system design.

I've heard that too, the Bose are very comfortable, as are the Sony's. It's just the portability question, when travelling the earbuds are obviously going to be smaller and lighter, but also easier to lose. Maybe instead of getting one pair for everything the solution is to just get one dedicated to home use but without the noise cancelling, and one set of travel headphones.

One thing I really miss are good on-ear cans. They are comfortable and don't get so hot in the summer, but they seem to have gone out of fashion. I'm still using 25 year old Sennheiser wired ones, but you can't get parts for them so I've been DIYing the foam pads.