triathlete

The problem with html5 apps right now is theres no good platform for developing them. Jquery mobile has issues. Sencha touch has issues. Ive looked at touch before but am concerned abut bugginess and i really dont want to learn c#.

The mobile app environment is a huge headache.

Parsing json is a pain in android. You have to do so may things to do what should be a simple straightforward thing. One article mentioned that library but i never looked at it.

I was trying to learn android recently and had to take a break due to increasing headaches. Theres so many issues. Some of which they mentioned in this article. One of which is that supposedly alot or some of the performance issues are fixed in 4.0. Of of curse nobody uses 4.0. So you have to just pretend those fixes dont exist.

And the xml views are a nightmare. I actually decided to learn ios instead maybe sometime next year.

Likewise agree. Too much freaking noise. Annoying interface and horrible ads. Im in the process of moving over to twitter.

Actually i just learned node a few months ago. If you want to ping me personally i can go through it with you step by step since theres a couple of things you have to figure out and its a bit difficult to remember them through a simple comment.

If youre interested leave me a contact email or whatever in reply.

To say this is a port of Node is to misunderstand 99% of what node is. In fact i dont really understand why you even relate this to node at all and why you use the node logo. Call it evented php or or a port of Tornado or something but its not node. If you want to learn what node is listen to Nodeup. Its an awesome podcast with core node people in it that talk about what node is and why it is what it is and why javascript is so integral to it.

Its unfortunate that right now none of the 3 major document stores seem to be doing all that well or are easy to use straight out of the box. I use and like mongodb but only for prototyping. I havent decided what to go with longer term if my projects have a need. Couchdb is interesting but seems to be going through some serious growing pains right now with the couchbase product being very confusing to figure out and use. Riak is also interesting but it seems more specialty then a general purpose tool.

Kind of a bummer.

For anybody wanting to learn about node the NodeUP podcast is excellent.

Personally id say Node and Rails simply shouldnt be compared in any way. They are just too different technologies. So node shouldnt even be concerned about trying to be rails at all. People are going to use whatever they want to regardless. So node should just do what its own users need. And thats it.

Mongodb is a json document store. I use it myself. It works very well with "node" because node of course uses javascript as its language.

Of course Rails took YEARS getting to the point of scalability. People are acting like it was scalable on the very first alpha release.

Plus if they already knew rails. I use node mostly now and wonder why people would use anything else. However if i had alot of expertise in rails i would probably use it for most everything as well until i was comfortable enough with node.

Im sorry but you make it sound like everybody that does rails is a perfect programmer. Rails itself has changed over the years and if you look at an app from years ago im quite sure it will be very different then a current rails app. So again this is just not an appropriate comparison.

Yes of course via express.js and railway and several other frameworks. Again node itself is just a set of libraries on top of of v8. So its not a proper comparison.

Personally i use express.js and roll my own framework essentially because i prefer to work that way.

The problem is that Rails has been around since what 2005. Node has been around for a much shorter period and has only stabilized over the past year. So they just arent comparible in that sense. Plus node works differently then Rails and i admit it takes time to get used to that.

If you do take the time to learn node though all i can say is its just AWESOME! So lets see how things are when node is 5 years old or so.

I use node for everything now myself for a number of reasons. The "problem" with node is that its still very young. And its a different programming model then people are used to. So its similiar to the whole RDBMS/document store argument. You use what works for your applicaiton.

The thing that annoys me personally is that they make it seems like there something wrong with node. And there isnt at all.

Completely agree. I tried to learn rails and gave up partly for this reason. I have been using node for a while now and LOVE it! I really dont understand why people bash node.

Mongodb and Cassandra are two completely different technologies with completely different use cases. Mongodb is more of a general database although its apparently used more and more for analytics whereas cassandra is more for parts of applications that need very high throughput.