4 ms·

I think you're underestimating how big the PHP ecosystem is compared to Go. Auth, Routing, and Sql code generation are basic things that every ecosystem offers.

I think you're underestimating how big the PHP ecosystem is compared to Go. Auth, Routing, and Sql code generation are basic things that every ecosystem offers. Even obscure languages have these things. Furthermore, Golang is a famous pain in the ass to parse other people's Json, but is fine for known data structures. It's a great example of where the simplicity of the language falls short as well. As a side note, golang doesn't seem to offer anything even close to what other ecosystems offer for Auth without using a third party service. They have some pretty basic libraries from what I've seen, but I could be wrong. These are not things that you're gonna roll in 10 minutes. When working for clients, and they need to connect to an obscure payment processing service, you could roll your own. But I don't want to be the one to tell them why we can't connect to these services without writing these things ourselves when their competitors can because they chose a language like PHP

zer00eyz 3y ago
>> As a side note, golang doesn't seem to offer anything even close to what other ecosystems offer for Auth without using a third party service. https://awesome-go.com/authentication-and-oauth/ https://awesome-go.com/authentication-and-oauth/ Theres ORY if you want your own in house auth zero... There are piles of other things out there. >>> They have some pretty basic libraries from what I've seen, but I could be wrong Basic, maybe... Minimal closer. I like to think of go as brutalist architecture its so drab and functional that it feels ugly, void, and lacking. Look at go's standard library. It's complete, but there isnt a lot of flash there. Good go packages maintain that stance. They give you enough to finish the job. Your not gonna find a package with a lot of "utility" functions in it, your not gonna find a lot of "left pad" like micro libraries. And when you adopt this sort of thinking you dont really need as many choices. When every thing is boiled down to "this is functional/working" it doesn't leave a lot of room for implementation details or interfaces as distinguishing features.

zer00eyz 3y ago

>> As a side note, golang doesn't seem to offer anything even close to what other ecosystems offer for Auth without using a third party service. https://awesome-go.com/authentication-and-oauth/ https://awesome-go.com/authentication-and-oauth/ Theres ORY if you want your own in house auth zero... There are piles of other things out there. >>> They have some pretty basic libraries from what I've seen, but I could be wrong Basic, maybe... Minimal closer. I like to think of go as brutalist architecture its so drab and functional that it feels ugly, void, and lacking. Look at go's standard library. It's complete, but there isnt a lot of flash there. Good go packages maintain that stance. They give you enough to finish the job. Your not gonna find a package with a lot of "utility" functions in it, your not gonna find a lot of "left pad" like micro libraries. And when you adopt this sort of thinking you dont really need as many choices. When every thing is boiled down to "this is functional/working" it doesn't leave a lot of room for implementation details or interfaces as distinguishing features.