Depending on how they are detecting root, you can always do a quick nandroid backup and then restore a non rooted firmware for the duration of your movie then just reverse the process. It is easier than it sounds and can be fairly well automated down to a sub 5 minute one-click process. The only real fly in the ointment is if they are detecting an unlocked bootloader or just the os itself. Of course, this will get razor sharp focus from very sharp hackers so expect a solution in 5...4...3...
I think Microsoft has a legitimate chance in this space but there are hundreds of millions of devices from many manufacturers that also have a very good chance. It is very likely that the streaming to the television duties will remain a competitive market with a mix of devices in people's homes. Also, an xbox is a significant investment for people living in in developing countries. Those people are much more likely to invest in something cheaper. An arm based set top box can be put together and sold for much cheaper than the cheapest high end game machine no matter the economies of scale. I just think pinning the medal on Microsoft is a bit premature.
He is saying what he will do. Why are you criticizing him as if he were positing it as a general solution? I'm getting a pool installed. Is that wrong because millions of apartment dwellers can't? I don't get you people that seem to think everybody should be the same.
Wait, what? What happened to the Wii, playstation, tablets, google tv's, apple tv's, slingboxes, boxee boxes, etc.? Did they all get outlawed and summarily destroyed? You are counting chickens before the evolution of birds here.
Listen, jackass. In order for me to take you up on your "challenge", I would have to 1. give a shit what you think and 2. take you seriously.
Hell just look up "Broke drivers" or any variation thereof on Ubuntu, the "Linux for humans" forum. I did recently and quit counting at over 14 THOUSAND hits!
I just did the same thing on sevenforums.com. The list stretches on and on. Note, dumbass, ubuntuforums.org are for every version of Ubuntu the sevenforums is just for Windows 7. How about a little bit of intellectual honesty, dipshit?
Your entire driver model is a piss poor joke!
I know you are a troll but to inject a little common sense into this, how do you expect hardware to work on an operating system it wasn't designed for? That's like asking why windows 7 won't install on a Sparcstation. The landfills are full of printers and scanners that won't work with Win7. I don't see you crying about that. Generally, if there is a driver for a piece of hardware that has been officially written for Linux it works better there. I had a USB cellular dongle I got from Verizon a couple of years ago that was atrocious in Windows. Took over a minute to connect from cold, would constantly time out and hang necessitating pulling it out and reinserting it. On Linux, it connected in less than 10 seconds and never had to be reinitialized. On hardware that is made for both Linux and Windows, the Linux experience is usually better. My girlfriend has a laptop with integrated wi-fi and when she boots it into Windows, you have to wait a good minute for it to initialize and the little donut to quit spinning in the tray over the network icon for the internet to work. When I boot it into Linux, it's up and ready to go before the desktop even fully loads. All in all, in about half the time it takes Windows. Now, of course, for you trolls, Linux can't win so despite these things because your 2 dollar winmodem doesn't work, Linux is shit. Why don't you just admit that you run a click and drool/part replacer repair shop and Windows is your bread and butter so you have a vested interest in hating anything else. If I made my living as a pathetic virus "ambulance chaser", I'd champion Windows too.
But you stick your head in the sand little man, you pretend it is all a global conspiracy by the evil M$ to keep your "quality" away from the masses when in reality the masses have spoken in a loud single voice and said "DO NOT WANT to your broke ass driver clusterfuck and CLI jerking off.
So, when Linux is built on hardware made for it, marketed well and made available to the masses, it doesn't sell?
Your argument is basically "Nobody would want to target a specific gui" when in fact, if there was only a single GUI people would be writing apps that target it. It's the lack of a single gui that prevents those kinds of apps (or at least makes it much more difficult).
Are you fucking retarded? The "GUI" (btw, what the fuck are you talking about? Widget toolkit? Not a programmer much, fucktard?) is irrelevant to how you write your applications. You pick a toolkit and you write your application. Kind of like on Windows, you can use tkinter, gtk+, Qt or whatever you want. They all work equally well on any desktop. It's really a question of which one you are most comfortable with. Every platform has multiple toolkits you can use. Windows, OSX, Linux, fucking OS/2, all of them. You don't even make sense.
Yes, some apps do in fact target the compositing engine. For example, plug-ins for the compositing engine.
Really, numbnuts? Plugins written for a particular program only work on that program? No shit. Firefox plugins only work on...drum roll...Firefox. What is your point? That you are an idiot? I get it.
So, my question for you is this. Did your mom go to have an abortion and just change her mind after a third of your brains had been sucked out? Because, then you might have an excuse.
The fact that you can replace your GUI with something else is great, from an end user perspective.. but terrible from a developer perspective.
How so? I can write my app with GTK or Qt and as far as what "GUI" someone is using, it will work on 99.9 percent of Linux desktops. If it doesn't, it's because that person really doesn't want it to work.
Take, for example, desktop compositing. In Linux, it might or might not be there, and if it is there, there might bet half a dozen different API's.
What are you talking about and pray tell what way does this impact me as a developer? Are you saying I need to interact directly with the compositing engine? Because I don't. That's absurd unless I'm specifically targeting that with my application. Are you confused?
Beryl
is installed on nobody's computer as of several years ago when it merged into Compiz. Your points amount to nothing more than "I don't like Linux" handwaving.
While cool, bash completion still only works for commands for which the completion has been defined. In PowerShell cmdlets, functions, aliases and even script files inherently interact with the shell to provide metadata about parameters, types, defaults etc so that
tab-completion is defined by the very same declarations that drive parameter parsing. As soon as you declare a parameter for a command, function or even your own script file, tab completion is working
Maybe so but when the command is defined in bashcompletion it's done. At the end of it, whether it's "easier" in PS or not, it boils down to the same thing. The guy up the thread was completely ignorant to the fact that you could have tab completion of parameters in bash at all which is what was corrected and rightfully so.
help is integrated and will document the parameters using the same declarations, regardless of whether you actually provide textual descriptions for the paraneters (help documentation is integrated and you can document parameters with a simple comment convention - which goes for both cmdlets, functions and script files).
Help works very well on *nix for the command line. Just type "man $COMMAND" and get educated. If you want your script to have that you can. Or you can just put the documentation inside of the script. Again, it boils down to the same thing.
Look, nobody here is arguing that PowerShell is better than bash or other shell scripting environments.
Yes. Yes, they are. And the arrogance and presumptuousness is quite galling. That is why you are getting the backlash.
Lastly, as mentioned, PowerShell works just fine with stdio as output by any normal process. All of its functionality is a superset of what is available in UNIX scripting. In either case, the power lies not with the shell. That serves only as the glue to compose other utilities together.
No it is not. PS does not have the ability to parse text and pass it to stdin like the bash utilities cut, grep, sed, awk, xargs, etc. can.
All of its functionality is a superset of what is available in UNIX scripting. In either case, the power lies not with the shell. That serves only as the glue to compose other utilities together
Fine, it's a superset. Ipython is a superset of bash which wipes its ass with powershell every day of the week and twice on Sunday.
Is it because you cannot tolerate the mere thought that somebody at Redmond actually came up with a cool innovation over the traditional shells?
I think it's more the arrogance and presumptuousness with which you PS boosters speak of its supposed superiority as if it is a forgone conclusion. We get it, you like it. It uses objects. Some people prefer the text stream and don't see the objects as superior. I know, what a concept, right? For people well versed in bash, grep, awk, cut, sed, etc. are very comfortable and efficient tools. You people remind me of the mono-ites that just can't bear the thought that someone doesn't see your pet project as the holy grail of computing.
Every example you just posted requires you to actually examine the output of each of the commands, and apply brittle and convolted text parsing structures like grep and awk.
Translation: it's foreign to me and I don't want to learn it. There is nothing convoluted about any Unix command once you learn how to use it. Grep and awk are second nature to many people. That's a particularly weak and, quite frankly intellectually dishonest argument when presented to expers and power users like many people on Slashdot are.
All of if these break when the author alters the output text format.
The core utilities have been going strong for 30-40 years and most changes have only added features not taken old ones away. You have no idea what the future has in store for PS so that too is a weak argument.
Instead of building scripts based on brittle text parsing, they are built on a self documenting model that provides. There is no text parsing. That's extra work. Why do it?
There is nothing PS can do that can't be accomplished by streams of text. The Unix model is very simple, every argument I've seen against it has amounted to little more than strawman bs,and unlike your flavor of the week utility, it will be here long after we are all long gone.
Half of the power in Bash is the ability of the various commands to not only output to text but to take their input as common text from standard in or a file. Usually the text is passed around and filtered between several discrete commands before whatever it is you are doing is accomplished. In PowerShell, can text be passed around, piped, grepped, sorted, etc. as well as in Bash?
The same thing that happens when the text format output by one program isn't understood by the text input format of a second.
What, I use another tool from the toolkit to filter the text into what I need? That's second nature and very easy once you take the time to learn what is available and how to use it. Kind of like with every other tool on a computer aimed at experts and power users.
Piping objects it's a joy instead of dealing with spacing and grep-everything...
I like grepping. Its regular expression syntax gets me exactly what I need everytime and since I actually took the time to learn how to use it, it's like second nature.
I hate all those arcane command line options
They may be arcane to you that doesn't mean they are arcane to somebody else. PowerShell is extremely verbose compared to Bash. That seems pretty arcane to me.
If microsoft provides the Win32 API on ARM it will only take a recompile to make them run on ARM.
Keep dreaming. It will take much more than a simple recompile.
It doesn't really matter that the x86 binaries that exist today do not run on ARM.
You are discounting legacy software that will never be recompiled for anything. Also, you are presuming that ISV's are going to care about Windows 8 on ARM. That is extremely speculative at this point particularly in light of the tepid response WP7 has had.
That list was just compiled to illustrate the point that.net is not the great savior of Windows' on ARM that it is purported to be. And if Windows 8 is presented as just that "Windows 8" and it has been so far, then there will be many people that expect their software to run. When it doesn't they're going to be disappointed. There is the long tail of the Windows ecosystem that adds much of the value to the platform. With this new direction, they lose that. Even with that added value, Windows has had little success on tablets. This won't even have that ecosystem in its favor. Now that the tablet version of Android has USB host, it's not too many steps away from being a legitimate competitor to Windows in any guise. And between now and the Win 8 release date, its position is only going to strengthen.
Slashdot Mirror
Depending on how they are detecting root, you can always do a quick nandroid backup and then restore a non rooted firmware for the duration of your movie then just reverse the process. It is easier than it sounds and can be fairly well automated down to a sub 5 minute one-click process. The only real fly in the ointment is if they are detecting an unlocked bootloader or just the os itself. Of course, this will get razor sharp focus from very sharp hackers so expect a solution in 5...4...3...
Here's a video of some guy showing off his OG Droid. If you look carefully, the first app he fires up is netflix.
CANONICAL: Admit Unity is a total failure, ask for our forgiveness and never, ever do it again! /Rant off
Taking this into account:
GNOME: Stop your "War On Users" by hiding user configurations or ripping them out!
What would you suggest Canonical do instead?
I think Microsoft has a legitimate chance in this space but there are hundreds of millions of devices from many manufacturers that also have a very good chance. It is very likely that the streaming to the television duties will remain a competitive market with a mix of devices in people's homes. Also, an xbox is a significant investment for people living in in developing countries. Those people are much more likely to invest in something cheaper. An arm based set top box can be put together and sold for much cheaper than the cheapest high end game machine no matter the economies of scale. I just think pinning the medal on Microsoft is a bit premature.
He is saying what he will do. Why are you criticizing him as if he were positing it as a general solution? I'm getting a pool installed. Is that wrong because millions of apartment dwellers can't? I don't get you people that seem to think everybody should be the same.
xbox is poised to be blah blah blah
Wait, what? What happened to the Wii, playstation, tablets, google tv's, apple tv's, slingboxes, boxee boxes, etc.? Did they all get outlawed and summarily destroyed? You are counting chickens before the evolution of birds here.
Apple will still make money there out of the gate because of the markup on Macs. The converse with Ms isn't true. I agree this smells funny.
Hell just look up "Broke drivers" or any variation thereof on Ubuntu, the "Linux for humans" forum. I did recently and quit counting at over 14 THOUSAND hits!
I just did the same thing on sevenforums.com. The list stretches on and on. Note, dumbass, ubuntuforums.org are for every version of Ubuntu the sevenforums is just for Windows 7. How about a little bit of intellectual honesty, dipshit?
Your entire driver model is a piss poor joke!
I know you are a troll but to inject a little common sense into this, how do you expect hardware to work on an operating system it wasn't designed for? That's like asking why windows 7 won't install on a Sparcstation. The landfills are full of printers and scanners that won't work with Win7. I don't see you crying about that. Generally, if there is a driver for a piece of hardware that has been officially written for Linux it works better there. I had a USB cellular dongle I got from Verizon a couple of years ago that was atrocious in Windows. Took over a minute to connect from cold, would constantly time out and hang necessitating pulling it out and reinserting it. On Linux, it connected in less than 10 seconds and never had to be reinitialized. On hardware that is made for both Linux and Windows, the Linux experience is usually better. My girlfriend has a laptop with integrated wi-fi and when she boots it into Windows, you have to wait a good minute for it to initialize and the little donut to quit spinning in the tray over the network icon for the internet to work. When I boot it into Linux, it's up and ready to go before the desktop even fully loads. All in all, in about half the time it takes Windows. Now, of course, for you trolls, Linux can't win so despite these things because your 2 dollar winmodem doesn't work, Linux is shit. Why don't you just admit that you run a click and drool/part replacer repair shop and Windows is your bread and butter so you have a vested interest in hating anything else. If I made my living as a pathetic virus "ambulance chaser", I'd champion Windows too.
But you stick your head in the sand little man, you pretend it is all a global conspiracy by the evil M$ to keep your "quality" away from the masses when in reality the masses have spoken in a loud single voice and said "DO NOT WANT to your broke ass driver clusterfuck and CLI jerking off.
So, when Linux is built on hardware made for it, marketed well and made available to the masses, it doesn't sell?
Your argument is basically "Nobody would want to target a specific gui" when in fact, if there was only a single GUI people would be writing apps that target it. It's the lack of a single gui that prevents those kinds of apps (or at least makes it much more difficult).
Are you fucking retarded? The "GUI" (btw, what the fuck are you talking about? Widget toolkit? Not a programmer much, fucktard?) is irrelevant to how you write your applications. You pick a toolkit and you write your application. Kind of like on Windows, you can use tkinter, gtk+, Qt or whatever you want. They all work equally well on any desktop. It's really a question of which one you are most comfortable with. Every platform has multiple toolkits you can use. Windows, OSX, Linux, fucking OS/2, all of them. You don't even make sense.
Yes, some apps do in fact target the compositing engine. For example, plug-ins for the compositing engine.
Really, numbnuts? Plugins written for a particular program only work on that program? No shit. Firefox plugins only work on...drum roll...Firefox. What is your point? That you are an idiot? I get it.
So, my question for you is this. Did your mom go to have an abortion and just change her mind after a third of your brains had been sucked out? Because, then you might have an excuse.
The fact that you can replace your GUI with something else is great, from an end user perspective.. but terrible from a developer perspective.
How so? I can write my app with GTK or Qt and as far as what "GUI" someone is using, it will work on 99.9 percent of Linux desktops. If it doesn't, it's because that person really doesn't want it to work.
Take, for example, desktop compositing. In Linux, it might or might not be there, and if it is there, there might bet half a dozen different API's.
What are you talking about and pray tell what way does this impact me as a developer? Are you saying I need to interact directly with the compositing engine? Because I don't. That's absurd unless I'm specifically targeting that with my application. Are you confused?
Beryl
is installed on nobody's computer as of several years ago when it merged into Compiz. Your points amount to nothing more than "I don't like Linux" handwaving.
$ ps -eo pid,rss | numgrep /800000..80000000/ | kill `cut -f1 -d' '`
While cool, bash completion still only works for commands for which the completion has been defined. In PowerShell cmdlets, functions, aliases and even script files inherently interact with the shell to provide metadata about parameters, types, defaults etc so that
tab-completion is defined by the very same declarations that drive parameter parsing. As soon as you declare a parameter for a command, function or even your own script file, tab completion is working
Maybe so but when the command is defined in bashcompletion it's done. At the end of it, whether it's "easier" in PS or not, it boils down to the same thing. The guy up the thread was completely ignorant to the fact that you could have tab completion of parameters in bash at all which is what was corrected and rightfully so.
help is integrated and will document the parameters using the same declarations, regardless of whether you actually provide textual descriptions for the paraneters (help documentation is integrated and you can document parameters with a simple comment convention - which goes for both cmdlets, functions and script files).
Help works very well on *nix for the command line. Just type "man $COMMAND" and get educated. If you want your script to have that you can. Or you can just put the documentation inside of the script. Again, it boils down to the same thing.
ps | where-object {$_.Processname -eq "iexplore"} | foreach-object {$_.Kill()}
Golf clap. Bash:
$ killall firefox
Look, nobody here is arguing that PowerShell is better than bash or other shell scripting environments.
Yes. Yes, they are. And the arrogance and presumptuousness is quite galling. That is why you are getting the backlash.
Lastly, as mentioned, PowerShell works just fine with stdio as output by any normal process. All of its functionality is a superset of what is available in UNIX scripting. In either case, the power lies not with the shell. That serves only as the glue to compose other utilities together.
No it is not. PS does not have the ability to parse text and pass it to stdin like the bash utilities cut, grep, sed, awk, xargs, etc. can.
All of its functionality is a superset of what is available in UNIX scripting. In either case, the power lies not with the shell. That serves only as the glue to compose other utilities together
Fine, it's a superset. Ipython is a superset of bash which wipes its ass with powershell every day of the week and twice on Sunday.
Is it because you cannot tolerate the mere thought that somebody at Redmond actually came up with a cool innovation over the traditional shells?
I think it's more the arrogance and presumptuousness with which you PS boosters speak of its supposed superiority as if it is a forgone conclusion. We get it, you like it. It uses objects. Some people prefer the text stream and don't see the objects as superior. I know, what a concept, right? For people well versed in bash, grep, awk, cut, sed, etc. are very comfortable and efficient tools. You people remind me of the mono-ites that just can't bear the thought that someone doesn't see your pet project as the holy grail of computing.
Every example you just posted requires you to actually examine the output of each of the commands, and apply brittle and convolted text parsing structures like grep and awk.
Translation: it's foreign to me and I don't want to learn it. There is nothing convoluted about any Unix command once you learn how to use it. Grep and awk are second nature to many people. That's a particularly weak and, quite frankly intellectually dishonest argument when presented to expers and power users like many people on Slashdot are.
All of if these break when the author alters the output text format.
The core utilities have been going strong for 30-40 years and most changes have only added features not taken old ones away. You have no idea what the future has in store for PS so that too is a weak argument.
Instead of building scripts based on brittle text parsing, they are built on a self documenting model that provides. There is no text parsing. That's extra work. Why do it?
There is nothing PS can do that can't be accomplished by streams of text. The Unix model is very simple, every argument I've seen against it has amounted to little more than strawman bs,and unlike your flavor of the week utility, it will be here long after we are all long gone.
What happens in Linux when program 1 outputs text formatted such that program 2 can't grok it?
Um, there are commands like sort, grep, cut, et al whose sole purpose is to format text on the command line.
You are obviously not new to this so why are you trying to be misleading?
probably
.
Everything actually has a text representation
Half of the power in Bash is the ability of the various commands to not only output to text but to take their input as common text from standard in or a file. Usually the text is passed around and filtered between several discrete commands before whatever it is you are doing is accomplished. In PowerShell, can text be passed around, piped, grepped, sorted, etc. as well as in Bash?
The same thing that happens when the text format output by one program isn't understood by the text input format of a second.
What, I use another tool from the toolkit to filter the text into what I need? That's second nature and very easy once you take the time to learn what is available and how to use it. Kind of like with every other tool on a computer aimed at experts and power users.
Piping objects it's a joy instead of dealing with spacing and grep-everything...
I like grepping. Its regular expression syntax gets me exactly what I need everytime and since I actually took the time to learn how to use it, it's like second nature.
I hate all those arcane command line options
They may be arcane to you that doesn't mean they are arcane to somebody else. PowerShell is extremely verbose compared to Bash. That seems pretty arcane to me.
("ps aux" and "ps -aux")
Kind of a silly quibble there.
I think you mean Alt+d.
Why not? This seems like a pretty good idea to me. Every little bit counts especially with netbooks and tablets.
If microsoft provides the Win32 API on ARM it will only take a recompile to make them run on ARM.
Keep dreaming. It will take much more than a simple recompile.
It doesn't really matter that the x86 binaries that exist today do not run on ARM.
You are discounting legacy software that will never be recompiled for anything. Also, you are presuming that ISV's are going to care about Windows 8 on ARM. That is extremely speculative at this point particularly in light of the tepid response WP7 has had.
That list was just compiled to illustrate the point that .net is not the great savior of Windows' on ARM that it is purported to be. And if Windows 8 is presented as just that "Windows 8" and it has been so far, then there will be many people that expect their software to run. When it doesn't they're going to be disappointed. There is the long tail of the Windows ecosystem that adds much of the value to the platform. With this new direction, they lose that. Even with that added value, Windows has had little success on tablets. This won't even have that ecosystem in its favor. Now that the tablet version of Android has USB host, it's not too many steps away from being a legitimate competitor to Windows in any guise. And between now and the Win 8 release date, its position is only going to strengthen.