4 ms·
Thanks for sharing this with HN :)
by joshowens 12y ago
Thanks for sharing this with HN :)
- stared 12y agoMy pleasure. I like this meta-introducation approach - i.e. when there is abundance of introductions its worth make an introduction to introductions. As a side note, one of things that made me using Meteor.js is the easiness of starting (largely to great official examples and tutorials). BTW: I highly recommend Discover Meteor by Sacha Greif & Tom Coleman (https://www.discovermeteor.com/ https://www.discovermeteor.com/). One of the best tutorial books I went through.
- puranjay 12y agoQuestion as an aspiring web developer with a moderate-high degree of comfort in Javascript, and low-moderate comfort in Ruby: would you recommend giving 100% to mastering Rails, or dabbling with Meteor from time to time? The aim is to not get a job as a developer, but build my own projects. Apologies if this kind of question is better suited for Stackoverflow
- stared 12y agoFor side small side projects, where you want start and move quickly - I totally recommend Meteor. Before knowing _any_ framework I started reading on Meteor - and literally in hours, I had a simple app. (Actually, it's how I use it. I am mainly data scientist; I do some webdev, but its not my main thing.)
- stared 12y ago@joshowens, one more comment - the compilation is excellent, but for packages I think that (especially for a newcomer) it would be better to add a one sentence desc per package (especially as one do not need to start with learning all of them!) rather than providing 3 links (if one wish, one can easily jump from Atmosphere to GitHub).