3 ms·

It's easier developing for the web, where your code is less likely to break or require drastic changes over time. But yes, almost all businesses need at least s

It's easier developing for the web, where your code is less likely to break or require drastic changes over time. But yes, almost all businesses need at least some ongoing maintenance.

Aloha 8y ago
Try running a PHP app from 2008, today, and let me know how that works for you. There are decent odds it wont run well on modern versions - I can go down and look at every other web technology and point out the same thing - no computer program lives in stasis (except possible on z/OS)
- rpeden 8y ago
  OTOH, an ASP.NET web app written in 2008 and not touched since then would probably still run happily now if you bumped its version up to .NET 4 or 4.5. C# has had Linq and lambdas since 2007 so there's a decent chance the code would be decently pleasant to work with, too. Some devs might find 2008 Web Forms apps a bit crufty in 2018 but if you squint and pretend your .aspx is inside a render method issued of a separate file, the mental model isn't all that different from a SPA.
  - cm2187 8y ago
    With .net core the writing is on the wall that the full .net framework will go the way of .net 1.1 (the .net team highlighted that it is too burdensome to maintain both frameworks in parallel). I am not sure that the new Microsoft has the same commitment to support legacy code than the Microsoft of the last 20 years.
    - oldmanhorton 8y ago
      They've made it clear that .NET Framework will be supported for many, many years. It just won't be getting as many new features. The point of the discussion here is about depreciating and removing and breaking existing tech, which will almost certainly not happen with .NET anything. Note that even VBScript still gets security updates. It's unimaginable that anything targeting .NET Framework will break (short of a bug) for at least a decade, and probably much longer.
- cwyers 8y ago
  That's still just one runtime needing support at a time. OS upgrades happen in waves, and at a cadence you don't choose. Hosted server products, you choose when to update the server stack and you can stop supporting older versions.
z3t4 8y ago
for static semantic html its stable. but for dynamic web sites with JavaScript there can be breaking changes. it can get tricky when you do hacky stuff in order to support all platform and older browsers.

It's easier developing for the web, where your code is less likely to break or require drastic changes over time. But yes, almost all businesses need at least some ongoing maintenance.

Aloha 8y ago

Try running a PHP app from 2008, today, and let me know how that works for you. There are decent odds it wont run well on modern versions - I can go down and look at every other web technology and point out the same thing - no computer program lives in stasis (except possible on z/OS)

rpeden 8y ago
OTOH, an ASP.NET web app written in 2008 and not touched since then would probably still run happily now if you bumped its version up to .NET 4 or 4.5. C# has had Linq and lambdas since 2007 so there's a decent chance the code would be decently pleasant to work with, too. Some devs might find 2008 Web Forms apps a bit crufty in 2018 but if you squint and pretend your .aspx is inside a render method issued of a separate file, the mental model isn't all that different from a SPA.
- cm2187 8y ago
  With .net core the writing is on the wall that the full .net framework will go the way of .net 1.1 (the .net team highlighted that it is too burdensome to maintain both frameworks in parallel). I am not sure that the new Microsoft has the same commitment to support legacy code than the Microsoft of the last 20 years.
  - oldmanhorton 8y ago
    They've made it clear that .NET Framework will be supported for many, many years. It just won't be getting as many new features. The point of the discussion here is about depreciating and removing and breaking existing tech, which will almost certainly not happen with .NET anything. Note that even VBScript still gets security updates. It's unimaginable that anything targeting .NET Framework will break (short of a bug) for at least a decade, and probably much longer.
cwyers 8y ago
That's still just one runtime needing support at a time. OS upgrades happen in waves, and at a cadence you don't choose. Hosted server products, you choose when to update the server stack and you can stop supporting older versions.

z3t4 8y ago

for static semantic html its stable. but for dynamic web sites with JavaScript there can be breaking changes. it can get tricky when you do hacky stuff in order to support all platform and older browsers.