So I Tried Using Go Again...

[@jalalle1995]

boring languages let you focus on the right problems rather than being lost in the jungle of obscure features and tool chain fights

[@SteveKuznetsov]

Solve cool, complex and interesting problems, don't solve boring problems where you need to use complex languages to get your kicks!

[@nikkehtine]

Golden piece of advice

[@BasharAlkhalili]

Finally! Somebody gets it!

[@avithedev]

Well said

[@younes_khx]

the best thing i read today , i hate how everyone says golang is borring , bro just dont make a todo app then

[@paca3107]

​@@younes_khx excatly! imo frameworks such as next.js are much more boring because for most of the time you use ready solutions, instead of buliding your own.

[@khan8719]

What people don't get is languages like golang, zig and c is about the simplicity of code that means you can open any external library and easily understand the code, since language is extremely simple and straightforward on the contrary open any rust, c++ JavaScript or java library and its extremely difficult to see what is going So those programmers who want to understand what is going on inside the library can easily do so.

[@everythinggoes850]

It's still boring

[@paologaleotti8478]

@@everythinggoes850 Yes, and it's a good thing haha. You get work done, it's productive and it's a very "industrial" language. it just works without going crazy with 1000 npm modules and things that changes costantly. its boring

[@guillemgarcia3630]

I can understand how a dependency works in golang by just "goto definition" many times. It is impossible in typescript. For me that's a selling point.

[@pookiepats]

Golang is not great, my ass. Empty interfaces suck. //methods REALLY SUCK and this is a Go specific thing ! Wtf is this: Func (r Receiver) thisSucks() { //trash-code } Itoa & Atoi are trash substitutes for enumeration As is: Const = { Hell No No Thanks } Why suffer in a terrible “simple” language that doesn’t afford you legitimate type safety OR ergonomics There are so many misconceptions about Go and most are gracious, it’s not a very good language but has a good build system that is honestly its only real selling point

[@user-eg6nq7qt8c]

@@everythinggoes850 The lang is boring, writing the code and building things is still a lot of fun.

[@eugbyte1822]

Go's simple code is a selling point, but the bad thing is that it results in more boiler plate code, e.g. filtering a list of numbers in Go vs JS / C#.

[@nikkehtine]

I don't think that's really a negative because things like filtering a list are very simple, straightforward and fast to make, so in practice there is no difference

[@paca3107]

I dont think so

[@user-eg6nq7qt8c]

we have iterators now so that should be solved if you want map, filter, reduce type stuff, right?

[@channyeintun6411]

It's 2024. You can't say about boiler plate code in Go anymore. If so, may be skill issue.

[@catofdeepblack]

This is the difference between a real engineering and the content creation

[@gunarcom]

the way go's fmt does vertical alignment of structs is so nice.

[@nasko235679]

You bring up a great point about GO project structure. There are so many ways to structure a project, but what I've found is simply doing whatever feels intuitive to you is the way to go. I structure my GO projects a lot like a laravel project, because that's what I'm used to ,but you can even structure it similarly to a nextJS project in a lot of ways and it still works. Funnily the recommended go way of internal and package feels the least intuitive to me.

[@ncpurge789]

THIS!

[@CJS-r2l]

"An idiot admires complexity, a genius admires simplicity" - Terry Davis

[@RyoukenDofus]

The thing with ts and drizzle is that If I change something on the drizzle schema automatically vscode tells me if I mess up something even in the frontend, and thats someting very difficult to echieve in other techs. Literally the schema becomes the heart of your app

[@bmdavis419]

Yea I did not get into any of it here but there are tons of things like this that make me prefer TS

[@hamm8934]

You get the exact same thing with Go, SQLc, and Templ. The only difference is in this stack, your source of truth are literal .sql files. You change a table or query method in your .sql, and your IDE tells you immediately at every level of the app. When I see comments like this, I really think it's a case of people not adventuring enough. I'm pretty you get the same with livewire and laravel. Even Django and jinja templates with pydantic are pretty close to this today.

[@FloodGold]

I know from experience, crazy will burn you out fast. You are warned.

[@swallace21]

go really needs a full featured liveview implementation on top of templ

[@eligbuefelix7988]

I think go is best suited for microservices and heavy backend computations. Exposing golang directly to the frontend can often be tough.

[@siya.abc123]

The problem is that JavaScript developers love to be hand held with abstractions on abstractions on abstractions. There's nothing we can do about that 😂

[@AScribblingTurtle]

If you just want to screw around, that is fine. Getting sucked into that seemingly endless, black hole of the packages and node_modules can be fun. However, Clients don't pay to cure your "Boredom" they pay for results. In that regard. Having simple straight forward language like Go is awesome.

[@minma02262]

Nah. Dont listen to this guy. Use boring stack so you can focus on the domain problem, and move on to other stuffs. Don't waste your life like this. If you experienced enough, structuring project is not a big deal, you know where the complexity will creep in eventually. Missing libraries and functions are a big deal.

[@kode4food]

"Verbose and boring" is a feature

[@massy-3961]

Best full stack with Golang + Frontend is Connect RPC

[@IamI16]

Want to try this out. Can you share your good and bad experience about this stack?

[@massy-3961]

@@IamI16 Essentially is a typesafe Rest implementation. Learning the Buf CLI isn't the hardest thing, but its definitely isn't simple. Middleware are hard to target on a per route basis, but its an RPC so that's expected. Validation can be done in the protobufs but the API is a little annoying. But its definitely an amazing DX. Changing schemas affect the types of every language, and on RPC calls, its typesafe so you know what must be passed in and what you will receive without having to parse JSON and cast a type or use Zod.

[@VIKTOR-pw8eu]

What's the VSCode theme looks so cool?

[@jitxhere]

Honestly its just the orms that I am not switching to go. I can write basic queries but I really want that magic that Drizzle and Prisma brings. Too dependent on it and their typesafety

[@hazimdikenli]

I think that Deno2 is going to solve most of the JS/TS Tooling issues, just need a year or two.

[@ooijaz6063]

Have you tried ent orm + huma to generate openapi definitions? Ent is kinda like type safe query builder and huma can generate automatically openapi definitions so we can have rpc on the frontend when combined with openapi-ts

[@oumardicko5593]

Honestly i felt like his(theo) hate for go was being seen cuz i couldn't understand why the heck graphql 🙃

[@JagaSantagostino]

Copilot make Go a brand new language for me, reducing the cost of all the parts I hated close to zero

[@Beyram1501]

Golang gets the job done without having any issues whatsoever, and that's very boring hahahaha. That's why I only use it for fun stuff so that the fun part comes from the project idea instead of the code.

[@AlexandrGakhov]

What do u think about ts Effect lib?

[@DuckyChannel]

You should give Rust a go, if the project it right for it. Would love to hear your takes on Rust

[@duongphuhiep]

nutx, next.. is "backend for frontend".. while go is more suitable of a backend for backend, micro-services

[@dandogamer]

I mean you can do the crazy stuff you talked about in go, you would just have to do most of it yourself

[@mariuscostache2681]

Go is the perfect language for me. I’m done fighting code complexity and I am no fan of the magic some modern frameworks are doing behind the scenes. Also, like someone commented before, maybe go is not the best tool for web development.

[@Alex.Shalda]

Are there any performance gains on using go + react for a website, or just stick with typescript + go + nextjs? I mean, why should someone use go for a website?

[@jed271]

there is a performance gain and server cost reduction

[@Malix_Labs]

Golang is definitely "it works, it's right, it's fast, but it's boring" I think it kind of show that its design is almost perfect (error handling syntax aside), but if you're into fun stacks, Golang doesn't really fit

[@alefumero]

If u had to redo a project because a dependency bump you should literally look for a new hobby

[@bmdavis419]

Nah it’s not a redo it’s just copy pasting the code, it’s a very common thing in react native lol

[@hectorcast943]

Basically why am burnt out on golang, file structuring a project just makes me eh

[@tranquangthang8897]

go go

[@hamm8934]

SQLc is the best way to do SQL in go

[@Nuraddinhassan]

boring is good, that mean is simple

[@devyb-cc]

ben, try kotlin

[@7heMech]

0:43 seems like a TS issue to me.

[@gmonie619]

complex is cool?

[@everythinggoes850]

Go's limited type system is boring

[@codeline9387]

rewrite project coz of package version bump, lmao

[@bmdavis419]

NOT REWRITE, should have been more clear I just make a new project with the new deps then copy paste everything over and it works. Yes react native is that stupid

[@codeline9387]

@@bmdavis419 next time try to remove node modules and local cache/tmp/build folders

[@_SaulDesigns]

@@bmdavis419probably deleting node_modules and package-lock.json followed by npm install likely would fix your issue

[@codeline9387]

@@bmdavis419 next time try to remove node_modules and local tmp, cache or build folders

[@codeline9387]

@@bmdavis419 lol, why I can't reply

[@patriciohernandezballester2485]

Si alguien tuviera la amabilidad de resumir un poco que dice ... pq no logro entiender casi nada, habla muy rápido y no vocaliza

[@tranquangthang8897]

I think what he is trying to say is that go is simple/reliable/verbose which make it a little bit boring compare to nextjs and phoenix which have some exciting features. (I might get the wrong idea though)

[@HoussamElbadissi]

You can by the way turn on captions, they're pretty accurate, and you can even auto-translate them into your language.

[@patriciohernandezballester2485]

@@tranquangthang8897 Thanks

[@npc-drew]

Go language promises simplicity but delivers constraints: - String-typed APIs force unnecessary type conversions. - CSV parsing performs slower than Python's Pandas library. - Language ecosystem lacks mature libraries. - Developer freedom feels restricted. - Speed advantages diminish with real-world implementations. - Developer productivity suffers from missing tooling.

[@AlexanderSuraphel]

What is you go to for API/web implementation?

[@npc-drew]

@ None, I use Ho for backend only, and the language provides the needed parts to build server.

[@nikkehtine]

as a developer I never felt my freedom being restricted in Go so I don't know where that one came from

[@npc-drew]

@@nikkehtine that one wasn’t an individual point but frustrations from some of the others, why can’t I just define the incoming data as whatever type I want instead of receiving one type and converting it adding enough overhead that this part of the program is slower than even Python, and how come reading CSV is 10-20s slower than in Python too.

[@paca3107]

skill issue

[@tawandagamedevs]

this video just wasted my time

[@MarkVergelBanguis]

Go isn't for web development.

[@saadhabashneh5587]

For what then?