Arunoda coming back to Meteor?

[theara]

@arunoda I missed you!!! Welcome back
I learned more from you!

[arunoda]

@captainn

At the company I now work for, this low level consideration is the primary driver of tech decisions. Technically, we could use Meteor, even when not using Mongo. But they won’t even look at it, because it seems so full stack. The sad thing is, Meteor’s vertical integration (primarily its build system, and legendary backward compatibility which makes evergreen development such a breeze) would save everyone a lot of time. It’s just a hard sell without that focused purpose messaging.

Yeah! true that. I have seen the same comment in other places.

[arunoda]

Oh! Very sorry If my commented made you angry.

If you want to pursue your own vision , it is better than you create your own fork under a new name.

There’s no need for such thing. We never even looked for that option even in the past.

As you already know, I have moved on due to various reasons.
I just wanted to say hi to some old friends. That’s why I am here.

[arunoda]

Thanks for the details.

I didn’t know about https://montiapm.com/.

Wow. Thanks for anyone who’s maintaining this.
I really want to give it a try.

[cloudspider]

This is all good news I need to restart my vue ddp project again

[waldgeist]

Thanks Arunoda for sharing your thoughts. Actually, I also missed you when you left, since you were one of my main inspirations at that time, and I learned a lot from you. I don’t expect you to work with Meteor again, but it’s great to see you here.

[efrancis]

One great package missing from this list is meteor-desktop which adds Electron as a first-class build target. My business relies heavily on this and it’s a fantastic way to get a Meteor app bundled as a cross-platform desktop application.

[vikr00001]

@arunoda @filipenevola – seen in a previous thread. The post quoted was directed to MDG, and also was potential advice to Tiny.

@alan99

How did you lose Arunoda, a 20x dev and evangelist? A blunder for the ages. Next time, try money . (smh)

[alawi]

Thanks @efrancis, yes it is missing here.

I’ve created another thread for this list, please share you comment there so we (as a community) can co-create this list.

@alan99

How did you lose Arunoda, a 20x dev and evangelist? A blunder for the ages. Next time, try money . (smh)

I agree with this comment, that was indeed a business and management blunder for ages.

Anyway, we’ll keep this thread for Arunoda

[florianbienefelt]

@zodern is maintaining Monti APM:) We’re happy customers!

[sacha]

@vlasky

The main problem we had over the last few years was wasting our energy dealing with losers spreading anti-Meteor FUD.

It is also unfortunate that a personality cult had developed around your name and a number of people reacted with ongoing public expressions of hysterical mourning and gloom after you announced your departure.

That’s a really poor attitude towards someone who literally gave years of their life working for free to build the foundations for a good chunk of the Meteor ecosystem.

Shooting the messenger and blaming people who point out Meteor’s issues might feel good, but it’s not going to do one bit to fix these very real issues, and it’s not a great look for you.

[alawi]

Actually, I’ve to agree with @vlasky on this one, he made a factual observation, at least to my mind.

There is indeed a lot of misinformation and FUD around Meteor (and also valid criticism), and there is a personality cult around his name.

People who never used the tech, sitting on the fence repeating what everyone else is saying even inside the Meteor forum despite clear facts, it is a waste of energy and they are indeed losers, they lost an opportunity to use their time/energy better and build something profitable with the tech, instead of just fiddling around with JS frameworks.

I don’t think vlasky statements undermine Arunoda (and his team) work, they are very factual and so his contribution. But @vlasky work has been undermined by misinformation and FUD, he has been saying there is SQL support for years yet he/we gets the same false rehearsed messages (it does not scale, no SQL support, nextjs/x is better, it’s for toy projects, it’s not secure, and the infamous declaration it is dead…)

We (as a community) keep complaining about the FUD outside the Meteor forum, yet inside the forum, we don’t make the effort to correct the misinformation. So I’ve to agree with @vlasky on this one.

@sacha

literally gave years of their life working for free to build the foundations for a good chunk of the Meteor ecosystem.

He was making a profit (Kadira/MUP) and I think he would have made more money if he waited little more especially with GitHub sponsorship, I’m willing to bet that the entire Meteor community would have paid him (even now if he decides to contribute again), it was indeed a loss and I think MDG has a large part to play with it.

[sacha]

I guess if you’re charitable you can read his post in a better light, but I thought the overall tone (calling people “losers”) was unwarranted. Anyway I don’t want to derail the discussion in a negative way so my apologies if I overreacted.

[hemalr87]

@alawi

I’m willing to bet that the entire Meteor community would have paid him (even now if he decides to contribute again)

Yupp.

This is filler text - please ignore

[cloudspider]

That’s why I did not say goodbye to the Meteor forum when I needed a break. I’m still a huge fan, but unfortunately I was so occupied with other stuff on other frameworks for the companies I work for that I did not have a lot of spare-time to remain active on the Meteor forum.

Actually I’ve lately been spending my time on teaching people why they should not do everything themselves. The benefit of freedom does almost never outweigh the burden of having to maintain your own codebase on area’s that are not the core business. Even worse, that code is almost always less efficient, un- or badly tested and has almost no documentation, no community and might even require full rewrite, because of bad practices in core parts of the API.

I’ve been on repeat for the last couple of years: “Do we want to deliver value? Or do we want to deliver code?” “Do you need to build your own BFF? Why do you hate Meteor, but love building BFF’s? Are you and your business THAT special? Seems to me that we’re just building another webshop?”

[qnipp]

Thanks for this comprehensive list.

It should be part of the homepage in the section Why Meteor?

Tutorials for using MySQL, Grapher and RedisOplog would be fine, so that even newcomers see the broadness and scalability of Meteor.

[alawi]

Thanks @qnipp!

The list has its own thread now, check it out. Also, please like and share any suggestions you might have.

@qnipp

It should be part of the homepage in the section Why Meteor?

Yeah, once it is stable, I’ll try to discuss it with them to see where to best include it. There are a lot of great work within and around Meteor that needs to be made more visible to the external audience.

[seba]

Happy to see you’re back here @arunoda !

[manthony]

@sacha

Shooting the messenger and blaming people who point out Meteor’s issues might feel good, but it’s not going to do one bit to fix these very real issues, and it’s not a great look for you.

Yep. Anyone mention any problem past or present and they get accused and attacked. Not a way for a community to grow itself.I feel better about it though. If arunoda gets that then anyone can (and does).

[seba]

Btw, I also think there’s a lot of FUD that has hurt Meteor. But:

1. Arunoda owes us nothing.
2. Meteor was hurt way more by the lack of attention and poor (nonexistent) communication it received from MDG after they pivoted towards apollo.