Choosing a Development Stack

medium.com

1 point·ironmagma··3 comments

I couldn't agree more with the recruitment, and the future momentum of the stack you choose.

I try to stay straight through JavaScript. Fast and gets the job done on most projects these days. Most API's support Node.js and so does AWS Lamba etc. I want to build a web based platform at https://ikooru.com/ I am just bouncing between react and angular libraries more than frameworks.

It's not that things like PHP are not an option. But other than the front end WordPress site... or if you are build wp apps. I'd rather go with Facebook and Google using JavaScript libraries than fight an up hill battle in the future.

Even just restricting yourself to the Node ecosystem, there are a surprising number of options. ReasonML, Rust, Clojurescript, Purescript, and even oddballs like Idris can compile to something runnable in JS land and `require()` node modules. With so many options, the decision can be a little more complicated now.

Very true, that's why I think sticking to one framework is sooo much better. Because just like you said in JS land "so many options, the decision can be a little more complicated now."

Keeping it simple is were I am at... and if I need something from a python ML library I just connect it through Lambda on AWS or use an API for their data tools. JS is catching up in ML too though.

Even more interesting will be seeing the AI coming is VS code. That might break down many barriers when it comes to winning the framework battle.

Reply on news.ycombinator.com