Go + Go + Sqlite
How do you access SQLite? I’d love a “pure” go way to do so
I like modernc.org/sqlite[1] - a port of the C SQLite3 library to Go. No need for CGo, so straightforward to build and cross-compile.
Ask HN: What is your preferred “full-stack in a box” solution and why?
31–37 of 37 posts
Re: Ask HN: What is your preferred “full-stack in a box” solution and why?
#32RedwoodJS. I feel like I am the only one to ever mention it on HN. It feels like I know a secret that no one else knows. Here's how the landing page describes it " Built on React, GraphQL, and Prisma, with full TypeScript support, and Webpack/Babel ready to go with zero config. Redwood gives you the workflow you love, but with simple conventions and helpers to make your experience even better. "
I played with RedwoodJS over the holidays and there is a lot to like. However it does paper over a lot of complex things with fairly leaky abstractions currently. Expect to have to understand how GraphQL, Prisma, and React work whenever you encounter something that doesn't quite work.
This is not uncommon with most frameworks in the early days. I used Ruby on Rails since just before 2.0 and it was similar back then.
But the team behind RedwoodJS is great, and there's a nice community on Github, Discourse, and Discord. So I'm expecting great things.
Plus it's nice to have an omakase approach to learning all of the new frontend tech and getting something working quickly.
Re: Ask HN: What is your preferred “full-stack in a box” solution and why?
#33Personally, I tend to go with Ruby on Rails and PostgreSQL run on Heroku. I recognise it has its limitations — Heroku’s pricing isn’t favourable for large apps, for example — but, combined with Hotwire [1] (which now comes out of the box, IIRC), it’s a powerful solution for most LOB apps. [1] https://hotwire.dev
I'm trying Hotwire for a personal project and have really been enjoying it so far, but it is very different from what I'm used to (more SPA-y frameworks like React + JSON API). My main fear is that I'm tying myself too much to Rails-specific libraries and that upgrades and migrations will be harder.
I have to admit that I worried about this for a while. I’m not sure on your risk tolerance, but I found solace in that Rails was developed by 37signals for Basecamp back in 2004, and they’ve been maintaining it ever since.
Re: Ask HN: What is your preferred “full-stack in a box” solution and why?
#34Personally, I tend to go with Ruby on Rails and PostgreSQL run on Heroku. I recognise it has its limitations — Heroku’s pricing isn’t favourable for large apps, for example — but, combined with Hotwire [1] (which now comes out of the box, IIRC), it’s a powerful solution for most LOB apps. [1] https://hotwire.dev
Do you use Heroku's managed PostgreSQL service?
Unless I’m working with existing databases, yes.
Re: Ask HN: What is your preferred “full-stack in a box” solution and why?
#35Typescript, React & Posgres or SQLite. I’m really enjoying Remix.run. It’s shares some commonalities with SvelteKit & NextJS. . This is subjective of course, but I enjoy how in Remix there is only 1 way to fetch data, which I believe is simpler mental model & way to get started with or work with: “The fundamental difference here is that Next.js has four "modes" for getting data on the page: (1)getInitialProps - calle…
For reference, the linked article is in no way an apples-to-apples comparison.
Re: Ask HN: What is your preferred “full-stack in a box” solution and why?
#36RedwoodJS. I feel like I am the only one to ever mention it on HN. It feels like I know a secret that no one else knows. Here's how the landing page describes it " Built on React, GraphQL, and Prisma, with full TypeScript support, and Webpack/Babel ready to go with zero config. Redwood gives you the workflow you love, but with simple conventions and helpers to make your experience even better. "
I played with RedwoodJS over the holidays and there is a lot to like. However it does paper over a lot of complex things with fairly leaky abstractions currently. Expect to have to understand how GraphQL, Prisma, and React work whenever you encounter something that doesn't quite work. This is not uncommon with most frameworks in the early days. I used Ruby on Rails since just before 2.0 and it was similar back then.…
I haven't hit that yet. One of the principals I am following in my side project is to keep everything as simple as possible (he says while using a JS stack!). I know React but have been getting to grips with using GraphQL and Prisma.
TIL what omakase means. Thanks!
Re: Ask HN: What is your preferred “full-stack in a box” solution and why?
#37Simple PHP/MySQL backend with any frontend, usually Vue.js + TypeScript for quick projects and React + TypeScript for larger ones.
I really like Vite and the Vue3 setup script syntax, I might switch entirely to VueJS in the future, but the React libraries are better.