2. VueJS for frontend
3. Hosted on Laravel Forge (using AWS)
4. Amazon RDS - MySQL (or similar) -- relational databases still solve most of the things I need, unless there were specific reasons to switch to a nosql
5. Tailwind CSS
251–260 of 736 posts
2. VueJS for frontend
3. Hosted on Laravel Forge (using AWS)
4. Amazon RDS - MySQL (or similar) -- relational databases still solve most of the things I need, unless there were specific reasons to switch to a nosql
5. Tailwind CSS
HTMX has been very promising, I have bumped into one or two bugs with it but there are always simple workarounds due to the sheer surface area of HTTP+HTML.
Postgres for great JSON support, keeping some stuff out of rigid schemas is critical for developing MVPs.
Earlier quoted context omitted.
It’s funny that only in our industry “time tested”/“battle tested” is called old school and frowned upon. No wonder we see software bloat everywhere.
Eh, I think experimental physicists and medical imaging also lean towards newer tech.
Because this is actually capable of handling a decent workload for really cheap compared to cloud.
There's a few tricky bits to do with logs and reporting, but the benefits outweigh the pain.
Vue on the frontend.
Last time I used BootstrapVue and it worked well. I'd want to re-evaluate that decision next time, have a look at some of the newcomers. I'm aware Bootstrap is now considered to be passe.
I really like the Vue philosophy and it pairs with Go nicely. Last time I ended up using ESBuild to actually build the Vue bundles from inside the Go server, which was interesting but I'm not sure I'd do that again.
Earlier quoted context omitted.
Have you found any good managed places to deploy modern .NET apps other than Azure? My experience is you can either use Azure, in which it's fairly abstracted for you but overpriced, or you can use something like DO where it's more reasonably priced but you have to handle everything yourself.
I think we need to be super precise when we use the word "managed". Today, we use EC2/Azure VMs to run a lot of .NET 6+ apps. I consider these to be managed resources. My involvement with those servers is an email from the hypervisor ~once a year politely requesting a reboot. I don't think .NET has any specific implications regarding where the product is hosted. If you are referring to the Microsoft insight/Azure int…
.NET 7 & SQLite. Because I wouldn't need anything else. Also, it could potentially be my final stack depending on the size of my business & market. The current Kestrel web server implementation is extraordinarily fast (i.e. millions of requests per second fast). Vertical scaling isn't exactly a problem now that we have 2S servers with 256 cores (and beyond).
Have you found any good managed places to deploy modern .NET apps other than Azure? My experience is you can either use Azure, in which it's fairly abstracted for you but overpriced, or you can use something like DO where it's more reasonably priced but you have to handle everything yourself.
Personally big on Rails (use it at work every day). But, my last MVP I did with TS/Next/Mantine/Supabase/Vercel. Reasons: - I've been using Rails as an API only, so having to grok views felt like a waste. My React skills made me feel that learning how to make complex views in my backend was a waste of time. - One type of bug I hate is ensuring my API calls have the right schema. With Supabase and TS in the frontend,…
Same, Next.js, Vercel, Prisma, Supabase. I push to my GitHub repo and the site is live and deployed in less than a minute. With the stack you can use the same language, DTOs, libraries, etc.. both server and client side. Server side rendering ensures a graceful handoff between server rendered state and the resulting app state on the client. I’m also using MUI which includes all the components you need for a front end…
- Validations
- Translations
- Error and request logging and auditing
- Security (CQRS, CORS, CSRF)
- Permissions and a way to integrate it with your authentication (does supabase handle this? don't know)
- Email sending
- Background jobs
- Caching
- File uploading
- Rate limiting
- ...
Every time somebody suggests "just" Next.js, just "Remix", just "flask" or just [insert minimalist framework] I think they're either building something pretty trivial, or wasting a lot of time on rebuilding or integrating things you get for free with batteries included frameworks.
I built Call Stacking ( https://callstacking.com/ ), a modern Ruby on Rails debugger, with Jumpstart Pro and 1.5 hours a night over the course of 4 months. We have four kids, host an exchange student, a new puppy. Our schedules are full . Nothing compares to the productivity of Ruby on Rails. Especially when coupled with a high-end template like Jumpstart Pro ( https://jumpstartrails.com/ ).
I used something similar ( https://bullettrain.co/ ) in the past. Have you taken a look at that? Bullet train used to charge but now are apparently open source.
I know of Andrew Culver through Twitter and he seems like a genuinely nice person.
Earlier quoted context omitted.
Eh, I think experimental physicists and medical imaging also lean towards newer tech.
Eh.. you'd be surprised. Medical Imaging isn't as radical as you may think it is (I spent 7 years doing projects for the exploitation of medical images).