Comments for AeroXperience http://www.aeroxp.org Windows Enthusiast Community Sat, 07 Nov 2009 18:36:20 +0000 http://wordpress.org/?v=2.6.2 Comment on The Effects of Leaks: A Candid Interview by nexus http://www.aeroxp.org/2009/10/the-effects-of-leaks/#comment-2436 nexus Mon, 02 Nov 2009 18:50:06 +0000 http://www.aeroxp.org/?p=1239#comment-2436 you know it sounds like he would be more ok with it happening (but its never really 'right') If people wouldnt bother him or the rest of microsoft for info/deets/etc. Each time a leak happens. If people would wise up and remember that a leak doesnt come with any express garentees or support and NOT bother MS at all, then it sounds like this source and the rest of microsoft would be happier, but people cant establish that. Its as if a physical brick wall needs to go up and seal off microsoft so they wont be bothered each time a leak hits the tubes. We all know leaks hurt a company and this basically wasnt anything we didnt know, but now is reinforced because it comes from the horses mouth. To me the source of this story could also make his life a bit easier by establishing an unwritten 'law' that says to all who question me about an unsacntioned build I will hang up on you or ignore your emails, txt, etc. By sticking to such a 'law' he wouldnt be feeding the animals and they wouldnt keep coming back, so to speak. I do however understand its not just that easy in most cases, but thats a good start to put into place when you can. To the greedy public who is going to get a leak no matter how tight the iron fist: Appreciate you got anything, because you luck says you didnt have to, and be quite appreciate it for what it is, if its broke its broke, and DO NOT bother them and let them carry on their work. If you have sources or what not in a company and you get a leak (from the tubes) dont bother that source for deets or info on what has leaked. Let him or her do their job. Also to the greedy public now can you see why sinofsky doesnt want the public or beta testers to have more than just the beta and the RC? Do you see why office never had intermin milestone release? this is exactly why. you know it sounds like he would be more ok with it happening (but its never really ‘right’) If people wouldnt bother him or the rest of microsoft for info/deets/etc. Each time a leak happens. If people would wise up and remember that a leak doesnt come with any express garentees or support and NOT bother MS at all, then it sounds like this source and the rest of microsoft would be happier, but people cant establish that. Its as if a physical brick wall needs to go up and seal off microsoft so they wont be bothered each time a leak hits the tubes.

We all know leaks hurt a company and this basically wasnt anything we didnt know, but now is reinforced because it comes from the horses mouth. To me the source of this story could also make his life a bit easier by establishing an unwritten ‘law’ that says to all who question me about an unsacntioned build I will hang up on you or ignore your emails, txt, etc. By sticking to such a ‘law’ he wouldnt be feeding the animals and they wouldnt keep coming back, so to speak. I do however understand its not just that easy in most cases, but thats a good start to put into place when you can.

To the greedy public who is going to get a leak no matter how tight the iron fist: Appreciate you got anything, because you luck says you didnt have to, and be quite appreciate it for what it is, if its broke its broke, and DO NOT bother them and let them carry on their work. If you have sources or what not in a company and you get a leak (from the tubes) dont bother that source for deets or info on what has leaked. Let him or her do their job.
Also to the greedy public now can you see why sinofsky doesnt want the public or beta testers to have more than just the beta and the RC? Do you see why office never had intermin milestone release? this is exactly why.

]]> Comment on The Effects of Leaks: A Candid Interview by stitch http://www.aeroxp.org/2009/10/the-effects-of-leaks/#comment-2435 stitch Mon, 02 Nov 2009 05:10:59 +0000 http://www.aeroxp.org/?p=1239#comment-2435 All of you kids need to redirect your hate towards this MSFT developer to /dev/null because it's just pure bullshit that makes me hope you get hit by a bus. As he said, most of these leaks are obtained from 3rd parties, which is called piracy. Which is you know, illegal? While I don't support it at all I'm not against it in certain ways[1]. These builds spread faster than genital warts and then that's when rumors start, all because some bored kids wanted to be able to show off. While certain employees should be holding up to their NDA (which at most other places, you breach it and your ass is gone), I don't entirely blame them like I blame bored kids who want some e-Bling. I personally have nothing to do with any pre release stuff of anything unless i directly need it for $REASON and I have legitimate access to it, if I want something to show off I have a good looking girlfriend for that, who I have sex with, lots of sex. [1]: http://www.eff.org/cases/capitol-v-thomas All of you kids need to redirect your hate towards this MSFT developer to /dev/null because it’s just pure bullshit that makes me hope you get hit by a bus.

