31–40 of 45 posts
Take a step back and think hard about what you need the stack to do.
If you are very proficient in a stack and it will do the task with dependency he’ll or too many junk layers, that is the best one to use.
If you care about what is sexy or popular or cool, you’re doing it wrong
Flour, sugar, salt, baking powder, eggs, milk, and butter The pancake stack Never neglect the importance of a healthy breakfast for the startup grindset
Earlier quoted context omitted.
I would go for something similar. I would try supabase + Astro. With astro you can have more choice in frontend framework, vanilla js, alpinejs, react, svelte, vue. I recently made a portfolio website for my girlfriend and the experience was awesome. https://zhazira.design/ If anyone's hiring junior designers ;)
If you are building a blog or something content Astro is a great choice! The portfolio looks great, congrats! I hope she will find a job soon, and good for you for building & promoting it ;D
I personally really like their approach to templating and components as well as server vs client side JavaScript.
Depends on which programming language you’re most familiar with. For python I would go with Django and htmx, Ruby, rails plus Hotwire, Php, Laravel with livewire or inertia, Elixir, Phoenix with liveview, C sharp, asp.net razor pages and htmx, Java, spring boot and htmx, JavaScript, express or sailsjs and htmx
Full .NET stack. - Self-hosted identity management, "ASP.NET Core Identity", using new scaffolding from .NET 8 - Blazor, using the "Auto" mode from .NET 8: Default to SSR, autopromote to Server mode for live updating components - EF Core for DB handling The idea is to focus on keeping things simple and easy for the developer. The most annoying part about the stack is the way Microsoft names things. Keeping the render…
.NET is such a cluster of poor naming choices
Supabase + Next.js is what I'm using. To cover your list: - Auth: Supabase has auth, with oauth support for many services. Also prebuild UI for login forms etc. It's really easy to set up - Live updates: Supabase has a realtime api to send messages, or subscribe to db changes - Database: Supabase is basically a Postgres database with a bunch of stuff on top, it generates a REST/GraphQL api from your schema, meaning y…
Seems very interesting. What would recommend for followings: 1) Background jobs - Something like Sidekiq for Rails. 2) Admin Dashboard - Something admin interface of Django or active-admin for Rails 3) Authorization 4) Is NextJs good for working with Websockets ? Do you have/know any git repository which implements this stack ?
https://github.com/seomoz/qless Is the original project.
Full .NET stack. - Self-hosted identity management, "ASP.NET Core Identity", using new scaffolding from .NET 8 - Blazor, using the "Auto" mode from .NET 8: Default to SSR, autopromote to Server mode for live updating components - EF Core for DB handling The idea is to focus on keeping things simple and easy for the developer. The most annoying part about the stack is the way Microsoft names things. Keeping the render…
I just want to note how much time would be lost to confusion on my team, if we had to differentiate between "Server Side Rendering" and "Server mode"... .NET is such a cluster of poor naming choices
It is my main gripe with the .NET ecosystem. Don't get me started on Azure..
But once you get over the hump and understand the meaning of the subtle differences, it's possible to make sense of it.
and Use Swift for macOS app and iOS apps
use flutter to make iOS and android apps
My latest is the macOS app that is a window manager
For the rest of your questions,
- Auth: Auth0. Simple to get started, and depending on your plan you can enable SSO for business clients.
- Frontend: Plain ol' HTML, CSS, and minimal JS. This is where HTMX and AlpineJS comes into play. Elements can be updated without a whole page reload creating a better user experience.
- Backend: Go. A language I love to use. Fast, simple, and deployed very quickly.
- Database: Turso. Dead simple, easy to use, and with easy replication to different regions.
My app code is all contained in a monolith, which is deployed onto a dedicated web server. I can either update the server resources or using a load balancer I can deploy more servers running the application to increase scale (if necessary).
I've started using what I've dubbed the HAG (HTMX, AlpineJS, Go) stack for my "startup". It's really simple and easy to get into. I do try to minimize the use of third party packages/modules to reduce my attack surface. For the rest of your questions, - Auth: Auth0. Simple to get started, and depending on your plan you can enable SSO for business clients. - Frontend: Plain ol' HTML, CSS, and minimal JS. This is where…
I've been looking at HTMX + Go for some time but I just don't know if it's worth it over React which I already know. Is it really more productive, or is it simply a ideology/hype thing? I'm also a Go fan because it values simplicity, which I think we should all strive for, so the HTMX + Go combo appeals to me, even though I haven't looked at HTMX as I mentioned. Having to use C# and TypeScript at work, I start to see the real appeal of simplicity more and more... I'm becoming a grug brained dev :O