4 ms·
This is cool and reminds me of the Twitter clone[1] I included as a coding exercise in my book[2]. It's a very good way to learn as a basic Twitter clone is rel
by dom96 7y ago
This is cool and reminds me of the Twitter clone[1] I included as a coding exercise in my book[2]. It's a very good way to learn as a basic Twitter clone is relatively simple to implement.
1 - https://github.com/dom96/nim-in-action-code/tree/master/Chapter7/Tweeter https://github.com/dom96/nim-in-action-code/tree/master/Chap...
2 - https://book.picheta.me https://book.picheta.me
- jedimastert 7y agoA basic twitter clone sounds like a reasonable Hello World for new web frameworks
- sansnomme 7y agoOnly if you include stuff like auth and migrations. https://github.com/gothinkster/realworld https://github.com/gothinkster/realworld It's pretty easy to tell which frameworks are mature and which are not simply by looking at how many wheels that need to be reinvented.
- jedimastert 7y agoI don't know that I agree, or at least that's not always the goal. I've found that the more "wheels" already in the framework, the more opinions the framework has, and sometimes I just need something dead simple. Laravel, for instance, has so many really nice wheels, but it's organization can feel restrictive at times. web.py, on the other hand, has basically no wheels but I can drop into a project really quick. Maturity is a spectrum, and sometimes you don't need a wagon when a bike will do.
- sansnomme 7y agoThere are tons of Flask/Sinatra level abstraction frameworks. They bring nothing new to the table. Stuff like auth and migrations are difficult problems, which is exactly why you need a framework. Any halfway decent web dev can cobble together yet another expressjs lookalike, but there are few that can reliably build Devise type authentication solutions. Ever wondered why most build-a-blog web framework demo tutorials tend to conveniently skip user registration/auth?