Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Meteor, a realtime JavaScript framework

meteor.com

Post reply on HN
Print view View original

141–150 of 350 posts

Re: Show HN: Meteor, a realtime JavaScript framework

#141

Post by mcantelon »

DancingWolf wrote: post #45

It was a few years since I was "in" with the new things happening in the web-world. But how did JavaScript come to be the new "cool" language? It got some horrible problems with object oriented stuff, some really strange bugs/features, and it's slow-ish. I liked making cool stuff with JavaScript, but compared to something like ruby isn't this a step backwards? I can see the advantages of this framework, but it still…

>it's slow-ish.

Not compared to Ruby. ;)

>I liked making cool stuff with JavaScript, but compared to something like ruby isn't this a step backwards?

http://fingernailsinoatmeal.com/post/292301859/metaprogrammi...

Re: Show HN: Meteor, a realtime JavaScript framework

#142

Post by sleight42 »

debergalis wrote: post #128
amirhhz wrote: post #117

Earlier quoted context omitted.

That puzzled me, too, I started browsing the code and noticed there's not a lot of testing of the project code itself: https://github.com/meteor/meteor/tree/master/tests So I agree, it would be good to hear from the devs about their opinions and thoughts on testing. (Is there a chance that they think the "realtime-by-default" approach lessens the need for testing?) I'm no testing zealot, but I've found writing tests…

We've actually written a lot of testing for the core framework packages -- those tests are in each package directory. Look for *_test.js files. https://github.com/meteor/meteor/tree/master/packages/ You're 100% right though. We don't have a fully baked story yet for application level testing. It's something we're trying to push forward as soon as we can.

Cool. Thanks for clearing that up.

Don't get me wrong: I want to like Meteor. But I've found automated tests too important to my workflow to live without.

Re: Show HN: Meteor, a realtime JavaScript framework

#143

Post by polychrome »

Great work!

I have to ask, I know that Mongo is all the rage these days, but how quickly could you add MySQL support? I can already see several uses for this, but I need to tie into legacy systems.

In terms of security (say a dashboard), could you just disable the system from being able to modify the DB and just read it?

Re: Show HN: Meteor, a realtime JavaScript framework

#145

Post by cfontes »

Do you plan to charge for it at some point? because for me it's not clear.

Is there a business model or just releasing it for people to use in their business and if improved contribute back ?

Because I cannot see anyone adopting it without those questions answered.

Anyway, nice thing you guys have build... keep it going !

Re: Show HN: Meteor, a realtime JavaScript framework

#150

Post by edwinnathaniel »

debergalis wrote: post #128
amirhhz wrote: post #117

Earlier quoted context omitted.

That puzzled me, too, I started browsing the code and noticed there's not a lot of testing of the project code itself: https://github.com/meteor/meteor/tree/master/tests So I agree, it would be good to hear from the devs about their opinions and thoughts on testing. (Is there a chance that they think the "realtime-by-default" approach lessens the need for testing?) I'm no testing zealot, but I've found writing tests…

We've actually written a lot of testing for the core framework packages -- those tests are in each package directory. Look for *_test.js files. https://github.com/meteor/meteor/tree/master/packages/ You're 100% right though. We don't have a fully baked story yet for application level testing. It's something we're trying to push forward as soon as we can.

From product adoption perspective, you guys are going to win a lot more users if you can support the following scenario:

1) unit-tests

2) integration-tests

3) provide at least guidance/best-practices on client-side testing in the _headless_ scenario (no complex setup of remote machines with 3-4 browsers installed etc)

People may have their opinions about testing UI/client-side (is it end-to-end? is it worth? not testing using the browser no-go?, etc) but the fact that Meteor is leaning toward more code in the client-side will definitely put testing in almost make-or-break decision for a group of developers.

GWT with their MVP approach is definitely heading toward that direction and it is quite unfortunate that the client-side JS community out there haven't picked up that style (some brushed GWT off because it is Java).

Rails won the heart of many Java developers not only because of its simplicity but also because of automated testing.

So, show how easy it is to test the whole Meteor app and I (almost) guarantee you will get many more developers (especially those who skipped the Rails boat).

Post reply on HN