3 ms·
I currently work for an MS consulting shop. Historically, my tools have been Asp.Net MVC / WebForms / WebAPI / WCF, MSSQL Server, and your standard HTML5/JS/CS
by ep103 13y ago
I currently work for an MS consulting shop. Historically, my tools have been Asp.Net MVC / WebForms / WebAPI / WCF, MSSQL Server, and your standard HTML5/JS/CSS3.
A few years ago I realized I loved javascript, so I've been studying everything frontend with the hope of eventually leaving the JS hating MS world, and going somewhere more JS oriented. For JS I've learned a good deal of Backbone, Angular, Node.js, and soon I'll be focusing on WebGL.
I am familiar with npm.
I usually roll my own assets. Most solutions I've worked on haven't had a heavy art presence, and having basic-decent photoshop / design understanding has been sufficient.
As for company requirements, I really don't have any. I just know that I'm going to pick at least one on that list to dive into, and was hoping for community input before I put the time to learn investment in a framework. I mean, if most development shops use one over the other, then I'd love to learn that one! Or if one is up and coming, then that would be great too...
- malandrew 13y agoGiven your situation, I'd say component, bower and browserify are all interesting and worth checking out. Bower really doesn't do much other than resolve dependencies, but that doesn't mean you won't find it useful. If you are really into the node.js ecosystem and your back-end is node.js, then browserify is worth checking out. If not, I'd opt for component.
- ep103 13y agoThank you!