The last few lines of the article shed some light on OP's opinion of browsing with JavaScript disabled:
"you need to support browsers that don't have JavaScript enabled.
... ok, that last one was sufficiently low-probability that I'll stop there before I start telling you not to use Meteor if your customers gave up their computers in favor of the abacus."
[meteor dev] Ted and Nick found the issue. The site was running in development mode (what you get with "$ meteor run") instead of the direct bundle. That's now fixed.
In development mode, we wrap the whole application inside a monitoring process that includes a proxy server. It's how we support hot code push on a laptop, among other things. But it's not a configuration we intended for production use at scale. We'll think about how to make a clearer recommendation in the docs.
This could be anything, and be completely unrelated to meteor or related in a way that has no bearing on the claims of the article. He did just launch, after all.
I'm excited to try out your dating site given that it's built with Meteor and I'm a fan, but having to sign up three of my female friends to see it first is a buzz kill.
Perhaps you could consider a limited preview account for us HNers that doesn't let us date anyone but does let us check out what you built and sort of inspect things. That will help shine some positive light on Meteor with our crowd, many of whom will likely be unwilling to share an experimental Jewish dating site with their Facebook friends on a whim.
yes, that's very "mid-period facebook" to force invitations on three friends (indeed I'm not sure that Facebook allows that any more for apps because of the annoyances).
I'd also like to try it too, otherwise, since it's for both Jewish and Allies, as it were.
What are the advantages to using Meteor over Rails/Django/Express, etc., for a dating site? Sure, the client server model is compelling, but you're giving up not only the Ruby/Python ecosystem, but the Node one as well. Did you consider something like Derby.js, which uses npm and is built on express?
I liked the article a lot, got excited about giving Meteor a go for our next project, but then I checked out your website and got bummed. It takes +10 seconds to load ... the "loading " message. And then it just sits there, spinning the jewish logo.
jspot dev here. fixed speed issue with help from Nick Martin from Meteor. Turns out I was running a dev-mode proxy to auto-reload code, but Nick figured out we could bypass it in the nginx config. Should be much faster now.
I think Meteor is fantastic in most respects but the REST-unfriendliness of it is a little puzzling in this day and age. It would be really nice to see it play well with others.
You could try setting your mobile browser (default, or say Dolphin) to report itself as a desktop client. Workaround, and I usually have one of my mobile browsers set up like this for suboptimal mobile sites.
ams6110|13 years ago
aroman|13 years ago
"you need to support browsers that don't have JavaScript enabled.
... ok, that last one was sufficiently low-probability that I'll stop there before I start telling you not to use Meteor if your customers gave up their computers in favor of the abacus."
jacalata|13 years ago
amadeus|13 years ago
This site barely works... Simply hangs with spinning jewish logos...
debergalis|13 years ago
In development mode, we wrap the whole application inside a monitoring process that includes a proxy server. It's how we support hot code push on a laptop, among other things. But it's not a configuration we intended for production use at scale. We'll think about how to make a clearer recommendation in the docs.
sgdesign|13 years ago
So don't blame Meteor :)
gfodor|13 years ago
primigenus|13 years ago
Perhaps you could consider a limited preview account for us HNers that doesn't let us date anyone but does let us check out what you built and sort of inspect things. That will help shine some positive light on Meteor with our crowd, many of whom will likely be unwilling to share an experimental Jewish dating site with their Facebook friends on a whim.
triplesec|13 years ago
stuffihavemade|13 years ago
pqdbr|13 years ago
mcot2|13 years ago
I understand they are moving towards this by having a protocol and different adapters for other databases.
belisarius222|13 years ago
saint-loup|13 years ago
stavrianos|13 years ago
unknown|13 years ago
[deleted]
paulyg|13 years ago
svachalek|13 years ago
debergalis|13 years ago
Thanks. We're getting close to implementing a principled approach to REST endpoints and server-side routing. https://trello.com/card/page-model-server-side-rendering-res...
ibudiallo|13 years ago
triplesec|13 years ago
orangethirty|13 years ago
belisarius222|13 years ago
adambom|13 years ago
krapp|13 years ago
jbm|13 years ago
asdfadsfasdf|13 years ago
[deleted]