3 ms·

Mostly a lack of good web frameworks which are performant and have good devex. Jester the main Nim framework doesn't even have a webpage and that doesn't inspir

Mostly a lack of good web frameworks which are performant and have good devex. Jester the main Nim framework doesn't even have a webpage and that doesn't inspires any confidence. Httpbeast may be fast but it feels like just a PoC. It doesn't even have docs. Prologue is the most promising one IMO, but it is still very new and its performance isn't as good. But I do keep a check on it. Overall, Nim needs something like Lucky, Athena, Azu Toolkit etc to feel like a serious web dev language. That said, I have always been thinking of rolling with just the stdlib stuff so I may do that one of these days.

dom96 5y ago
Author of Jester here. I agree that a nice website would be great to have for Jester (and I do intend to create one), but I think you place far too much importance on Jester having one. Jester/HttpBeast is used in production by big web apps[1], why doesn't this inspire enough confidence and possibly even more than the other web frameworks you've mentioned? I think there is an inherent bias that all humans have for shiny design, you should definitely keep it in mind when choosing a technology. 1 - https://forum.nim-lang.org/ https://forum.nim-lang.org/
- ziotom78 5y ago
  I understand that it is frustrating to hear somebody telling you that they lack confidence in your tool simply because it «lacks a webpage», maybe after you have spent so much time creating and polishing it! However, considering the huge amount of languages/webframework pairs (D+Vibe? Nim+Jester? Crystal+Whatever? Go? Rust? etc.) available today, it is understandable that people pick simple criteria like this to decimate their number of choices. The alternative to start playing with each tool for a few days to rank them and pick the best choice is obviously not possible.

3 ms·

Mostly a lack of good web frameworks which are performant and have good devex. Jester the main Nim framework doesn't even have a webpage and that doesn't inspir

by rishav_sharan 5y ago

dom96 5y ago
Author of Jester here. I agree that a nice website would be great to have for Jester (and I do intend to create one), but I think you place far too much importance on Jester having one. Jester/HttpBeast is used in production by big web apps[1], why doesn't this inspire enough confidence and possibly even more than the other web frameworks you've mentioned? I think there is an inherent bias that all humans have for shiny design, you should definitely keep it in mind when choosing a technology. 1 - https://forum.nim-lang.org/ https://forum.nim-lang.org/
- ziotom78 5y ago
  I understand that it is frustrating to hear somebody telling you that they lack confidence in your tool simply because it «lacks a webpage», maybe after you have spent so much time creating and polishing it! However, considering the huge amount of languages/webframework pairs (D+Vibe? Nim+Jester? Crystal+Whatever? Go? Rust? etc.) available today, it is understandable that people pick simple criteria like this to decimate their number of choices. The alternative to start playing with each tool for a few days to rank them and pick the best choice is obviously not possible.