4 ms·
Maybe next time you should wait before shooting from the hip with some pointless rant. Other people have already provided some real insight into the issue. It
by melling 13y ago
Maybe next time you should wait before shooting from the hip with some pointless rant.
Other people have already provided some real insight into the issue. It doesn't sound like it's a major issue. Larry just wants people to pay or do the work themselves, if they're going to lag behind on older versions. It costs him extra money and development wasted time. He should make it even more painful so companies must upgrade. When I hear people tell me they're still using Java 1.4, I find it very hard to think they're not being extremely lazy.
- chii 13y ago> they're still using Java 1.4, I find it very hard to think they're not being extremely lazy. or they are running an app that they either don't have the source, or don't have the budget to update.
- lttlrck 13y agoOr don't need to. A decade is not so long.
- wavefunction 13y agoIf you knew me IRL, you'd know that's not my MO (not shooting from the hip with a rant, though there was a point to it, sir) Besides, like you said, there were other people to provide real insight into the issue. My post was just what it was, and you can downvote it accordingly...
- eli 13y agoOld runtime == "extremely lazy"? Who's shooting from the hip now?
- arkitaip 13y ago1.4 was released in 2002. If you haven't updated your code in over a DECADE, you are being incredibly lazy or incompetent.
- lttlrck 13y agoOr you did a good job in 2002.
- icebraining 13y agoOutside the SaaS world, software often runs for much longer than the developer supported period - it's not rare for the software company to go bust way sooner than the software itself.
- nknighthb 13y agoIf the requirements haven't changed, why should the code?
- derleth 13y agoIf the requirements include "keeping time with up-to-date knowledge of time zones without costing us money", guess what, the requirements now mandate a code change. Requirements may not change, but environments do, and continuing to meet requirements in the face of changing environments is something that will often mandate changing code or requirements. When the world shifts, something often has to shift along with it, lest the whole thing break.
- nknighthb 13y agoTime zones are not code, they are data in a defined format that the code is already equipped to handle. Updated time zone data is not a reason to change code.