Live data from Hacker News

Ask HN: What are the best web tools to build basic web apps as of October 2016?

news.ycombinator.com

41–50 of 85 posts

Re: Ask HN: What are the best web tools to build basic web apps as of October 2016?

#41
post #9

http://stateofjs.com/ If you're really unpatient, I'll click on the first link for you[0]...which reveals the popular frameworks. This is based on real data since it's a survey, not just one or two comments on HN. [0] http://stateofjs.com/2016/introduction/

Thanks for a great link, but it's only JS – meaning all other backend frameworks were not included in the survey.

Yeah, that is very true unfortunately. I'm really into node though, so js is all I need :)

Re: Ask HN: What are the best web tools to build basic web apps as of October 2016?

#42
post #39

1. I work with Django, Django Rest Framework, React, works well. I heard that Vue might be an interesting option. Honestly there's a myriad of tools/framework around there, you have to ask yourself what are you trying to achieve? Is it a one shot app you'll build over the week end? Something that you'd like to maintain over time? That may scale? Are you working alone on this or not? Is it an exercise to learn a new s…

+1 for http://stackshare.io/

Re: Ask HN: What are the best web tools to build basic web apps as of October 2016?

#45
post #27

I'm going to go out on a limb and suggest this stack (especially if you're into functional programming): Haskell + Elm or PureScript + Postgres The best part about it is that it helps you catch many errors at compile time, instead of having your app crash at run time. For keeping your Haskell and Elm data types in sync while maintaining sanity, I recommend elm-export [0], which will automatically generate the Elm typ…

Thanks for the recommendations. I need to study both Elm (never used it) and PureScript (have just played with it). I am almost ready to publish my first Haskell book (my take on getting started the easy way, with a tutorial for a subset of the language and some cookbook style coding recipes to play with). I am thinking of doing a volume II cookbook that covers web development, and other topics. I use scotty and yeso…

Looking forward to your book! A volume II sounds like a good idea too.

So far I've only used Yesod myself, but Spock looks very promising and I've heard great things about Servant for writing APIs.

Re: Ask HN: What are the best web tools to build basic web apps as of October 2016?

#46
post #45

Earlier quoted context omitted.

Thanks for the recommendations. I need to study both Elm (never used it) and PureScript (have just played with it). I am almost ready to publish my first Haskell book (my take on getting started the easy way, with a tutorial for a subset of the language and some cookbook style coding recipes to play with). I am thinking of doing a volume II cookbook that covers web development, and other topics. I use scotty and yeso…

Looking forward to your book! A volume II sounds like a good idea too. So far I've only used Yesod myself, but Spock looks very promising and I've heard great things about Servant for writing APIs.

Servant looks great. I have only spent a few hours playing with it, but from what I have seen, I like it.

Re: Ask HN: What are the best web tools to build basic web apps as of October 2016?

#50
post #45

Earlier quoted context omitted.

Looking forward to your book! A volume II sounds like a good idea too. So far I've only used Yesod myself, but Spock looks very promising and I've heard great things about Servant for writing APIs.

Servant looks great. I have only spent a few hours playing with it, but from what I have seen, I like it.

Servant is still _very_ rough around the edges, imo. I like it a lot for mocking APIs [0], but I'd be wary about using it in production for anything other than a small service.

Right now I'm keeping an eye on servant-auth [1] and the GHCJS implementation of servant-client [2], as they're both extremely compelling.

[0] Recently, I needed to test something against a work-in-progress API. I wrote out a rough type-level specification and had servant-quickcheck generate arbitrary data. When I needed to test more concrete data, it was trivial to incrementally move endpoints over to concretely defined stubs.

[1] https://github.com/plow-technologies/servant-auth

[2] https://github.com/LumiGuide/servant/tree/client-ghcjs

Post reply on HN