Earlier quoted context omitted.
There should be a concept called "engineering privilege". I see some companies do things that are widely out of their core product and engineers there just having fun with a bunch of different stuff with seemingly no commitment to bring in revenue. They'll re-invent/re-write things constantly, write a new compiler/package manager for their chosen language, create new frameworks, new open source projects unrelated to…
My favorite example was from Joel Spolsky's company, where bright engineers got bored with working on bug tracking software so they wrote their own C# compiler.
It may seem weird nowadays but at the time it made sense since wasabi was "transpiling" VBScript (on which their existing codebase was written since they were all into Microsoft products at the time) to other languages in environments where VBScript didn't exist (e.g. IIRC they could transpile to PHP - and there isn't "one" PHP).
They were basically making shrink-wrap software running on an environment (the web) that wasn't made for shrink-wrap software (especially at the time) and came up with a technical solution to it.
FWIW they weren't the only to attempt something like that. HaXe is basically the same idea and was used to port a ton of games from Flash to all sorts of platforms and Monkey was another similar attempt (i think most people aren't aware of these two because they were gaming related and really limited to indie games).