But it's that silly rich apps phrase that's the problem. I still love Rails, and still use it for a lot of apps I build. And I deeply apologize for using the phrase rich apps I don't think I've ever said such Enterprisey words before.īut yeah, things are different now. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. It's always been a nightmare to deal with all of the aspects of that silly language.īut wowza, things have changed. I have truly hated JavaScript for a long time. there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js) however, without writing completely in JavaScript, we would not have seen the results we did. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app. We’re using JavaScript for everything – both front and backend. Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks) Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Async/Await is powerful and easy to use (Async/Await vs Promises). With ES6 and Node.js v10.x.x, it’s become a very capable language. We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |