I would be hesitant to choose a language with a GC to develop games on a mobile device.

I would love to work for a remote company. I had partial remote work for awhile and wanted to just go full remote.

Someone shared this too: https://github.com/lukasz-madon/awesome-remote-job

I like Python's syntax, I enjoy how easy it can be to get up and running with something real. I also like that Ubuntu comes with it, but everything else is crappy. I don't like the package system, pip is not that great and needs work. The almost cult like refusal to upgrade to 3.x weakens the community resulting in less available modules. It's also not a very strong contender for web development.

Not as strong as other languages perhaps, but Django & co. are more than capable of turning out nice web stuff.

That's not the work of Communism, that's the work of a mad dictator using his power to change his government into an authoritarian sovereignty.

If it was actually communism, he would have never had that kind of power.

If I was going to be nitpicky, it was not actually communism, but it was partly the work of some aspects of communist theory, as the idea of state communism was that you had to go through this immense struggle and remake society before you got to the nice fluffy city on the hill.

However the folk who rose to the top realised that if they wanted to stay on top, they had to keep the struggle bit going indefinitely.

Never mind that the nation was a bad starting point from the outset...

I really need someone to explain to me what they love so much about React.js. I tried it out and I absolutely hated the way components didn't understand their relation with other components. I had to chain a callback all the way down to my ListItem Component just so it could set which item was selected in the component and let other components know that. If you ever end up adding another parent component you have to rewrite all those top level components to pass that information down.

That's because you used React alone, which works as a top-down view engine. If you want to modify something in the view, you have to go back to the top and modify the model. Instead of doing it manually, Facebook has created the Flux architecture to help you scale this process efficiently.

So Facebook created an architecture to solve a problem their new web framework introduced?

No, they created an architecture and decoupled their web framework from it.

Which was a poor decision, imho. Using React only makes sense with Flux, why separate them? Furthermore, the examples on React's docs use the pass-down-the-event-handlers madness, instead of using Flux. React+Flux is a good solution, but the documentation leaves a lot to be desired.

React components can be brought into any architecture. Using them with flux certainly simplifies many things, but by the same token, flux apps can be written using other libraries (react based like om, or even full frameworks like angular). The decoupling is good. It lets you try out a component from http://react.rocks/ without diving into a fully architectured SPA.

I think if you need to pass callbacks several levels down you should consider some form of event system so that you may decouple your components from the hierarchy.

Try going sideways once things get too nested for callbacks not to be arduous: https://github.com/rpflorence/react-training/blob/gh-pages/l...

Another option (albeit currently an undocumented one) is to use contexts to obviate the need to pass things down manually: http://davehking.com/2014/11/15/introduction-to-contexts-in-...

You have a very topical understanding of how to structure an app with react then.

That's because React only makes sense if used with Flux. Otherwise just use Ractive.js - components can communicate with each other via events, so you don't have to pass event handlers down the hierarchy.