If I remember correctly, these guys will generate petabytes of data per day Rechecking your facts would be in order. Some 10 to 15 petabytes are expected to be saved per year according to sources I have seen, though only a small fraction of the raw sensor data will be permanently recorded.
14Pb for 170k employees isn't so much - 83 gigabytes per person. If you add up the total disk space in an average office you'll get more than that. Except that you miscalculated by a factor of a thousand.
And of course he wasn't paid. Why would anybody ever think that? Notice that he only denied being "paid off", not being "paid". And he mentioned two specific companies that did not pay him. Read into that what you will.
I too respect and appreciate the apology, but it doesn't fix the fairly significant credibility problem that Lyons and Forbes have as a result of his part articles. It would seem that Daniel Lyons only apologized to his readers, not to the people he has wrongly attacked. I therefore do not accept that his apology as it stands is full and sincere, or deserving of my respect.
This kind of thing should have been anticipated. Software patents are Evil. At least Linux won't be impacted. I wonder what sort of person modded you down.
That didn't stop Microsoft from suing Lindows.... For the record, Microsoft won. For the record, Microsoft settled and wrote a check for $20 million. It seems that if the case had gone to trial, Lindows had a good chance of turning the tables on Microsoft by invalidating the Windows[tm] trademark. Which is, after all, an ordinary English word and is not supposed to be trademarkable. Adds a little bite to the old saw about throwing stones in glass houses, does it not?
For a large percentage of corporations a centralized repository is the only way to go. I think git has the right idea but needs to integrate with a centralized server. What happens in the large corporate is, devs end up keeping their "working copy" of the code on their local machine because if they just checked their experimental/broken stuff in, other devs would complain. Same for creating branches in the central repository, if you are doing it for you own experiments you will get unpopular fast. So what happens instead is, a dev makes changes to their checked out copy and does not check in for days or weeks at a time, then bits of this work get lost for one reason or another. Meanwhile, development on the trunk eventually orphans the experiment, merging is too much work and chances are, the whole experiment will get lost or rot too much to be useful and get thrown away. Don't tell me it doesn't happen - a lot.
do try to go easy on the phrase "paradigm shift" in your explanation even if this is one; marketdroids love over-using it and it's come to be a code phrase for "same old, same old". It's a paradigm shift. Try it, you will see.
Simple enough? Oh you want reasons. OK, I will mention just one: have you ever experienced a source control system that can allow an arbitrary number of developers to work in parallel, each with multiple parallel development threads in their own local repository? If not, then you will experience the paradigm shift soon after you begin using it. Soon after that, you will be preaching. Oh, and it is also a passable source control system even for a single developer working with a single repository. Arguably more stable than SVN, which is not too bad in its own right. Git has some amazing features like Git-bisect, which is used to track down regressions.
Did he slam it, or did he say that it's fine, just not appropriate for a project as distributed as the kernel? The former. I was able to load the article, but can't get it back now. He said something like it's "good enough" for many people, but no one's really excited about SVN. To me, that's crap. SVN does what it does very well. What more could you really want from a centrally-managed versioning system? How about a true versioned rename instead of emulation via delete+create? How about not being able to recover in any obvious way if you rm -r a subtree instead of svn rm it? Just two of the more painful issues that come to mind.
Better than CVS, that about sums it up. I think that anybody still using CVS instead of SVN is crazy, but SVN still delivers less than I had expected. Maybe over time things could improve. Rewrite the whole back end, throw away the versioning filesystem idea and just keep the command set, that would work. The command set is not too bad (well... some oddities but not nearly as bad as cvs). SVN would still not be distributed in any meaningful way, but lots of people don't need that.
Hmm. And make any local changes be a true branch, now that would be forward progress. Also unlikely to happen because of the huge pile of existing code that makes it hard to even contemplate a deep hack like that. But we shall see.
Q: India is one of the major producers of software engineers, yet we don't contribute much to the Linux domain. The interviewer is not correct. There are a goodly number of India-based developers who contribute to the Linux kernel. Suparna Bhattacharya and Badari Pulavarty come to mind, there are lots more.
To some extent, the heavy influence of India-based developers on the kernel is due to IBM having a major lab there, which is being emulated by a number of other Linux-backing corporations. The quality of technology education seems exceptionally high from what I can see, and to be honest, the Indian culture seems to be oriented towards higher things than money.
Now I know everyone loves google but other than using open source products what exactly have they done to help out the community? For example, zumastor/ddsnap. You're welcome:-)
Heh. I know a few folks that work for the patent office. Wonderful, intelligent folks tasked with the impossible, who also have no control over the politics of policy. Do they feel the slightest bit guilty for the part they play in the cynical intellectual property land grab?
IMHO the networking stack is quite uninteresting. On the bottom, it's constrained by the networking protocols and network interfaces. On the top it's constrained by the Unix and socket interfaces. That doesnt leave a whole lot of room for innovative bits in the middle. Even if I accept your conclusion, which I don't, the lovely thing about open source is that you can add your own protocols and interfaces as you please. Obviously, only something really amazing has a chance to survive, but it was ever thus in the jungle.
If you actually knew anything about Bill Gates (or Steve Jobs), you would know that money has never been his motivation. Oh and according to you he shorts the U.S. dollar for, um, altruistic reasons? Color me skeptical.
Have you ever used XP or 2000? It's not shitty". It's certainly not the best thing ever, but it sure as fuck beats using Linux for a desktop machine. Really? On the few occasions I have used Microsoft's desktop in the last few years I found it clumsy, non-intuitive, slow and incomplete compared to KDE. At times I really wonder why all those Windows users put up with it. Oh right, they don't know anything else.
This sort of thing isn't always on purpose. Some people think "open source" means they can use the code however they please. John Carmack understands perfectly what the GPL is all about, and surely nobody needs to be reminded what a huge contributer he is to open source and open standards. Certainly an oversight and public humiliation is not in order.
do people really find HDD noise annoying enough at 7.5K rotational speeds to justify the extra cost and complexity? Yes. I have a Shuttle SD11G5 Pentium-M based box for an always-on server, which sits in the bedroom closet. The shuttle cooler is roughly 27 db at 1 meter. The WD5000KS drive in it, picked for its quietness, is about 29 db at 1 meter. At night when all is quiet I can hear the unit clearly, even 3 meters away in the closet. If I could get the whole thing down to 25 db @1m I would like it more. That would be achieved by running with the fan stopped under normal-to-medium load and this hard disk.
To be honest, I think the 25 db level can be achieved just by further improving the mechanical parts. As far as quietness goes, the pipes and pumps you need for water cooling add up to something more like a geek trophy than a practical system. But for a performance system that wants water cooling for the processor anyway, this may be attractive. Note that there still has to be a fan or big heat sink to cool the water. According to the laws of thermodynamics, there is no such thing as getting rid of heat, you just move it around.
Though it almost makes we want to spit my coffee, I have to say that I do not see anything evil here... yet. Quite the contrary, it would seem on first blush. An RF grant is pretty clearcut, see the big discussion about that leading up to the famous W3 decision to require RF grants for all new web standards.
Still, there are still ways to game an RF grant, for example, nothing stops Microsoft from supporting slightly off-standard formats in its own software and refusing to grant an RF license covering those changes to other implementors, using the argument that the original RF grant does not cover any extensions. I suppose the big question is, are other implementors free to extend the format also or does the RF grant evaporate as soon as an implementor extends the standard, perhaps in an effort to match Microsoft's own extensions? In which case the playing field would be far from level, and we have seen all too many times what happens when Microsoft manages to tilt the playing field. I simply haven't drilled into this enough to know what is true here, and no doubt, close readers will find other aspects of the grant to worry about.
I wouldn't mind having a 'frozen' Wikipedia on CD-ROM. Who knows how long the site will last, and like my Quanta Press CDs, I would be able to benefit from it a decade later. Luckily for you, the entire Wikipedia database is yours for the taking, and always will be. You may have to click on some scary waiver in regards to possible unknown origin of some of the image files, which are distributed separately from the main Wikipedia text if I recall correctly.
CDROM encyclopedias were all the rage -- Encarta was a household name for maybe 5 years. Now thankfully completely buried by Wikipedia, and with it Bill's dreams of owning all the content in addition to all the platforms. Oh wait... XBox... I guess that zombie is not quite dead yet.
I was thinking that, yes a bubble may pop, and I thought the word "bubblehead", not that I would ever say such a thing in actual words. Well, having met the man in person I can say that he is actually more intelligent than you would think from his web persona. Hopefully he will eventually complete the transition from clueless wintel camp follower to actual netizen, unlike most of his peers.
Slashdot Mirror
I wonder who modded you troll?
Simple enough? Oh you want reasons. OK, I will mention just one: have you ever experienced a source control system that can allow an arbitrary number of developers to work in parallel, each with multiple parallel development threads in their own local repository? If not, then you will experience the paradigm shift soon after you begin using it. Soon after that, you will be preaching. Oh, and it is also a passable source control system even for a single developer working with a single repository. Arguably more stable than SVN, which is not too bad in its own right. Git has some amazing features like Git-bisect, which is used to track down regressions.
Better than CVS, that about sums it up. I think that anybody still using CVS instead of SVN is crazy, but SVN still delivers less than I had expected. Maybe over time things could improve. Rewrite the whole back end, throw away the versioning filesystem idea and just keep the command set, that would work. The command set is not too bad (well... some oddities but not nearly as bad as cvs). SVN would still not be distributed in any meaningful way, but lots of people don't need that.
Hmm. And make any local changes be a true branch, now that would be forward progress. Also unlikely to happen because of the huge pile of existing code that makes it hard to even contemplate a deep hack like that. But we shall see.
To some extent, the heavy influence of India-based developers on the kernel is due to IBM having a major lab there, which is being emulated by a number of other Linux-backing corporations. The quality of technology education seems exceptionally high from what I can see, and to be honest, the Indian culture seems to be oriented towards higher things than money.
Quite the contrary it would seem. Microsoft is still unabashedly evil. Look no further than the shenanigans in Massachusetts.
To be honest, I think the 25 db level can be achieved just by further improving the mechanical parts. As far as quietness goes, the pipes and pumps you need for water cooling add up to something more like a geek trophy than a practical system. But for a performance system that wants water cooling for the processor anyway, this may be attractive. Note that there still has to be a fan or big heat sink to cool the water. According to the laws of thermodynamics, there is no such thing as getting rid of heat, you just move it around.
Though it almost makes we want to spit my coffee, I have to say that I do not see anything evil here... yet. Quite the contrary, it would seem on first blush. An RF grant is pretty clearcut, see the big discussion about that leading up to the famous W3 decision to require RF grants for all new web standards.
Still, there are still ways to game an RF grant, for example, nothing stops Microsoft from supporting slightly off-standard formats in its own software and refusing to grant an RF license covering those changes to other implementors, using the argument that the original RF grant does not cover any extensions. I suppose the big question is, are other implementors free to extend the format also or does the RF grant evaporate as soon as an implementor extends the standard, perhaps in an effort to match Microsoft's own extensions? In which case the playing field would be far from level, and we have seen all too many times what happens when Microsoft manages to tilt the playing field. I simply haven't drilled into this enough to know what is true here, and no doubt, close readers will find other aspects of the grant to worry about.
I was thinking that, yes a bubble may pop, and I thought the word "bubblehead", not that I would ever say such a thing in actual words. Well, having met the man in person I can say that he is actually more intelligent than you would think from his web persona. Hopefully he will eventually complete the transition from clueless wintel camp follower to actual netizen, unlike most of his peers.