As he said, most of these leaks are obtained from 3rd parties, which is called piracy. Which is you know, illegal? While I don’t support it at all I’m not against it in certain ways[1]. These builds spread faster than genital warts and then that’s when rumors start, all because some bored kids wanted to be able to show off. While certain employees should be holding up to their NDA (which at most other places, you breach it and your ass is gone), I don’t entirely blame them like I blame bored kids who want some e-Bling. I personally have nothing to do with any pre release stuff of anything unless i directly need it for $REASON and I have legitimate access to it, if I want something to show off I have a good looking girlfriend for that, who I have sex with, lots of sex.

[1]: http://www.eff.org/cases/capitol-v-thomas

]]> Comment on The Effects of Leaks: A Candid Interview by Roknrol http://www.aeroxp.org/2009/10/the-effects-of-leaks/#comment-2417 Roknrol Mon, 26 Oct 2009 23:48:29 +0000 http://www.aeroxp.org/?p=1239#comment-2417 The ridiculous thing is that M$ can fix the majority of their own problems with the review/release process simply by doing what other companies already do: Apple doesn't seem to have much of a problem with leaks, so maybe M$ is hiring people (qualified people, no doubt) that maybe can't be trusted to be involved in the Development process. Beyond that, pretty much anyone that downloads/installs Alpha/Beta releases understands that they are not Final Builds. Yes, you get some people that don't know the difference, but by and large most computer users aren't even interested in the "next best thing". I agree with the earlier poster that mentioned the M$ $pin that they can't put on their software when there's been a leak. Unfortunately, for M$, they've made it a habit of releasing software that had no business being released as a "Final Build" in the past. They've done it ENOUGH times in the past to make IT people a bit nervous about the next "great" OS coming out of Redmond. Speaking from a Support perspective, knowing full well that your bosses wife is going to insist on installing the latest and greatest and that you'll have to support the new OS when it's released is a freaking nightmare...and it's all compounded by M$'s SOPs, which are desperately in need of a review. The ridiculous thing is that M$ can fix the majority of their own problems with the review/release process simply by doing what other companies already do: Apple doesn’t seem to have much of a problem with leaks, so maybe M$ is hiring people (qualified people, no doubt) that maybe can’t be trusted to be involved in the Development process.

Beyond that, pretty much anyone that downloads/installs Alpha/Beta releases understands that they are not Final Builds. Yes, you get some people that don’t know the difference, but by and large most computer users aren’t even interested in the “next best thing”. I agree with the earlier poster that mentioned the M$ $pin that they can’t put on their software when there’s been a leak. Unfortunately, for M$, they’ve made it a habit of releasing software that had no business being released as a “Final Build” in the past. They’ve done it ENOUGH times in the past to make IT people a bit nervous about the next “great” OS coming out of Redmond. Speaking from a Support perspective, knowing full well that your bosses wife is going to insist on installing the latest and greatest and that you’ll have to support the new OS when it’s released is a freaking nightmare…and it’s all compounded by M$’s SOPs, which are desperately in need of a review.

]]> Comment on Internet Explorer 8 can be removed from Windows 7 by Julie http://www.aeroxp.org/2009/03/ie8-functionally-removable/#comment-2410 Julie Mon, 26 Oct 2009 15:05:02 +0000 http://www.aeroxp.org/?p=912#comment-2410 It does not uninstall Internet Explorer 8 it only shuts it down. You cannot install Explorer 6 or 7 in Windows xp Mode because it says 8 is still there. It just shuts it off. It does not uninstall Internet Explorer 8 it only shuts it down. You cannot install Explorer 6 or 7 in Windows xp Mode because it says 8 is still there. It just shuts it off.

]]> Comment on The Effects of Leaks: A Candid Interview by Jan Schotsmans http://www.aeroxp.org/2009/10/the-effects-of-leaks/#comment-2407 Jan Schotsmans Mon, 26 Oct 2009 14:23:20 +0000 http://www.aeroxp.org/?p=1239#comment-2407 Hrm, anyone notice: "that was an unplanned leak" Is someone validating what I've been saying about the funky stuff even Microsoft pulls? Hrm, anyone notice:

