News for hackers. Stuff that matters.
Re:Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember by asciihacker on Tuesday August 30, 2016 @11:05AM (#12390782)
Speed is one thing, but the fact that you must replicate your business model client AND server-side with Elm is a huge minus. I would take ScalaJS over any 4 of those frameworks any day.
Re:Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember by jeremiep on Tuesday August 30, 2016 @11:25AM (#12390979)
Why not just use Clojure?

You've got datomic on the server and datascript on the client, transit on the wire, reader conditionals to share code and much more. Plus everything can be modified as its running.

When it comes to web frameworks I don't really care about performance as much as I care about managing complexity. Which is why I'm looking at om.next over all the other frameworks.

And managing complexity is not something you can benchmark in toy projects - every single framework is virtually the same at such a small scale.

Re:Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember by premium-concern on Tuesday August 30, 2016 @02:08PM (#12392424)
Clojure doesn't even have types.

I think the languages aren't really comparable from a maturity and support pov. Clojure is mainly done by hobbyists and enthusiasts. There is a large gap in terms of tooling that can't be closed in a few years.

Re:Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember by asciihacker on Tuesday August 30, 2016 @12:00PM (#12391279)
> Why not just use Clojure?

I guess as a professional Python developer, it would take some time to get used to all the parentheses. I've used Emacs for 20+ years, but outside of elisp I've never been comfortable with s-exprs.

I had never heard of om.next. I think this is what you mean: https://github.com/omcljs/om ?? correct?

> And managing complexity is not something you can benchmark in toy projects - every single framework is virtually the same at such a small scale.

Well, looking at how much garbage was needed to implement todomvc in Backbone kept me from considering it any further :)

Re:Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember by throwanem on Wednesday August 31, 2016 @06:04AM (#12397194)
> looking at how much garbage was needed to implement todomvc in Backbone kept me from considering it any further

And in this you were wise! Or at the very least fortunate.

Re:Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember by Roboprog on Tuesday August 30, 2016 @11:42AM (#12391141)
Or just use Javascript as-is, with perhaps Node.js or Nashorn on the back end.

But I actually like Javascript.

Re:Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember by Roboprog on Tuesday August 30, 2016 @11:43AM (#12391150)
And not so much care for the transpiler hoop jumping routine.
Re:Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember by jmite on Tuesday August 30, 2016 @10:25PM (#12395537)
I like my types, without runtime overhead of type checks
Re:Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember by appsappsapps on Tuesday August 30, 2016 @01:38PM (#12392141)
Elm on the frontend and Haskell on the backend is a sensible choice, though at that point you may be better off with PureScript on the frontend.
Re:Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember by Mickydtron on Tuesday August 30, 2016 @03:49PM (#12393285)
I have a hobby project that uses Elm on the front end with Elixir and Phoenix on the back end, and that has been working really well. Elm's event machine like architecture goes well with Phoenix's native support for channels, although the elm library for Phoenix Channels is definitely not production ready.

It has been a very bizarre experience having dynamic typing on the back end and static on the front end, though. Everything feels slightly topsy turvy.

Re:Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember by jmite on Tuesday August 30, 2016 @10:25PM (#12395540)
I think server side Elm will come eventually. It's just taking time.