I totally agree with keeping the code writing at home. Outsourcing it causes obvious problems like this recent one, and likely isn't as cost effective in the long run all things considered. Also agreed they bear the responsibility. In fact seeing another article on Slashdot today saying Microsoft has taken the responsibility and suspected the offending project - so they are doing as they should and not trying to hide or justify it. All in all, hope this is a good enough reasons for such companies to decide to keep their code writing at home. My fingers are crossed.
Folks it's Microsoft "China" which means the Chinese culture working in a Microsoft owned building in China. There is likely major cultural misunderstanding or forces that are at work here beyond the fact the brand is Microsoft. That's a very hard thing to manage for any transcontinental company.
Somebody should create closed source versions of the open source projects that are most often ripped off. Then give away (or sell) the proprietary versions. I don't mean fork it. I mean from scratch, in a clean room environment, to keep it untainted. It's the reverse situation of making an open source alternative to a free product.
Choosing a minor app that takes 189 freaking MB of memory for nothing but displaying sticky notes on the screen
The majority of that 189 MB is shared by all programs that need the Mono Framework. It's important to note that it's not duplicated for each app - the framework needs to be installed only once. Framing 189 MB in context of only one app can skew the reader's understanding of how the technology works.
..register more than 600 Slashdot accounts, keep using them until you get Moderator ability, then downvote EVERYTHING here to -1 as to not draw more attention to yourself online.
Even if you argue it was only intended for a small readership, what if those in the small readership are your potential employers? What to do now? Try not to spread it, duplicate or propagate further, but you just made that mistake by posting to Slashdot. So this latest incarnation of the info will be indexed by Google along with all comments, research on you and speculation about it. So you did it again...
At this point I like the suggestion somebody else posted about putting a lot of info about yourself online (good stuff) to dilute the perceived bad info.
Not having fought for their rights, Canadians are more or less content having none.
I wouldn't suggest Canadians don't care about their rights otherwise they wouldn't have fought the war of 1812 which came shortly after the Constitution.
Things swung the other way for the U.S.A. when Americans started giving up their rights and freedoms in the name of fighting "the war on terror" and unquestioned war, while Canadians still vehemently continue to defend their rights as they always have.
Not only did you not RTFA, you also didn't RTFH (History). My god how nearsighted.
If the people who can see through your invisibility technology aren't the people you're warring with or hiding something from, then your invisibility solution doesn't need to be foolproof. A solution can be perfect for a given situation even if it's not academically or technically perfect.
I bet one of them soon wonders how a slice of that might taste on a bun with Arbys sauce heated in the microwave. Juicy? Delectable? Just keep watching. Irresistible.
JavaScript is already out of the browser, but unofficially or rather unstandardized. Look at languages such as JavaScript in Flash, or the use of JavaScript in Acrobat PDF Reader, etc. Microsoft allowed their JScript (variant of JavaScript) to be used on the server side years ago in classic Active Server Pages - so I coded JavaScript on the server several years back.
However I am in support of a more official representation of JavaScript on the server.
Wikipedia has to keep growing. Any staid project will eventually succumb to demise. Maybe next for Wikipedia, implement a paid model based on micro-payments whereby contributors and editors have a fiscal incentive to stay contributing. There a many ways to provide incentives: special attribution/acknowledgements, free stuff, and many others. Keep up the momentum and the ideas. Don't move backward to a no rules model.
Ironically the Internet was supposed to solve that problem. Maybe they simply need multiple Internet connections from different providers and across different mediums: microwave, satellite, dial-up (yuck), pigeon. Expensive.
It' not like IE is open for people to download the nightly builds. I'm sure that Microsoft and its employees compile IE many times even though it might not be on the "nightly build" schedule in the most official sense.
Yes, if they're that paranoid then do due diligence and stuff Firefox into that same virtual machine that IE is running inside for the same reason - then put Google Chrome on your PC computer.
Web-based word processors have failed to rise above. So have many other kinds of web-based apps that mimic commonly used standalone apps like spreadsheets, presentation software, development studios - IDEs, paint programs, etc. etc.
Most web versions of applications are a poor man's user experience. I know people can come up with exceptions but these are not the norm and likely won't be for a long time.
Microsoft is certainly not going out of business because of web-based apps anytime in this dimension.
I doubt their future lies 100% in the cloud - that's just idealism or marketing - shifting public perception to compete with Google and the likes; however the reality is corporations will always want to control their own little part of the cloud, just as many/. people do.
They may cite disapproval with Apple's approval process but the reality the app store is getting diluted with more and more apps and developers, and it's getting tougher to make those million dollar apps. Like anything, the first on board have the best chance of benefiting the most fiscally and in popularity. I assume some of these developers are also getting disillusioned that the glory days are gone.
I totally agree with keeping the code writing at home. Outsourcing it causes obvious problems like this recent one, and likely isn't as cost effective in the long run all things considered. Also agreed they bear the responsibility. In fact seeing another article on Slashdot today saying Microsoft has taken the responsibility and suspected the offending project - so they are doing as they should and not trying to hide or justify it. All in all, hope this is a good enough reasons for such companies to decide to keep their code writing at home. My fingers are crossed.
Folks it's Microsoft "China" which means the Chinese culture working in a Microsoft owned building in China. There is likely major cultural misunderstanding or forces that are at work here beyond the fact the brand is Microsoft. That's a very hard thing to manage for any transcontinental company.
by Google http://www.google.com/search?hl=en&site=&btnG=Search&q=cache:http://imvivo.com/DetailsView/tabid/104/IndexID/1779944/Default.aspx
Somebody should create closed source versions of the open source projects that are most often ripped off. Then give away (or sell) the proprietary versions. I don't mean fork it. I mean from scratch, in a clean room environment, to keep it untainted. It's the reverse situation of making an open source alternative to a free product.
If they had be found to be orbiting 72 Virginis then a certain religious theory might have become more feasible. But no ...still pending evidence.
It'll make the boss make everybody get white noise generators. Forget the music policy change because it'll still stick.
The majority of that 189 MB is shared by all programs that need the Mono Framework. It's important to note that it's not duplicated for each app - the framework needs to be installed only once. Framing 189 MB in context of only one app can skew the reader's understanding of how the technology works.
Snafu cleared up and Microsoft didn't act evil about it, so nothing really to do here. Next article please.
..register more than 600 Slashdot accounts, keep using them until you get Moderator ability, then downvote EVERYTHING here to -1 as to not draw more attention to yourself online.
Even if you argue it was only intended for a small readership, what if those in the small readership are your potential employers? What to do now? Try not to spread it, duplicate or propagate further, but you just made that mistake by posting to Slashdot. So this latest incarnation of the info will be indexed by Google along with all comments, research on you and speculation about it. So you did it again...
At this point I like the suggestion somebody else posted about putting a lot of info about yourself online (good stuff) to dilute the perceived bad info.
I wouldn't suggest Canadians don't care about their rights otherwise they wouldn't have fought the war of 1812 which came shortly after the Constitution. Things swung the other way for the U.S.A. when Americans started giving up their rights and freedoms in the name of fighting "the war on terror" and unquestioned war, while Canadians still vehemently continue to defend their rights as they always have. Not only did you not RTFA, you also didn't RTFH (History). My god how nearsighted.
If the people who can see through your invisibility technology aren't the people you're warring with or hiding something from, then your invisibility solution doesn't need to be foolproof. A solution can be perfect for a given situation even if it's not academically or technically perfect.
I bet one of them soon wonders how a slice of that might taste on a bun with Arbys sauce heated in the microwave. Juicy? Delectable? Just keep watching. Irresistible.
JavaScript is already out of the browser, but unofficially or rather unstandardized. Look at languages such as JavaScript in Flash, or the use of JavaScript in Acrobat PDF Reader, etc. Microsoft allowed their JScript (variant of JavaScript) to be used on the server side years ago in classic Active Server Pages - so I coded JavaScript on the server several years back.
However I am in support of a more official representation of JavaScript on the server.
*Ass was hoped for.
How dare you argue against my point.
Wikipedia has to keep growing. Any staid project will eventually succumb to demise. Maybe next for Wikipedia, implement a paid model based on micro-payments whereby contributors and editors have a fiscal incentive to stay contributing. There a many ways to provide incentives: special attribution/acknowledgements, free stuff, and many others. Keep up the momentum and the ideas. Don't move backward to a no rules model.
>> or groups with similar power.
Yep this is ./ Don tinfoil hats now.
>> with no way to connect if/when it goes down.
Ironically the Internet was supposed to solve that problem. Maybe they simply need multiple Internet connections from different providers and across different mediums: microwave, satellite, dial-up (yuck), pigeon. Expensive.
It' not like IE is open for people to download the nightly builds. I'm sure that Microsoft and its employees compile IE many times even though it might not be on the "nightly build" schedule in the most official sense.
Yes, if they're that paranoid then do due diligence and stuff Firefox into that same virtual machine that IE is running inside for the same reason - then put Google Chrome on your PC computer.
All concerns about NSA and Windows 7 could also be applied to SE Linux http://www.nsa.gov/research/selinux/
Web-based word processors have failed to rise above. So have many other kinds of web-based apps that mimic commonly used standalone apps like spreadsheets, presentation software, development studios - IDEs, paint programs, etc. etc. Most web versions of applications are a poor man's user experience. I know people can come up with exceptions but these are not the norm and likely won't be for a long time. Microsoft is certainly not going out of business because of web-based apps anytime in this dimension.
I doubt their future lies 100% in the cloud - that's just idealism or marketing - shifting public perception to compete with Google and the likes; however the reality is corporations will always want to control their own little part of the cloud, just as many /. people do.
They may cite disapproval with Apple's approval process but the reality the app store is getting diluted with more and more apps and developers, and it's getting tougher to make those million dollar apps. Like anything, the first on board have the best chance of benefiting the most fiscally and in popularity. I assume some of these developers are also getting disillusioned that the glory days are gone.