7 ms·
It does look exciting, but I can't trust a framework that promotes saving data on a GET request.
by tonyblundell 14y ago
It does look exciting, but I can't trust a framework that promotes saving data on a GET request.
- NikolaTesla 14y agoDefinitely not promoting it! That's a convenience feature to make it easy to see what's happening during development. You can disable that behavior in your routing table.
- tonyblundell 14y agoIf it's on the homepage and in the docs, people will copy it without questioning it. That's why people use frameworks.
- mikermcneil 14y agoNot you though, sounds like!
- tonyblundell 14y agoSarcasm, nice. But seriously, I'm new to Node. If I see examples of bad practice on the home page, I've no way of knowing if the framework is going to be teaching me more bad practices in the areas I'm not familiar with yet.
- jameycribbs 14y agoI really hope you start using a framework. This would free up more time for you to develop a sense of humor! :)
- tonyblundell 14y agoA sense of humour normally gets you downvotes on here :-p
- deleted 14y ago[deleted]
- Kiro 14y agoWhy not?
- tonyblundell 14y agoBecause GET requests can be saved as bookmarks, copied and pasted, indexed by search engines, etc.
- mikermcneil 14y agoBy the way, I forgot to mention this before, but you can quickly disable this behavior in polices.js or routes.js config file when you're ready to switch to production. In 0.9, you'll be able to generate controllers with this feature disabled from the CLI as well.