sgdesign

I agree that Apollo is a subset of GraphQL, but I wouldn't have been able to collect any data on it unless it was a separate answer.

It's your fault for building something innovative that doesn't neatly fit in a pre-existing box… (same thing with Meteor actually!)

Author here, thanks!

You could adapt Telescope to work for Q&A: http://telescopeapp.org

Congrats on the launch! As a long-time user of Meteor I'm always excited to see other approaches to similar issues.

One thing that I always found a bit lacking with Meteor was pagination. The problem in a nutshell is that the client doesn't know how much data is potentially available on the server unless it requests it, making things like showing "page 1 of 12" type result counts tricky (I talk more about it here: https://www.discovermeteor.com/blog/pagination-problems-mete... )

I'd be curious to know how Horizon deals with that problem?

It's really hard to give much credit to an article talking about "Europeans" and "Americans" as if these were homogeneous groups.

I think the post makes it pretty clear that it's about how popular stories about various countries are, it's not trying to establish a popularity ranking of the countries themselves.

You should write your own post! I'd be curious to see score compared to country population.

I'd be curious to know what you find hard about React?

Also a CRUD app that just grows organically needs a well-tuned architecture too, once it grows large enough.

I meant it's not so much about the technical merits of Angular and React, as just picking one (React) and sticking with it.

Author here. Hopefully part 2 will answer your worries a little bit. In the meantime, check out Mantra [1] and the Meteor Guide [2].

1. https://kadirahq.github.io/mantra/ 2. http://guide.meteor.com/

I wouldn't say it's "extremely" outdated. The info inside is still valid, you can start with it and then complete your knowledge with the Meteor Guide.

A good solution would be having a 10000 character limit, but formatting under-140 tweets differently so they stand out more. This would encourage people to keep things short, while giving them a way to publish longer posts if they really want to.

It's funny to see the level of fetishism around sushi. Here in Japan the spectrum goes all the way from cheap 100-yen-a-plate sushi joints, to Jiro. So it feels like sushi is a dish just like any other. In fact it always seemed to me like Kaiseki cuisine is probably a lot harder to prepare.

And the "wash rice for three years" thing is just a leftover from the way apprenticeship traditionally work here, whether it's for sushi or any other craft. It's always seemed to me like a particularly inefficient way of training someone and passing on your skills.

I agree that a lot of people have preconceived notions and can be prejudiced, but I think "very, very racist" is going a bit overboard.

I don't think it would be very hard to find places that are a lot more racist that Japan. (Not that you'd want to go there…)

Rather than evaluate every framework under the sun to try and find the one that's perfect for your specific situation and needs, I would probably focus on finding something that's widespread, well-documented, has a lot of momentum behind it, and an active community. Right now that would probably be React or Meteor.

Awesome to see the Kadira team branching out beyond Meteor-only content, can't wait to check this out!

A currency-independent parallel banking system that uses smartphone apps sounds like a very cool thing, actually. It almost makes me wish that we had a chance to see it implemented.

Out of all the technologies out there right now I would say Meteor is the fastest to learn to get a prototype out the door quickly. Rails is also always a good option since it's so popular.

If your priority is building a prototype (and not becoming a developer) I would focus on being practical, as opposed to spending months finding and learning the "best" possible technology.

I've been "stopped and frisked" in France before, and it didn't seem out of the ordinary at the time. I just assumed random identity checks was part of the police's job. So I wonder how other countries' laws compare to the U.S. when it comes to random checks like this.

And of course, it happened maybe twice in my life, not a couple times a week.

The table of contents is right there on the homepage. And you can read the first four chapters for free here: http://book.discovermeteor.com

Just because they've raised $20M doesn't mean every single positive comment about Meteor is part of their "PR machine". How do you know people are not genuinely happy with it?

Disclaimer: I'm one of these "wide-eyed open-source evangelists", I guess.

Creator of Sidebar here. You're right, it's not the best showcase of Meteor. The reason it's this way is because it's running on a very old fork of Telescope (http://telescopeapp.org), and I haven't had time to update it.

But you make some good points. Meteor is not for everything, and if I had known from the start that Sidebar would end up being just a list of links I might have used a different stack (like Rails, or even a static site generator).

What's your criteria for telling that something was written by an evangelist and not just someone's actual positive experience with Meteor?

Nice tips. In Osaka there's Knowledge Salon in Umeda, but you need to know somebody there that can invite you as a guest, so it's not really drop-in…

Oh, and you should also post this over at http://www.startjapan.org/ :)

It should, but it doesn't yet. It's on the roadmap though.

Thanks for using Telescope :) Let me know if I can do anything to help!

Thanks for the kind words :)

There sure is! https://www.eventedmind.com/

Very cool! Thanks for yet another great contribution to the Meteor open-source ecosystem.

While I agree in principle, I think it's fair to point out that glueing various libraries together takes a lot more work than using an all-in-one solution like Meteor.

If you can do it, more power to you, but I'm pretty sure there's a large population of developers who just want something that works out of the box (I know I'm one of them).