It doesn’t really matter.
-
-
-
It's at minimum interesting :)
-
Alright.
Go
End of conversation
New conversation -
-
-
I thought one selling point of Reactjs was isomorphism so isn't there a need to run JavaScript as a part of the backend?
-
You still need to serve the application
-
That's my point a backend JavaScript engine to get isomorphism such as Node as a part or whole of the backend i.e Node in front of X
-
When I mean isomorphism I mean the page/data is rendered in the browser but it can fallback to server side rendering using the same code.
-
Not every react app uses react to prerender on the server (I think it's a small minority in practice but don't have exact numbers).
-
I realise that however I personally that it's one of the best selling points of React great for progressive enhancement.
-
It makes is *way* harder to maintain & deploy, so it is only valuable in some specific use cases, and for some of those there are better options than React.
-
Could you name a couple of them? We do a large SPA on React but also need highly SEO'd content so the only option currently is to pre-render by route and serve rendered html over nginx with progressive enhancement.
- 3 more replies
New conversation -
-
-
Any resources you found helpful in learning Go?
-
To be honest, I just did http://tour.golang.org and started building stuff. Most of my learning came while I was on the job.
-
I’ll check it out! Thanks.
-
This is by far the best resource i’ve found while learning it https://astaxie.gitbooks.io/build-web-application-with-golang/content/en/02.0.html … This is good too https://gobyexample.com
- 1 more reply
New conversation -
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Laravel/PHP
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Java Tomcat
-
No
@IslamAttrash.... Java ? Why ? Just why ?



pic.twitter.com/VpfFkHlgTB -
Hahahahaha


... If it was me absolutely I'll go with Node, but this the backend stack at work -
"It's already written, tested and works well" is my favorite argument for any language

-
If you mean "argument for any *App*", it's pretty robust argument indeed. If you really mean "argument for any language", it's unheard of, it doesn't make any sense

-
For using a specific language for a specific application, which is the only context in which the question "what language should I use?" makes sense. There is no single best language, and I don't think there ever could be.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.