I think its obvious Twitter moved to server side rendering for control / profitability reasons. Not performance.
Isomorphic JavaScript: The Future of Web Apps
91–100 of 123 posts
Re: Isomorphic JavaScript: The Future of Web Apps
#92If a single-page app is dependent on SEO it shouldn't even be a SPA to begin with.
Re: Isomorphic JavaScript: The Future of Web Apps
#93You keep using that word. I do not think it means what you think it means. Using precisely defined mathematical words in contexts where they only make sense vaguely to a layperson ruins their original usage. Make up a new word. Repurpose a shitty English word. But leave our damn maths words alone. Old man quarterto shakes his fist at you! Get off my smooth, compact lawn!
(author here) Good point. TBH, I have no idea what "isomorphic" means in the mathematical sense. I was inspired to use "isomorphic" from a 2011 article by Nodejitsu [1]. It seemed like a fine way to describe this approach. I would gladly use a better would if I were to find one. [1] http://blog.nodejitsu.com/scaling-isomorphic-javascript-code
Shall "multiplateform javascript [code]" be suitable here? Looks like this is all it's about: having a single js code generating the same results, with no dependance on the plateform.
Re: Isomorphic JavaScript: The Future of Web Apps
#94A great thing about the web is that a multitude of server side languages can be used. While I don't ever want to have to write the same template twice, having everything converge on nothing but Javascript doesn't seem like a very inspiring future to me.
If you are building a service or API, then you can do that in whatever language you like. The natural language for writing client side apps is JS (ok, the only language, for now).
"ok, the only language, for now" - which is deeply unnatural for such an innovative field as IT.
Re: Isomorphic JavaScript: The Future of Web Apps
#95Earlier quoted context omitted.
If you are building a service or API, then you can do that in whatever language you like. The natural language for writing client side apps is JS (ok, the only language, for now).
Correct. If you're already writing a bunch of JavaScript for the client-side, then just think about this approach as migrating some of that client, UI logic to the server.
To have two problems instead of one?
Re: Isomorphic JavaScript: The Future of Web Apps
#96Earlier quoted context omitted.
but who writes clientside logic before serverside logic ?
Front-end developers. Frankly, Node is a way for front-end developers to write server-side code without having to learn too much new stuff.
Yet they keep marketing it as a future for all developers. Thank you, but no, thank you.
Re: Isomorphic JavaScript: The Future of Web Apps
#97I like the basic idea, but my hope is that we can go the other direction and bring more interesting languages to the client side. I know this is done to some extent using JS or Asm.js as a compile target with a whole bunch of existing projects. But it would be great to see this really move forward. It seems like CoffeeScript did this rather successfully, and with source maps, the debugging story is getting better too…
Consider Clojure - an interesting language indeed, and the browser variant (ClojureScript) is gaining lots of interest.
Make it native across major browsers - that would be cool. At the moment it's just another transpiler.
Re: Isomorphic JavaScript: The Future of Web Apps
#98You keep using that word. I do not think it means what you think it means. Using precisely defined mathematical words in contexts where they only make sense vaguely to a layperson ruins their original usage. Make up a new word. Repurpose a shitty English word. But leave our damn maths words alone. Old man quarterto shakes his fist at you! Get off my smooth, compact lawn!
(author here) Good point. TBH, I have no idea what "isomorphic" means in the mathematical sense. I was inspired to use "isomorphic" from a 2011 article by Nodejitsu [1]. It seemed like a fine way to describe this approach. I would gladly use a better would if I were to find one. [1] http://blog.nodejitsu.com/scaling-isomorphic-javascript-code
> I have no idea what "isomorphic" means in the mathematical sense.
Programmers these days!...
Re: Isomorphic JavaScript: The Future of Web Apps
#99You keep using that word. I do not think it means what you think it means. Using precisely defined mathematical words in contexts where they only make sense vaguely to a layperson ruins their original usage. Make up a new word. Repurpose a shitty English word. But leave our damn maths words alone. Old man quarterto shakes his fist at you! Get off my smooth, compact lawn!
Whoa old man quarterto, who said the word ever belonged to math people in the first place? I could argue that math people have a bad habit of squeezing English words into strange contexts that corrupt the original meaning. Take "manifold" for instance, or "curl", or even something as harmless as "mode". They all meant perfectly fine things until the math people claimed them as their own. According to M-W "isomorphic"…
In my understanding, when we're talking about formal languages (which JS is), "isomorphic" has a fairly well-defined and strict meaning.
And there's a (unsolved) conjecture that every NP-complete language are p-isomorphic: http://en.wikipedia.org/wiki/Berman%E2%80%93Hartmanis_conjec...
Re: Isomorphic JavaScript: The Future of Web Apps
#100We do this sort of thing on the site I work on, Google+. Initial page-loads are rendered on the server, subsequent page-loads are rendered on the client. Really good for performance. It's just the templating system that's common code, though, the server is still Java.
sorry thurn, this is off topic: is there a complaint / improvement suggestion page for G+? there are some serious design bugs in G+ that we'd love to have/solve(d) :)