4 ms·

I had to do a survey of the modern web world for a greenfield project my company is working on, and I ended up with AngularJS 1.x and Rails. Angular is by far

by Ocerge 11y ago

I had to do a survey of the modern web world for a greenfield project my company is working on, and I ended up with AngularJS 1.x and Rails. Angular is by far the easiest to get in to, has the most stable libraries, and is relatively well known at this point. I know Angular 2 is coming and that everyone has moved on to React, but it's been more than successful at giving us a stable stack to work around while also producing something that works great for our customers. If React is still around in 3 years and has mature libraries for everybody to use, then sure, I'll take a look. But for now, I think my strategy of being a few laps behind is working, at least anecdotally.

tetha 11y ago
Quite honestly, if someone asks me for a technology for their backend, I'll ask if they need performance or flexibility. The answers will be Java if they want to be fast, or Ruby if they want to be flexible. Those are not shiny new kids on the block, but they are understood, proven technologies.
- aantix 11y ago
  Fast in what context? Fast web requests? Basecamp 2 had 50 millisecond responses when employing Russian Doll Caching and Turbolinks.
  - theodorton 11y ago
    I believe fast in terms of concurrency. Ruby comes out pretty bad compared to node.js.
    - sotojuan 11y ago
      If you want concurrency with Ruby-ish syntax (but a vastly different paradigm), check out Elixir.
- auvrw 11y ago
  why Ruby instead of Python? why Java instead of... well, i guess there isn't a language w/ GC and an ecosystem as "mature" as Java. with clojure, which is indeed shiny and new, some people have cake and eat it too: speed of the jvm + flexibility of scripting. i guess a samish sort of thing could be accomplished w/ jython+Java if clj is too flashy. anywho, i hear the "don't go for the glamor," thing and indeed try (i.e. make a conscious effort) to lag 'teh new hotness' by some interval. ES5 strict is usually good enough. indeed, tail calls are the one coolest feat.s ES6 to me, and they're pretty much everywhere unimplemented, including Babel, except maybe for some special cases. w/ Java... it's a language i wish would move toward vanishing -- or at least go one layer deeper than everyday application development. when i first started writing applets, it was the coolest thing ever: Sun was awesome, the same program ran everywhere, there was automagic memory management, etc... now, Oracle's laying down all kinds of noise a/b owning the language, there are other runs-everywhere platforms/methods (ES, LLVM), and the Java language itself just looks incredibly noisy unless one uses some of the really excellent (but wo/man-hour costly) tooling expressly designed for handling it.
  - tetha 11y ago
    > why Ruby instead of Python? Partially, because I've been burned too much by pythons packaging madness. But beyond that, there is a bunch of strong, mature tooling done in ruby. Rake as a task runner, Thor as a simple library for more complex tools, guard as a general nice-ness, if you wanna go there, the entire chef-stack. And if your main application is in ruby, there's very little overhead to use these strong tools to make your entire infrastructure better for little additional education, build chains or further investment.
ErikAugust 11y ago
I love Angular 1 because I can be quite productive in it, and expect to keep on keeping on with the Angular 1 branch for years. I will not be jumping to 2 nor will I jet off to learn React. Good to see others who have decided to keep on with what works.

by Ocerge 11y ago

tetha 11y ago

Quite honestly, if someone asks me for a technology for their backend, I'll ask if they need performance or flexibility. The answers will be Java if they want to be fast, or Ruby if they want to be flexible. Those are not shiny new kids on the block, but they are understood, proven technologies.

aantix 11y ago
Fast in what context? Fast web requests? Basecamp 2 had 50 millisecond responses when employing Russian Doll Caching and Turbolinks.
- theodorton 11y ago
  I believe fast in terms of concurrency. Ruby comes out pretty bad compared to node.js.
  - sotojuan 11y ago
    If you want concurrency with Ruby-ish syntax (but a vastly different paradigm), check out Elixir.
auvrw 11y ago
why Ruby instead of Python? why Java instead of... well, i guess there isn't a language w/ GC and an ecosystem as "mature" as Java. with clojure, which is indeed shiny and new, some people have cake and eat it too: speed of the jvm + flexibility of scripting. i guess a samish sort of thing could be accomplished w/ jython+Java if clj is too flashy. anywho, i hear the "don't go for the glamor," thing and indeed try (i.e. make a conscious effort) to lag 'teh new hotness' by some interval. ES5 strict is usually good enough. indeed, tail calls are the one coolest feat.s ES6 to me, and they're pretty much everywhere unimplemented, including Babel, except maybe for some special cases. w/ Java... it's a language i wish would move toward vanishing -- or at least go one layer deeper than everyday application development. when i first started writing applets, it was the coolest thing ever: Sun was awesome, the same program ran everywhere, there was automagic memory management, etc... now, Oracle's laying down all kinds of noise a/b owning the language, there are other runs-everywhere platforms/methods (ES, LLVM), and the Java language itself just looks incredibly noisy unless one uses some of the really excellent (but wo/man-hour costly) tooling expressly designed for handling it.
- tetha 11y ago
  > why Ruby instead of Python? Partially, because I've been burned too much by pythons packaging madness. But beyond that, there is a bunch of strong, mature tooling done in ruby. Rake as a task runner, Thor as a simple library for more complex tools, guard as a general nice-ness, if you wanna go there, the entire chef-stack. And if your main application is in ruby, there's very little overhead to use these strong tools to make your entire infrastructure better for little additional education, build chains or further investment.

ErikAugust 11y ago

I love Angular 1 because I can be quite productive in it, and expect to keep on keeping on with the Angular 1 branch for years. I will not be jumping to 2 nor will I jet off to learn React. Good to see others who have decided to keep on with what works.