Re:Ask HN: Have you worked on F# web apps in production?
by siwatanejo on Monday December 20, 2021 @05:07AM
(#29623039)
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.
[ Parent
| on HN ]
Re:Ask HN: Have you worked on F# web apps in production?
by jordanmarr on Monday December 20, 2021 @10:33PM
(#29633520)
For 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.
Re:Ask HN: Have you worked on F# web apps in production?
by siwatanejo on Saturday December 25, 2021 @10:19PM
(#29689358)
Note I advocated to use F# but not Fable. You're assuming in your answer that you need to interoperate with JS, why?
Re:Ask HN: Have you worked on F# web apps in production?
by isaacabraham79 on Tuesday December 28, 2021 @08:01AM
(#29713359)
Because JS is pervasive.
Re:Ask HN: Have you worked on F# web apps in production?
by isaacabraham79 on Tuesday December 28, 2021 @08:02AM
(#29713365)
What are you thinking of when you say "something goes wrong"?
Re:Ask HN: Have you worked on F# web apps in production?
by tunaxor on Monday December 20, 2021 @11:12PM
(#29633771)
When 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
Re:Ask HN: Have you worked on F# web apps in production?
by siwatanejo on Saturday December 25, 2021 @10:19PM
(#29689363)
My point was not comparing Fable vs plain JavaScript, but F# vs Fable.