“that was an unplanned leak”

Is someone validating what I’ve been saying about the funky stuff even Microsoft pulls?

]]> Comment on The Effects of Leaks: A Candid Interview by Name Required http://www.aeroxp.org/2009/10/the-effects-of-leaks/#comment-2400 Name Required Mon, 26 Oct 2009 12:50:13 +0000 http://www.aeroxp.org/?p=1239#comment-2400 If I read one more "you know" I may just throw someone out the window. If I read one more “you know” I may just throw someone out the window.

]]> Comment on The Effects of Leaks: A Candid Interview by reso http://www.aeroxp.org/2009/10/the-effects-of-leaks/#comment-2386 reso Mon, 26 Oct 2009 06:08:19 +0000 http://www.aeroxp.org/?p=1239#comment-2386 you know, i really found this article to be educational also, because i've seen it before where someone will post a leak of some sort, a leaked build, or leaked screen shots, something leaked, and they will say 'wow look it's so rough man this will be the worst most horrible experience ever' or 'look they cut this essential feature out it will be horrible' or 'look how sloppy everything is!'. from what i read of this dev's statements, he sounds like me when i'm working on anything, from my car to my computer. if an outsider peeked in and looked at it all while i'm in the middle it may look really sloppy. dirt all over, parts strew right and left, half of it doesn't even work, and i myself am just sloppy and dirty. dust on my nose, smudges on my glasses, grease on my hands. it really presents the idea that i am just a slob and also that the finished product will be horribly broken. of course, that is the not the case. i just need to get dirty and make a mess to get anywhere sometimes. i may wind up taking whole sections of my computer or car out and botching something together just to test something. it doesnt' look good at all, but it's just part of the process. when i'm done, it will be functional. it will work. it will in fact even look nice, but i have my process to work in and if you step into that while i'm busy and you don't know what is going on in my head, you won't be impressed. so please, save the hating on this dev for someone else. i'm glad he said something. it helps put these negative reviews of various Windows leaked builds (or WIP builds of anything really) in perspective. important things to realise i figure. thanks, anonymous dev. you know, i really found this article to be educational also, because i’ve seen it before where someone will post a leak of some sort, a leaked build, or leaked screen shots, something leaked, and they will say ‘wow look it’s so rough man this will be the worst most horrible experience ever’ or ‘look they cut this essential feature out it will be horrible’ or ‘look how sloppy everything is!’. from what i read of this dev’s statements, he sounds like me when i’m working on anything, from my car to my computer. if an outsider peeked in and looked at it all while i’m in the middle it may look really sloppy. dirt all over, parts strew right and left, half of it doesn’t even work, and i myself am just sloppy and dirty. dust on my nose, smudges on my glasses, grease on my hands. it really presents the idea that i am just a slob and also that the finished product will be horribly broken.

