Alas.

That soft hyphen would have been a blessing for the German e-books. Some texts are flush with the overly long words, making them very hard to read.

But Kindle (last time I checked) doesn't support it.

Neither the Calibre and few other e-book viewers/editors I have tried in the past.

In other words, in my experience the support is uniform and consistent: no support whatsoever, sadly.

P.S. On top of it, the Kindle devices I have, also have the rendering and text selection bugs when displaying/selecting the text around words (even if they are hyphenated) which are longer than the single visible line.

After watching the Japanese "Fafner" TV animation, I was quite intrigued by the whole "assimilation" idea. Tried to watch the Star Trek version of it - and was largely disappointed.

The "Q" are one hell of a plothole - but still pretty much the only "true" aliens in the Start Trek.

That's just another way of saying "more of the same".

I can understand why the entertainment industry is so obsessed with the canons: to not dilute value of the original.

But I still can't grasp the why the fans are so obsessed with the "more of the same"?

P.S. I like how Japanese animes often parody and make fun of themselves. I like how they sometimes shuffle the roles and characters. Occasionally the shenanigans are way too transparent and shallow - but sometimes very brilliant and deeps ideas come out of it.

Still.

Dismantling the centralized institutions one by one - DNS, IANA/RIRs, hosting providers - whatever Maelstrom is capable of - is a step in the right direction.

If sufficient number of decentralized alternatives appears, one can try to nest them like a russian dolls. More layers of the nested services - higher the privacy (at the potential cost of reliability).

That coming on the heels of the decentralized web solution coming from BitTorrent, Inc.

Pretty exciting times.

Any evidence to back up the claim?

When 10+ years ago I was moving from Linux to Windows, the case-sensitve file system was one of the major risk factors.

But even in the beginnng, I have encountered precisely zero problems with it. And I'm the type who works mostly on the terminal and should be directly impacted by the case-sensitive file names.

The thing is, these days, nobody types the filenames manually: it is either click in GUI with the mouse or filename completion on the command line. And even if the filenames needs to be typed manually, literally everybody universally uses the lower case. (That even on Windows. And I have helped in past correct the case handling in several Windows applications so that they create files with consistent upper/lower case names. Because users were complaining that it is inconvenient and kind of fugly that sometimes output filenames are upper case, sometimes lower case.)

As such, I consider case-insensitive file names to be a redundant feature.

I have an Asus ZenWatch. Below should be able to be done on any Android Wear device. In no particular order I use it for the following:

Check New Email
Check SMS
Check Caller ID
Check Weather
Check Calendar and Agenda
Check Google Now Cards (includes traffic card for my route home)
Check Other phone notifications
Dictate Notes
Check steps walked
Check Heart rate
Set Reminders
and Check the Time

Some Android Watches have a speaker in addition to the microphone so you answer and talk through your watch for phone calls. My watch can store music on the watch itself and play back through a paired BT headphones without my phone present. One could play games, but I do not see any point.
I am down to about 40% by Midnight most days. I do not see much issue with recharging it every day as I take it off every night and sticking in the charging cradle just means it is easy to find in the morning.

Android wear becomes really useful over other options if you enable Google Now. The latest generation of Android Wear watches actually look like a watch (Moto360, LG G Watch R, Asus ZenWatch). If those things do not matter, then get a Pebble or one of the high end Fitbits like a Charge or Surge, or a Nevo Watch ( http://igg.me/at/nevo/x/813785... ). The Nevo is a real watch, with basically a Fitbit Flex built in, and add in colored led notification lights. You will not be able to read an SMS or email on your Nevo, but you can tell the difference when your watch vibrates from a new notification.

It has nothing to do with wealth.

A quiet, kid-friendly neighbourhood street becomes literally a meat grinder.

I have lived twice near such streets. Once - juat as the street was transitioning from the "quiet, kid-friendly" to "meat grinder". Two kids were killed by speeding cars. Road bumps had only limited (and largely negative) effect: an idiot crashes his car on the road bump, traffic jam forms on both sides of the street and the whole city quarter is effectively blocked: no car can get in or get out.

The final solution community found was to cut the one "through" street in the middle, making out of it two dead-end streets.

And the poor customers gets duped into buying a counterfeit pods without even realizing it!

That must be stopped!

Think of the customers!!

There is a reason why JPEG is blocky. The blocky nature of the encoding preserves details better.

BPG blurs everything heavily. Small details and fine textures literally disappear.(*)

JPEG is definitely outdated and web could gain from a worthy replacement. But BPG IMO doesn't appear to be "it".

(*) I wonder how JPEG would fare on the images, decoded from BPG. Since fine details are removed by BPG, the JPEG would be smaller too.

Most of the web might be dynamic.

But most of the interesting content is quite static, changing relatively slowly. Consider Wikipedia or YouTube. Wikipedia updates relatively slowly. YouTube only adds new videos (and after Google's touches the comments and the recommendations are pretty useless anyway).

Search and the comments might need to stay dynamic - and centralized - but hosting costs would drop significantly if the bulk data transfers would be handled by the P2P network.

I have found a very good job near where I live and I have simply "canceled" their hiring "process" in the middle. Imagine: dozens phone calls to organize dozens of "interviews", scattered around the world. I have stopped around 5th or 6th "interview", which was around 9-12 month into the "process". In other words, I wasn't hired by Google on technicality that I got bored waiting (and found good job ~20min walking distance from home!)

All in all, I was pretty surprised to find that the hiring process in Google is so badly organized and is so poor in communication. Just like any other other employer, they let you wait and dangle, but the difference that they need 4-12 times more interviews and 4-12 times more waiting and dangling for weeks and months.

That whole thing doesn't make sense, unless your goal specifically is the magic "Google" badge on your CV.

Google engineers are just bunch of narcissistic douchebags. (Hey, I went through their hiring process - I know the types who would fit perfectly!)

GMail was one of the first indicators.

They fail to understand the purpose of e-mail, and as such we would never ever get the most basic and oldest of the e-mail client functions: folders.

But they would go on "reinventing" e-mail forever, with colors, tabs, bars, circles, ovals, shapes, and probably in far future odors. Because sitting down and making a finished product takes a commitment. But the only thing Google has ever apparently committed itself to.... Squirrel!