Need advice about which tool to choose?Ask the StackShare community!
#rust #elixir So am creating a messenger with voice call capabilities app which the user signs up using phone number and so at first i wanted to use Actix so i learned Rust so i thought to myself because well its first i felt its a bit immature to use actix web even though some companies are using Rust but we cant really say the full potential of Rust in a full scale app for example in Discord both Elixir and Rust are used meaning there is equal need for them but for Elixir so many companies use it from Whatsapp, Wechat, etc and this means something for Rust is not ready to go full scale we cant assume all this possibilities when it come Rust. So i decided to go the Erlang way after alot of Thinking so Do you think i made the right decision?Am 19 year programmer so i assume am not experienced as you so your answer or comment would really valuable to me
Next.js is probably the most enjoyable React framework our team could have picked. The development is an extremely smooth process, the file structure is beautiful and organized, and the speed is no joke. Our work with Next.js comes out much faster than if it was built on pure React or frameworks alike. We were previously developing all of our projects in Meteor before making the switch. We left Meteor due to the slow compiler and website speed. We deploy all of our Next.js projects on Vercel.
This basically came down to two things: performance on compute-heavy tasks and a need for good tooling. We used to have a Meteor based Node.js application which worked great for RAD and getting a working prototype in a short time, but we felt pains trying to scale it, especially when doing anything involving crunching data, which Node sucks at. We also had bad experience with tooling support for doing large scale refactorings in Javascript compared to the best-in-class tools available for Java (IntelliJ). Given the heavy domain and very involved logic we wanted good tooling support to be able to do great refactorings that are just not possible in Javascript. Java is an old warhorse, but it performs fantastically and we have not regretted going down this route, avoiding "enterprise" smells and going as lightweight as we can, using Jdbi instead of Persistence API, a homegrown Actor Model library for massive concurrency, etc ...
Pros of Meteor
- Real-time251
- Full stack, one language200
- Best app dev platform available today183
- Data synchronization155
- Javascript152
- Focus on your product not the plumbing118
- Hot code pushes107
- Open source106
- Live page updates102
- Latency compensation92
- Ultra-simple development environment39
- Smart Packages29
- Real time awesome29
- Great for beginners23
- Direct Cordova integration22
- Better than Rails16
- Less moving parts15
- It's just amazing13
- Blaze10
- Great community support8
- Plugins for everything8
- One command spits out android and ios ready apps.6
- It just works5
- 0 to Production in no time5
- Coding Speed4
- Easy deployment4
- Is Agile in development hybrid(mobile/web)4
- You can grok it in a day. No ng nonsense4
- Easy yet powerful2
- AngularJS Integration2
- One Code => 3 Platforms: Web, Android and IOS2
- Community2
- Easy Setup1
- Free1
- Nosql1
- Hookie friendly1
- High quality, very few bugs1
- Stack available on Codeanywhere1
- Real time1
- Friendly to use1
Pros of Phoenix Framework
- High performance120
- Super fast76
- Rapid development70
- Open source62
- Erlang VM60
- Well designed46
- Channels45
- Easily Scalable39
- Very extensible35
- Restful35
- Functional Programming11
- Inspired by Rails10
- Great community10
- Beautiful code8
- Ecto8
- Scalable6
- Fault tolerant6
- LiveView feature5
- Elegant4
- Insanely fast and easy4
- Feels like working with rails framework with more power4
- Built-in websocket support3
- Benevolent dictator that decides project course3
- Great integration with GraphQL3
- 2
- Front-End Agnostic2
- Functional approach1
Pros of Trailblazer
- Trailblazer allows creating sane, large apps in Rails5
- Separates business logic from framework3
- Sound Software Architecture principals2
- Improves maintainability2
- Makes Rails better1
Sign up to add or upvote prosMake informed product decisions
Cons of Meteor
- Does not scale well5
- Hard to debug issues on the server-side4
- Heavily CPU bound4
Cons of Phoenix Framework
- No jobs6
- Very difficult5
Cons of Trailblazer
- Hasn't been on Thoughtworks radar since 20141