The TFS gives away the "criminal" practices - "polygraph-beating techniques, which are said to include controlled breathing, muscle tensing, tongue biting and mental arithmetic. " - so now they will come after/. as well...:-)
And maybe, commenters who quote TFS...
Fortunately when the sit me down for interrogation, now I know all that is needed is byte the tongue for not giving away the ID numbers of my fellow/.ers; So, don't worry!
This is the 3 or 4th/. post worried about the fate of microsoft surface...as if one should care! Just let it die! It is a bad product, with a bad startegy and bad timing! Why care at all? With either Surface RT or not, or Microsoft itself. Pointing to desparate Microsoft-fans blog posts trying to save it is as little "news for nerds' as I can imagine.
If a software failure allows an user to gain control of his own device, 'a.k.a." Jail breaking, it is not a "security hole" - it is a freaking FEATURE! T.F.A. an the headline puts it as if it was a bad thing.
There is actually very little correlation between being "legit" and benefiting the artist. The vry statement "legit and benefit the artist" imply in buying one of the bigest lies of the current system.
Or one could instead grab any android phone, install an app with a Python interpreter and have something to match the matlabs and mathematicas of the desktop (for only the cost of the hardware, not having to fork thousands of $$ in software license).
"The 64-bit ARM ISA is pretty interesting: it's more of wholesale overhaul than a set of additions to the 32-bit ISA."
OS based on Linux and OSS just need athat GCC supports it, which it already does, and Microsoft will only need another 12 years of rewriting^w research until they can come up with Windows RT 64.
I think the closest thing I have seen close to this is the "Commitee to Nuke the Whales" - a troll operation set-up in one of late Robert Anton Wilson's novels.
They woul dhave a bad time coming along anyway, since they can't be compatible with the secure boot (UEFI) way of working (workaround if one prefers), that is being adopted by major distributions: all Kernel level code, and X11 code, will have to be signed to work out of the box in a UEFI restricted boot environment. And any distro that would sign binary code coming from NVIDIA or whoever else would be mad.
It may be we get some months across a new "no working 3d drivers" dark ages on the Linux desktop, but one way or the other, the time for proprietary drivers is past.
All paranoid xenphobic US atitudes taken in context, this is onethat makes some sense. I just wish all other countries in the World would do the same thing towards US government hooked-up and not-trustable Microsoft.
Let me see! I sit e here atop this 60 bilion of yearly reveneue, and tell others to invest 5 billion over 5 years, so that I can get people to hire that are cheaper tahn foreigners? Riiiight!
Will we do when malware gets "legitimate" signatures for the new and secure "secure boot" we will have in all PC's from now on. I don't think such malware will be so easily removed, or even detected. As things stand, any legitamate use of UEFI's secure boot feature, even if one would be fool enough to believe in their "it improves security" falacy is bogus - and it will be bad(tm) when the root-kit, hyper-visor-level signed malware starts to strike the PC World.
It is 2012, and we have things like git and mercurial on these days. If there is no server available, you just put your codebase on version control in place, without having to configure a single file. It just won't work if you don't have 2 or 3x free disk space as your source files take - but in that case you have deeper problems than the ones we are dealing with.
You could get one of tens presentations on what it does, point them to the wikipedia article on version control -- but I see all of that as orthogonal to actually using it.
Just _do_ use git or mercurial on the project - you should already be doing it, and you know that. Btw, those 2 systems are light years ahead anything proprietary V.C. tools have to offer nowadays - not ot mention the complete desburocratization on initally versioning a code base to start with: no need to setup a server, no need to a complicated build process to get the newest version running. Just relax, init the repo, add the files, and you are rolling.
Slashdot Mirror
After the Orwell's 1984 fiasco had not Bezzos "promised" he would never use this feature again?
(Yanking content from the users?)
The TFS gives away the "criminal" practices - "polygraph-beating techniques, which are said to include controlled breathing, muscle tensing, tongue biting and mental arithmetic. " - so now they will come after /. as well... :-)
And maybe, commenters who quote TFS...
Fortunately when the sit me down for interrogation, now I know all that is needed is byte the tongue for not giving away the ID numbers of my fellow /.ers; So, don't worry!
H.I.F.T.F.Y.
This is the 3 or 4th /. post worried about the fate of microsoft surface ...as if one should care! Just let it die! It is a bad product, with a bad startegy and bad timing! Why care at all? With either Surface RT or not, or Microsoft itself. Pointing to desparate Microsoft-fans blog posts trying to save it is as little "news for nerds' as I can imagine.
as will Java, the new Cobol. So what?
> Just that Java would die, just that java would die.
Ah /. ..sometimes I just miss the ubiquitous "like" and "+1" buttons there are in the web today.
Just check the graphs here - Nokia is but a walking corpse by now:
http://communities-dominate.blogs.com/brands/2013/01/second-picture-in-the-nokia-destruction-saga-greatest-individual-management-mistake-ever-made-nokia-.html
But in this case one can't know if the moderators took the O.P. seriously or not - I'd bet that some of them did.
> It's (the end of) 2012, why the hell are people STILL putting their data stores in web-accessible directories below DocumentRoot?
Because PHP.
In 2012 Slashdot - your funny comments are moderated insightful!
Dear slashdot,
If a software failure allows an user to gain control of his own device, 'a.k.a." Jail breaking, it is not a "security hole" - it is a freaking FEATURE!
T.F.A. an the headline puts it as if it was a bad thing.
Really, even on superuser.com - where this kind of question is _the_ focus, this one would closed as too broad.
And can a VMWare hosted Linux desktop do 3D? And about decent 3D?
There is actually very little correlation between being "legit" and benefiting the artist. The vry statement "legit and benefit the artist" imply in buying one of the bigest lies of the current system.
I think the best comparison for these calculators is this: http://xkcd.com/768/
Or one could instead grab any android phone, install an app with a Python interpreter and have something to match the matlabs and mathematicas of the desktop (for only the cost of the hardware, not having to fork thousands of $$ in software license).
"The 64-bit ARM ISA is pretty interesting: it's more of wholesale overhaul than a set of additions to the 32-bit ISA."
OS based on Linux and OSS just need athat GCC supports it, which it already does, and Microsoft will only need another 12 years of rewriting^w research until they can come up with Windows RT 64.
(I stand corrected: the Linux kernel itself was up and running on ARM 64 even before GCC ofically supported it: http://www.phoronix.com/scan.php?page=news_item&px=MTIwNzU )
I think the closest thing I have seen close to this is the "Commitee to Nuke the Whales" - a troll operation set-up in one of late Robert Anton Wilson's novels.
They woul dhave a bad time coming along anyway, since they can't be compatible with the secure boot (UEFI) way of working (workaround if one prefers), that is being adopted by major distributions: all Kernel level code, and X11 code, will have to be signed to work out of the box in a UEFI restricted boot environment. And any distro that would sign binary code coming from NVIDIA or whoever else would be mad.
It may be we get some months across a new "no working 3d drivers" dark ages on the Linux desktop, but one way or the other, the time for proprietary drivers is past.
All paranoid xenphobic US atitudes taken in context, this is onethat makes some sense. I just wish all other countries in the World would do the same thing towards US government hooked-up and not-trustable Microsoft.
Let me see! I sit e here atop this 60 bilion of yearly reveneue, and tell others to invest 5 billion over 5 years, so that I can get people to hire that are cheaper tahn foreigners? Riiiight!
And, oh genius, explain me how an S.O. that is running under an undetectable and undeletable hypervisor would be able to update the "UEFI blacklist"?
Will we do when malware gets "legitimate" signatures for the new and secure "secure boot" we will have in all PC's from now on. I don't think such malware will be so easily removed, or even detected. As things stand, any legitamate use of UEFI's secure boot feature, even if one would be fool enough to believe in their "it improves security" falacy is bogus - and it will be bad(tm) when the root-kit, hyper-visor-level signed malware starts to strike the PC World.
> just because it can run on your desktop does not mean it should.
But it is still about 3 orders of magnitude better than having no version control at all.
It is 2012, and we have things like git and mercurial on these days. If there is no server available, you just put your codebase on version control in place, without having to configure a single file. It just won't work if you don't have 2 or 3x free disk space as your source files take - but in that case you have deeper problems than the ones we are dealing with.
You could get one of tens presentations on what it does, point them to the wikipedia article on version control -- but I see all of that as orthogonal to actually using it.
Just _do_ use git or mercurial on the project - you should already be doing it, and you know that. Btw, those 2 systems are light years ahead anything proprietary V.C. tools have to offer nowadays - not ot mention the complete desburocratization on initally versioning a code base to start with: no need to setup a server, no need to a complicated build process to get the newest version running. Just relax, init the repo, add the files, and you are rolling.