3 ms·
Flow + OCaml is a great example of this approach failing IMHO. I ran into tons of issues that were difficult to debug myself, and things like the regex format a
by vaughan 6y ago
Flow + OCaml is a great example of this approach failing IMHO. I ran into tons of issues that were difficult to debug myself, and things like the regex format and config file conventions being different were also problematic. Compile times are also annoying.
Something undervalued is the debuggability of using a single language. There are so many times I need to debug some tooling, and being able to to just open the stack trace and place a breakpoint/console.log is incredibly valuable. I do it all the time for webpack/babel.
Having to switch to a new toolchain to debug something is tedious, and often impossible to reach the same convenience of JS-based tools.
I think the future is taking small pieces of JS-based tools and adding native extensions to speed up parts of them.
- q3k 6y ago> being able to to just open the stack trace and place a breakpoint/console.log is incredibly valuable. I do it all the time for webpack/babel. This is something I achieve by using multi-languge-aware build systems and/or vendoring. I can then add a log statement to a compiler implemented in C which emits binary shader code that in turn gets parsed by Rust, and immediately see results after running the usual test target. No need to limit myself to a single language.
- xwolfi 6y agoHehehe
- sime2009 6y ago> There are so many times I need to debug some tooling, and being able to to just open the stack trace and place a breakpoint/console.log is incredibly valuable. I do it all the time for webpack/babel. That sounds more like an indictment of Webpack than anything else.
- brundolf 6y agoI'm not sure what kind of exotic stuff GP is doing but I've never had to do anything like this with webpack or babel