Is this project a serious one? If it is, go for something mature and something you are familiar with even if it's "unsexy" like PHP and jQuery [1]. Learning a new technology while building your product can be fun, but it is often counterproductive. Unless your project has specific needs which only a few technologies can fulfill, it'll be just fine. Choosing something familiar allows you to focus on your project instead of your tech stack.<p>Don't worry too much about choosing the "wrong" language or framework. What you build matters more than how you build it. For example, many would recommend Postgres over MySQL for good reasons, yet those who use MySQL are doing just fine [2]. Their advantages are often insignificant in practice, so feel free to ignore the hype (especially here on HN)!<p>Angular, React, Vue are all fine choices for building SPAs. Rails is kind of out of place here (it's not a front-end framework). The hype around it has died, but Rails itself is still very much alive, and it's very mature. ClojureScript and Elm may need a bit more getting used to depending on your experience. Their communities are relatively small though, so you'll have less resources available.<p>[1] PHP gets a bad rap for its past, but modern PHP really isn't so bad (very Java or Ruby like, depending on the framework that you choose). jQuery is "old", but reliable. Not a good idea if you're building something highly interactive, but if you only need "a little bit of JS" then it seems like a good fit. SPAs have many advantages, but are also much more complex, so avoid building one if you don't need to.<p>[2] <a href="https://www.mysql.com/customers/" rel="nofollow">https://www.mysql.com/customers/</a>