Don't wonder, hover your mouse cursor over the variable and behold the glory of tooltips.
Now what happens when you change the name of a return type from a commonly used function? Have fun with your maintenance nightmare. If you are lucky the compiler will complain, if you are unlucky you break existing code without knowing it.
That's the thing, it won't be Netflix, etc implementing DRM applications or plugins. They will continue to use Silverlight or something else that implements the DRM they require and we will have lost the opportunity to rid the internet of plugins.
That's great but you don't represent the majority of the internet. Most people do want streaming video and couldn't care less if it happens to be encrypted. A good platform enables the functionality people want.
Doesn't matter if it's a plugin or if it's an application. It's going to be platform specific either way, which we should be moving away from. A pile of platform specific applications cause far more wasted effort then implementing a DRM scheme on top of existing video code ever could.
Better to have something that works and is closed source then have nothing.
I don't really want a netflix plugin, a hulu plugin and a bank plugin. I kind of get the feeling most slashdotters would agree it's much better to have one plugin that runs on multiple platforms then a mess of single use plugins with widely varying platform support. Or even better, have a single interopable standard that makes browser plugins redundant.
Office 2010 is in no way a forced upgrade (sucks if your work requires you to use a certain version but that's not really relevant). The UI changes are documented well in advance with betas, blogs, conferences, etc. Google likes to change their UI without any significant notice and kill off entire products at a whim. That's the difference they are trying to point out.
After a couple releases of heavy bug fixing sure. Netscape 6 eventually became firefox and is successful now too. But this is after the company died off.
OSX wasn't a rewrite, they grabbed a lot of code from BSD and various other projects. NT wasn't a rewrite either, it used a lot of existing code from OS/2. In fact when it was still under development it was even going to be called OS/2 3.0. Even then, both projects were years late and vastly over budget.
If you have an example of a rewrite of a non-trivial piece of software working out well and shipping on time and on budget I'm interested to hear about it. My experience has been that rewriting instead of refactoring is a plan that is doomed to fail. People grossly underestimate the value of an existing code base.
The windows 7 style desktop is still in both the ARM and x86 versions. What this article is pointing out is that only a select few apps will be able to run on the desktop on ARM. x86 desktop remains more or less unchanged.
It would be horrendously slow and eat battery like mad. It's helpful to keep in mind that WOA is an iPad competitor (read: touch screen UI). Running these old keyboard and mouse interfaces on a touchscreen would make for a terrible user experience, ask anyone that has used a XP or win 7 tablet. Now add in the amount of extra effort that would be required to write not just an x86 emulator but ensuring 100% compatibility with the existing APIs and it becomes clear why Win32 is a non-starter on ARM.
For the people that absolutely cannot live without legacy Win32 code, there will be x86 devices in similar form factors as the ARM devices. There was a whole pile of them unveiled at CES this year.
Just correcting a misconception here. The amount of RAM in use has no effect on power usage. RAM takes electricity whether it contains useful information or not.
Indeed. It is a factual piece of reporting expressing anti-SOPA opinions. Does it really matter if the opinions come from an editor or a third party? I don't think it does. The focus should be on what is being said not who is saying it.
Slashdot Mirror
Don't wonder, hover your mouse cursor over the variable and behold the glory of tooltips.
Now what happens when you change the name of a return type from a commonly used function? Have fun with your maintenance nightmare. If you are lucky the compiler will complain, if you are unlucky you break existing code without knowing it.
I wonder if Windows 8 will have an emulation layer for x86 on the ARM.
Nope.
Really? You need a citation that Youtube and Netflix are popular? GTFO.
Do you pay a lot of attention to what brand of sugar or salt you buy? Probably not - because salt is salt.
Ask the same question to a Jew.
No companies are appreciably different from each other when you eliminate what they are actually selling from consideration.
That's the thing, it won't be Netflix, etc implementing DRM applications or plugins. They will continue to use Silverlight or something else that implements the DRM they require and we will have lost the opportunity to rid the internet of plugins.
That's great but you don't represent the majority of the internet. Most people do want streaming video and couldn't care less if it happens to be encrypted. A good platform enables the functionality people want.
Doesn't matter if it's a plugin or if it's an application. It's going to be platform specific either way, which we should be moving away from. A pile of platform specific applications cause far more wasted effort then implementing a DRM scheme on top of existing video code ever could.
Better to have something that works and is closed source then have nothing.
I don't really want a netflix plugin, a hulu plugin and a bank plugin. I kind of get the feeling most slashdotters would agree it's much better to have one plugin that runs on multiple platforms then a mess of single use plugins with widely varying platform support. Or even better, have a single interopable standard that makes browser plugins redundant.
Office 2010 is in no way a forced upgrade (sucks if your work requires you to use a certain version but that's not really relevant). The UI changes are documented well in advance with betas, blogs, conferences, etc. Google likes to change their UI without any significant notice and kill off entire products at a whim. That's the difference they are trying to point out.
RTFS. It was released in Japan some time ago. Your friend had one shipped in.
You can't make a decision based on intent or benefit, you have to make a decision based on evidence.
Seems completely rational to me. Maybe read the entire post instead of making a snap judgement based on half a paragraph?
After a couple releases of heavy bug fixing sure. Netscape 6 eventually became firefox and is successful now too. But this is after the company died off.
OSX wasn't a rewrite, they grabbed a lot of code from BSD and various other projects. NT wasn't a rewrite either, it used a lot of existing code from OS/2. In fact when it was still under development it was even going to be called OS/2 3.0. Even then, both projects were years late and vastly over budget.
If you have an example of a rewrite of a non-trivial piece of software working out well and shipping on time and on budget I'm interested to hear about it. My experience has been that rewriting instead of refactoring is a plan that is doomed to fail. People grossly underestimate the value of an existing code base.
Both actually. No word on what they are going to do with the browserless EU editions.
Yes because rewritting a browser is such an excellent decision that doesn't kill projects and companies.
Ah conspiracy theories... the lazy mans excuse to convince yourself you "won" an argument.
https://market.android.com/details?id=com.microsoft.office.onenote&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5taWNyb3NvZnQub2ZmaWNlLm9uZW5vdGUiXQ..
Wow! Would like to share what you are smoking with the rest of us?
The windows 7 style desktop is still in both the ARM and x86 versions. What this article is pointing out is that only a select few apps will be able to run on the desktop on ARM. x86 desktop remains more or less unchanged.
It would be horrendously slow and eat battery like mad. It's helpful to keep in mind that WOA is an iPad competitor (read: touch screen UI). Running these old keyboard and mouse interfaces on a touchscreen would make for a terrible user experience, ask anyone that has used a XP or win 7 tablet. Now add in the amount of extra effort that would be required to write not just an x86 emulator but ensuring 100% compatibility with the existing APIs and it becomes clear why Win32 is a non-starter on ARM.
For the people that absolutely cannot live without legacy Win32 code, there will be x86 devices in similar form factors as the ARM devices. There was a whole pile of them unveiled at CES this year.
[Citation Needed]
Seriously. No one other then OEMs have their hands on them yet. How do you know this?
Just correcting a misconception here. The amount of RAM in use has no effect on power usage. RAM takes electricity whether it contains useful information or not.
My kingdom for a mod point...
Indeed. It is a factual piece of reporting expressing anti-SOPA opinions. Does it really matter if the opinions come from an editor or a third party? I don't think it does. The focus should be on what is being said not who is saying it.