The fact that the FCC's move provoked this reaction from Verizon shows that the FCC did something right.

"Old" doesn't mean "antiquated".

Just sayin'.

Systemd is as worrying to me as the next user, especially since there are *still* stupid PulseAudio bugs that have persisted for years since Lennart got his hands on the audio system. But since I don't have the time or inclination to write a better alternative, I'm just sitting back and watching the show, and therefore I guess I need to be OK with the outcome.

Data science is to machine learning as "full stack" is to web development. i.e. a horrible buzzword.

This article should be entitled "Will Facebook's Reactive Native shake up the whole mobile industry?". This story is in need of a textbook application of Betteridge's Law.

Google has so much data on everybody in the world that they could probably do a far better job at predicting insurance risk by means of proxy variables than anybody else.

Glom and BOND are your two main graphical database frontend options in the Linux world. Or you could try developing something in the cloud with Google Apps, scripted with Javascript, using a Google Spreadsheet or the Google Drive API as the "datastore". Or you could get even fancier and build a cloud database app with Firebase, it's pretty amazing (and they just released Angular bindings for Firebase, so you get data binding to UI widgets built in).

The Dell XPS 15 Touch. It's amazing.

There's no reason they need to decrypt connections to throttle them. Throttling after a threshold data burst rate over a sustained period of time would be sufficient.

Just sayin'.

See also: GNOME 3.0

And I'm calling it: I'll get 10 replies saying "submit a patch, not a bug report". I know that code walks the talk. But see the third paragraph in my original post.

I estimate I have reported over 3000 bugs over the years across maybe 80 different open source projects. I would say that 5% of the bugs I have reported have ever been fixed intentionally by the developers. Some of the bugs have become obsolete or "accidentally fixed" with subsequent code changes; some have been marked WONTFIX with a range of justifications; but the vast majority have been ignored, and are still sitting open in a bugtracker somewhere. Some projects like Fedora close most of my bug reports after the bugs expire a couple of releases into the future. I'm not quite sure why I bother, except that some projects like Eclipse are fast to respond and always fix the bug -- this sort of proactive and responsive attitude keeps me going.

I get it, there's no reason I can ever justifiably expect a developer to fix my pet bug, given that they choose what they work on -- except that if they fix the bug, the software will be better, which should really be the goal. My bug-reports are objective, carefully researched, and properly written, with minimal test cases / repro instructions, required logs, etc. etc. -- and I'm a developer myself, so I understand what's needed.

No, I don't have time to figure out how to build, test and isolate bugs in every product I find a bug in -- the developers can do that much faster than me, they are already set up to build and run the code, and they know the code better than I could hope to. So reporting bugs is my contribution. I would love to see a bit more responsiveness to contributions across all open source projects, even if fixing bugs feels like laborious busy-work.

There are much bigger problems with the physics in Interstellar, which Kip Thorne is not willing to address now that he has his name on a book claiming that the movie is unusually scientifically grounded. He should have run the plot past some colleagues.