News for hackers. Stuff that matters.
Re:Poll: What Language would/do you use to build a web appli... by 1qaz2wsx3edc on Friday June 14, 2013 @04:01PM (#5882118)
Why would build a prototype to only throw it away? This seem naive.
Re:Poll: What Language would/do you use to build a web appli... by tudborg on Friday June 14, 2013 @04:27PM (#5882297)
You need to go look up "prototype" ;)
Re:Poll: What Language would/do you use to build a web appli... by xiaoma on Friday June 14, 2013 @05:03PM (#5882487)
1) Seeing things in action often clarifies my design.

2) You can build things really fast with Meteor.

3) After you know what you're doing you can develop the robust version much more quickly. This time savings is often significant.

4) Since Meteor is built on Node, you don't throw everything away. You can actually keep quite a few functions and nearly all your handlebars intact when you port to the final project.

I'm not saying working this way is for everyone, but it works well for me.

Re:Poll: What Language would/do you use to build a web appli... by 32bitkid on Friday June 14, 2013 @04:09PM (#5882168)
you and I have very different definitions of "prototype"
Re:Poll: What Language would/do you use to build a web appli... by Zikes on Friday June 14, 2013 @04:07PM (#5882154)
I think the prototype in this case is more to flesh out the idea and its associated functions, without concerns for code quality or security.

It would help a lot in building the road map for an application, but you definitely wouldn't want to use any of it in production.

Re:Poll: What Language would/do you use to build a web appli... by 1qaz2wsx3edc on Friday June 14, 2013 @04:20PM (#5882248)
Some frameworks are designed to help with this step though. For instance: Rails has scaffolds & generators, angular.js has directives (plain old html views you can open), html itself can be used for mock-ups (and there are plenty of others as well).

Specifically, why build a partially functional prototype only to throw it away for another framework down the road.

It seems naive to me, because the effort you put into the prototype is mostly dropped (except for high-level mental models). Rather then building a throw-away prototype, I think it's better idea to build a prototype you can refactor and improve, with one set of tools.