It's unfortunate that companies try to get increased quotas so they can recruit aliens willing to work for low wages, at the expense of older, experienced American workers who have become "too expensive" in terms of wages and benefits.
You're an anonymous coward, and a troll. I'm an alien, I'm earning more then average American, dare to say I'm getting more than quite a lot of Americans in the field I work. Not because I'm an alien, because I work harder. Even though my employer takes every advantage of me they can think of.
Low wages is a convenient myth for those looking for excuses. The real reason is they're afraid of competition.
You guys (born American) have nothing to lose. I've lost everything when I moved to US and had to start from ground zero when I was more than 30 years old (you were saying something about "older, experienced" people?). Imagine being treated like a 16 years old, with no credit history, no rental history, $2K relocation advance (which I of course! had to pay back) and a family of four.
Hey, I didn't move here because the life is better, but because here it makes sense and has a future. And my kids have a future, too. My 11 year old kid was second is his class, leaving far behind the native English speakers. And this is less than 3 years of speaking English AT ALL.
Bottomline: stop looking for excuses and badmouthing those whose English is as good as yours. Everyone in this country is from someplace else, and this is what makes this country great.
No doubts, Gnome looks slow and unstable in comparison with KDE. But, the funny fact, I'm using neither and staying with good old FVWM. Call me an old-timer, but there's the only thing that prevents me from switching to KDE: limitations on the virtual desktops.
I have 36 of them (6x6 grid) since about 1994, and here's a breakdown:
12 xterms, everything else for Netscape or any other applications.
And believe me, 12 xterms is *almost* enough, and definitely not too many.
But, the KDE supports (supported?) only 8 desktops, and forces me to 4Wx2H grid, instead of giving me a freedom to configure it the way I like.
Gnome does it, but their pager lags for some reason (maybe they thought the lazy redraws makes the apps appear to be faster?) and that is the pain in the neck - the chances of getting lost for 10-15 seconds once in a while are quite real.
So getting back, is it that difficult to implement a flexible desktop layout scheme with a pager that doesn't lag?
VisualAge seems to be The One for the beginner programmers. It seems to help you to organize all your stuff, and do half of the work for you, and keep it neat and clean all the time.
But, as you start having a clue, or even worse, see it first time when you do have a clue, unpleasant surprises await you down the road.
Disclaimer: all the facts below are based on my experience with not the latest version of VA, your mileage may vary.
1. VA doesn't let you control your source code. It enforces its own understanding of how it should look like, specifically:
- Own indentation conventions. It does let you specify the tab size, but all effect of that option is how the code *looks* within VA. If you export your code, it reformats it according to its own preferences, and the version I used didn't care about Javasoft coding standard and just blindly set the indentation to one tab (8 characters), even if you specified the tab size to be 4.
- Method ordering. Sorted alphabetically, which is incredibly stupid. My own preference is to group the methods by relevance. Worse than that, when I imported my code into VA, it rearranged everything.
- Autogenerated javadoc comments for the method signatures. Like, @param p java.lang.String, as if I'm blind and don't see it myself. If I want comments, I put them there, if I don't, I might rely on the fact that javadoc makes a reference to the parent method.
Consequence: the code you produce is not standard, which makes cooperative development difficult. Someone else's code you modify gets screwed up, see below why it's bad.
2. VA provides a poor cooperation with the version control systems. It may be possible, but within a time I could afford to dedicate to that task, it wasn't possible to make it work with CVS, which is a de-facto standard for UNIX. Plus, the abovementioned source code management completely screws up the diffs. And God forbid if your team has some people working with VA, and some other who don't - VA forces everyone to behave as it wants. Classical "Vendor Lock-Up" antipattern.
3. VA provides poor runtime support. The version I used didn't even produce the line numbers in the exception trace. The reason is understandable - it doesn't have the line number concept as such due to its way of maintaining the code, but how do I care? I want to know where it happened. And don't tell me I can use the debugger, because there's no intelligent way to use it in the servlet development in particular and any heavy multithreaded system development in general.
I could ramble on and on, but these facts alone made me deeply despise the VA and I recommended my company to ban it completely.
Of cource, IDE is great for the completely clueless because it allows to replace the "educated decision" pattern to be replaced by "educated guessing", but there's a danger of locking up the mindset to the extent that whomever affected will not be able to even *see* the limitations, save to overcome them.
Do you think that non-participatroy Linux users (people like myself who don't contribute code) would really voluntarily downgrade our Linux experience in order to punish RHAT for some ethical quibble?
Count me in. I recently killed RH6.0 on my other box and installed SuSe. Not for political reasons, but just because it was slow like <censored> and unstable like hell.
The creeping featurisis (one of Antipatterns, if you know what I'm talking about) alone can easily kill it. A recent article about FreeBSD had a point here - if it doesn't work, let the ones who can and want do it, but don't let those who don't know what is 'RTFM', let alone do it, get even close to it.
One of languages that is not native in the North America has a saying: "Never show unfinished work to the fool".
Slashdot Mirror
Low wages is a convenient myth for those looking for excuses. The real reason is they're afraid of competition.
You guys (born American) have nothing to lose. I've lost everything when I moved to US and had to start from ground zero when I was more than 30 years old (you were saying something about "older, experienced" people?). Imagine being treated like a 16 years old, with no credit history, no rental history, $2K relocation advance (which I of course! had to pay back) and a family of four.
Hey, I didn't move here because the life is better, but because here it makes sense and has a future. And my kids have a future, too. My 11 year old kid was second is his class, leaving far behind the native English speakers. And this is less than 3 years of speaking English AT ALL.
Bottomline: stop looking for excuses and badmouthing those whose English is as good as yours. Everyone in this country is from someplace else, and this is what makes this country great.
No doubts, Gnome looks slow and unstable in comparison with KDE. But, the funny fact, I'm using neither and staying with good old FVWM. Call me an old-timer, but there's the only thing that prevents me from switching to KDE: limitations on the virtual desktops.
I have 36 of them (6x6 grid) since about 1994, and here's a breakdown:
12 xterms, everything else for Netscape or any other applications.
And believe me, 12 xterms is *almost* enough, and definitely not too many.
But, the KDE supports (supported?) only 8 desktops, and forces me to 4Wx2H grid, instead of giving me a freedom to configure it the way I like.
Gnome does it, but their pager lags for some reason (maybe they thought the lazy redraws makes the apps appear to be faster?) and that is the pain in the neck - the chances of getting lost for 10-15 seconds once in a while are quite real.
So getting back, is it that difficult to implement a flexible desktop layout scheme with a pager that doesn't lag?
VisualAge seems to be The One for the beginner programmers. It seems to help you to organize all your stuff, and do half of the work for you, and keep it neat and clean all the time.
But, as you start having a clue, or even worse, see it first time when you do have a clue, unpleasant surprises await you down the road.
Disclaimer: all the facts below are based on my experience with not the latest version of VA, your mileage may vary.
1. VA doesn't let you control your source code. It enforces its own understanding of how it should look like, specifically:
- Own indentation conventions. It does let you specify the tab size, but all effect of that option is how the code *looks* within VA. If you export your code, it reformats it according to its own preferences, and the version I used didn't care about Javasoft coding standard and just blindly set the indentation to one tab (8 characters), even if you specified the tab size to be 4.
- Method ordering. Sorted alphabetically, which is incredibly stupid. My own preference is to group the methods by relevance. Worse than that, when I imported my code into VA, it rearranged everything.
- Autogenerated javadoc comments for the method signatures. Like, @param p java.lang.String, as if I'm blind and don't see it myself. If I want comments, I put them there, if I don't, I might rely on the fact that javadoc makes a reference to the parent method.
Consequence: the code you produce is not standard, which makes cooperative development difficult. Someone else's code you modify gets screwed up, see below why it's bad.
2. VA provides a poor cooperation with the version control systems. It may be possible, but within a time I could afford to dedicate to that task, it wasn't possible to make it work with CVS, which is a de-facto standard for UNIX. Plus, the abovementioned source code management completely screws up the diffs. And God forbid if your team has some people working with VA, and some other who don't - VA forces everyone to behave as it wants. Classical "Vendor Lock-Up" antipattern.
3. VA provides poor runtime support. The version I used didn't even produce the line numbers in the exception trace. The reason is understandable - it doesn't have the line number concept as such due to its way of maintaining the code, but how do I care? I want to know where it happened. And don't tell me I can use the debugger, because there's no intelligent way to use it in the servlet development in particular and any heavy multithreaded system development in general.
I could ramble on and on, but these facts alone made me deeply despise the VA and I recommended my company to ban it completely.
Of cource, IDE is great for the completely clueless because it allows to replace the "educated decision" pattern to be replaced by "educated guessing", but there's a danger of locking up the mindset to the extent that whomever affected will not be able to even *see* the limitations, save to overcome them.
Am I the only one who smells sarcasm in this message? Too bad...
The creeping featurisis (one of Antipatterns, if you know what I'm talking about) alone can easily kill it. A recent article about FreeBSD had a point here - if it doesn't work, let the ones who can and want do it, but don't let those who don't know what is 'RTFM', let alone do it, get even close to it.
One of languages that is not native in the North America has a saying: "Never show unfinished work to the fool".