Icecreamsushi
Icecreamsushi on Hacker News
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.
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'll take a look.
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?
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.
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)?
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 beta a few years ago.
Posted by
Icecreamsushi on Sunday April 19, 2020 @09:15AM
from the ask-hn dept.
I was a full-stack dev in a Californian startup in 2012. I knew ES6 and CSS's specs by heart. Except for the "ensure IE6 compatibility", life was simple and vanillaJS was still a thing. AngularJS was the default choice, and Laravel was the cool framework to do backend stuff.I became CEO of a SaaS startup and stopped programming for the past 8 years. I now want to get back to developing my own...