News for hackers. Stuff that matters.
Re:Don't use Hadoop when your data isn't that big (2013) by eropple on Wednesday May 24, 2017 @11:47AM (#14410876)
At this point, I'm not sure I agree. I am...not a fan of JavaScript, to put it mildly (though ES6 does a lot to suck less). But for my money, nothing out there is better at templating even static HTML than React and JSX. The compositional nature of components is way better than any other templating stack I've ever used and it's pretty easy to bake it into static HTML (Gatsby and `react-html-email` being awesome projects for it).

I'm sure there are declarative, object-oriented (rather than text-oriented) templating engines out there that use an approach like React's. But I would consider using an imperative, text-oriented templating language a yellow, if not red, flag in 2017.

Re:Don't use Hadoop when your data isn't that big (2013) by paulddraper on Wednesday May 24, 2017 @09:02PM (#14414646)
I use Twirl, included in the Play Framework (Scala/Java).

It is functional (well, as functional as React), and templates compile to plain 'ol functions, so compatibility and static typing is the same as the rest of the your program.

Obviously, if I needed a SPA or something, it's not what I would use, but again, not everything should be an SPA.

Re:Don't use Hadoop when your data isn't that big (2013) by eropple on Thursday May 25, 2017 @12:52PM (#14418468)
You don't need to use React as a SPA, though, is what I'm saying. (When using React, those component trees, too, compile to 100% plain-ol'-functions.)

Twirl is fine, insofar as it's attached to the Play (that's not to impugn you for picking it, my history with Play is colorful and frustrating). I wouldn't raise a flag for that. But not using something in this vein definitely is, and React is probably the most accessible way to do it for the 90-95% case of developers.