News for hackers. Stuff that matters.
Re:Avoid rewriting a legacy system from scratch by stranglin... by mbesto on Tuesday February 18, 2020 @05:50PM (#22361254)
What do you mean?

Technically speaking, you can build software on an outdated and unsupported framework, sure. But why on earth would you, for example, continue building your software on PHP 5.6 (EOL Jan 2019) when anytime a CVE is identified, you're basically SOL in being able to patch it.

Re:Avoid rewriting a legacy system from scratch by stranglin... by detaro on Tuesday February 18, 2020 @06:05PM (#22361379)
Sure, you shouldn't just stick with the old and add features. You should focus an incremental rewrite to bring you closer to a switch to something supported early (e.g. dumping dependencies that won't migrate with you, preparing the code base for a quick conversion of incompatible language features, ...). Only few technologies are such dead-ends that isn't possible.

But once it's too late no migration strategy rids you of the old codebase and it's environment now. With the full rewrite you need to maintain and run it until that's done. With the strangler the old code still runs until it is replaced.

Re:Avoid rewriting a legacy system from scratch by stranglin... by mbesto on Tuesday February 18, 2020 @06:49PM (#22361666)
I'm so confused. What are you suggesting that's any different from what I said?
Re:Avoid rewriting a legacy system from scratch by stranglin... by detaro on Wednesday February 19, 2020 @07:22AM (#22364868)
Apologies, then I must have misunderstood your original comment.
Re:Avoid rewriting a legacy system from scratch by stranglin... by mbesto on Wednesday February 19, 2020 @09:54AM (#22365924)
All good!