- JAVASCRIPT RSS READER INSTALL
- JAVASCRIPT RSS READER SOFTWARE
- JAVASCRIPT RSS READER CODE
- JAVASCRIPT RSS READER DOWNLOAD
We have a rather decent deploy flow going on to ensure stability and maintainability. Every desktop version of the application is deployed inside of Electron, allowing us to bridge the gap between web and desktop.Īs for the back-end API, that’s another story. In all, it costs us a few dollars a month to host. The web version of Winds is statically hosted on S3 with CloudFront.
JAVASCRIPT RSS READER CODE
Being that Winds 2.0 is open-source, we wanted to share a few of the tools we use to get the job done when it comes to getting our code from our machines up to the server. It’s rare that you hear about how a company deploys and manages code.
JAVASCRIPT RSS READER INSTALL
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.Nearly every developer knows or can, at the very least, read JavaScript.Here’s a quick breakdown of some of the reasons why we chose JavaScript: 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. More importantly, JavaScript’s maturity has started to shine with the added support of the Async/Await syntax.
JAVASCRIPT RSS READER SOFTWARE
Sure, it has its quirks – single threaded, callback hell, etc.– but we believe that it’s possible to build great software in any language.įor Winds, JavaScript has been a great choice to foster a community around the project. What’s funny about JavaScript is how many people complain about it being an inadequate language.
Most of our team is experienced with Go and Python, so Node was not an obvious choice for this example app. If you were brave enough to explore the codebase, you probably noticed that we’re using JavaScript for everything – both front and backend. We want it to be easy for anyone to be able to notice something they don’t like about their RSS/Podcast experience and easily submit a pull request with a fix or addition. Our hope with this project is to make a contribution to #ReviveRSS.Īnother core goal for Winds is to enable a wide range of developers to contribute. One of our goals with Winds is to answer the questions we had been asking ourselves: What if a community of developers and designers could create an RSS experience that’s simplistic and polished? Could this reverse the downward spiral of less users taking advantage of the technology and more publications dropping support? We realize that many RSS power users are developers, designers and journalists.
Next up, let’s talk a little bit about the Winds 2.0 stack and why we chose to go with the technologies we did (and why we chose to build Winds in the first place!).
JAVASCRIPT RSS READER DOWNLOAD
To get started with Winds 2.0, you can try the web version or download the application here, or if you feel more adventurous head over to GitHub and spin it up locally.
Winds, however, is based on Node.js, MongoDB Atlas, Express, PM2, Bull, Babel and React. You may have seen the blogpost that StackShare wrote about how Stream powers the activity feeds for 300 million users using Go, RocksDB and Raft. The tech stack for Winds is completely different from that of Stream. Going into it, there was no way to anticipate how popular Winds 2.0 would become - would it be an absolute hit or an epic failure and waste of time? The team enjoys building example apps so I knew it wouldn’t be a total loss, and it’s been rewarding to see this new iteration being used so extensively in the first month after release. Since launching in mid-May the application ranked #1 on Hacker News for over a day, has 5,200 stars (and counting) on GitHub and became a trending app on Product Hunt.
The initial response around Winds 2.0 has exceeded all of our expectations. Winds started out as a simple example app for Stream, but thanks to an outpouring of support from our awesome community we decided to focus more time and energy on the project.
0 kommentar(er)
