66 karma · joined January 9, 2022
Contact me on ycombi@mbvlabs.com or twitter @mbvisti
A web framework for Golang that has support for inertia as well as an opinionated set of tools which an agent friendly CLI.
Just released v1.0.0 last week and getting a few QOL features in now!
It connects to your cloud accounts, provisions hardened servers, and handles deployments, logs, and monitoring.
Currently open for alpha (free) access
It follows a lot of the conventions of Rails which is probably why it has turned out quite well
Location: Barcelona, Spain Remote:Yes Willing to relocate: No Technologies: Golang, Postgres, Docker, Terraform, Pulumi, Ruby On Rails, Typescript, AWS Résumé/CV: https://linkedin.com/in/mortenvistisen Email: hackernews@mbvlabs.com
They work well for some problem sets. But, 3 months are not a long time. This post is a reflection of me using these things heavily over 1+ year and problems keeps creeping up.
And good, you shouldn't give a shit about what I believe. I'm just a random guy on the internet. But, I'm not the only one to start noticing these problems.
The goal is to approach the developer experience you get from Rails, but in Go, while keep as many of the idioms from Go.
Yeah I tried out Buffalo as well but felt like they ended up doing too much!
If you check it out, I'd love to hear what you think! It's not ready for a v1 yet, still very exploratory.
https://github.com/mbvlabs/andurel
Probably only building for myself here but super fun to explore how that would look like.
It's meant to be a 'rails-like' experience in Go without too much magic and conventions.
Basically, speeding up development of fullstack apps in Go using templ, datastar, sqlc with an MVC architecture and some basic generators to quickly setup models, views and controllers.
Building web applications & APIs for scale with 10 years of experience.
I predominately specialize in creating scalable systems for start-ups and scale-ups. I can help with systems design, creating an mvp, upskill your team assist you in going from 0 to 1.
Recent experiences as largely between in the AI/ML space: - integrate full-text search across all popular CMS - backend for large outreach platform - systems architecture and data pipeline for AI vision product in the pharmacy space - move client's infrastructure to AWS
Primary technologies: Go, JavaScript, TypeScript, PostgreSQL, Docker, HTML/CSS/Tailwind, AWS, Linux, terraform, DigitalOcean
Site: https://mortenvistisen.com or https://mbvlabs.com LinkedIn: https://www.linkedin.com/in/mortenvistisen Email: hi@mbvlabs.com Github: https://github.com/mbvisti or https://github.com/mbvlabs
When you have lots of options you always have lots of opinions, just human nature. When working with low-level problems I get how having lots of options is good since you need to be precise. But, most people work on web-related problems. These have most likely been solved in one way or another before. I don't want to discuss in PRs if you should use x/y/z language feature, I don't think that's relevant for a lot of technical solutions.
You like Rust and hate Go, that is very clear. But maybe before you call me arrogant and put words in my mouth, read back my comments. I haven't trashed other languages or told people that what they like is shit. Simply that I like Go, and that I don't agree with your arguments.
I once did a short gig with a start-up that used Kotlin and the CTO was very enthusiastic about Kotlin. He showed all the things you could do in the languages like adding behavior to an integer that would be applied throughout the program. He was excited and I was a little horrified haha. But huge companies have been built using Kotlin so who am I to judge?
I'm in the same boat as you, I want to solve problems and build products.
The repetition in Go, in my experience, mostly happens at the beginning and then you only have to deal with ‘if err != equal nil’, which to be fair is probably a good thing. Is it really more verbose and repetitive than error handling in rust?
I would love to have the type system rust has in go. It really allows you to be expressive and put in guard rails in a way you can’t using go. But I don’t think most applications need that.
My experience tells me something different than yours, maybe I’m wrong. But I can’t reconcile your arguments with my experience writing rust web applications. Even if I still miss writing my queries using sqlx and my views with asakama.
I've found that combination to give me amazing DX and appropriate speed of development.
I use Go professionally and would most likely choose that if I had to do any new “serious” web dev project. But the Rust eco system has come a long way. Plus, the borrow checker aren’t really that tedious once you get use to it. At that point you get a lot of benefits!