Concurrency and speed aside, Go is just simple to pick up and easy to build working applications with minimum dependencies. This makes it a perfect Swiss Army Knife for many situations, even if it’s not an individual or a team’s core technical competence.
As a friend of mine said once, “Go is 21st Century pseudo-code that actually works”.
Cheers for the awesome blog! It's rare to see one these days, which is dedicated to a niche topic like automotive UX design and is not trying to sell you consulting services (like mine, lol).
Plausible is a gulp of fresh air in the sea of products and services that try to sell one's identity in exchange for a free service. I have started using it for one of my sites, then recently migrated another, and planning to do the same with the rest of my projects.
Moreover, Plausible being an open-source product, it gives anyone a chance to contribute to it and make it even better. As soon as I realised that it was written in Elixir/Phoenix, I just couldn't wait but find ways to help. Although my contributions to the project have been small until now, the guys were really kind and addressed the changes I pointed out almost immediately.
As someone who has discovered Elixir after years of working with various tech stacks, I can say that there is enough goodness in it for everyone. Having more technically diverse people in the community will help us better understand and work with the best behind it - Erlang.
This is more of a general inquiry at this point. I love both Go and graphics programming. At some point I thought, I might actually write a short book combining both topics. As we all know, Go is much more than just a language for writing Web services, yet most materials teach only this side of it. I thought that by using Go to teach a different context (e.g. computer graphics), I might give it a different spin and bring in some fresh minds into the community.
What do you think? Will this be something useful for the general Go community? Feel free to share feedback as well as resources (e.g. libraries, tutorials, etc) which you want to see featured there.
I personally found "Go in Practice" really good. What makes this book different is that it is very hands on. Rather than teaching the Go syntax, it goes directly into some practical aspects of everyday software, and explains them from the perspective of the language.
You can check it out on Amazon (https://amzn.to/2YLsBiN) and support my humble contribution to the blogging world. Thanks!
"[none of the arguments], has to do with the tools themselves, as much as it does with our way of using them. We have come to a point in our development, in which 24/7 availability is perceived as normal and expected behavior. Yet, to blame it on the tools we use, is like blaming it on the hammer for accidentally hitting your finger while trying to hang a picture. Indeed, the tools we use, have certainly made it easier for us to reach this point, but ultimately, it is us who pulled the trigger, not the tools."
So, the Swift compiler is slow? I mean, I expected it to be slower than Objective-C due to its dynamic nature, but that slow?
Disclosure: I write Android apps, so I'm only occasionally peeking at how the iOS dev scene is developing. I've already been thinking of trying to write Android apps in Scala, but maybe this Swift to Java compiler is also worth looking at
Yes, I know, I'm in this business myself. This was just my quick 2cents comment. Wasn't really intended personally, or to be offensive against the product.
As a friend of mine said once, “Go is 21st Century pseudo-code that actually works”.