Wow, that was unbelievably irresponsible of Ars Technica. I think you're correct in your assessment. It is pretty much all of us.

Even laying aside the FAA, I believe that it wouldn't be too hard to get widespread public support for pretty strict regulations of these devices. And I wouldn't be too opposed to some regulations either.

As an RC airplane enthusiast, who likes to dabble in FPV and UAVs, I must say that I'm not surprised. However my feelings are a mix of outrage at the FAA as well as understanding. When a few irresponsible people use their toys in ways that are, well irresponsible, I'm not at all surprised to see the FAA come down hard on everyone. I think in many ways this is a tragedy of the commons. A few idiots have actually ruined it for everyone. When a toy has the power to kill people, or to hurt them, and people do stupid things with them, then it ceases to be a toy. We are now seeing stories in the news almost weekly of stupid people flying their toys in reckless and dangerous ways.

That said, I don't see how the FAA's rules are enforceable, nor do I see how the FAA can actually claim to have the authority to make rules in an an area that, as far as I can tell, congress has never granted them the power to do.

If FAA truly has the power to regulate a hobby, then they need to have a framework in place to allow this activity to continue safely. It's happening everywhere in the world. Banning it in the US will only put companies behind the curve who want to develop and use the technology.

Yes I agree. I'm also happy that NASA is making progress on this. I think it's a worthwhile endeavor, even if it is tied to earmarks and corporate welfare, much moreso than SpaceX's lucrative NASA contracts.

I also am excited at what SpaceX is doing. They are certainly the farthest along, and most likely to succeed in the near term. Who knows. Maybe in the future if SpaceX is the only American company visiting the space station and hauling astronauts, they could just take over space station operations and open it up to civilian scientists. That'd be cool. If dangerous and impractical.

