15:[[31170481,{"by":"contr-error","descendants":158,"id":31170481,"kids":[31171641,31172822,31170974,31171577,31172374,31171424,31170542,31170906,31171757,31171754,31171970,31171815,31171702,31171631,31171530,31171447,31172535,31170600,31172112,31172280,31175502,31177806,31170840,31171470,31175334,31199474,31170996,31179105,31204727,31174124,31171799,31172714,31171566,31177780,31173190,31171857,31172548,31171511,31207043,31172464,31171917,31171735,31171920,31170825,31171687,31172956,31171859,31175053,31171795,31192295,31178392,31171450,31171856,31172108,31177919,31301309,31226667,31177170],"score":106,"text":"I'm currently going through Destroy All Software's screencasts [0]. They're heavily based on Ruby + Rails and TDD, although most of the concepts probably do do translate to other languages.

Since the screencasts are over 10 years old now, I'm wondering if Ruby on Rails is still going strong. What resources would you recommend to get into Ruby/Rails specifically? Same question for TDD? Thanks!

[0] https://www.destroyallsoftware.com/screencasts/catalog","time":1650994526,"title":"Ask HN: Is Ruby on Rails still relevant?","type":"story"}],[15355676,{"by":"christianalfoni","descendants":9,"id":15355676,"kids":[15355714,15383481,15355782,15357427,15363446,15355957,15360261,15363384,15355895,15357459],"score":17,"time":1506587984,"title":"Cerebral – Declarative state and side effects for popular JavaScript frameworks","type":"story","url":"http://www.cerebraljs.com"}],[10620250,{"by":"nbenita","descendants":4,"id":10620250,"kids":[10620329,10625689,10622979,10623750,10620304],"score":8,"text":"Hey guys,

I'll start with some context - I'm a UX designer at Wix.com, where I also get to play around with front-end development (Prototyping).

Whenever a framework like React or Angular comes up in a conversation with fellow designers, I will always have a hard time explaining what these tools are/why do we use it.

(I think) I'm having a hard time explaining, because I had never built anything meant for 'production', nor with vanilla.

What I usually end up with, is:\n"a framework asks that you write your code in a specific manner, according to a set of rules. In return, it will do some super clever assumptions, such that your end product will be better (Maintainable, performant, etc...)".

I feel like this explanation could be better.\nAny thoughts?

Thanks!","time":1448366062,"title":"Ask HN: Explaining front-end frameworks to a designer","type":"story"}],[8887019,{"by":"tommoor","descendants":91,"id":8887019,"kids":[8889939,8888285,8888396,8887596,8889906,8887651,8891740,8888141,8888943,8890408,8888288,8888458,8888980,8887406,8891371,8888352,8887640,8890425,8891129,8890159,8906004,8887595,8889279,8888077,8888739,8887568,8888069,8889825,8887564],"score":334,"time":1421251044,"title":"NW.js","type":"story","url":"http://nwjs.io/"}]]

user:	hipertracker
created:	January 9, 2015
karma:	6
about:	https://github.com/hipertracker

1.	8 years ago \| discuss
2.	ReactJS + addons + JSX (--harmony) for Meteor(atmospherejs.com) 1 points by hipertracker 11 years ago \| 0 comments
3.	React + Reflux + Routing + ES6 with Experimental ES7 Syntax + Semantic-UI(github.com) 2 points by hipertracker 11 years ago \| 0 comments