Please create an account to participate in the Slashdot moderation system


Forgot your password?

Comment: Re:Why hyphenation in an e-text? (Score 2) 224

by ThePhilips (#48653111) Attached to: Amazon "Suppresses" Book With Too Many Hyphens

There is a unicode character known as a soft hyphen. The soft hyphen indicates where to break a word if it doesn't all fit on a line. This character should be used instead of a hard hyphen most of the time.

Too bad eBook readers are very inconsistent in their support for that. Some readers display an icon indicating an unknown glyph, many fail to insert the hyphen....


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.

Comment: Re:Never could get into Star Trek (Score 1) 105

by ThePhilips (#48644439) Attached to: Behind the Scenes With the Star Trek Fan Reboot

3. Badly done aliens, with a lame explanation.

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.

Comment: More of the same (Score 1) 105

by ThePhilips (#48644425) Attached to: Behind the Scenes With the Star Trek Fan Reboot

intent on keeping true to the spirit of Gene Roddenberry's television show.

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.

Comment: Re:BitTorrent Maelstrom (Score 1) 86

by ThePhilips (#48641069) Attached to: Tor Network May Be Attacked, Says Project Leader


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).

Comment: Re:Case insensitive file systems were a bug (Score 1) 147

by ThePhilips (#48632135) Attached to: Critical Git Security Vulnerability Announced

I dont know if its a bug, it makes navigation more simpler.

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.

Comment: Re:Waaaaa.... Whaaaaaaaa. (Score 1) 596

by ThePhilips (#48607735) Attached to: Waze Causing Anger Among LA Residents

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.

Comment: Too much smoothing (Score 3, Interesting) 377

by ThePhilips (#48572995) Attached to: Bellard Creates New Image Format To Replace JPEG

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.

Comment: Re:dynamic sites ? (Score 1) 67

by ThePhilips (#48571515) Attached to: BitTorrent Launches Project Maelstrom, the First Torrent-Based Browser

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.

Comment: Re:Google engineers... (Score 2) 239

by ThePhilips (#48521597) Attached to: Google Hopes To One Day Replace Gmail With Inbox

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.

Comment: Google engineers... (Score -1, Flamebait) 239

by ThePhilips (#48519743) Attached to: Google Hopes To One Day Replace Gmail With Inbox

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!

Comment: Re:All right, allow me to expose my ignorance (Score 1) 647

by ThePhilips (#48490149) Attached to: Debian Forked Over Systemd

"monolithic in architecture" - that means its a single binary with no dependencies [...]

No. Single binary with no dependencies means monolithic design.

For example Linux kernel : single binary with no external dependencies, but internally its architecture is still modular. And the implementation of modules in Linux is still largely "monolithic", since kernel are just pieces of the live kernel, not compatible between different kernel version, which reside on hard drive, not in memory. And when they are loaded into the memory they pretend to be an integral part of the kernel.

[...] which is wrong otherwise every single binary with depending on a library is a monolith. this smart-ass mis-definition of "monolith" is one used by detractors of any system they don't like.

You seem to fail to grasp the difference between design and architecture. Your CS education has failed you. Pick a copy of Booch's OOAD and read it up.

Comment: Re:All right, allow me to expose my ignorance (Score 1) 647

by ThePhilips (#48483953) Attached to: Debian Forked Over Systemd

Or I forgot to add "beardy" to "*NIX guys"? Who knows.

What people do not understand, do not grasp yet, is that SystemD brings Linux closer to the *BSD. Pretty soon, SystemD would start dictating kernel version and kernel configuration, turning the whole Linux ecosystem upside down, and making it just like the BSD: a system which contains not only the kernel, but also the whole shebang of userspace tools and libraries.

But it does it the Windows way, instead of the traditional *NIX/BSD way, and that is what provokes most of the protests.

Slashdot crowd is special and doesn't see that modern "Linux admin" is not much different from "Windows admin". RHEL and SLES already lock down the system (both with semi-proprietary software and support contracts) to the point where admin can only press the button to accomplish something. If there is no button - then it is impossible. In other words: just like the Windows. (In part, of course, because these days Windows too, similarly to Linux, allows some level of automation from command line or (Visual Basic or PowerShell) scripts.)

"Hey Ivan, check your six." -- Sidewinder missile jacket patch, showing a Sidewinder driving up the tail of a Russian Su-27