News for hackers. Stuff that matters.
Re:Deku: How we built our functional alternative to React by throwaway1979 on Tuesday May 12, 2015 @09:48AM (#9531705)
I'm disappointed for a different reason. I'm just sick and tired of the delta new thing. Frontend dev as it is practiced today is horrible ... libraries and frameworks seem to have shelf lives measured in months!

I was watching a video posted this morning (how NYT uses Go) and the dev was mentioning how challenging their system used to be with different languages - Python, PHP, Java and Groovy ... so they decided to redo major chunks in Go. Seriously?

I don't pretend to have the answer ... stopping to innovate isn't going to cut it. But I increasingly feel that as a tech worker, I'm on a train careening towards a ravine without a bridge. But hey ... lets go faster and it'll be a fun ride!

Re:Deku: How we built our functional alternative to React by vorg on Tuesday May 12, 2015 @03:47PM (#9534372)
> their system used to be with different languages - Python, PHP, Java and Groovy ... so they decided to redo major chunks in Go. Seriously?

Valid reason for a rewrite, especially considering the quality of one or two of those languages. A language can look and run OK when used for a script calling system code, but when those scripts are glued together and become the system, all sorts of problems can manifest. It's only sensible someone there looked at the sit and planned out a replacement.

Re:Deku: How we built our functional alternative to React by geon on Tuesday May 12, 2015 @10:57AM (#9532207)
> libraries and frameworks seem to have shelf lives measured in months!

What "shelf life"? If the library works for what you app needs it to do, there is no use by date.