@josh88
Experienced Front End Developer
I am a front end developer with more than 5 years of experience developing for the web. Currently, I am experimenting with Go and JavaScript MVC frameworks.
Nothing here yet.
No blogs yet.
If you want to build a modern enterprise application and want to go with a framework I'll suggest you to go with either Bootstrap or Foundation. You will have a great set of plugins/components to build complex UIs. And regarding JavaScript frameworks three names come to my mind : Angular Backbone React We have had success with both Angular and Backbone in past. React is a little advanced, IMO. Also if you are going with Backbone then you may combine it with a framework like Marionettejs .
I would say that UUIDs are secure provided they are of "Version 4" and that they have been generated with a secure random number generator. If this is the case then it will address most of the security concerns. Also V4 UUIDs ensure 122 random bits out of total 128. So, the probability that an attacker guesses your token correctly is very less. Therefore, the bottom line is check how UUIDs are generated in your code and if they are of V4.
I started learning HTML and CSS 5 years back. Just like every beginner I went to the W3Schools and TutorialsPoints. As I was always inclined towards designing, I didn't dive deep into JavaScript. However, I quickly understood how jQuery worked and some of its popular animation functions. Mistakes I did : I wasted much time in just reading, didn't practise the code. Didn't go through the basics of JavaScript. If you want to write better webapps in future, you have to understand the good parts of JavaScript . Didn't stick to any one resource to learn programming. Recommended resources : If you are just starting to learn web programming, you should follow the following websites HTML5Doctor Mozilla Docs HTML5 Rocks CSS Tricks
That perfectly summarizes it! I completely agree with ""People only care about end product". Cutting edge doesn't mean it's always better. Choice of technology should be a perfect balance of how well you know the technology and the things you can achieve with it.
I have used both - so here is my opinion on both the stacks. Meteor : Meteor is very good for building realtime apps. In meteor your database (MongoDB) is realtime - so all your connected users see the updated data. There is no need of any extra work like setting up sockets and other stuff. Both Client and Server share the same code which means the amount of coding needed to achieve something is reduced. What took weeks will now take days or even hours to implement. Meteor has got good community support and the development is going on actively. More and more people are collaborating to release libraries for Meteor. So, no doubt you will get good support from the proactive community. So, the tldr is that if you are developing a realtime app and you are eager to try out something exciting then go for Meteor. MEAN MEAN stack is older and mature in my opinion. So, naturally you will find a lot of libraries and frameworks to support you. The ecosystem is larger and you will get a lot of help from people around you. If your app is more API driven and doesn't need realtime features (may be very less) you may rather go with MEAN stack. Both Meteor and MEAN stack use Node.js and MongoDB. So, the only thing that is different is the involvement of Angular in MEAN stack and realtime database in Meteor. If you are a fan of Node.js or server side JavaScript then you can have that in both the stacks. The question is do you want to use Angular on the frontend or just Meteor? This is a matter of preference and the task at hand. If you have a tight schedule and you are already comfortable with MEAN then you should go for it. Otherwise if you want to learn something new you can try out meteor. Hope this helps! May be Evan You (@yyx990803) from Meteor team can give a better comparative analysis. I'll invite him.