rs_al

We use java. So theoretically we'll have to upgrade to the latest jdk to get the changes (although hopefully sun might ship it as a patch, which will be great). Upgrading the jdk is not something we take lightly. In the last two years we've done it once.

We won't need to re-code. But we'll need to re-verify our software on the new JDK. The next version will start in a few months. We'll need to test that version exclusively with the new jdk. Then we ship, maybe around may or june. Our customers will get it, but then we have to convince them to upgrade- that's the hard part. They've only got a few months left at this point, and upgrading is usually something they do over the course of a year or two or more. As it is, we rolled out the most recent jdk change over a year and a half ago, and there's still plenty of customers who haven't upgraded past that yet, and we've only got a year and a half to get the next one out.

More than likely, we may have to re-certify old releases on the new jdk. I know it doesn't sound too scary, "ooh jdk version", but in the past we tried to upgrade the jre browser plugin (for a swing interface) from 1.3.1_09 to 1.3.1_11. It fixed a bug we had encountered in _09, but introduced an even nastier bug where our graphs in our monitor console didn't show the latest hour of activity- so we rolled back to _09.

Our software has lots of scheduling. An hour off here or there could delay shipments by days if it doesn't line up on the calendars correctly. The software also schedules service appointments (like in-home delivery or installation). An hour there could mean an end-user gets promised a 9:00 appointment with the installer and the installer shows up at 8:00 instead - maybe the guy isn't even home or the business not opened. On a case-by-case basis, they're minor at best but these things can quickly add up into thousands of dollars of lost revenue. Considering the average American could hope to save about 10 cents or so over the course of the year, it's hard to see the savings.

And as far as the chain of command stuff goes - no. Just wrong. You don't get high up on the ladder by making up stupid ideas and just telling people to do them, except in politics appearently, but that's because you get groupies who do anything you say because you have the same party affiliation. In real life you don't have the "USA USA #1" factor, and your boss can get fired just the same as you.

Buck Fush

[quote==DdogG=]all this because of a clock?

really... the point is that some of you are freaking out over a minute change in routine 2 years from now.... seriously, if you REALLY knew what you were talking about, you would not be so paranoid about the change. It is not a big deal.
QUOTE]

You have obviously never supported a legacy application that (At least in my situation.) is installed mostly on unsupported OS's. I have 200 remote users with 60% of them on Win98. MS no longer supports 98, so I'll have no patch from them. This isn't the end of the world, but it really sucks.



I work 70 - 80 hours a week. If that's lazy by your standards, then you're a workaholic.

jex

What was point No.2 again?

Aaah I see why the change needs to be made...


Oooh and No.6

__________________
Jex