Icecreamsushi

3 ms·

1. 1.▲
   by Icecreamsushi 6y ago

   Eactly. I was targeting personal ease of use. I remember that handling authentification in JS was a pure nightmare, so I have a strong bias towards frameworks handling that for me.
2. 2.▲
   by Icecreamsushi 6y ago

   Ok thanks for the link!
3. 3.▲
   by Icecreamsushi 6y ago

   This article relates really well my feeling now: https://hackernoon.com/how-it-feels-to-learn-javascript-in-2...
4. 4.▲
   by Icecreamsushi 6y ago

   I "was" good at ES6. ;) Thanks for the answer. Indeed the fragmentation of the JS ecosystem makes it quite difficult to know where to stand. The link to roadmap.sh helped me see a clear path. Thanks for the mention of Netlify, I&#
5. 5.▲
   by Icecreamsushi 6y ago

   Ok, glad to have a python-point of view. Why did you switch from Laravel to Django? I prefer to use Python than PHP, but except for data-science stuff, I never used python for web dev. I suspect that the learning curve is not that steep?
6. 6.▲
   by Icecreamsushi 6y ago

   Perfect thanks. I'll go with Laravel. I still have a question about how Vue does on mobile, but a quick search for Vue.js made it clear how easy it is.
7. 7.▲
   by Icecreamsushi 6y ago

   Thanks a lot!
8. 8.▲
   by Icecreamsushi 6y ago

   Thanks! I think I'll go with Laravel indeed. Vue.js looks more adapted than React, but would that be a bit more difficult to develop a mobile app with Vue than with React (using React Native)?
9. 9.▲
   by Icecreamsushi 6y ago

   Thank you so much! The visualisation makes it very clear to see where I stand. I love it. It's funny to see how much has been developed after the "Build Tools" section in those past few years. Most of the technologies were in
10. 10.▲
    Ask HN: How to get back to web programming after a 8-years break?

    12 points by Icecreamsushi 6y ago|19 comments