he/him 
@sebmck in Rome, have you abstracted away the 'host environment' in any way to make the toolchain available in contexts like the browser? Certainly would be amazing to have a tight, UX friendly ecosystem like that in the browser.
Yeah, enough is abstracted that it could work outside of Node. I’ve minimised my usage of Node APIs. There’s abstractions around the parts they matter. In fact, it would be easy to make Rome has WebWorkers for workers instead of spawning processes. The RPC is very agnostic.
-
-
Could also prettily run in Deno then?
-
Potentially*
- 7 more replies
New conversation -
-
-
I'm hoping for one cohesive toolchain to 'rule them all'. These days 'JavasScript' means so many different things: - ES201X - JSX? - TypeScript? - Of course I can import css! And less, and sass but sometimes as modules, or not. - .vue! - Node standard library or browser? -
-
When building higher level tools for a wide audience of developers across different frameworks, the permutations become impossible to follow. Each tool builds upon existing foundations and expectations that further partition expectations. Very few can be hooked without forking.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.