Beautiful. Minor feedback: rather than having a "use golang" directive, just allow imports of .go files. This is more idiomatic for JS bundlers.
Beautiful. Minor feedback: rather than having a "use golang" directive, just allow imports of .go files. This is more idiomatic for JS bundlers.
That would also avoid the problem with this syntax, that it's not a valid Go file (it doesn't start with `package ...` and I don't think a bare top-level string is valid), which lots of editors will be pretty unhappy about.
Definitely not a minor feedback, there's no reason to write go in a .js file. Vite/rollup are perfectly able to "load" certain file types and parse them however you like.
There’s no reason to unilaterally dismiss others use cases, this debate is as old as ReactJS (mixed JS and HTML).
Modern tools often make this tradeoff, like Astro, and none of the tools authors are claiming you need to use the tool.
Yes, the pattern can be abused, but dogmatic rules against mixing languages may also entail downsides.
I stand firm that there's no reason to write go in a .js file other than ragebaiting, especially with that "use" directive that clearly everyone is hating on Twitter at the moment (due to Vercel, etc)
To be clear I'm fine with importing .go from JS, it's the "go in file.js" thing I don't like.
Should also help with syntax highlighting.