4 ms·
I built https://primerlabs.io https://primerlabs.io. A conversational learning medium designed for people who wish to learn Computer Science on their own. The
by ai_ia 5y ago
I built https://primerlabs.io https://primerlabs.io. A conversational learning medium designed for people who wish to learn Computer Science on their own.
The tech stack is Meteor.js for backend and React + Apollo Graphql for front end. I use AWS lambda for Anki Card Generation generation and Latex-based PDF Generation for personalised Books. The main website uses self-hosted Ghost blog. Using Ghost for the main website + blog, saves a lot of time with SEO and Image compression. While compiling Latex on AWS Lambda Container is pretty slick.
Deployment: Docker, AWS Beanstalk
> Why did you choose it?
It's been an absolute joy working with Meteor. You can prototype quickly. For instance, last week, I was trying to add anonymous accounts i.e. no need to sign up to view the application and can merge directly once the user is ready to sign up. It took me a half a day of work to do that in Meteor.
There is a feature of real-collaborative learning I want to add in the application i.e. you can learn with friends and see their responses, notes in real time. Meteor has real-time capabilities using pub-sub which makes it quite easy to do so.
> Do you think your choices had any impact on your success?
The product is not mainstream yet. A small number of people who use it, love it. It requires a bunch of more courses to make the value proposition clearer to the users. But Meteor.js enabled me to prototype quickly since this is the third iteration of the product which I finally thought was closer to what I had in mind.
I am not in anyway associated with Meteor. I really love Meteor, that's all.
- ecmascript 5y agoInteresting with someone who loves meteor. Personally, I really dislike Meteor and have extensive experience with it. At work we're moving away from Meteor and that itself is a daunting task even if we're moving to a normal node backend and most stuff is copy-n-paste. Stuff like background jobs etc are impossible in Meteor since there is really no good way of utilizing the cluster module or worker threads in node. Several times we've had issues with the entire app goin down due to Meteor. Also it has very poor performance and many requests takes a lot longer than a normal request for whatever reason if you transmit a lot of data. It adds several seconds probably due to some meteor magic. But it's nice that you've found success with it, just goes to show that everyone's needs are different.