On Wed, 30 Dec 2015 12:33:17 -0800 (PST), Greg Trzeciak <gtrzec...@gmail.com> wrote:
>I am actually more interested with long term viability of Whalesong >than being able to run it right now, hence my questions related to >bootstrapped version (and compiler + expander in Racket). My >current understanding is that outside of narrow use Whalesong is >too risky a bet at least until it becomes selfhosted. I don't see how Whalesong's utility is limited by being dependent on Racket. Self hosted development tools are a convenience but certainly are not necessary ... people have been successfully doing cross development for approximately 75 years. The merits of ubiquitous Javascript aside, *browsers* simply are not designed to run complex guest software: their "process" isolation lies somewhere between lousy and non-existant, and their tasking and event handling ability is very poor wrt native GUIs. [Chrome-OS may solve some of these problems, but few people use it.] I have 5 browsers: IE, Firefox, Chrome, Safari and Edge. Individually and as a group, they are most *unreliable*, crash prone software that I need to use routinely. I would not want to be forced to run a "mission critical" desktop style application under any of them. Server side Javascript is a different issue - mainly because the implementation is better. But Racket works perfectly well for server side development too. YMMV, George -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
