Unlike systemd developers, I listen to users.

That is much of what is wrong with systemd. It only takes a few moments to understand how sysvinit works.

Yes, to a degree. It absolutely is. Remember, a single program should do one thing, and do it well, and either pipes or scripting should be used to get to the next step. It doesn't matter whether you log in through a getty or through a ssh daemon or through a telnet daemon launched from inetd, you're still going to go through /bin/login. So yes, that is the Unix way, which you willfully do not understand for the purposes of supporting systemd.

Again, you do have to exercise some care when buying a device. Look it up on XDA-Developers before buying, and never buy a device which hasn't already been subjected to some scrutiny. You don't just get a free pass, you have responsibilities.

What you're not explaining is that the people who are making all the money are able to dodge the taxes.

The SVU episode

I had been a long-time fan of Law & Order in general, following SVU more-or-less (I preferred the original, mainly due to the characters of Jack McCoy and Lennie Briscoe). I knew that they were not exact on police procedure, and would often spin current events with extra drama to create episode plots, but I thought that was horrible. They portrayed the "Gamergate" side utterly unrealistically: as foul as some claiming to be part of the movement have been, including threats of kidnapping and rape, I have zero expectation that any would rise to the actual actions. There was no mention of journalistic ethics in the episode. Then, they end the episode with the moral "If you actually go out and beat women up, you can get them to quit even if you are found guilty/killed on a rooftop while apparently under some psychological delusion."

It was bad writing, bad characters, bad memes/references ("redchan", some completely made up terms), and bad outcomes. The whole thing was character assassination no matter which side you are on, if any, and made me stop watching SVU. (Not a hard decision, as it's mainly become the Olivia Benson Show; while I like Mariska Hargitay, they are relying on her character to carry the series at this point. If I find myself hoping that Ice T's character would get more development/screentime, something has gone wrong...)

What are these multiple providers of which you speak?

Where I live we have the choice of Time-Warner cable or no cable, and there's no sign of that changing in my lifetime.

Not to be confused with the Five Eyes principle, which means that the government's just going to read it anyway.

We have qualifications to run for Congress now?

Bellini plans to use a lightweight, indestructible floating capsules, or "personal safety systems" made from aircraft-grade aluminum in what's called a continuous monocoque structure

So a giant ball... made out of a monocoque? Unless I'm mistaken, the emphasis should be on the monoball, since monocoques are the most common variant, while monoballs are somewhat of an exception.

And sometimes you have bivalves or whatnot, and a monocoque just isn't sufficient. Sometimes what's required is a bicoque. I think the engineers might be relying on false information if they believe the motion of the ocean is going to compensate.

So if you need a framework so you can pretend to have a native version of the application

No, you need a framework so you don't need to reinvent the wheel for every project you work on. With Sencha's frameworks, I can write a pretty slick-looking responsive site in a few hours (or days, for something larger) that would take literally months to roll on my own (and for the record, yes, I can and have rolled my own, back in the dark ages).


why not just focus on having a webpage instead of a shitty application which is just a web page?

Two reasons. First, it increasingly doesn't make sense to force your end users to download and install potentially untrusted code - never mind needing to maintain separate versions for every major platform you target (oh, you want this on iOS and Android and Windows and Linux and OS X, etc?), when you can accomplish the same result in one nice tidy webapp. Second (and you can fairly call this a matter of personal preference), IMO just about everything looks like crap in a browser on a phone, and even that assumes the browser handles it correctly (yeah, like I want to support Chrome and FireFox and *shudder* MSIE and Dolphin and Safari and Opera, etc - Going right back to all the joys of supporting multiple OSs, woo hoo!).

The concept of a "webpage" hasn't limited itself to some statically published version of a document-with-markup in over 20 years; that model lost so thoroughly that pining for it doesn't even count as beating a dead horse anymore, more like trying to clone a mammoth from frozen DNA.


This sounds like lazy people who want to claim they have an app, when all they're doing is pointing to a web page.

It really doesn't matter to me what you want to call it, whether an app or a webpage or a widget or a three-handled family gredunza, if it accomplishes the intended goal... All just a matter of using the right tool in your box for each task - Sure, you can hammer in a screw, but sometimes a plain ol' nail will do the job just as well.

Sounds like a job for.. Bookmrkr! Do you love bookmarking? What to broadcast your bookmarks to your social network? Check out Bookmrkr!!

If only it were that easy. The problems with cross-platform development are myriad. The LCD experience has already been outlined, so here are the others:

1) It's write once, TEST everywhere, and you can't debug the code you actually wrote -- only the specific translation of that code into native code. And that sucks beyond words. It can be incredibly time consuming to the point where it easily erases any time you saved in development. And the longer the lifecycle, the more of your budget this is going to consume.

2) On a related note, profiling and performance tuning is a bear. If you do anything that requires performance, cross-platform is the wrong way to do it.

3) The potential for bugs is twice as high, because now you don't just have to worry about bugs in the native SDK, but also in the abstraction as well. While the OEM can generally afford to test the hell out of their SDKs, cross-platform suites have much less resources at their disposal. And it shows.

4) You are always playing catchup. New features take longer to implement, because you have to wait for the third party to either implement the new feature, or to implement it right.

5) You're needlessly adding another layer of dependence. None of the "popular" third party platforms are anywhere close to guaranteed that they'll be around in a month, or 6 months, let alone 2 years from now. If your favorite library goes away, you find a new one and make a few changes. If your entire SDK goes away, you're fscked.

If your software doesn't matter at all, if it's just a hobby, has no business case, and you have no plans (or potential) for going commercial, then by all means, use whatever development tool strikes your fancy. Personally, I would never recommend that anyone use cross-platform tools for anything they plan to support indefinitely. Even for a prototype or an MVP -- too often the prototype becomes the codebase for the final software, despite prior assurances to the contrary. Don't waste effort developing something you can't build on, unless you have no other choice.

It has RDA of calories, and if you're drinking soda, then 100% of the calories are from sugar (or corn syrup, for most soda in the US). There is no RDA for sugar specifically because there are no scientific guidelines, not because the FDA is part of some grand conspiracy to keep it a secret.

What? Most artists never make anything on record sales, they get their money from tours, doing commercials...

There's a handful of them on the left coast, and they're putting in another handful on the right coast. Statistically nobody in the middle of the country buys interesting vehicles anyway. Toyota is about to start selling a FCV finally, and they're licensing their fuel cell to BMW and it will probably make it into an i5 in a year or two.

The real problem with hydrogen is that it is horribly annoying at best. It's just dumb on every level.