Recently, a company switched from Scala to Go and were able to considerably increase CPU efficiency and memory efficiency this way.
But that's not the true success story. (Although we Gophers love to hear "from x to Go" success stories, don't we?)
The results of initial comparisons were quite bad: Go was slower! But the team was not willing to take this result as a fact.
They dug deeper.
And found the real bottlenecks.
This is the true success story behind the "success story". If you do not give up early, if you persist, if you work your way around the obstacles, there is a chance that you reach your initial goal and reap the benefits of your hard work.
Also in the latest Applied Go Weekly Newsletter issue:
Why Service Weaver (the application framework for Go that was announced in early March) is not CORBA or DCOM. These ancient concepts tried to make remote function calls appear just like local function calls. On the surface, Service Weaver might do the same, but looking closer, it's rather the other way round.
Go tip: Never do this when calling a goroutine! (Ooh, is this too clickbait-y?)
After-work fun: Play Roboden, a game written with Ebitengine
And more articles, videos, and projects from the last week.
I’m #OpenToWork again! I’m a #backend engineer with 10+ years of experience in differently-sized organizations and a specialization in #Elixir.
I’m comfortable working closely with the business doing product work, as well as focusing on the tech infrastructure, system design, and algorithm side of things. I’ve also spent some time as a tech lead. Apart from Elixir, I have done work in .NET, C++, Dart, Ruby, and even #Fusion360. I’d be excited to get some professional experience with #Rust or #golang.
Buzzword-wise I’ve had production experience with #SQL and NoSQL dbs, event-sourced systems, devops work using AWS, Terraform, Ansible, Docker, #GraphQL/absinthe, #Kafka, and more
I’m at nietaki@gmail.com if you wanna get in touch 😉
I'm really excited about the @gotosocial project. The world needs more compiled software that harnesses the true power of CPUs.
I had a look at the #gotosocial roadmap, and it seems very well planned out. I'm not familiar with #golang, but I hope I can help out some time after my thesis! #activitypub#fediverse#selfhosting#selfhosted
I was seriously considering submitting a talk for #gopherconeu this year, titled “Who is afraid of (web) frameworks?” Now, I’m running around thinking that this will probably bring me more hat than generate a constructive discourse.
What should I do? Are we beyond the point of discussing those topics in the #golang community?
Anyone who knows #react or some other front end type stuff want to help me with a small project? Looking to created a frontend for #gotosocial (#golang powered #mastodon like service). Just something super basic.
To understand them better, I will not stop with just reading and documenting, but might write a app (server, client, bot) to solidify my understanding.
There are different approaches to developing apps for #fediverse
• a typical mastodon app implements both front-end and back-end
• #gotosocial type of apps implement only backend api (along with cli all in #Golang )
• apps like @sengi_app are only at the front-end
• @brianmmdev is implementing a fediverse app via #serverless model
As mastodon picks up steam, we will see different types of apps
Long-term systems guy, working at a large manufacturer of chat apps since the term "SRE" was new.
Usually making something and pretending to be less geeky than I actually am. Usually still reads as "extraordinally geeky." Ask me about my off-road Jeep and its Prometheus instance.
Mostly #golang these days. The past is full of Ruby, C, and Perl. The future probably has Rust.
Other than that--family, photography, bikes, and 3 siberian cats.
I’m Welsh-Californian, living in #dublin#Ireland. My day job at wordtothewise.com involves #email, #privacy, #software development in #golang, and making the internet a better place.