"It achieves breathtaking performance, made possible by the almost complete absence of features." While pithy, I'm not really sure that's the best way of selling your product.
Reminds me of http://vanilla-js.com/
Quinn – A web framework designed for things to come
11–20 of 30 posts
Re: Quinn – A web framework designed for things to come
#12It's a rite of passage to create a crappy, half baked web framework. It's a great thing that every web developer should do so that they understand, end to end, the tensions facing the creators of web frameworks, the tradeoffs between the various attempts to balance purity with convenience, and how much 'magic' you want a framework to perform vs how much should be completely explicit.
However, nobody should ever use these frameworks, there are probably 5000 of them floating around out there in github, and beyond an exercise in pedagogy they are mostly half broken and stupid.
So to the author of Quinn: don't let this get you down, stay excited, but realize that it's possible that you can't just swoop in and do something great on your first try. OTOH, node.js' ecosystem is so amateurish and shitty that maybe you actually could.
Re: Quinn – A web framework designed for things to come
#13On an unrelated note, do arrow functions inherit the parent context's `this` and `arguments` correctly in Node or io.js now?
I believe the arguments should not be available in arrow functions according to the spec.
(source: discussion here https://github.com/Microsoft/TypeScript/issues/1609)
Re: Quinn – A web framework designed for things to come
#14> Instead of taking the response as a second argument, the dispatch function is expected to return the response... The moment the function returns, both the status code and all headers are known.
I highly doubt this convention will work. You need to be able to return errors or DB information in the response code and headers, which would be impossible since Node is nonblocking. Even something as basic as storing session information in Redis suddenly becomes impossible. This seems like it gives a very minor benefit and causes a whole lot of problems.
Re: Quinn – A web framework designed for things to come
#15On an unrelated note, do arrow functions inherit the parent context's `this` and `arguments` correctly in Node or io.js now?
They explicitly do that in ES6:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
Re: Quinn – A web framework designed for things to come
#16> Quinn was created to address the utter lack of small, elegant web frameworks in the node ecosystem. Uhhh, that's because all those frameworks linked are designed to get you up and running with almost everything you need quickly, not just handling routing and leave you setting up boilerplate.
Yes, and if you want to seriously build a product, each and every one of those would be a better fit than Quinn. I'm saying that as the author of Quinn. It's a bunch of thought experiments, not a production-ready piece of software.
You should make it more clear. By default, when we see a page like that, we assume that someone is putting it up to use it.
Re: Quinn – A web framework designed for things to come
#17> Instead of taking the response as a second argument, the dispatch function is expected to return the response... The moment the function returns, both the status code and all headers are known. I highly doubt this convention will work. You need to be able to return errors or DB information in the response code and headers, which would be impossible since Node is nonblocking. Even something as basic as storing sessi…
That's why quinn uses async/await
Re: Quinn – A web framework designed for things to come
#18Title attribute of the massive image on the top of the page
"Huge logo to hide any actual information"
Re: Quinn – A web framework designed for things to come
#19It's a rite of passage to create a crappy, half baked web framework. It's a great thing that every web developer should do so that they understand, end to end, the tensions facing the creators of web frameworks, the tradeoffs between the various attempts to balance purity with convenience, and how much 'magic' you want a framework to perform vs how much should be completely explicit. However, nobody should ever use t…
You can call it amateurish and shitty all you want, but I'll take Express (on Node) over Flask or Tornado (on Python) any day.
Re: Quinn – A web framework designed for things to come
#20Earlier quoted context omitted.
Yes, and if you want to seriously build a product, each and every one of those would be a better fit than Quinn. I'm saying that as the author of Quinn. It's a bunch of thought experiments, not a production-ready piece of software.
You should make it more clear. By default, when we see a page like that, we assume that someone is putting it up to use it.
Definitely a valid point. I updated the wording a bit already. It was definitely not meant for a larger audience in its current form.