I’m looking into writing up a new book. Here is my proposal:
https://rediscover.meteorjs.community/
Let me know if you are interested!
5 Likes
Redis-cover MeteorJS - I don’t get it. Is this about Redis or is it about Meteor?!
1 Like
Re-discover MeteorJS
1 Like
Fully agree. The web returns the old, dead packages on top positions whilst the newest fork which is Meteor 3.x compatible isn’t shown on page 1 as not many people discussed it
1 Like
Great idea! Do you plan to release it as a free book this time? IIRC, there was a paid version when it originally came out (but I got it for free because I helped translating it to German).
1 Like
Returning Veterans and Ambitious Beginners
I really like this sentiment. Meteor is still facing plenty of problems one of the is the lack of educational content so every bit counts.
And I really like how you’re reviving this old book. On one hand it benefits you so as not to start from scratch but also acts as a marketing gimmick towards OG Meteor developers who had long left the community. 
2 Likes
That depends. It will time to write this and maintain this. I’m looking into options that would allow me to do this, but so far to make it free is not working for me financially.
That said I would like to also do translations as well.
1 Like
wow, congrats @storyteller !
An options to mantain it for free is make it as open source book, guinding the community here to help you conclude it.
But for sure, write an book is prettry hard, it demands so much effort, time and dedication, mantain it for free is a complex decision.
let us know how we can help you on it.
I filled out the landing-page’s form 
1 Like
I didn’t want to bring this up to not put you down and be all negative but believe me you’re gravely mistaken to consider that putting this behind a paywall would grant you any significant profit or even enough to cover the time spent on it.
Your best bet is to release this for free and add a donation or use it to promote any other products.
Meteor developers pool is continuously shrinking, most OGs migrate off of Meteor for one reason or another and I’m saying this from first hand experience not some speculation. So your book wouldn’t mean much to this group. On the other hand, there’re not too many new comers who’re seriously interested in Meteor like it’s the next React. Meteor isn’t backed up [Insert Mega corpo] and thus it has little to no traction for new comers to spend any money whatsoever. Again, your best bet is to release in the hopes that it’d help nurture a new wave of Meteor developers that in time would positively impact your career financially or otherwise.
Lastly, there’s another problem that I’m curious what’s your stance on it? The Meteor community hasn’t really stabilized yet, many packages are still in dire need for update. So at best you can only explain basics that’re hard to change and currently stable but any tutorials that build serious application wouldn’t be really optimal. I mean you’d not want them to install some beta version of a package!
3.0 has sent a shockwave across all community packages that made us reconsider whether some packages are worth the effort of continuing to update or can be integrated into the core or even abandoned all together. And frankly, the dust hasn’t settled yet.
To give more concrete examples:
- Grapher - It’s still in the works and we don’t know even if people would continue to use it versus something like @pmogollon’s nova.
- Meteor-Files - No matter how much I tried to nag @dr.dimitru he’s still yet to respond to some my comments and hey I don’t blame him at all. It’s FOSS he has no obligation and can do whatever the hell he wants, even inject some malicious script for all I care. But as it’s currently stands, this is a crucial package that’s still under beta and you can’t risk forking it and fragmenting the community even further or even encourage others in a tutorial. This is a very sensitive and crucial subject and as an educator you bear a considerable responsibility.
I did issue a tutorial before so I’m knees deep in these conundrums and it ain’t pretty. 
Can’t Tiny support you with a donation? I think having a book like that would be very valuable for them and the Meteor community in general.
As already stated elsewhere, besides some good tutorials like this, Meteor is lacking a well maintained packages repo. I don’t mean the Community packages, they are great. I’m looking at Packosphere. There’s way too many packages that are unmaintained. I’d kick them out and keep the “good ones” (not really kick them out, but set them to deprecated and only show them on demand).
The cathedral vs the bazaar
I’d always vouch for a wild west
Packosphere solved this in a smart way as @copleykj added a deprecated notice that a package hasn’t been updated in a long time. Maybe he can also 3.0 tag?
1 Like
I’m in talks with Meteor Software, but the response has been… disappointing (sadly I live in an expensive country, that I’m trying to escape, so I can’t afford to be cheap about it). Sadly I don’t have the finances to be altruistic here or have the runway to count on possible future return.
So, I guess, the conclusion is not to waste time on this project?
That said, the response to the latest Meteor Impact promotion has not been bad, so I do still have a hope.
1 Like
I wouldn’t remove the packages completely, also because they are still in use. But I would show “well-maintained” packages above all others in all searches. For me, the main criteria would be: time of last update, do they have a github repo link? If I would try to get into Meteor for the first time, it would be super frustrating to see all these abandoned packages first. Gives you the feeling no-one is using the platform actively anymore.
To be super honest with you: I don’t think anyone would pay for it. The old community is already deeply into the tech, and for new members, this would be a very valuable onboarding tool, but nothing I’d pay for when I’m getting into the tech. Yet sill, I would love to see this book, to foster adoption. Meteor is still a really nice platform. Over all these years, I’ve quite often looked for alternatives, but always came back. So, if I were Tiny, I’d use this opportunity to get some decent docs for newbies. Besides, I would not release this as a physical book. I’d release it in the same style as the Meteor guide. And maybe automate the translation this time, if any. Otherwise, it would be hard to keep things up-to-date.
1 Like
Yeah, I’m personally thinking that updating the live docs is the best way to go before a book. I personally typically don’t read books on tech libs/frameworks, but rely on the actual docs. I love the idea of better documentation. Maybe the docs can have more content. I like how in the old days people were writing interactive docs on *.meteor.com. If the docs were a Meteor app with interactive content, that would be so nice (f.e. click a button, it increments a counter, or while reading about collections there’s a demo with a chat box that anyone can type into, that will clear every day, or etc).
(In fact I really miss *.meteor.com. They should have kept it, and simply monetized it! That seems like a missed opportunity. It was so easy to get apps running that way, in Meteor’s spirit of making things easy.)
AFAIK, it’s still there, but now under the name of Galaxy. And yes: the free version for docs was genius, it helped a lot to get into the framework. Though I can understand they stopped it after a while.
It is now *.meteorapp.com