3 ms·
Honestly, I got so lost in the article that I'm not sure that I understand what the point was. IMO: It was always hard to justify preserving legacy ASP code on
by gwbas1c 7y ago
Honestly, I got so lost in the article that I'm not sure that I understand what the point was.
IMO: It was always hard to justify preserving legacy ASP code once Microsoft made the decision to end-of-life the entire ecosystem. Web development was much newer than, and it was common to completely rewrite web applications in the "language du jour."
IMO: It's also easy to justify "fun" projects like writing your own compiler.
Maybe I'm just being a "Monday Morning Quarterback," but would it have made more sense to build an ASP -> ASP.Net converter as a standalone product?
- jerf 7y ago"Honestly, I got so lost in the article that I'm not sure that I understand what the point was." You're 7 years late to a dead controversy. If you were in the middle of it, it would make a lot more sense as rebuttals to specific complaints made at the time. Since the Internet Does Not Forget, perhaps those complaints will even come back up in this post, in which case the article may make more sense in hindsight. But I'm not going to be the necromancer. If you want to do your own thread necromancy, https://hn.algolia.com/?dateRange=custom&page=0&prefix=true&query=wasabi&sort=byPopularity&type=story https://hn.algolia.com/?dateRange=custom&page=0&prefix=true&... should pretty much get you there, if you ignore the articles that are about the condiment. (And the top one is something else, too; FogCreek Wasabi is a compiler, not a storage platform.)
- sokoloff 7y agoWas part of an ASP->ASP.net conversion project whose project plan amounted to: “load it up in Visual Studio, switch from ASP VB to VB.net, edit until all red underlines are removed from the codebase. Should take 6-12 weeks.” 3 years later, we were almost done.
- thrower123 7y agoI am dreading this transition when it becomes necessary for .NET Framework -> .NET Core. On the surface, it's not too different, but then you look deeper, and here is a dependency that changed completely between it's old Framework version and the new Core one, there's a place that we're using Linq-to-SQL instead of EF, there's an SDK that we use that is never going to be updated to a Core version, etc.
- gwbas1c 7y agoI believe it's coming in .Net 5, if I understand the roadmap correctly. At least it's not a 100% new language skinned to look like the old one!
- stronglikedan 7y agoHaha just be glad the original ASP wasn't created by ASPRunner, and all you have is the source code, like the project I'm currently rewriting.