joshowens

Never trust AI. Just because it should do the thing you ask, doesn't mean it won't go off the rails. Check and balances, trust but verify. Or don't trust at all and put restraints in place.

Fun read.

Wow, what a crazy read. I'm not sure how any of us stand a chance in running a secure network in this new age. Only a matter of time until models can find the zero day exploits themselves and fast...

Author here. The biggest gap I hit after removing MCPs was APIs without CLIs.

GitHub has gh, AWS has aws, but most SaaS APIs have nothing. That's why I'm building CommandSpec. The tool takes any OpenAPI spec and generates a typed Go CLI. Every endpoint becomes a command, every parameter becomes a flag. The AI discovers operations via `--help` instead of preloading every possible tool definition.

Happy to answer questions about the setup or CommandSpec.

I suspect that we didn't get enough Ember responders, because I do think they have a reasonable sized community. 9k responses is likely not enough to draw a reasonable conclusion that it isn't popular. I wish we could have paired up npm downloads or some other stat besides some of this data...

What did ES5 change to then? I never heard. Honestly, ES2015 just seems odd to me.

9k responses certainly weren't from SV alone. I know alot of the Spacedojo Slack channel took the survey and I think like 2 out of 300 live in SV.

Would be fun to maybe turn ip addresses into lat/long and map out where the responses came from...

Personally I prefer this type of content because I can set it to 2x and speed through and pick up the things I need to know.

Some of us don't have the luxury of mainlining r/javascript all day long.

This looks awesome

This is exciting, been thinking of trying out Redux and this will hopefully save time

Offline support is tricky because each app needs to implement what happens in the case of data conflict. Meteor already has the groundDB package that allows for offline support in local storage. I would imagine you could implement a read only option into local storage once they release reactive graphQL.

Well said! I actually think the community has done a ton of work on Electron and we will see the desktop option soon too.

This announcement is exciting on many levels and I think some of the unspoken bits will be interesting later too. I hear they are working directly with people at Facebook on this project.

Just listened to the first few minutes. Sashko needs a better mic for sure. Enjoying so far.

I think when you look at the companies using React now, you start to understand why it is gaining ground quickly. Couple that with the fact that Facebook has dumped a lot of efforting into the tooling around it, it makes sense to me.

Not having to spend money on Blaze will make them more competitive as a hosting business. Frankly, when is the last time you saw a billion dollar unicorn hosting business? Or a hosting IPO?

I doubt we will see SQL support. We will likely see something with GraphQL instead.

Why would the post be business focused? The guy that wrote it doesn't run "Meteor the business", he just loves the framework itself.

I am not even sure how a CMS got mentioned and compared here.

> First, Rails is not my job. I don't want it to be my job. The best frameworks are in my opinion extracted, not envisioned. And the best way to extract is first to actually do.

You are slightly wrong in your history of Meteor. It was extract from an app they built. Unlike Basecamp or Facebook, the app died off and they focused on just building the framework. So while it was extracted, I think MDG has missed a lot of the learnings that something like Rails gets from core contributors that are building applications and the framework together.

MDG has actually talked about taking one week twice a year to build 'apps' with the framework, but that just hasn't been enough. I am glad they are finally working with Meteor itself to build Galaxy and supporting Galaxy customers as well, that really gets some skin back in the game.

Imo, this post is just a manifestation of the deeper issue around profitability and the fact that MDG will need to jettison some of it's development costs and pick up a much larger base of customers if they want to be profitable.

Which PaaS also builds it's own programming framework...

I am biased, but http://joshowens.me and http://meteorpodcast.com. There is also https://crater.io

You can easily use things like Heroku and Modulus to host your site. I think perhaps you are misinformed about your options and should read up a bit more.

I use Digital Ocean with MUP and it works great with minimal efforts.

If you enjoyed the article, retweets are appreciated: https://twitter.com/joshowens/status/622022975584342016

Thanks for reading everyone!

Jeez, I should have totally mentioned how to use Chrome to see the DDP data. You don't really need a separate package for it.

Thanks. Yeah, always one of those 'wow' moments during my Mastering Meteor class :)

It is a neat feature. I also hear that it will persist changes from node-inspector web interface back to your code itself... I didn't mention in the article as I didn't have time to confirm it myself.

Yeah, I am thinking of adding a debugging section as a PR to the Meteor docs.

Thanks. I was on the fence about listing testing as another form of debugging. Didn't feel right, but maybe I will write a separate article on that at some point.

Thoughtbot had one and shut it down, was called copycopter.

I love Meteor Toys, so handy for development in a Meteor app :)

I guess money and a degree from MIT makes the code look/smell better?

Spoken like a true person who spent an hour investigating the platform and then moved on. All of the issues you've pointed out are solved using third-party packaging.

Yes, I know of tons of applications that have a large code base and use Meteor.

Go look at places like ClassCraft, WorkPop, MixMax, FantasyHub, etc.

Plenty of teams are scaling both the code base and the app servers to handle thousands of concurrent connections.

What is stopping you from trying Meteor, really? Your questions are more focused on the culture of building an app, not about the framework itself.

You need to get a Meteor category in there :)