Before rich client/ajax took off, it was more than adequate for most e-commerce, web publishing, and internal administrative applications. Truth be told, it still is, but it's just soooo 2001.
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...Without that, you'd have to rewrite, in which case, why not rewrite in an existing language?
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.
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?
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.
http://jacob.jkrall.net/wasabi-the-parts/a_first_program.htm...