of course, that is the not the case. i just need to get dirty and make a mess to get anywhere sometimes. i may wind up taking whole sections of my computer or car out and botching something together just to test something. it doesnt’ look good at all, but it’s just part of the process. when i’m done, it will be functional. it will work. it will in fact even look nice, but i have my process to work in and if you step into that while i’m busy and you don’t know what is going on in my head, you won’t be impressed.

so please, save the hating on this dev for someone else. i’m glad he said something. it helps put these negative reviews of various Windows leaked builds (or WIP builds of anything really) in perspective. important things to realise i figure.

thanks, anonymous dev.

]]> Comment on The Effects of Leaks: A Candid Interview by NR http://www.aeroxp.org/2009/10/the-effects-of-leaks/#comment-2384 NR Mon, 26 Oct 2009 05:20:39 +0000 http://www.aeroxp.org/?p=1239#comment-2384 The way I see it is this: A company doesn't like leaks because then information is released without the ability for PR to put their unique "spin" on it, to downgrade the flaws and talk up the major points. Yes, in some instances you will have an incomplete view of the big picture, but allowing speculation is part of what makes the web such a marvel of modern man. We are connected in a way that all of our input can and very well may be considered on a specific topic, and what the leaked build (or info) "may become" or what it is presently is no different. In fact, leaked builds can lead to additional functionality that the finalized product would have never had, in some cases, because the community as a whole is able to look at the unfinished picture and paint another "use" for the product. All of this would never have happened if the "this is what the product is, and only is, and ignore this over here" was ever released about the product. This right here is precisely why the proprietary model should be put down like a sick dog, and open source models of business should be embraced. The way I see it is this: A company doesn’t like leaks because then information is released without the ability for PR to put their unique “spin” on it, to downgrade the flaws and talk up the major points. Yes, in some instances you will have an incomplete view of the big picture, but allowing speculation is part of what makes the web such a marvel of modern man. We are connected in a way that all of our input can and very well may be considered on a specific topic, and what the leaked build (or info) “may become” or what it is presently is no different. In fact, leaked builds can lead to additional functionality that the finalized product would have never had, in some cases, because the community as a whole is able to look at the unfinished picture and paint another “use” for the product.

All of this would never have happened if the “this is what the product is, and only is, and ignore this over here” was ever released about the product. This right here is precisely why the proprietary model should be put down like a sick dog, and open source models of business should be embraced.

]]> Comment on The Effects of Leaks: A Candid Interview by Dave http://www.aeroxp.org/2009/10/the-effects-of-leaks/#comment-2372 Dave Mon, 26 Oct 2009 01:00:24 +0000 http://www.aeroxp.org/?p=1239#comment-2372 Cool article. I never really thought about what the software vendor's feel about the leaks - I just assumed it was mostly their own marketing (any publicity is good publicity, you know what I'm saying?) but I guess this isn't what the marketing department wants, really. Not a long read - but an educational one. Cool article. I never really thought about what the software vendor’s feel about the leaks - I just assumed it was mostly their own marketing (any publicity is good publicity, you know what I’m saying?) but I guess this isn’t what the marketing department wants, really.

Not a long read - but an educational one.

]]> Comment on The Effects of Leaks: A Candid Interview by Jason http://www.aeroxp.org/2009/10/the-effects-of-leaks/#comment-2370 Jason Mon, 26 Oct 2009 00:39:22 +0000 http://www.aeroxp.org/?p=1239#comment-2370 Kevin, the guy gives the impression that he's fine with doing his job but wouldn't mind his job being made a little bit easier. Everyone wishes the same whenever the opportunity presents itself. It's an anonymous interview, and the odds of this guy being found out are basically nil. He can vent his frustrations if there's little risk of being caught, and I would too. Kevin, the guy gives the impression that he’s fine with doing his job but wouldn’t mind his job being made a little bit easier. Everyone wishes the same whenever the opportunity presents itself.

It’s an anonymous interview, and the odds of this guy being found out are basically nil. He can vent his frustrations if there’s little risk of being caught, and I would too.

]]>