Sometimes it's hilarious listening to those demanding changes in Federal, national standards in the US, who've clearly never travelled outside the coasts and/or packed, urban dorm living...

Being able to stream 18 videos at once is nice. But you got along perfectly well beforehand. Broadband is about reliable, reasonable hardline (except for certain buildout locations where LTE is being petitioned as a replacement) information communication... It's NOT intended as the tail wagging the dog on Millennial cord-cutting.

This... seriously. I'm reminded of the giant Dev vs Ops split within the technology sector right now. On one side you have grizzled SysAdmins who've BT,DT and deal with operational engineering, and on the other are Developers primarily focused on making something work well "in theory", on their laptop.

"Oh My Science!"

If you're doing calculations on time using intervals, and one second matters to you, you should be using a raw number instead of calculating the "23:59:59" yourself. If the UTC conversion is too much, use TAI instead and be done with it:

From http://en.wikipedia.org/wiki/International_Atomic_Time:

International Atomic Time (TAI, from the French name Temps atomique international[1]) is a high-precision atomic coordinate time standard based on the notional passage of proper time on Earth's geoid.[2] It is the basis for Coordinated Universal Time (UTC), which is used for civil timekeeping all over the Earth's surface, and for Terrestrial Time, which is used for astronomical calculations.

I'm still quite happy with my Sony Dash as an alarm clock every morning. It's is only 5 years old, but that's relatively ancient in internet time.

I wish I had mod points... I'd mod you up.

You're supposing that "Sony" is a single massive thing -- it's not. It's a conglomerate with many separate units that share relatively little other than a name and some discounts at the Sony Store.

Proof: The hackers have done nothing outside of Sony Pictures. If there'd been interoperability in the layer that they got into, we'd be seeing data from other "Sony"s out there as well.

SOE/SMSS/SNEI learned a lot after what happened in 2011. But a movie studio that deals mainly with corporate accounting to pay actors and production companies, and the occasional internal creative discussion, has a far different calculus to make on what to secure how than an Online Game company, or the one handling end-user billing (read: PCI) data for a storefront (PSN).

You're going to see a giant top down review come out of this, of course, but implementation will probably still be handled by individual corporate units to some extent.

Sony wasn't attacked because they were vulnerable or had particularly lax security, they were attacked for political reasons by a foreign power. I guarantee you that if Viacom has been producing The Interview they would have had a similar attack against them and would probably have fared little better.

One can imagine all sorts of objections to this ("I take too long", "I like staring at onions, but I don't like eating them", etc...), however a self-reported 98% success rate -- or at least, 98% of the time they end up with a pizza with their preferred ingredients and/or that they end up really liking -- would explain why Pizza Hut decided to roll ahead with this -- seemingly weirdly ahead of its time -- tech right away.

98% approval suggests that browsing an appetite are more firmly linked. If the numbers hold up outside of the focus groups and small study areas, I'd expect this technology to spread far and wide. Carls Jr. (a/k/a Hardee's) and Jack in the Box already use the kiosks in several locations here in San Diego; a camera and tracker wouldn't be that much of a step and could provide a quite different experience.

Eventually, we just keep rediscovering old concepts. Store-and-forward is basically Zone Mail Hour, and the first time I read about the Deep Space network concepts, all I could think of was interplanetary FidoNet, or WWIVnet.

This is one of the keys, and why the Lennart-hate is slightly more justified than the usual OSS spats.

Actively pushing to deprecate and then FORCE TO BE REMOVED initscripts from the Fedora RPMs was a way, similar to the integration of udev and GNOME, of forcing adoption and making migration back to other init systems difficult. This is classic embrace-and-extend, anti-competitive behavior except instead of Microsoft leveraging its weight, it's a developer making a power play.

As for how and why Fedora agreed to this... Well, there are a couple of different things at play. To some extent, it's felt like for a few years now the developers in the community have been pushing things and the sysadmins in the community have been busy doing their jobs or otherwise not paying attention. Suddenly Fedora is all about people running on their laptops and their little docker VMs with very little thought to the poor schlub who's dealing with a half-broken system at 3am in the morning. I can't say I blame Fedora specifically -- communities go awry all sorts of ways -- but I do wish RedHat had and has been taking administrator feedback into account with RHEL7.

Suffice to say, there's a lot of concern out there.

Please, please, PLEASE can the folks who are setting this up call it "Skynet"? Thanks.

Here, let me Google that for you

Also, from 2008 Davos:

Just how crazy is Al Gore? That was the question that popped, once again, into my brain as I read a January 24 Agence France Press news story out of the Davos meeting of business and political elite. Gore asserted that, “the North Pole ice caps may disappear entirely during summer months within five years”

I was instantly reminded of the story that ran in The New York Times in August 2000 claiming that the Pole was free of ice for the first time in 50 million years. It wasn’t, of course, because people who have actually been to the Arctic quickly noted that, in the summer, some ice actually does melt there. The Times retracted it three weeks later.

This kind of apocalyptic nonsense has been ratcheting upward ever since the new century began and my theory is that lunatics like Al Gore know that they are running out of time when it comes to imposing draconian restrictions on the use of every form of energy known to mankind. This is the purpose of the global warming hoax.

Given that developers are the new kingmakers, Red Hat needs to get out in front of the developer freight train if it wants to remain relevant for the next 20 years, much less the next two.

It's very hard to avoid a snarky response, but I'll try.

* Developers are not kingmakers
* Developers are not system administrators
* Developers don't understand operations
* Developers often don't understand scale engineering unless they can abstract it away by not thinking too hard about anything
* Red Hat Enterprise Linux (and its derivatives) are not intended to be shiny new, but to be reliable
* Use Fedora if you want bleeding edge, or re-package things yourself. RPMs aren't hard.

This. Actually, in RHEL/CentOS, you can simply run /etc/rc every minute via cron and it'll sync what's running with what's supposed to be, assuming things have been /sbin/service stopped. (And if they haven't been cleanly stopped, you need a specialized tool that understands how to *TEST* the service rather than rely on subsys.)

You can see this in Development vs Operations, Bay Area Startup Hipster Programmers vs System Administrators Who Have To Carry The Pager, Big Data vs Simpler Analysis, and a lot of other places in the industry right now....

There's an influx of talent that doesn't seem to understand the fundamentals of system architecture, or assumes they have all the answers and can/should hard-code them into the design, preventing "the Unix Philosophy" from being applied by the operator who's trying to deal with the crisis at 3 in the morning. "whatcouldpossiblygowrong", ergo I shall design this in C, and if you need more flexibility than I'm offering then You're Doing It Wrong.

What they don't understand is that they don't have all the answers... Nobody does. The only solution is to leave as much flexibility available as far down the stack as possible to allow the folks who have to deal with this (eg, system administrators) the ability to do their jobs. Replacing shell scripts with C code and the unix toolkit with monolithic binary blobs does not help the situation.

systemd does a few things right (cgroup management, for one), and promotes the state of the art in a few areas that probably only could be dealt with at the PID1 level... Also, as the original article admits, there's nothing inherently wrong with working to speed up boot times across the board. All of these things are irrelevant and outweighed by enforcing declarative styles on system configuration, and the sheer philosophical hazard of taking all these disparate functions and putting them into a program.

It makes absolute sense for Android, and perhaps an embedded system that just needs systemd and busybox. For a regular Linux userland, it takes us in the wrong direction.