Re:Killing Off Wasabi
by tptacek on Thursday June 25, 2015 @02:11PM
(#9779811)
Not sure I follow.
[ Parent
| on HN ]
If you go to the trouble to write your own language, make it not terrible?
Public Abstract Class Animal
Abstract Function Speak() As String
Overridable Function Eat() As String
Return "Yum!"
End Function
End Class
Public Class Dog Inherits Animal
Override Function Speak()
Return "Woof!"
End Function
Override Function Eat()
Return Base.Eat() & " Woof!"
End Function
End Class
http://jacob.jkrall.net/wasabi-the-parts/classes.html#access...It wasn't written that way to facilitate future spaghetti code, but to make sure the old stuff still worked.
Without that, you'd have to rewrite, in which case, why not rewrite in an existing language?
That isn't Classic ASP code, that's more .NET-ish stuff. So it wouldn't have required a rewrite to avoid it, right?
Re:Killing Off Wasabi
by tedunangst on Thursday June 25, 2015 @07:32PM
(#9781589)
That's the ++ in the ASP++. Stock ASP/VB works (or worked) too, but lots of new syntax was added to support .net.
Re:Killing Off Wasabi
by tedunangst on Thursday June 25, 2015 @03:09PM
(#9780214)
Another volunteer to rewrite all the existing ASP code!
He means if they were going to compile to ASP and PHP anyway, they could have at least gone with a better source language than ASP++.
Re:Killing Off Wasabi
by mwcampbell on Thursday June 25, 2015 @02:50PM
(#9780097)
ASP++ Was the path of least resistance given where they started, which was classic ASP and VBScript.
I suspect that many of the armchair critics can't relate to being constrained by decisions made years ago at the start of a project -- decisions that one might now regret but nonetheless constrain the way the codebase can evolve.
The path of least resistance would have been to write the ASP-to-PHP transpiler, check in the PHP, and stop there.
Re:Killing Off Wasabi
by tedunangst on Thursday June 25, 2015 @09:52PM
(#9782076)
That would, at a minimum, have created substantial turbulence on the windows side. Continuing to ship the same windows installer with the same system requirements was less resistance.
I can relate, for sure, but it's not like they'd written a 50 million line operating system in ASP.
At the point you've decide to build a terrible new internal-only language just to maintain a single bug-tracking app codebase ... perhaps you aren't been doing an accurate cost/benefit analysis?
Literally every single person on this thread agrees: if you're going to rewrite code by hand, you wouldn't deploy something like Wasabi. Wasabi exists entirely to facilitate not rewriting.
You've also got several current and former FC'ers on this thread, all? of whom don't like Wasabi as a language, all saying that from a pure cost/benefit perspective, Wasabi paid off.
Re:Killing Off Wasabi
by tedunangst on Thursday June 25, 2015 @07:44PM
(#9781638)
Wasabi is a case study in technical debt. This entire thread is a case study in I wasn't there, but I know more about it than the people who were.
Re:Killing Off Wasabi
by TheOtherHobbes on Thursday June 25, 2015 @09:07PM
(#9781953)
And possibly of Greenspun's Tenth Rule. (Wasabi, not the thread.)
Re:Killing Off Wasabi
by reality_czech on Thursday June 25, 2015 @11:23PM
(#9782309)
s/but/because