3 ms·
Why depend on Fable? If something goes wrong, you need to hunt some bug in horrible javascript code. I would still use F# but not Fable.
by siwatanejo 5y ago
Why depend on Fable? If something goes wrong, you need to hunt some bug in horrible javascript code. I would still use F# but not Fable.
- isaacabraham79 5y agoWhat are you thinking of when you say "something goes wrong"?
- jordanmarr 5y agoFor the same reason that people depend on TypeScript. The JS output created by Fable is fine to read, and I very rarely, if ever, need to look at it.
- siwatanejo 5y agoNote I advocated to use F# but not Fable. You're assuming in your answer that you need to interoperate with JS, why?
- isaacabraham79 5y agoBecause JS is pervasive.
- tunaxor 5y agoWhen you use better tooling like vite/snowpack the code produced by fable is served as is, and it's really close to the F# sources, the webpack bundle used in development is what looks horrible in reality
- siwatanejo 5y agoMy point was not comparing Fable vs plain JavaScript, but F# vs Fable.