Quit'your'belly aching. Teachers don't have it so bad.
Teacher salaries are decent for old-timers. Their salaries have nothing to do with performance or capability, but are exactly proportional to years of service. I thought this is the way teacher's like it - $$$ negotiated by union rules, not performance.
And, unlike engineers, teachers get sweet pension plans (most engineers these days don't have more than a 401K).
And, unlike engineers, teachers get much more in the way of vacation (even more than Swedish engineers), and much more in the way of sick time - which by the way, rolls over from year to year. I recall a teacher I know retiring TWO YEARS early due to accumulated sick time.
And I don't by this "40-60" hours a week of lesson plans - how many high school teachers do you remember that were winging it from 10 year old notes - I remember having quite a few?
Responding to the last comment in the parent post:
Actually, JBOSS has led the way in features, with Weblogic playing catch-up.
Versions of BEA WebLogic were fully released to the world before the first line of JBOSS code was even written - so how could JBOSS "lead the way"? (Aspects? *sarcasm*)
most people I know who have used both prefer JBOSS.
True in context, but useless information otherwise. Who are these people? Here is statement that is also true in context, but equally useless: Most people I know that have used both prefer WebLogic. Now here is something harder to argue with: BEA WebLogic's customer list at BEA's website. I invite all and sundry to post a link to comparable list for JBOSS.
Of course JBOSS may have its uses, being free, but it otherwise simply fails to directly match up with *any* commercial app server, not just WebLogic. And the failure is not just in features and customer base, but also in terms of testing, reliability, performance, long term support, J2EE certification, professionalism, and documentation. And these differences, for anyone that bothers to do even a small amount of research, aren't small.
Slashdot Mirror
Quit'your'belly aching. Teachers don't have it so bad.
Teacher salaries are decent for old-timers. Their salaries have nothing to do with performance or capability, but are exactly proportional to years of service. I thought this is the way teacher's like it - $$$ negotiated by union rules, not performance.
And, unlike engineers, teachers get sweet pension plans (most engineers these days don't have more than a 401K).
And, unlike engineers, teachers get much more in the way of vacation (even more than Swedish engineers), and much more in the way of sick time - which by the way, rolls over from year to year. I recall a teacher I know retiring TWO YEARS early due to accumulated sick time.
And I don't by this "40-60" hours a week of lesson plans - how many high school teachers do you remember that were winging it from 10 year old notes - I remember having quite a few?
Responding to the last comment in the parent post:
Actually, JBOSS has led the way in features, with Weblogic playing catch-up.
Versions of BEA WebLogic were fully released to the world before the first line of JBOSS code was even written - so how could JBOSS "lead the way"? (Aspects? *sarcasm*)
most people I know who have used both prefer JBOSS.
True in context, but useless information otherwise. Who are these people? Here is statement that is also true in context, but equally useless: Most people I know that have used both prefer WebLogic. Now here is something harder to argue with: BEA WebLogic's customer list at BEA's website. I invite all and sundry to post a link to comparable list for JBOSS.
Of course JBOSS may have its uses, being free, but it otherwise simply fails to directly match up with *any* commercial app server, not just WebLogic. And the failure is not just in features and customer base, but also in terms of testing, reliability, performance, long term support, J2EE certification, professionalism, and documentation. And these differences, for anyone that bothers to do even a small amount of research, aren't small.