I'm not sure I agree. This seems more like the manufacturing world equivalent of automated unit and integration testing of software. Essentially, if anything starts going wrong due to a minor change you make, you're made aware of the situation immediately and can correct it.
Essentially, it's a lot of time and effort that on first blush does absolutely nothing, because in the optimal case, nothing ever happens. But the end result is that you can make minor changes or corrections with more assurance that you're not negatively affecting the quality of the final product.
It's a casualty in that it never really took off. If it was anyone but Valve with their barrels of money being made from Steam, it probably would have been shuttered long ago. Honestly, I've always thought one of the problems was that Valve didn't just build the thing themselves and run a certification program similar to other console makers. There's little money to be made on the hardware side, so I'm not sure why they thought 3rd party manufacturing would be a good idea.
Assuming you're not talking about strictly personal projects, that means managing your own internet-facing servers. What could possibly go wrong with an amateur doing that?
GitHub is free for open source projects, and most everyone knows about it and knows how to use it. What's not to like? One of the great things about git is the fact that you always have a copy of the entire repo locally, which means lock-in is pretty much impossible.
The notion that MS would somehow lock out command-line access to GitHub or turn it into a MS or Visual Studio-only product is absurd, if for no other reason than it would screw over MS devs just as badly as everyone else. Yeah, shocker, a lot of MS and Windows devs use command line tools as well, and a lot of their stuff is on GitHub.
I mean, MS is moving in the complete opposite direction, making Windows work better with Linux tools, Visual Studio targeting multiple platforms and using multiple toolchains, and releasing Electron-based cross-platform apps like VS Code. Even.NET has been open sourced.
I'm not saying I like this idea of this acquisision, but I don't see why they'd want to kill GitHub. This isn't the year 2000, and Linux and open source are no longer their boogeyman. Microsoft is literally in the business of renting and managing Linux servers, and it's a massive revenue source for them.
Sounds like you haven't worked there for a while. Source Depot is pretty much abandonware at this point, and only a few teams with a lot of legacy dependencies are using it. Most teams are moving to git.
Have you noticed all the tight git integration occurring in Visual Studio, or how Microsoft has actually been contributing to git to improve performance on extremely large projects? It's because all their internal teams are using git, and we get the integration as a benefit.
You have a lot more faith in the apparently all-encompassing power of EULAs over existing law than I do. No matter what a EULA says, it's not legally binding unless a court AGREES that it's legally binding. And I very much doubt a court would take kindly to changing a EULA of an already purchased license into a rental, just because Microsoft wants to. It's about as silly as arguing that Microsoft could legally sell me into bondage if they happened to slip such language into their EULA.
I'm sure by 2020 you'll have forgotten about this ridiculous prediction of yours and have long since moved onto some other dire warning for Windows users.
I think you're forgetting that most individuals purchase a Windows license that is tied to their hardware, not to them personally. So the next time they buy a new computer, they pay for Windows once again. That's how Microsoft makes money off consumer or small business users.
Besides, I'm pretty sure Microsoft can't legally force anyone who has purchased a license to use their OS in perpetuity to start renting it any more than a car dealer can do that for a car that's paid off. They'd trigger the largest class action lawsuit in history, possibly along with government action (although who knows with this administration), if they tried it. Note that when this article is talking about "end of support", they're talking about patch and upgrade support for older versions of Windows 10, not the current version. Unless there's some compatibility issue (and it's easy enough to roll back individual computers on a small scale), there's no reason for anyone NOT to be up to date.
I don't trust Microsoft at all, as I'm sure they'd love to dip their hand into a cookie jar like that, but I think they're far too fearful of killing off the remainder of their PC business if they did something that reckless. They're all-in with the cloud, and so I think will be happy to keep growing in that area, and leaving their legacy Windows products as they roughly are now for the time being and the foreseeable future.
If you're not doing it often, it's really not that cost-effective to buy a car only for those rare occasions. If you ARE doing it fairly often, then it probably is. And if you don't want to bother with renting a car, then stick with the large capacity ICE vehicle, or whatever, or go hybrid-electric, since those have much greater range.
I'm not some EV zealot who pooh-poohs any reasonable objections to their current practicality. But given that any traveling I do more than 120 miles at a time is on an airplane, I'm pretty sure an EV is right in my strike zone, and quite practical for me. For others, it might be workable only as a second car, and for still others, it's just not workable yet at all.
In the rare case of a break-down, you can always get a rental or loaner if you just happen to need long range. But the odds of needing long range just as your ICE breaks down seems pretty low, if you don't need it often.
My family lives in a town 60 miles away, so for me, I need a 150 mile car at minimum. But I almost never travel further than that. My next car will certainly be EV, but I'm not going to buy a new car until my ICE doesn't run well anymore. It's long since paid for, and I don't have extra money to flush down the toilet like that. Besides, the longer I wait, the better and cheaper they get.
I'm marginally hopeful that the lack of backward compatibility will be a thing of the past now that the major players are using more commodity hardware. If they *don't* do it, they'll have to face some very tough questions about why they deliberately chose not to. I think many gamers will consider that a valuable feature going forward.
I do like that, design-wise, they're not simply copying the iPhone. The price is absurdly expensive and I'm not interested in high-end camera accessories, so I'm not in the least bit interested in this, but I think I like the way it looks at first glance. It's pretty distinctive. I'm not sure why people keep trying the 3D holography gimmick, though.
Personally, I had to stop using it because of performance issues. Nothing I tried fixed the periodic freezes that would lock the client up for 30 to 60 seconds or so. I would never have stopped using it except for that.
I think it's because they're still refining very fundamental control, motion, and construction / configuration issues. These can be easily applied to military applications as well as civilian ones. It's really just a matter of context and optional packages. You can't imagine that mini-spot robot doing bomb disposal in a war zone? Or strap a weapon to the end of that arm instead of a hand manipulator to go after an enemy combatant that's holed up in a building? That's an easy conversion to make, I'd wager.
That's an interesting observation. The very notion of self-awareness may be considered somewhat superficial and unnecessary to a being of pure logic, although it's hard to say for certain. Maybe it's just the notion of emotionless intelligence is too alien for us to relate to, because it's completely outside our practical experience.
Not likely, as the whole point of this work is to enable Windows developers to use some of their favorite native Linux-based tools. It would completely ruin the point if they introduced some artificial incompatibility. Remember, Microsoft is also hosting native Linux in Azure, right alongside their own Windows Server OS. This means they have, in fact, every reason to ensure these systems remain as compatible as possible with native Linux.
Microsoft is not motivated by ideology, but by money. Linux used to be a competitor to Windows, their big money-maker, so they hated Linux. Now Linux is making money for them in Azure, so they're embracing Linux and, to some extent, open source. Because money. You don't need to make things any more complicated than that.
I agree - the monster truck comment seems inane and misplaced.
It seems more likely to me that a self-aware AI would be completely indifferent to most forms of entertainment or stimulation, such as monster truck shows or symphonies or games of chance, because it doesn't have endorphin centers in an organic brain to tickle. There are no incentives for non-rational pursuits built into their core such as humans have unless they've been specifically programmed to favor those things.
And one would hope that anyone creating such a system would imbue the better human qualities such as compassion, empathy, justice, etc into the core feedback loops which motivate the AI. A 100% rational AI would likely end up being rather terrifying, simply because it would, by it's very nature, lack any "humanity,"
I live in California and will be fired for creating a hostile work environment if I put anything that might offend in my documentation. That's why my code is completely devoid of comments.
That creates a hostile work environment for competent programmers.
Slashdot Mirror
I'm not sure I agree. This seems more like the manufacturing world equivalent of automated unit and integration testing of software. Essentially, if anything starts going wrong due to a minor change you make, you're made aware of the situation immediately and can correct it.
Essentially, it's a lot of time and effort that on first blush does absolutely nothing, because in the optimal case, nothing ever happens. But the end result is that you can make minor changes or corrections with more assurance that you're not negatively affecting the quality of the final product.
all valve did is challenge developers to make the most disgusting and controversial game they can. it will not end well.. for anyone.
That would be "trolling."
Uh, no... Microsoft used an internal version of Perforce called Source Depot for version control prior to the switch to git.
I think you might have meant to say "if it wasn't self defense". Otherwise, it's obviously not "senseless" nor a murder.
It's a casualty in that it never really took off. If it was anyone but Valve with their barrels of money being made from Steam, it probably would have been shuttered long ago. Honestly, I've always thought one of the problems was that Valve didn't just build the thing themselves and run a certification program similar to other console makers. There's little money to be made on the hardware side, so I'm not sure why they thought 3rd party manufacturing would be a good idea.
Assuming you're not talking about strictly personal projects, that means managing your own internet-facing servers. What could possibly go wrong with an amateur doing that?
GitHub is free for open source projects, and most everyone knows about it and knows how to use it. What's not to like? One of the great things about git is the fact that you always have a copy of the entire repo locally, which means lock-in is pretty much impossible.
The notion that MS would somehow lock out command-line access to GitHub or turn it into a MS or Visual Studio-only product is absurd, if for no other reason than it would screw over MS devs just as badly as everyone else. Yeah, shocker, a lot of MS and Windows devs use command line tools as well, and a lot of their stuff is on GitHub.
I mean, MS is moving in the complete opposite direction, making Windows work better with Linux tools, Visual Studio targeting multiple platforms and using multiple toolchains, and releasing Electron-based cross-platform apps like VS Code. Even .NET has been open sourced.
I'm not saying I like this idea of this acquisision, but I don't see why they'd want to kill GitHub. This isn't the year 2000, and Linux and open source are no longer their boogeyman. Microsoft is literally in the business of renting and managing Linux servers, and it's a massive revenue source for them.
Sounds like you haven't worked there for a while. Source Depot is pretty much abandonware at this point, and only a few teams with a lot of legacy dependencies are using it. Most teams are moving to git.
Have you noticed all the tight git integration occurring in Visual Studio, or how Microsoft has actually been contributing to git to improve performance on extremely large projects? It's because all their internal teams are using git, and we get the integration as a benefit.
You have a lot more faith in the apparently all-encompassing power of EULAs over existing law than I do. No matter what a EULA says, it's not legally binding unless a court AGREES that it's legally binding. And I very much doubt a court would take kindly to changing a EULA of an already purchased license into a rental, just because Microsoft wants to. It's about as silly as arguing that Microsoft could legally sell me into bondage if they happened to slip such language into their EULA.
I'm sure by 2020 you'll have forgotten about this ridiculous prediction of yours and have long since moved onto some other dire warning for Windows users.
I think you're forgetting that most individuals purchase a Windows license that is tied to their hardware, not to them personally. So the next time they buy a new computer, they pay for Windows once again. That's how Microsoft makes money off consumer or small business users.
Besides, I'm pretty sure Microsoft can't legally force anyone who has purchased a license to use their OS in perpetuity to start renting it any more than a car dealer can do that for a car that's paid off. They'd trigger the largest class action lawsuit in history, possibly along with government action (although who knows with this administration), if they tried it. Note that when this article is talking about "end of support", they're talking about patch and upgrade support for older versions of Windows 10, not the current version. Unless there's some compatibility issue (and it's easy enough to roll back individual computers on a small scale), there's no reason for anyone NOT to be up to date.
I don't trust Microsoft at all, as I'm sure they'd love to dip their hand into a cookie jar like that, but I think they're far too fearful of killing off the remainder of their PC business if they did something that reckless. They're all-in with the cloud, and so I think will be happy to keep growing in that area, and leaving their legacy Windows products as they roughly are now for the time being and the foreseeable future.
If you're not doing it often, it's really not that cost-effective to buy a car only for those rare occasions. If you ARE doing it fairly often, then it probably is. And if you don't want to bother with renting a car, then stick with the large capacity ICE vehicle, or whatever, or go hybrid-electric, since those have much greater range.
I'm not some EV zealot who pooh-poohs any reasonable objections to their current practicality. But given that any traveling I do more than 120 miles at a time is on an airplane, I'm pretty sure an EV is right in my strike zone, and quite practical for me. For others, it might be workable only as a second car, and for still others, it's just not workable yet at all.
In the rare case of a break-down, you can always get a rental or loaner if you just happen to need long range. But the odds of needing long range just as your ICE breaks down seems pretty low, if you don't need it often.
My family lives in a town 60 miles away, so for me, I need a 150 mile car at minimum. But I almost never travel further than that. My next car will certainly be EV, but I'm not going to buy a new car until my ICE doesn't run well anymore. It's long since paid for, and I don't have extra money to flush down the toilet like that. Besides, the longer I wait, the better and cheaper they get.
Lucky me. My next car will apparently be hydro-powered then.
I'm marginally hopeful that the lack of backward compatibility will be a thing of the past now that the major players are using more commodity hardware. If they *don't* do it, they'll have to face some very tough questions about why they deliberately chose not to. I think many gamers will consider that a valuable feature going forward.
I do like that, design-wise, they're not simply copying the iPhone. The price is absurdly expensive and I'm not interested in high-end camera accessories, so I'm not in the least bit interested in this, but I think I like the way it looks at first glance. It's pretty distinctive. I'm not sure why people keep trying the 3D holography gimmick, though.
Personally, I had to stop using it because of performance issues. Nothing I tried fixed the periodic freezes that would lock the client up for 30 to 60 seconds or so. I would never have stopped using it except for that.
I think it's because they're still refining very fundamental control, motion, and construction / configuration issues. These can be easily applied to military applications as well as civilian ones. It's really just a matter of context and optional packages. You can't imagine that mini-spot robot doing bomb disposal in a war zone? Or strap a weapon to the end of that arm instead of a hand manipulator to go after an enemy combatant that's holed up in a building? That's an easy conversion to make, I'd wager.
That's an interesting observation. The very notion of self-awareness may be considered somewhat superficial and unnecessary to a being of pure logic, although it's hard to say for certain. Maybe it's just the notion of emotionless intelligence is too alien for us to relate to, because it's completely outside our practical experience.
Not likely, as the whole point of this work is to enable Windows developers to use some of their favorite native Linux-based tools. It would completely ruin the point if they introduced some artificial incompatibility. Remember, Microsoft is also hosting native Linux in Azure, right alongside their own Windows Server OS. This means they have, in fact, every reason to ensure these systems remain as compatible as possible with native Linux.
Microsoft is not motivated by ideology, but by money. Linux used to be a competitor to Windows, their big money-maker, so they hated Linux. Now Linux is making money for them in Azure, so they're embracing Linux and, to some extent, open source. Because money. You don't need to make things any more complicated than that.
I'm thinking the 'I' should stand for 'Inflated' as well.
What ever the rats were eating may now end up with a massive increase in population..
Well... yeah. That was the entire point of the project.
I agree - the monster truck comment seems inane and misplaced.
It seems more likely to me that a self-aware AI would be completely indifferent to most forms of entertainment or stimulation, such as monster truck shows or symphonies or games of chance, because it doesn't have endorphin centers in an organic brain to tickle. There are no incentives for non-rational pursuits built into their core such as humans have unless they've been specifically programmed to favor those things.
And one would hope that anyone creating such a system would imbue the better human qualities such as compassion, empathy, justice, etc into the core feedback loops which motivate the AI. A 100% rational AI would likely end up being rather terrifying, simply because it would, by it's very nature, lack any "humanity,"
This revelation is so important that a simple three-dot ellipsis just won't cut it!
I live in California and will be fired for creating a hostile work environment if I put anything that might offend in my documentation. That's why my code is completely devoid of comments.
That creates a hostile work environment for competent programmers.
If a Duplex realizes it's talking to another Duplex, will it go into 56K modem mode and just talk electronically?