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.
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).
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.
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.
I know Yi So-Yeon, the first Korean astronaut. She said she hated space. She wanted to throw up the whole time, and felt like her head was going to explode. (Both of these symptoms are caused by gravity not pulling things downwards, as well as the vestibular system being screwed up.)
Personally, I have been on a Zero-G "Vomit comet" flight, and it *was* "frickin awesome" until about the 15th parabola, then I started feeling extremely nauseated. I'm lucky we landed before I needed to throw up (some poor shmuck paid $6000 for the flight and had to strap himself into a seat so he could throw up constantly into a bag after the very first parabola). However, I have never felt more motion-sick -- it was *awful* -- and it didn't subside for over five hours after we landed.
Almost all hardware manufacturers *do* mine with all the hardware they make. They make it and mine with it even after you have paid for it. They then ship it to you right before the break-even point. There are endless stories out there about missed shipping deadline after missed shipping deadline, mining hardware companies making empty promises, and would-be miners receiving hardware a few months too late, by which point their projected return is orders of magnitude smaller than it would have been due to the increase in network hash rate between when they paid for the hardware and when they received it.
Findings include that... suggesting a bad match is a good match causes people to converse nearly as much as ideal matches would.
All this means is that OKC's match algorithms suck: there's only a weak correlation between match scores and real-world compatibility (like with every other dating site).
Oh, and the reason I finally got PRK was because I realized PRK cost the same amount as my Canon EOS 5D Mark II, and I valued seeing things with my eyes more than through a camera lens. I sold the camera and got PRK.
Slashdot Mirror
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.
This test is rather silly, it's easy to come up with a chaotic system that is "beautiful".
Congratulations to the researchers. They just re-invented PageRank.
Whoever wrote this article is just trawling.
Yet another up-to-the-minute story.
Q: If an atom slams into another atom in the forest, and nobody is around to hear it, did it make a phonon or not? A: Yes.
They're reinventing the wheel. A better solution is to use an inverted hyperbolic cosine catenary curve.
People who live in brick houses with tile roofs in earthquake zones are just asking for trouble.
I know Yi So-Yeon, the first Korean astronaut. She said she hated space. She wanted to throw up the whole time, and felt like her head was going to explode. (Both of these symptoms are caused by gravity not pulling things downwards, as well as the vestibular system being screwed up.)
Personally, I have been on a Zero-G "Vomit comet" flight, and it *was* "frickin awesome" until about the 15th parabola, then I started feeling extremely nauseated. I'm lucky we landed before I needed to throw up (some poor shmuck paid $6000 for the flight and had to strap himself into a seat so he could throw up constantly into a bag after the very first parabola). However, I have never felt more motion-sick -- it was *awful* -- and it didn't subside for over five hours after we landed.
Almost all hardware manufacturers *do* mine with all the hardware they make. They make it and mine with it even after you have paid for it. They then ship it to you right before the break-even point. There are endless stories out there about missed shipping deadline after missed shipping deadline, mining hardware companies making empty promises, and would-be miners receiving hardware a few months too late, by which point their projected return is orders of magnitude smaller than it would have been due to the increase in network hash rate between when they paid for the hardware and when they received it.
Findings include that ... suggesting a bad match is a good match causes people to converse nearly as much as ideal matches would.
All this means is that OKC's match algorithms suck: there's only a weak correlation between match scores and real-world compatibility (like with every other dating site).
Building roads all over a continent is one of the fastest ways to decimate species.
Oh, and the reason I finally got PRK was because I realized PRK cost the same amount as my Canon EOS 5D Mark II, and I valued seeing things with my eyes more than through a camera lens. I sold the camera and got PRK.