So first off, I am not a developer and have never needed or used any source control system. So no stake in this argument.
To the people threatening to leave GitHub...I'm sure MS could care less since you never paid a cent to keep your precious GitHub running. In fact, it is losing money hand-over-fist and not likely to around much longer, anyway. They won't miss you.
Now I can sort of understand why MS might want to buy an up-and-running source control shop, but it's hard to understand why they significantly overpaid for it. There's probably a common relationship going on between the current paying GitHub customer base and MS's own base. That could be worth a lot for both parties. Then this would seem to be more of a full-service offering to enterprise. It makes no difference that MS already has it's own service. It's just a choice for your customers like different grades of gasoline (car analogy here).
I'm sure the other major cloud players will be either buying up the other small guys or rolling their own soon, so you'll have a really nice choice of which devil will own your soul... if that's your attitude.
No reason why the HoloLens tech couldn't be adapted to that output. I think the key here is the integrated local room mapping and navigation software. The output could be a combination of anything. Therefore, a practical device could very well be something fairly lightweight since the support for video would probably be eliminated.
Sounds like this system would have crashed unzipping ANY large file under ANY OS because it was the application that the CPU couldn't properly execute.
I hate to break up this paranoia-fest, but the government --- and the NSA in particular --- has little, if any, reason to want a "backdoor" into generally used crypto system. Since secrets have a way of not being secret for very long, the existance and means of access of such a backdoor would quickly become available to our advesaries. At that point they could pretty much wreck our economy at will.
So, as you can see, a "defense agency" would have far greater motivation to ensure a robust system rather than one which is weakly armored.
The book list appears to be about Management Information Systems, not Operating Systems. While Linux might very well host an MIS, it certainly isn't an MIS; all the criticism seems pretty much misplaced.
This article is not another opportunity for those who have Seen the Light Along the One True Path to wonder why other's don't "get it". I know it's hard to believe, but for some people, choosing an operating system is more like choosing a shipping carrier. Now, maybe you really ought to spend more time considering your OS, but you've got to respect that maybe other people's jobs are just as complex in their way as yours.
And don't tell me, "Well, the answer is still Linux, it'll just take a while to sink in". The uncomfortable question that Linux is always the answer to is "What systems do you know anything about?"
While "planting" may be far-fetched, if SCO was still in the litigation business you might worry about them suing you because one of their former employees used SCO IP in your code (we're talking non-conspiracy theory here). That happens with everyday job changes, but would you hire more carefully because of SCO's rep?
I would envision something along the lines of a PostScript-level language as an intermediate... something at a fairly high semantic level with dispatchable computation elements. You've got to be able to describe computations large enough to be worthwhile sending out to a bunch of fast processors while freeing the programmer of having to manage all this. Thus, a new high level language for programmers and a new intermediate one for fabrics of machines. Nobody says the intermediate can't be compiled deeper.
Interestingly enough, Optima waited pretty much exactly 6 years after the Sep 1997 grant date to file the suit, obviously to let the industry get as big as possible. BTW, my reading of laches (IANAL) would indicate the industry might be be protected by laches for the period before the suit but not after; if Optima prevails then they'd have to get licences to continue operating.
Problem 1. A rectangular vat 2mX2m in floor area is filled to height 2m and thus contains 8 cubic meters=8200kg water. A cubic meter block of ice is lowered into the vat; since it's mass is 917kg, where is the water level now? Ans: The block displaces 917KG liquid water, the volume of which is 0.89 cu m. The total volume of the liquid and displacing ice mixture is now 8.89 cu m. The height is 8.89/4 = 2.22 m.
Problem 2. A rectangular vat 2mX2m in floor area is filled with 9117 kg of water. How high is the vat filled? Ans: Since water density is 1025 kg cu meter the vat contains 9117/1025 = 8.89 cu m of water. With a floor area of 4 sq m the height will be 8.89/4 - 2.22 m.
A technician friend of mine reported that at the Federal building in Boston the procedure was to walk up to the metal detector, put your tool bag on a table, walk thru the detector, and then pick up your tool bag (uninspected).
"Better" is planning for disaster as part of the system's initial design. In the early days, I hated D/R planning because of all the lousy details and the fact that sometimes you could never really get things back exactly the way they were. Later, enlightenment struck and I realized you could design a system that was hard to backup or one that was easy to backup.
Therefore, don't build something that you'd hate to have to replicate. You should design for recovery from the get-go. Another benefit: recoverable designs end up being simpler and easy to manage.
... using VM. Not everything can be measured in pure dollars and cents. Consider: All the stuff written about "what-if" this or that fails because I have only one box can largely be ignored. All that fail-over stuff is built under the skin of the box. Just because you don't see it as multiple distinct boxes doesn't mean it's not under the covers (multiple power supplies, cpu's, busses, etc.).
When something goes wrong in an app you can right off generally cross-off hardware problems. That's because, if there are hardware faults, the system brings in spares and shoots out diagnostics on EXACTLY what's wrong, right down to the card level.
So if the sys is quiet about the hardware, it isn't the hardware.
One very big advantage is being able to run multiple versions of your OS's simultaneously. That means you don't have to worry about the crusty app running on the dusty box nobody remembers anything about. It's all on your M/F and will move right over if you change hardware.
And, of course, business recovery is a dream since your not talking about replicating all those unique boxes you've accumulated over the years.
In general, VM should be looked at as a management tool more than pure power under the hood. If you need to manage your corporate computing needs at a corporate, strategic level, VM's for you. But that doesn't mean there won't be a few instances where you've got to have the pure dedicated power for one app. But as the years go by and some apps hang around and must be maintained while focus moves onto other things, you will be very happy you've got VM there to manage your own sanity.
From the Applachain Mountain Club guidebook to Mt Washington: "Mt. Washington has a well-earned reputation as the most dangerous small mountain in the world." "... the worst conditions on Mt. Washington are approximately equal to the the worst reported from Antarctica."
Not to over-emphasize, since hundreds play around there daily, but, at least for mountains, size doesn't matter.
Slashdot Mirror
So first off, I am not a developer and have never needed or used any source control system. So no stake in this argument. To the people threatening to leave GitHub...I'm sure MS could care less since you never paid a cent to keep your precious GitHub running. In fact, it is losing money hand-over-fist and not likely to around much longer, anyway. They won't miss you. Now I can sort of understand why MS might want to buy an up-and-running source control shop, but it's hard to understand why they significantly overpaid for it. There's probably a common relationship going on between the current paying GitHub customer base and MS's own base. That could be worth a lot for both parties. Then this would seem to be more of a full-service offering to enterprise. It makes no difference that MS already has it's own service. It's just a choice for your customers like different grades of gasoline (car analogy here). I'm sure the other major cloud players will be either buying up the other small guys or rolling their own soon, so you'll have a really nice choice of which devil will own your soul ... if that's your attitude.
No reason why the HoloLens tech couldn't be adapted to that output. I think the key here is the integrated local room mapping and navigation software. The output could be a combination of anything. Therefore, a practical device could very well be something fairly lightweight since the support for video would probably be eliminated.
"... including the testing."
Somehow making alcohol in Tennessee seems appropriate.
Sounds like this system would have crashed unzipping ANY large file under ANY OS because it was the application that the CPU couldn't properly execute.
I hate to break up this paranoia-fest, but the government --- and the NSA in particular --- has little, if any, reason to want a "backdoor" into generally used crypto system. Since secrets have a way of not being secret for very long, the existance and means of access of such a backdoor would quickly become available to our advesaries. At that point they could pretty much wreck our economy at will. So, as you can see, a "defense agency" would have far greater motivation to ensure a robust system rather than one which is weakly armored.
This article is not another opportunity for those who have Seen the Light Along the One True Path to wonder why other's don't "get it". I know it's hard to believe, but for some people, choosing an operating system is more like choosing a shipping carrier. Now, maybe you really ought to spend more time considering your OS, but you've got to respect that maybe other people's jobs are just as complex in their way as yours.
And don't tell me, "Well, the answer is still Linux, it'll just take a while to sink in". The uncomfortable question that Linux is always the answer to is "What systems do you know anything about?"
While "planting" may be far-fetched, if SCO was still in the litigation business you might worry about them suing you because one of their former employees used SCO IP in your code (we're talking non-conspiracy theory here). That happens with everyday job changes, but would you hire more carefully because of SCO's rep?
I would envision something along the lines of a PostScript-level language as an intermediate ... something at a fairly high semantic level with dispatchable computation elements. You've got to be able to describe computations large enough to be worthwhile sending out to a bunch of fast processors while freeing the programmer of having to manage all this. Thus, a new high level language for programmers and a new intermediate one for fabrics of machines. Nobody says the intermediate can't be compiled deeper.
I thought the old saying was "the odds of winning the lottery are the same whether you play it or not".
Interestingly enough, Optima waited pretty much exactly 6 years after the Sep 1997 grant date to file the suit, obviously to let the industry get as big as possible. BTW, my reading of laches (IANAL) would indicate the industry might be be protected by laches for the period before the suit but not after; if Optima prevails then they'd have to get licences to continue operating.
Problem 1. A rectangular vat 2mX2m in floor area is filled to height 2m and thus contains 8 cubic meters=8200kg water. A cubic meter block of ice is lowered into the vat; since it's mass is 917kg, where is the water level now? Ans: The block displaces 917KG liquid water, the volume of which is 0.89 cu m. The total volume of the liquid and displacing ice mixture is now 8.89 cu m. The height is 8.89/4 = 2.22 m. Problem 2. A rectangular vat 2mX2m in floor area is filled with 9117 kg of water. How high is the vat filled? Ans: Since water density is 1025 kg cu meter the vat contains 9117/1025 = 8.89 cu m of water. With a floor area of 4 sq m the height will be 8.89/4 - 2.22 m.
That, they didn't change.
While the telemarketer may have a constitutional right to speak, I don't have a constitutional obligation to listen.
A technician friend of mine reported that at the Federal building in Boston the procedure was to walk up to the metal detector, put your tool bag on a table, walk thru the detector, and then pick up your tool bag (uninspected).
"Better" is planning for disaster as part of the system's initial design. In the early days, I hated D/R planning because of all the lousy details and the fact that sometimes you could never really get things back exactly the way they were. Later, enlightenment struck and I realized you could design a system that was hard to backup or one that was easy to backup.
Therefore, don't build something that you'd hate to have to replicate. You should design for recovery from the get-go. Another benefit: recoverable designs end up being simpler and easy to manage.
... using VM. Not everything can be measured in pure dollars and cents. Consider: All the stuff written about "what-if" this or that fails because I have only one box can largely be ignored. All that fail-over stuff is built under the skin of the box. Just because you don't see it as multiple distinct boxes doesn't mean it's not under the covers (multiple power supplies, cpu's, busses, etc.). When something goes wrong in an app you can right off generally cross-off hardware problems. That's because, if there are hardware faults, the system brings in spares and shoots out diagnostics on EXACTLY what's wrong, right down to the card level. So if the sys is quiet about the hardware, it isn't the hardware. One very big advantage is being able to run multiple versions of your OS's simultaneously. That means you don't have to worry about the crusty app running on the dusty box nobody remembers anything about. It's all on your M/F and will move right over if you change hardware. And, of course, business recovery is a dream since your not talking about replicating all those unique boxes you've accumulated over the years. In general, VM should be looked at as a management tool more than pure power under the hood. If you need to manage your corporate computing needs at a corporate, strategic level, VM's for you. But that doesn't mean there won't be a few instances where you've got to have the pure dedicated power for one app. But as the years go by and some apps hang around and must be maintained while focus moves onto other things, you will be very happy you've got VM there to manage your own sanity.
From the Applachain Mountain Club guidebook to Mt Washington: "Mt. Washington has a well-earned reputation as the most dangerous small mountain in the world." "... the worst conditions on Mt. Washington are approximately equal to the the worst reported from Antarctica." Not to over-emphasize, since hundreds play around there daily, but, at least for mountains, size doesn't matter.