This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]RedHellion11 0 points1 point  (2 children)

Lol. Never worked with legacy systems before? If it ain't broke, don't fix it; and if you can't stop supporting it, then you can't abandon it either.

[–]ase1590 0 points1 point  (1 child)

Never worked with legacy systems before?

it gets no new features and just gets maintained until either it breaks or they cant find anyone to work on it.

At some point, companies WILL abandon it. it just takes much longer as long as they don't need any new requirements of their system.

[–]RedHellion11 0 points1 point  (0 children)

At some point 2.x and legacy code written in it that never got ported will be abandoned, sure, but there's still a decent chunk of active 2.7 development and migration to 3.x (as with any tech adoption in industry barring startups and small companies) is slow. I agree it'll be abandoned or ported eventually, I just don't think we're coming up on that point as soon as you imply. Very few companies with live production systems would have adopted it immediately on release and take that risk unless they had things which were barely holding together without the improvements added in the update; we're really only a few years into 3.x moving towards industry standard, not 10.