Another incredible MS f@#k-up
-
If any MS buttheads are listening, go see if you can find the incompetent asshole responsible for the 'Windows XP Application Compatibility ANALyzer. This low-grade shareware quality piece of s&%t is supposed to test an app's readiness for inclusion in the 'Windows Catalog'. A do-nothing MFC app (MFC 7.1) causes a number of errors in the Obsolete API category... but that's only a hint of the fun that's about to start. I tried running a non-trivial app with this joke of a test tool. It wouldn't run at all - but not because it failed a compatibility test (no test other than the obsolete API was selected, and the app uses none, except those included in the MFC code). Experiments indicate the reason it wouldn't run is that a folder in the path, and the app name itself, have spaces in them. The 'tool', if one was to so glorify this piece of puke, is apparently unable to deal with this test of programming skills. But wait - that's only the start. Since the failed attempt to run said app under the Compatibility ANALyzer, it now won't run at all. Apparently a registry/system modification is made by the ANALyzer such that all attempts to run said app will log ANALyzer data. But since the ANALyzer is incapable of dealing with a space in the path, it is now impossible to run said app at all - either through the VS.NET 2003 IDE, or even by double clicking the file in Windows Explorer. I removed the app entry from the ANALyzer's list, to no avail. I've uninstalled the ANALyzer and the modifications remain in place. I've searched the likely locations in the registry to try and find the offending entry, with no luck. So not only does the tool not work for s$&t, it now prevents me from (apparently) ever running that app/working on that project again, unless (it seems) I re-format my HD and re-install everything. Oh yeah, I'm going to try that again! Ask me if I f#$%*&g care about inclusion in the goddamn Windows f^^&$#g Catalog!!! At this point, I'm about ready to return the new Visual Studio, Windows XP Pro and every other f&*(@#g thing I've bought from Bill's bunch of boneheads in the last 6 months and begin developing for Linux.
AntiAlias wrote: At this point, I'm about ready to return the new Visual Studio, Windows XP Pro and every other f&*(@#g thing I've bought from Bill's bunch of boneheads in the last 6 months and begin developing for Linux. Do that, and I'm sure you're going to love ddd, (x)emacs, make, rpm (especially this one - it is soooo reliable), tcl/tk, GCC (its compilation speed is great - you'll have plenty of time for browsing the internet). But best of all, you are going to make big bucks :)
-
Psst....look up The Lounge is rated PG. If you're about to post something you wouldn't want your kid sister to read then don't post it. Good Luck with Linux, you've got a HUGE market there. BW "In a world full of people, only some want to fly,Isn't that crazy?" - Seal
brianwelsch wrote: Good Luck with Linux, you've got a HUGE market there. :laugh: Sorry, couldn't resist Rado
-
If any MS buttheads are listening, go see if you can find the incompetent asshole responsible for the 'Windows XP Application Compatibility ANALyzer. This low-grade shareware quality piece of s&%t is supposed to test an app's readiness for inclusion in the 'Windows Catalog'. A do-nothing MFC app (MFC 7.1) causes a number of errors in the Obsolete API category... but that's only a hint of the fun that's about to start. I tried running a non-trivial app with this joke of a test tool. It wouldn't run at all - but not because it failed a compatibility test (no test other than the obsolete API was selected, and the app uses none, except those included in the MFC code). Experiments indicate the reason it wouldn't run is that a folder in the path, and the app name itself, have spaces in them. The 'tool', if one was to so glorify this piece of puke, is apparently unable to deal with this test of programming skills. But wait - that's only the start. Since the failed attempt to run said app under the Compatibility ANALyzer, it now won't run at all. Apparently a registry/system modification is made by the ANALyzer such that all attempts to run said app will log ANALyzer data. But since the ANALyzer is incapable of dealing with a space in the path, it is now impossible to run said app at all - either through the VS.NET 2003 IDE, or even by double clicking the file in Windows Explorer. I removed the app entry from the ANALyzer's list, to no avail. I've uninstalled the ANALyzer and the modifications remain in place. I've searched the likely locations in the registry to try and find the offending entry, with no luck. So not only does the tool not work for s$&t, it now prevents me from (apparently) ever running that app/working on that project again, unless (it seems) I re-format my HD and re-install everything. Oh yeah, I'm going to try that again! Ask me if I f#$%*&g care about inclusion in the goddamn Windows f^^&$#g Catalog!!! At this point, I'm about ready to return the new Visual Studio, Windows XP Pro and every other f&*(@#g thing I've bought from Bill's bunch of boneheads in the last 6 months and begin developing for Linux.
Wow, just what I want to walk in to first thing Monday morning--a profane, obscene post ranting in a most offensive manner. Sorry, but I can't be bothered to filter through the filth and try to get to the actual content of the post (if indeed there is any).
-
If any MS buttheads are listening, go see if you can find the incompetent asshole responsible for the 'Windows XP Application Compatibility ANALyzer. This low-grade shareware quality piece of s&%t is supposed to test an app's readiness for inclusion in the 'Windows Catalog'. A do-nothing MFC app (MFC 7.1) causes a number of errors in the Obsolete API category... but that's only a hint of the fun that's about to start. I tried running a non-trivial app with this joke of a test tool. It wouldn't run at all - but not because it failed a compatibility test (no test other than the obsolete API was selected, and the app uses none, except those included in the MFC code). Experiments indicate the reason it wouldn't run is that a folder in the path, and the app name itself, have spaces in them. The 'tool', if one was to so glorify this piece of puke, is apparently unable to deal with this test of programming skills. But wait - that's only the start. Since the failed attempt to run said app under the Compatibility ANALyzer, it now won't run at all. Apparently a registry/system modification is made by the ANALyzer such that all attempts to run said app will log ANALyzer data. But since the ANALyzer is incapable of dealing with a space in the path, it is now impossible to run said app at all - either through the VS.NET 2003 IDE, or even by double clicking the file in Windows Explorer. I removed the app entry from the ANALyzer's list, to no avail. I've uninstalled the ANALyzer and the modifications remain in place. I've searched the likely locations in the registry to try and find the offending entry, with no luck. So not only does the tool not work for s$&t, it now prevents me from (apparently) ever running that app/working on that project again, unless (it seems) I re-format my HD and re-install everything. Oh yeah, I'm going to try that again! Ask me if I f#$%*&g care about inclusion in the goddamn Windows f^^&$#g Catalog!!! At this point, I'm about ready to return the new Visual Studio, Windows XP Pro and every other f&*(@#g thing I've bought from Bill's bunch of boneheads in the last 6 months and begin developing for Linux.
So, man: What are you complaining about??? Application Compatibility ANALyzer did the job purfectly: Your application is not compatible and will never be included in 'Windows Catalog'. "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me
-
If any MS buttheads are listening, go see if you can find the incompetent asshole responsible for the 'Windows XP Application Compatibility ANALyzer. This low-grade shareware quality piece of s&%t is supposed to test an app's readiness for inclusion in the 'Windows Catalog'. A do-nothing MFC app (MFC 7.1) causes a number of errors in the Obsolete API category... but that's only a hint of the fun that's about to start. I tried running a non-trivial app with this joke of a test tool. It wouldn't run at all - but not because it failed a compatibility test (no test other than the obsolete API was selected, and the app uses none, except those included in the MFC code). Experiments indicate the reason it wouldn't run is that a folder in the path, and the app name itself, have spaces in them. The 'tool', if one was to so glorify this piece of puke, is apparently unable to deal with this test of programming skills. But wait - that's only the start. Since the failed attempt to run said app under the Compatibility ANALyzer, it now won't run at all. Apparently a registry/system modification is made by the ANALyzer such that all attempts to run said app will log ANALyzer data. But since the ANALyzer is incapable of dealing with a space in the path, it is now impossible to run said app at all - either through the VS.NET 2003 IDE, or even by double clicking the file in Windows Explorer. I removed the app entry from the ANALyzer's list, to no avail. I've uninstalled the ANALyzer and the modifications remain in place. I've searched the likely locations in the registry to try and find the offending entry, with no luck. So not only does the tool not work for s$&t, it now prevents me from (apparently) ever running that app/working on that project again, unless (it seems) I re-format my HD and re-install everything. Oh yeah, I'm going to try that again! Ask me if I f#$%*&g care about inclusion in the goddamn Windows f^^&$#g Catalog!!! At this point, I'm about ready to return the new Visual Studio, Windows XP Pro and every other f&*(@#g thing I've bought from Bill's bunch of boneheads in the last 6 months and begin developing for Linux.
Pissing and moaning about Microsoft here is akin to bitching about GWB in a public setting - you're going to get assaulted and probably censored. Remember, your problems are your obviously own making, and never consider that Microsoft is anything but the best. But as usual, the fine folks here miss the whole point of your story, in that the product that ships as part of the development tool and is touted as a feature has totaly screwed up by *not* following the design guidelines in regards to spaces in filenames, and has additional modified your registry settings so that your program can no longer operate. Again, it's much more fun and worthwhile to punish you verbally. Your manager has been notified, and it will go in your permanent record. The fix, aside from deleting this program, is to modify the registry and remove the setting for the specific application name that you're developing that is causing this problem. You might also want to consider making image backups of your system, and in addition, purchase a registry monitering/backup tool that can do daily diffs.
Todd C. Wilson (meme@nopcode.com) NOPcode.com "Flow with whatever may happen and let your mind be free: Stay centered by accepting whatever you are doing. This is the Way." - Chuang-Tzu "Zen in the Martial Arts"
-
Psst....look up The Lounge is rated PG. If you're about to post something you wouldn't want your kid sister to read then don't post it. Good Luck with Linux, you've got a HUGE market there. BW "In a world full of people, only some want to fly,Isn't that crazy?" - Seal
-
If any MS buttheads are listening, go see if you can find the incompetent asshole responsible for the 'Windows XP Application Compatibility ANALyzer. This low-grade shareware quality piece of s&%t is supposed to test an app's readiness for inclusion in the 'Windows Catalog'. A do-nothing MFC app (MFC 7.1) causes a number of errors in the Obsolete API category... but that's only a hint of the fun that's about to start. I tried running a non-trivial app with this joke of a test tool. It wouldn't run at all - but not because it failed a compatibility test (no test other than the obsolete API was selected, and the app uses none, except those included in the MFC code). Experiments indicate the reason it wouldn't run is that a folder in the path, and the app name itself, have spaces in them. The 'tool', if one was to so glorify this piece of puke, is apparently unable to deal with this test of programming skills. But wait - that's only the start. Since the failed attempt to run said app under the Compatibility ANALyzer, it now won't run at all. Apparently a registry/system modification is made by the ANALyzer such that all attempts to run said app will log ANALyzer data. But since the ANALyzer is incapable of dealing with a space in the path, it is now impossible to run said app at all - either through the VS.NET 2003 IDE, or even by double clicking the file in Windows Explorer. I removed the app entry from the ANALyzer's list, to no avail. I've uninstalled the ANALyzer and the modifications remain in place. I've searched the likely locations in the registry to try and find the offending entry, with no luck. So not only does the tool not work for s$&t, it now prevents me from (apparently) ever running that app/working on that project again, unless (it seems) I re-format my HD and re-install everything. Oh yeah, I'm going to try that again! Ask me if I f#$%*&g care about inclusion in the goddamn Windows f^^&$#g Catalog!!! At this point, I'm about ready to return the new Visual Studio, Windows XP Pro and every other f&*(@#g thing I've bought from Bill's bunch of boneheads in the last 6 months and begin developing for Linux.
Have you tried right-clicking the exe and checked to see if the compatibility mode under the compatibility tab has been changed by the tool? You can reset the compatibility mode to see if the app will work again. Good luck!
-
If any MS buttheads are listening, go see if you can find the incompetent asshole responsible for the 'Windows XP Application Compatibility ANALyzer. This low-grade shareware quality piece of s&%t is supposed to test an app's readiness for inclusion in the 'Windows Catalog'. A do-nothing MFC app (MFC 7.1) causes a number of errors in the Obsolete API category... but that's only a hint of the fun that's about to start. I tried running a non-trivial app with this joke of a test tool. It wouldn't run at all - but not because it failed a compatibility test (no test other than the obsolete API was selected, and the app uses none, except those included in the MFC code). Experiments indicate the reason it wouldn't run is that a folder in the path, and the app name itself, have spaces in them. The 'tool', if one was to so glorify this piece of puke, is apparently unable to deal with this test of programming skills. But wait - that's only the start. Since the failed attempt to run said app under the Compatibility ANALyzer, it now won't run at all. Apparently a registry/system modification is made by the ANALyzer such that all attempts to run said app will log ANALyzer data. But since the ANALyzer is incapable of dealing with a space in the path, it is now impossible to run said app at all - either through the VS.NET 2003 IDE, or even by double clicking the file in Windows Explorer. I removed the app entry from the ANALyzer's list, to no avail. I've uninstalled the ANALyzer and the modifications remain in place. I've searched the likely locations in the registry to try and find the offending entry, with no luck. So not only does the tool not work for s$&t, it now prevents me from (apparently) ever running that app/working on that project again, unless (it seems) I re-format my HD and re-install everything. Oh yeah, I'm going to try that again! Ask me if I f#$%*&g care about inclusion in the goddamn Windows f^^&$#g Catalog!!! At this point, I'm about ready to return the new Visual Studio, Windows XP Pro and every other f&*(@#g thing I've bought from Bill's bunch of boneheads in the last 6 months and begin developing for Linux.
-
Pissing and moaning about Microsoft here is akin to bitching about GWB in a public setting - you're going to get assaulted and probably censored. Remember, your problems are your obviously own making, and never consider that Microsoft is anything but the best. But as usual, the fine folks here miss the whole point of your story, in that the product that ships as part of the development tool and is touted as a feature has totaly screwed up by *not* following the design guidelines in regards to spaces in filenames, and has additional modified your registry settings so that your program can no longer operate. Again, it's much more fun and worthwhile to punish you verbally. Your manager has been notified, and it will go in your permanent record. The fix, aside from deleting this program, is to modify the registry and remove the setting for the specific application name that you're developing that is causing this problem. You might also want to consider making image backups of your system, and in addition, purchase a registry monitering/backup tool that can do daily diffs.
Todd C. Wilson (meme@nopcode.com) NOPcode.com "Flow with whatever may happen and let your mind be free: Stay centered by accepting whatever you are doing. This is the Way." - Chuang-Tzu "Zen in the Martial Arts"
He would have gotten a better reception if either A) he moved it to the Soapbox, or B)Kept his anger in check long enough to make people even want to read his post thoroughly, let alone possibly offer up advice for the situation. Todd C. Wilson wrote: But as usual, the fine folks here miss the whole point of your story Well, this will happen to us blind sheep. Bii-i-i-ihhlll (read as Baa-a-aaah) ;) BW "In a world full of people, only some want to fly,Isn't that crazy?" - Seal
-
You're right. It's clearly more important to avoid offending CPers than it is to alert them (albeit a bit stridently) to a buggy dev tool.
-
You're right. It's clearly more important to avoid offending CPers than it is to alert them (albeit a bit stridently) to a buggy dev tool.
Strident? I don't think so. More like 14 year old adolescent with no clue about how to deal with people. Take it to the Soapbox - if you're old enough. Anna :rose: Homepage | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work. Trouble with resource IDs? Try the Resource ID Organiser Visual C++ Add-In
-
He would have gotten a better reception if either A) he moved it to the Soapbox, or B)Kept his anger in check long enough to make people even want to read his post thoroughly, let alone possibly offer up advice for the situation. Todd C. Wilson wrote: But as usual, the fine folks here miss the whole point of your story Well, this will happen to us blind sheep. Bii-i-i-ihhlll (read as Baa-a-aaah) ;) BW "In a world full of people, only some want to fly,Isn't that crazy?" - Seal
-
If any MS buttheads are listening, go see if you can find the incompetent asshole responsible for the 'Windows XP Application Compatibility ANALyzer. This low-grade shareware quality piece of s&%t is supposed to test an app's readiness for inclusion in the 'Windows Catalog'. A do-nothing MFC app (MFC 7.1) causes a number of errors in the Obsolete API category... but that's only a hint of the fun that's about to start. I tried running a non-trivial app with this joke of a test tool. It wouldn't run at all - but not because it failed a compatibility test (no test other than the obsolete API was selected, and the app uses none, except those included in the MFC code). Experiments indicate the reason it wouldn't run is that a folder in the path, and the app name itself, have spaces in them. The 'tool', if one was to so glorify this piece of puke, is apparently unable to deal with this test of programming skills. But wait - that's only the start. Since the failed attempt to run said app under the Compatibility ANALyzer, it now won't run at all. Apparently a registry/system modification is made by the ANALyzer such that all attempts to run said app will log ANALyzer data. But since the ANALyzer is incapable of dealing with a space in the path, it is now impossible to run said app at all - either through the VS.NET 2003 IDE, or even by double clicking the file in Windows Explorer. I removed the app entry from the ANALyzer's list, to no avail. I've uninstalled the ANALyzer and the modifications remain in place. I've searched the likely locations in the registry to try and find the offending entry, with no luck. So not only does the tool not work for s$&t, it now prevents me from (apparently) ever running that app/working on that project again, unless (it seems) I re-format my HD and re-install everything. Oh yeah, I'm going to try that again! Ask me if I f#$%*&g care about inclusion in the goddamn Windows f^^&$#g Catalog!!! At this point, I'm about ready to return the new Visual Studio, Windows XP Pro and every other f&*(@#g thing I've bought from Bill's bunch of boneheads in the last 6 months and begin developing for Linux.
-
If any MS buttheads are listening, go see if you can find the incompetent asshole responsible for the 'Windows XP Application Compatibility ANALyzer. This low-grade shareware quality piece of s&%t is supposed to test an app's readiness for inclusion in the 'Windows Catalog'. A do-nothing MFC app (MFC 7.1) causes a number of errors in the Obsolete API category... but that's only a hint of the fun that's about to start. I tried running a non-trivial app with this joke of a test tool. It wouldn't run at all - but not because it failed a compatibility test (no test other than the obsolete API was selected, and the app uses none, except those included in the MFC code). Experiments indicate the reason it wouldn't run is that a folder in the path, and the app name itself, have spaces in them. The 'tool', if one was to so glorify this piece of puke, is apparently unable to deal with this test of programming skills. But wait - that's only the start. Since the failed attempt to run said app under the Compatibility ANALyzer, it now won't run at all. Apparently a registry/system modification is made by the ANALyzer such that all attempts to run said app will log ANALyzer data. But since the ANALyzer is incapable of dealing with a space in the path, it is now impossible to run said app at all - either through the VS.NET 2003 IDE, or even by double clicking the file in Windows Explorer. I removed the app entry from the ANALyzer's list, to no avail. I've uninstalled the ANALyzer and the modifications remain in place. I've searched the likely locations in the registry to try and find the offending entry, with no luck. So not only does the tool not work for s$&t, it now prevents me from (apparently) ever running that app/working on that project again, unless (it seems) I re-format my HD and re-install everything. Oh yeah, I'm going to try that again! Ask me if I f#$%*&g care about inclusion in the goddamn Windows f^^&$#g Catalog!!! At this point, I'm about ready to return the new Visual Studio, Windows XP Pro and every other f&*(@#g thing I've bought from Bill's bunch of boneheads in the last 6 months and begin developing for Linux.
Contrary to majority here: You've got my 5. And I want MSFT also to hear an outrage from all possible forums (with sister hearing or not) -- quality of latest products coming from MSFT is absolutely unacceptable. For those guys here who have nothing else to do, but to recommend you another forum: Cool down: you are in no position to tell others where is appropriate place for the message: Are you Administrators here? "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me
-
Hey, I dont care about the analyzer or who's fault it is. If its causing you soooo much trouble just stop using it. You seem to literally be in pain about using it, so just dont. If you think linux can do the job better, why *not* use it? Yeah you are obviously frusterated (dont worry, linux will never frusterate you) but a long rant on a primarily windows developers website isnt helping anyone. Either state your problem and ask for help, or just alert people of the true bug. No need for drama. Whats the big deal?
Well put! Matt Newman
Sonork: 100:11179 "Jokes should at least try to be intelligent - this is just toilet humor" - Heath Stewart -
Contrary to majority here: You've got my 5. And I want MSFT also to hear an outrage from all possible forums (with sister hearing or not) -- quality of latest products coming from MSFT is absolutely unacceptable. For those guys here who have nothing else to do, but to recommend you another forum: Cool down: you are in no position to tell others where is appropriate place for the message: Are you Administrators here? "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me
igor1960 wrote: you are in no position to tell others where is appropriate place for the message The guidelines for the Lounge are clearly posted. Matt Newman
Sonork: 100:11179 "Jokes should at least try to be intelligent - this is just toilet humor" - Heath Stewart -
If any MS buttheads are listening, go see if you can find the incompetent asshole responsible for the 'Windows XP Application Compatibility ANALyzer. This low-grade shareware quality piece of s&%t is supposed to test an app's readiness for inclusion in the 'Windows Catalog'. A do-nothing MFC app (MFC 7.1) causes a number of errors in the Obsolete API category... but that's only a hint of the fun that's about to start. I tried running a non-trivial app with this joke of a test tool. It wouldn't run at all - but not because it failed a compatibility test (no test other than the obsolete API was selected, and the app uses none, except those included in the MFC code). Experiments indicate the reason it wouldn't run is that a folder in the path, and the app name itself, have spaces in them. The 'tool', if one was to so glorify this piece of puke, is apparently unable to deal with this test of programming skills. But wait - that's only the start. Since the failed attempt to run said app under the Compatibility ANALyzer, it now won't run at all. Apparently a registry/system modification is made by the ANALyzer such that all attempts to run said app will log ANALyzer data. But since the ANALyzer is incapable of dealing with a space in the path, it is now impossible to run said app at all - either through the VS.NET 2003 IDE, or even by double clicking the file in Windows Explorer. I removed the app entry from the ANALyzer's list, to no avail. I've uninstalled the ANALyzer and the modifications remain in place. I've searched the likely locations in the registry to try and find the offending entry, with no luck. So not only does the tool not work for s$&t, it now prevents me from (apparently) ever running that app/working on that project again, unless (it seems) I re-format my HD and re-install everything. Oh yeah, I'm going to try that again! Ask me if I f#$%*&g care about inclusion in the goddamn Windows f^^&$#g Catalog!!! At this point, I'm about ready to return the new Visual Studio, Windows XP Pro and every other f&*(@#g thing I've bought from Bill's bunch of boneheads in the last 6 months and begin developing for Linux.
Microsoft has rarely held itself accountable for meeting its own logo requirements. Even VS.NET 2003 doesn't install correctly if you choose anything but the destination directory they default to - pathetic. MFC is so horribly antiquated at this point that they'll never get around to removing all of the deprecated API references and other obsolete baggage it has. ATL/WTL is only in slightly better shape. Unfortunately, the alternative is to develop your own framework which is not only time-consuming but likely to eventually suffer from the same problems. There's a word for this phenomenon: "entropy". It affects software just as much as anything else. Jim Lamb Brilliant Labs, Inc. http://brilliantlabs.com/[^]
-
igor1960 wrote: you are in no position to tell others where is appropriate place for the message The guidelines for the Lounge are clearly posted. Matt Newman
Sonork: 100:11179 "Jokes should at least try to be intelligent - this is just toilet humor" - Heath StewartMy Kid Sister is 21? What can't she hear? All foul language is censored so why get your panties in such a bunch over a fellow developer having a very bad day. Take away the fact that this is a public forum where we should be able to vent our frustration ( not be emotionless drones who never get angry ) and this lounge is useless. I'm not saying its the best place for it but i don't think they guy deserved to get verbally raped by the entire community population for venting a bit. Grow up people. My 2 cents. -- Joe Joseph Dempsey joseph_r_dempsey@yahoo.com "What?, Of course its fireproof! ...... < 10 Minutes later in the ER > Sorry..." How about, "Bugs?, of course there are not bugs .... < 3 weeks after Production Release > Sorry..."
-
igor1960 wrote: you are in no position to tell others where is appropriate place for the message The guidelines for the Lounge are clearly posted. Matt Newman
Sonork: 100:11179 "Jokes should at least try to be intelligent - this is just toilet humor" - Heath StewartThe guidelines for the Lounge are clearly posted. Yes. And should it be you to enforce those guidelines? Ever though about different occupation then? "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me
-
My Kid Sister is 21? What can't she hear? All foul language is censored so why get your panties in such a bunch over a fellow developer having a very bad day. Take away the fact that this is a public forum where we should be able to vent our frustration ( not be emotionless drones who never get angry ) and this lounge is useless. I'm not saying its the best place for it but i don't think they guy deserved to get verbally raped by the entire community population for venting a bit. Grow up people. My 2 cents. -- Joe Joseph Dempsey joseph_r_dempsey@yahoo.com "What?, Of course its fireproof! ...... < 10 Minutes later in the ER > Sorry..." How about, "Bugs?, of course there are not bugs .... < 3 weeks after Production Release > Sorry..."
I don't have a sister, let alone a kid sister. But this does not give me the right to stamp on other people's sensitivities. The public forum where you and I are posting messages is community driven, and there are a small number of very simple rules to be followed. The rules are there not to make it hell for us, but to make things as easy and as smooth as possible. I agree that there's a fellow developer who is upset, and needs to vent. But there's a separate forum here for venting and ranting and cussing. The lounge enjoys a very high visibility, and the top few message headlines can even be seen from the homepage. Most of the developers who come to this site also visit the lounge. We need to keep it clean and healthy, because of so many young fellow developers who come here. While we sympathise with the fellow developer in distress, we cannot allow the environment to be spoiled. Let's keep this place so everyone can enjoy it.
Regards,Rohit Sinha
Do not wait for leaders; do it alone, person to person.
- Mother Teresa