Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Join
12
Likes
24
Comments
What front-end framework are you using and why
by
Paul-Simon Emechebe
React.js has seem to be the most dominant answer, what do you guys think?
Vue.js is my top choice.
In my career I went through:
but finally, when it came to building a product I found myself most producing with Vue. For some cases also Nuxt.js.
Why:
Your millage may vary ;)
I had to use both ReactJS and VueJS professionally. I found VueJS lacking in TypeScript support, the ecosystem fragmented and slow to update, and just missing things I would expect for enterprise. In my opinion, it does not compare the the vibrant and cutting-edge ReactJS ecosystem.
I will say, VueJS is good when you need to bolt it onto an existing system.
Such as?
The biggest pain I remember was the lack of support, especially with fragmented Vue 2 / 3 and some libraries not updated or abandoned all together. Rewriting when you attempt an upgrade is not something you want to spend time doing.
In contrast, React 16 to 17 only changed three files of hundreds. React 18 and strict mode is a different matter though…
Thanks for sharing.
I jumped to Vue right after 3 went out of RC. I saw the library split between v2 and v3 but nothing major. In my use case at least.
So while your mileage may vary, I am quite happy with my choice.
Can't speak much about React. Never really tried it.
We use Scala.js + Laminar (https://laminar.dev/)
https://dev.to/raquo/my-four-year-quest-for-perfect-scala-js-ui-development-b9a
Check out the video: https://youtu.be/L_AHCkl6L-Q
Flutter is great, I can make a mobile app and turn it into a website and desktop app super easily, unlike with React or React Native.
Same here! Absolutely amazing framework. Been using it since an early beta and it was actually the trigger to get into app development for me. Always wanted to do that, and Flutter was much easier to start with than native.
For real. Flutter 3 is even better now.
We recently launched with SvelteKit + Tailwind Css + Firebase and love the developer experience. https://kit.svelte.dev/
It's easy to integrate with other technologies and we even have a portion of the site that includes a React component library and it was easy to do. I'd definitely look at SvelteKit again for my next project.
NextJS gives me everything I need!
ReactJS + Next JS! This gets the job done almost everything. So I didn't feel the need to use any other frontend framework.
Currently React and Next JS. I've dabbled a bit with Remix and it looks promising. Need to try building something with it.
Prior to these frameworks, I did a lot of work with Vue and some Angular... and before that jQuery. I feel like for me personally, React just makes a lot of sense and I've had a lot of longevity with it.
I've enjoyed using no framework lately, especially when starting small things like https://linkians.com. You can go surprisingly far with just document.createElement and friends.
Angular because I know it.
I feel like React is the best choice at this moment, especially for people relatively new to front-end development. In my opinion, community is key. A large community results in more available integrations, plugins, tutorials, Q&A posts (StackOverflow, Github, etc), and less bugs, which help people learn & get things done quicker.
Doesn't mean other front-end frameworks don't serve any purpose though. For experienced front-end devs, people who like to squeeze out a bit more performance or use cutting-edge tech, other frameworks may be a better choice.
React with Thin. It's a great match, React for the view layer and Thin for dealing with Database Access.
OKay, Ill check out Thin. Thanks man.
Is thin self hosted or is there a paid version too?
There's a paid version available, check https://thin.dev/pricing Self hosted is coming soon :)
Supabase and Thin seem similar. The tech is interesting but the authentication using PostgreSQL policies seem a bit wacky to me.
A long time back we moved away from not storing business logic in the DB layer.
What has changed fundamentally that these startups are again promoting these practices?
Or is it that a new generation is here who have forgotten those pains? :)
One major difference to Supabase is that Thin provides optimistic updates, so that e.g. write operations show up in the UI instantly.
I'd consider auth logic and business logic two different things (can be a bit blurry sometimes). With the Thin migration system it actually works very well (one common argument against putting this into the DB is always that it's hard to manage/version control). Another advantage for PG policies: When you're later adding other microservices to your app they can also automatically reuse the existing Postgres Policies and you don't need to duplicate them across different services.
:) That could also be a reason
Ya that makes sense and is a good use case.
I guess what scares me is to see triggers sending emails etc as in the thin docs.
As long as users are mindful I guess it shouldn't be an issue. But I really would love to see how it scales up to a large app with 100K users etc.
Like how complex a traditional back-end app gets and now imagine big chunks of that whole complexity is in the DB layer.
Having said that Thin is really cool.
At a certain point of complexity I think it might be useful to use a "normal" handwritten backend next to Thin. Basically doing all CRUD frontend stuff with Thin and then running the business logic with the handwritten Backend. If both use the same JWT private key, it should work right away.