Live data from Hacker News

The best Go framework: no framework?

threedots.tech

181–185 of 185 posts

Re: The best Go framework: no framework?

#181
post #178

Earlier quoted context omitted.

That’s because your premise is weak. You argue that Django is the wrong choice for lots of projects but the counter factual is that our job is to figure that out. We have to choose the lesser evil. It’s not convincing to just call everyone stupid. Everything is a trade off. You have no idea what those could be in any particular situation so that’s why your whole argument falls apart Then you focus on construction and…

You miss a crucial nuance that I did make: > there will be a lot of projects where Django is a very poor choice. often and lot is crucial - it's opposed to all . Because it implies exactly what you then continue to state: that its our job to figure out if this project is one of those "lot [..] with a poor fit" or one of the ones where it actually, and will remain, a good fit.

Yeah, look, you waffled this one but I still liked it. I can tell that you know what you’re doing and that you have something to say. I may not agree with it but I didn’t dismiss it.

But when I say premise is weak, it’s a technical term. Doesn’t mean it’s wrong.

I mean, in this case I do think that, but that’s why you’re getting so much pushback. Even if the premise was right, you’d still be getting pushback.

On the next post, remember to spend extra time there. It always comes back to haunt you.

Remember that the reader is smart but in a rush. The less words the better. Keep it country simple.

Re: The best Go framework: no framework?

#182

Earlier quoted context omitted.

Your comment made me realize I'm not truly anti-framework, I'm anti-sell-your-architecture-to-the-framework, which most frameworks want you to do. Problem is, many MANY people do not have sufficient experience to know the perils of putting the framework in charge of the architecture, so they do just that, and decry any other approach as "Java-esque." (That label says an awful lot in and of itself.) The impact of this…

I think you still are anti-framework by any reasonable definition of the word. Library = your code calls it, Framework = it calls your code.

Limiting the scope of what is exposed to the framework keeps you in control of the architecture.

This is probably why I find almost every framework deeply unsatisfying. Gin, in Golang, doesn't bother me much for whatever reason, but it doesn't seem to aspire to the same number of things as other frameworks.

Re: The best Go framework: no framework?

#183

Earlier quoted context omitted.

I’m really surprised there isn’t a solid batteries loaded framework in JS. There’s just no way I could use node + express over Rails / Django

Could you elaborate on some of the things you find express lacking? Asking because the team is evaluating using it.

I didn't like that you had to shop around for an ORM and database migration lib. It felt really like a patchwork kind of setup.

I think Express specifically was fine and great.

Re: The best Go framework: no framework?

#184
post #41

Earlier quoted context omitted.

You're saying that grpc and protobuf are over engineered but you're happy with Spring? gRPC and protobuf are just transport and serialization, they have nothing to do with business logic, on the other hand Spring is a heavy, bloated framework. Most Java frameworks are complicated backed by layers of abstraction and black magic. btw no framework does not mean you don't use any library, there are some good lib aka micr…

Spring Boot is actually a VERY easy to use framework. So much so that Netflix shifted out of writing their own libraries to using Spring boot. For example, the code below is a complete Spring Boot application with all of the default configuration in place. It will take just a couple of minutes to have this running and it provides quite a lot of features under the hood - which you don't need to worry about. @SpringBoo…

Writing a single get endpoint that returns string is easy in almost any language/framework today, you didn't really show anything with it. The real pain starts when you have to add database connection, migrations, auth, security and all that.

Re: The best Go framework: no framework?

#185
post #69

Earlier quoted context omitted.

By far my least favourite thing about the Java web ecosystem is how weirdly obscured the bootstrapping process for starting processes is. So much of how your application starts is determined by XML files and DI frameworks that I often have no idea (or am sometimes not even exposed to) where the `main` function is.

Caring about the main function in a framework-ey app generally makes as much sense as caring about the x86 initial boot code when launching mspaint.exe

I've seen devs write caches that were shared between customers because they didn't understand the lifecycle of Spring Autowired dependencies.

Understanding how the framework wires things together is important.

Post reply on HN