Thanks for the link, @Araq \-- I think I missed that one when I was reading a number of Nim + Node related posts.
I actually agree with not including nodejs in the core as it's more work and I'm not convinced the right abstractions are in place to really make this work well just yet. I'm noodling on the RFC, there are a bunch of intuitions I've developed around being exposed to this in Haxe but it's not a set of principles that I'd feel comfortable driving an RFC -- I can post what I have here or elsewhere for interested parties Mostly, I'm trying to collect various work in this space to get a shim for the VS Code extension that provides a stdlib look alike API. Either it already exists, is in a few pieces, various states of functioning, or some combination thereof. The ultimate purpose is to make it easier to extract functionality from here and into language servers and other tools as that's where much of this core functionality belongs, the extensionn should be mostly concerned with the interface (reporting, visualization, commands, orchestration, etc...). I'm not sure VS Code is the right thing long term for Nim and I don't want all that good stuff locked behind it too firmly. Heck, someone might want to make a pure browser version and/or use a bunch of it in a desktop or other version and I don't want to make it too hard for them in the long term. Better yet, there might be slices of capabilities that someone finds useful that they want to leverage elsewhere. I'll update my original post with a "manifest" of what I've found and as people turn more tidbits in perhaps that can form a catalog of all this type of work in Nim land.
