20 ms·
None of them are actually too good IMO. They are either super opinionated or don't remove the pain points in common web dev. Still waiting for something like E
by rartichoke 14y ago
None of them are actually too good IMO. They are either super opinionated or don't remove the pain points in common web dev.
Still waiting for something like Express in Go but I doubt it'll happen. I don't think anyone is serious about web development with Go based on what I see in the IRC channel and newsgroup on a daily basis, the lack of libs doesn't help either.
Edit:
I want to add that I attempted to step up and learn Go as I made a web lib similar to Express. I had a little success but most of the time the people on the IRC channel weren't very helpful.
Most people didn't understand the need for such a lib (something like Express), it's just a bunch of people parroting "it's so easy in Go, you don't need a lib!" but these are people who never built a single web app in their entire life or going into attack mode saying anyone who needs a super light weight lib is some type of scrub developer.
It made me instantly turn my shoulder to the Go community and it'll take some pretty good libs to make me change my mind because in the end getting stuff done is the only thing that matters and Go + reasonable web dev isn't close to solving that problem yet.
- bradrydzewski 14y agoI put together an experimental package based on express: https://github.com/drone/routes/tree/master/exp https://github.com/drone/routes/tree/master/exp
- rartichoke 14y agoYeah, I looked at that one for quite a bit. It still leaves a lot to be desired compared to Express but it was a good start. I thought the project was dead since it hasn't been updated in a while. I wasn't sure how to decouple the middleware functionality out of your lib so it could be applied to a different router.