For me what matters is rest, period. IE sleep. At any time during the flight in any direction, and as much of it as I can get. Traveling is very tiring anyway. If I get exhausted, say by staying awake coming west as you suggest, I just start feeling crappy and my sleep schedule will take far longer to adjust. Instead I just take a benadryl and sleep while I can. That means I wear a mask and earplugs and try to get 6 hours sleep or so coming west in the daylight. I'll be tired regardless, but less tired this way. That night (in whatever timezone I'm in), I try to sleep as close to my normal bedtime as possible, but earlier is okay. I'll take another benadryl if necessary. But then if I wake up in the night, it's important to not get up and do things. I just lay in bed, and I will fall asleep again. I'll soon be on a fairly normal schedule. The only lingering aspect of jet lag for me is that I do tire more earlier in the day, often going to bed by 8 or 9. But mornings and afternoons don't feel much different for me. That lasts about 5 days or so. If I can work things out so that my first night in country I can sleep for 10 hours or so, I have zero jet lag. One time I managed to stay awake until 7:30 pm, then crashed and slept until 9 am the next morning (did wake up at 3, but didn't get up). Felt wonderful and my schedule was fully adjusted.

Flying lie-flat business class also helps greatly!

I think the problem is that the nature of most of our jobs and work environments are repetitive, non-physical, dull, uninspiring, and often lacking in meaningful interpersonal communication. You can only take so many hours of that sort of stuff without burning out. In that context I understand and agree with the supposition that our productivity is hurting because of these long hours.

On the other hand, sometimes working long hours isn't that bad of a thing, but it depends on the context. Currently I'm working in a family partnership doing agribusiness (IE farming). Depending on the day I may be working from 8 to 14 hours a day. But since it's a lifestyle as well as a job, and family lives here on farm, it's not quite as soul-sucking as working 14 hours behind a computer screen, though sometimes I do spend hours doing things on the computer doing things like server maintenance, or the odd bit of software development, which is rather tiring after a few straight hours (maybe it's being behind a screen shining in one's eyes that makes jobs so fatiguing). Each day differs pretty significantly. Yesterday I put in some hours after supper and came in at 9:30 pm. Today I was done by 5. Those seasons that demand long hours do get old in a hurry, but they don't last forever, and there are other compensations. Also I take one full day a week off (Sunday). Most farmers really enjoy the lifestyle, and their families too, as well as many farm workers, despite sometimes putting in long hours, and they do find balance and it works out. At least for some people.

So it's not just a simple hours put in issue, but more of an inability to balance personal and family needs against an employer's demands, and the type of work these long hours consist of.

And hopefully in any lectures on Moore's Law, the students learn that Moore's Law refers to transistors on a die, not the speed of the chips. This 36-core chip probably jumps ahead of Moore's Law a bit, as it's got to be a fairly large die. In any event Moore's Law continues to hold, more or less. Other things like CPU speed have followed a similar trend in times past, but no longer do now.

Replace Windows with ReactOS? That's funny. Putin might have taken a passing interest in ReactOS for obvious reasons, but I'm highly dubious that anyone has replaced Windows with ReactOS for any reason, especially in the military. From what I can see ReactOS development crawls along at about the same rate it always has, with no sign that Russian money has caused any dramatic leaps in stability or usability.

It's like there's some strange black hole of information available on the internet that only happens around the super specific topic the Ask Slashdotter is interested in. I'm pretty sure all of these folks are the ones that were our best horses in Keener Bingo:

http://www.mathnews.uwaterloo....

Ding ding. Fuck, C# is fine and dandy and pretty fucking fast, if your target platforms and related asset and tool ecosystems are cool with it, and you're not boneheaded about what you're doing. Questions like these are so silly - if you do so much homework to know what you know and what you don't know, I'm pretty sure you're smart enough to find the right information, books, etc. What a passive aggressive inquiry. If you're convinced you can write an intelligently framed question with tons of context, then why on earth can you not do a little google mining for books that focus on C# game development? This discipline is hardly a secretive cabal.

After popping a bunch of benadryl and being satisfied that my condition wasn't worsening, I elected to make a regular appointment with my GP instead of going to Emergency.

I decided to take a few photos of the skin rash before it went away, which allowed the doctor (three days later, when I was totally fine again) to quickly identify that it was indeed an allergic reaction, and based on where it appeared, the subsequent interview helped diagnose the cause. Worked great!

How will visiting sourceforge help me see summaries of new software releases? Guess I'm confused. I always thought freshmeat.net (renaming and moving it to freecode.com was stupid IMO) was just a listing site, and that's what I've used it for the last 14 years. And it's still been useful at that. Takes money to pay the bills, but it seems to me that this is another example of Dice thinking they can takes something that's popular and monetize it without bothering to find out why it's popular, and what value it gave to the community.

Have you ever written an init script? As an admin you should have written one or two in your day. You'll know how fragile init scripts are, reinventing the wheel over and over again to do basic things like prevent a service from running twice. Want to restart a service automatically when it crashes? Well you hack another script that runs in a cron that uses hackish ways of determining if the daemon has crashed: Check for a running process, find out if it's responding, kill it if necessary, start it again. Gets unsupportable in a hurry on production systems. So we resort to third party solutions like supervisord, which work pretty well, but aren't integrated into the init system at all, so they don't obey runlevels. The two largest unix vendors have not shipped sysv init for many years. Solaris replaced it with SMF, and Apple with LaunchDaemon. systemd is superior to both systems.

As an admin surely you can see the benefit to creating simple daemon definition files that can get your daemon up and running (with restart, with protection against multiple instances) all with two or three lines of a simple text config file.

From what I can see systemd is modular, and if you don't want to use journald, you don't have to. On RHEL7 it's set to small, ram-based log for crash reporting only, with the real enterprise-required logging going to rsyslog which is a conventional logging facility.

I personally cannot find fault with Pottering's work. It just works for me (I am an admin also). I also am extremely grateful for pulseaudio also. It just works now, and lets me do things that no other system currently does, like record one program's output to mp3 while listening to music or watching videos. Can't argue with results.

If you read the article, or even the summary, you'll know the author indeed had roaming disabled. He only enabled roaming for one minute to get google maps to update, then disabled it again. And he also states that he never successfully got any data. Google Maps did not load. 50 MB is a lot of data for an unsuccessful attempt to connect.

So while your advice is sound, the original author also followed it and still got burned. He would have been happy to pay exorbitant rates for the 1.5 or so MB he actually needed. But not for 50 MB which in all likelihood the phone never used. Thus AT&T is still ripping people off by charging for data that they admit they cannot even accurately track. It is this that he wishes to call attention to.

After friends, coworkers, and sales people convinced her, my sister got a nice iPhone a year or so ago after having a crappy android phone for a couple of years. After one week she was so fed up with it. This was probably iOS 5 days. I'm sure things are better now but back then it had a hard time setting up her contacts and calendar to sync with Google. That and the lack of third-party keyboards caused her to give up on it and she exchanged it for a halfway decent Android phone which she quite likes. To this day she wonders why people can stand iPhones. To each his or her own.

All this isn't to say that Android doesn't suck; rather it sucks in different ways that work better for some people. To me battery life on Android is still pretty crappy after all these years.

For starters the Drake Equation is not something to really be "believed". It's just a way to form a guess. It doesn't tell anyone anything useful.

As for nuclear wars on extrasolar planets, we're just at the edge of being able to detect terrestrial extrasolar planets. We do not currently have the ability to gather the sort of data that might suggest an extrasolar planet had been the site of a nuclear war.