There's really only one thing to eat while reading a story like this (other than Moar Chocolate, for Research Purposes.) It's Scalzi's Schadenfreude Pie. Dark, bitter, sticky, chocolately.

Audio detection isn't nearly as broken as the article pretends. Sure if all you have is a single mic, then you have no hope. OTOH, with multiple mics, you can *localize* sounds, which means you don't need to recognize the sounds of a drone, just realize that there's some noise coming from something in the air where there shouldn't be anything. With a microphone array, you can actually pinpoint sound sources much weaker than ambient noise. It's certainly not trivial, but within the realm of what's realistic (assuming there aren't simpler solutions).

Holy fucking shit, who cares? If this was done by LETTER WIDTH, we wouldn't see the problem-

EXACTLY! That is why you do not want "N characters". I don't understand what your problem is here.

It is true that for this example most programmers would scan from the start, finding the longest string that fits with an ellipsis at the end.

What I was trying to point out is that if you want to be clever, you can guess as to an insertion point. But 11 bytes is just as good of a guess as 11 "characters" and since 11 characters requires scanning you are not saving any time.

You are perfectly correct that after you stick the ellipsis in there you need to test to see if the rendering fits and perhaps try another guess. The idea is that you will do fewer measurements, but that such insertion can be done using byte offsets, and "N characters" is a useless concept that never enters into it.

Yes

At least it's no longer flying in restricted airspace... :)

Meddia is not the same thing as software, so your examples really don't apply in this case. Better examples are:

ASHTON-TATE CORP. v. FOX SOFTWARE, INC. -- NO. CV 88-6837 TJH (TX).

Lotus Development Corp. v. Paperback Software International. U.S. District Court, District of Massachusetts. June 28, 1990. 740 F.Supp. 37, 15 USPQ2d 1577

The interpretation that the federal government is holding forth here is that both of these cases were adjudicated incorrectly.

If the Supreme Court fails to hear the current case, both of those previous cases are defacto overturned.

You can effectively say "goodbye" to the software industry, if companies are allowed to enforce interface copyrights. At least in the U.S.. Obviously, other countries will just ignore the U.S.'s idiocy, and continue on their merry way, and quickly surpass the U.S. in software development, just as they have in other economic areas.

Easy detection method #48:

(1) Send out a large electromagnetic pulse

(2) If it falls out of the sky, it was a drone

Well, thank you very much, telling me that I'd get better battery life if I installed the new Android version. As far as I can tell (at least with all previous Android versions), Google's instructions for installing the new software are "What? You don't have one of these three Google-brand phones? Then wait for your carrier!".

That's bad enough for my phone (which has a carrier, and Samsung's a reasonably major brand, though my previous HTC phone never got upgraded), but my tablet's Wifi-only, so there's no carrier, just a manufacturer who sold that model 2 years ago and doesn't have that tablet easily located on their website, and as far as I can tell, if I were to dump IceCreamSandwich for Cyanogen (who at least tell you what hardware resources you need for each version), I'd lose access to the Google Play Store?

Do you really think 12 happy faces fit in the same space as 12 letter 'i'?

This is why it is pointless to do such counting.

And what you propose would split betwen a letter and a combining accent, so it really isn't any better for trashing strings.

Basically as soon as the words "N characters" come out of your mouth you are wrong. All your description just does that for many paragraphs. Don't feel too bad however as there are many many other people, including ones working for Apple, who are wrong as well.

PS: the surrogate order does not depend on they byte order in UTF-16. You might want to check what you are doing if you thought that.

A lot of misinformed programmers use the term "Unicode" to mean encodings other than UTF-8, typically UTF-16 or UCS-2. For instance a function called "toUnicode" often is a translator from UTF-8 to UTF-16. Therefore when people say "Unicode strings" they almost always mean non-byte strings. I propose the best solution is to eliminate all such strings. It is true that byte strings would encode UTF-8 and thus be "Unicode" but the hope is that this would be so standard that there would be no need to ever specify this and they would be called "strings".

This.

It's pretty obvious that this is a punishment for adding encryption to Android devices, and for going to SSL for all web transactions, making it much more difficult to spy, despite administrative objections.

The recommendation is clearly punitive because Google has pissed the executive off, and consistently opted on the side of data protection, and has disclosed many of the recently discovered OpenSSL and SSSL protocol flaws which made eavesdropping easier.

If you're the sort of person who believes any and all business is merely a way to make profit and nobody who creates a company ever actually cares about the task they perform, then sure. Reality is more complex than that.

Re: China. iOS is in the minority in China. Even at the time of the iPhone 6 launch iOS market share was only 20%, but iOS market share always spikes around the time of a new iPhone launch, then falls back down in the other quarters. And China is a special case - Google isn't willing to play ball with the communist government so the services that make Android most useful are all blocked there. Apple cooperates so they can sell iOS as is, getting a built-in advantage. Despite this, Android still dominates.

I don't think there are any useful algorithms that need random access, except for searches that do not require the index to be "exact". Therefore you certainly do not need a reliable string[i]. You can make it return a pointer to byte i, which will work for most uses (ie searches for ASCII and replacing one ASCII byte with another).

Some complex searches do want to jump arbitrary amounts ahead, but do not require any "exact" location. Instead they want "a character near the middle" and so forth. In this case it might be useful to produce an iterator that points near byte i. A simple UTF-32 one would jump to byte i and then back up to the last non-continuation byte, unless there are 3 or more in which case it would stay where it first went (as that is the start of an error). Ones that return normalization forms would be much more complex. Something like this:

      utf16_iterator i(string, string.length()/2); // i now points near middle of string

Yes, we have UTF-8. You do know that it can hold non-English, right?

No you are wrong. What I propose does not fail any worse than what I think you are proposing, which is "search N Unicode code units forward and put the ellipsis there".

My scheme will not add an error. Either it will find the start of a character, or if there is enough trailing continuation bytes it will know that the string ends with an error and add the ellipsis after that (thus not adding an error and not removing it). As other posters here point out there is absolutely no need to count Unicode code points as it has nothing to do with how many "characters" there are.

A better scheme would be to actually measure the rendered string to see if it fits, and then do a weighted binary search for the correct location to place an ellipsis to get the longest string containing an ellipsis that fits. This still assumes that shorter strings render in a shorter area, which is still not true, but true enough that I think this may work.