DEV Community: Allison Piovani

4 Reasons for your Company to use Go

Allison Piovani — Tue, 01 Oct 2024 21:32:37 +0000

1 - Performance

Extremely efficient and fast, tools that require high efficiency and performance prefer Go for their backend. By compiling into native machine code, it can achieve extraordinary performance without requiring specific configurations within the code for each scenario.
When talking about Go, we must always mention concurrency, which involves tasks being executed simultaneously. Most languages on the market require adaptations to work in this model or something close to it. Go, on the other hand, brings this by default and in a simplified way.

Some features:

Memory management: it already has a garbage collector by default and mechanisms to avoid leaks.
Benchmarking tools.
Easily vertically scalable.
Facilitated use for ARM architecture.

2 - Learning Curve

Go has a simple and concise language that can initially seem strange but is quickly overcome by more experienced developers. Even the way it works is quite similar to other languages, making it easy to navigate between files.
As a first language to learn, its approach is quite simple, even for learning OOP, even though it has its own way of doing things, making learning possible without much suffering.

3 - Market Adoption

Despite being a new language, it already has several libraries and frameworks that can facilitate development.
Some companies that already use Go: Google, Uber, Netflix, Dropbox, IBM, Spotify, Microsoft, and many others. This list just keeps growing.
Clouds:

GCP (Google Cloud Platform): Go was born within Google, so it was very well tested and refined in its projects. We can say that GCP is Go's first home.
AWS (Amazon Web Service): already provides the latest versions in its Lambdas, machines configured to be executed if certain events occur.
Azure: I've never had much contact, but Microsoft has a very cool initiative involving Azure and Go, it's worth checking out later. Considering this, I believe Azure is also more than prepared to handle Go.

4 - Maintenance

Its main concept is to be simple, simplicity favors the maintenance of code over the long term, also reducing the delivery time of implementations.
It has code debugging easily configurable in IDEs if it doesn't come by default, very well established and tested by the market.
It brings native support for automated testing and reports, ensuring that new versions of the application are still behaving as expected.
Its package management is quite simple, having only one main manager model.
Other important maintenance points:

The community is constantly growing and is very collaborative.
It has a very well-written and organized official documentation.
It has been working on technologies like WebSocket, Http/Https, gRPC, HTML 2 for years.

Thanks for reading! Leave a comment or like to let us know what you think.

Why doesn't Go have Ternary?

Allison Piovani — Sun, 09 Oct 2022 15:09:59 +0000

One things I miss most about Go is Ternary, coming from PHP and Node where the ternary is already well established, I understand how it can be controversial since a lot of them use complex logic in them, that would fit more in IF, Else and Switch. It's like a famous quote form the comics: "With great power comes great responsibility".

The discussion about the Go and Ternary isn't new, there are a lot of issues on the topic, I'll leave her sources for you to delve into, I'll summarize the points that I think are most important on both sides, and the give my personal conclusion.

Benefits

1) Drastucally reduces the use lines code.

var n T
if expr {
    n = trueVal
} else {
    n = falseVal
}

var n = expr ? trueVal : falseVal

2) If the problem is the sumbols ?, :. =, an approach that not even in python can be quite interesting.

x := "yes" if true else "no"

3) Languages like C and C++, which are the example base of Go, have ternaries.

4) Variable that nedd a value default if no value is assigned to it, for example: service port.

Disadvantages

1) When there is more than one expression to be validated, the ternary operation is difficult to read and it becomes impossible to determine its consummation.

var b1, b2, b3 bool
...
var s = b1 || b2 ? b2 && b3 ? b1 && b3 : "s1" : "s2" : "s3": "s4"

2) Can replaced by operations like IF, ELSE and Switch.

3) Deviates from Go's goal of clarity and simplicity when it comes to syntax.

Conclusion

The ternary will not come to version 1.20 (at this time we are on 1.19), discussions are whether it will come in version 2 of Go, but the reality that will hardly come, the communicates it despite being divided the majority from what I see defends that should still keep the aspects of simplicity in its syntax, even if it requires more lines of code.

The biggest fear of communicating is the creation of more complex codes, I personally prefer autonomy for developers and their teams to choose the best way to write, one more option would be nice, since there are countless that make more sense to use just one line than to use at least 3.

No everything is lost, if it is really necessary there are packages in Go that create the ternaries in Go or leave it very close to what we have in other languages, example: ternary, logically we must have other scattered around Github.

Sources

VS Code Extension - Git Graph

Allison Piovani — Fri, 09 Sep 2022 03:46:34 +0000

Today I was talking about a tool that helped me a lot, to unravel the Bug, which apparently is not wrong, let's find out the reason more calmly.

At the moment of desperation a graphical tool on the git path was indispensable, so that the two weeks work of 4 developers has been undone, thanks to this tool I was able to browse the changes and map the changed and relevant files that could cause the Bug.

And before you ask, couldn't you do that in the Github UI? Yes, it could be done, but not with such speed, when loading pages you lose a precise time if you don't lose your train of thought.

As another tool in armory didn't really do it, its installation my VS Code is so light that I don't even feel the difference. I hope I don't need it anytime soon, but if I do, I'll definitely waste a lot less time this time.

If you don't believe me, I suggest you try it, you can find it in the VS Code extensions browser or in the links below:

UUID

Allison Piovani — Sun, 17 Jul 2022 02:21:44 +0000

Universally Unique Identifier or GUID Globally Unique Identifier which in practice it's the same thing.

It's composed by 128 Bits represented by 32 digits Hexadecimal, divided by 5 groups separeted by "-" with struct: 8-4-4-4-12.

The goal identify unique information in the System, whithout a central chord.

Exist 5 versions, the first digit from third batch, is separated to identify the version of UUID.

Versions

v1
Uses timestemp to generate the UUID, also can use NodeID which is an identifier, usually for that MAC of the computer, or URL or prefixed data key.

v2
Very similiar to v1, but the use of NodeID is mandatory to present a security group, this group may be related to entities or some context of the application. But veru little used.

v3 and v5
It also use NodeIDas prefix. In v3 is used an MD5 hash key, while in v5 a has key of the SHA-1 algorithm is used, this second being more advised for development.

v4
It is the most used version, in this case all characters are randomly generated.

Benefits

It's also a form of information security, the ID format increment informs how many users there may be on the plaform, important information for competitiros;
Greater security if you don't have Authorization control in the application.

Disadvantages

Makes debugging records more complex;
Increase in the cost of storage, storing in string format, char(32) can make the performance of queries quite heavy, a solution is to store in binaries;
Must have a position rule, since the collision is possible.

Go

Inside Go we have a lot of packages that press UUID, but in this demo we will use the official google package Package, in addition to supporting all of the above versions. The project link is here: Project