Skip to main content

How Strict is Golang? #GolangDev

Author Bill Tanthowi Jauhari
pixabay.com


Hello everyone, in this occasion I would like to share about the strictness of golang. what kind of strict? let see below.

Golang is the functional programming that really have concern about performance, giving limitation to prevent overuse memory is the big deal. for example, golang has a variative type of data such as int, string, boolean, float, array etc. I wonder that you are thinking about "what kind of strictness that is? its totally similar other language", YES. but golang have specification in numeric type of data such as int have int8, int16, int32, int64. golang also have uint8, uint8, uint32 and uint64 which is its really strict you know. the following number after type of data is stand for the length. Obviously you could use the largest type of data for all the variables, but you know it could overwhelming if you put int64 in "is_valid" variable right? joking :D. golang really care about performance, because each length of variable is matters for memory.

yes! golang its totally directing you to put type of data according to the length. the more you strict about the type of data, the more your apps got faster. 

but in the other side, golang also have flexible type of data, like Any in Swift. you could put a lot of values in variable, its called null interface data type. I know its weird, I totally agree with you, but you know thank god for this type, because we need flexibility also in some cases. such as dealing with JSON or Dictionary values, you can't use other data type instead of interface, maybe you can use array or slice but you need put the seem data type for each key n values. for example .

in above example, you put all the data type as string, it's totally works but "age" key is belongs to numeric data type right? and you unable to do that if you are only using array or slice, that's why we need interface this time. for example


in above example, you could see the example of using null interface data type, we finally enable to put the right data type for "age" key.  see the output below.


you could use interface for any kind of cases but it's totally not recommended, because you could ruin the performance. I recommend you only using interface if dealing with Dictionary or JSON cases.

Conclusion

Golang is totally strict language, but it's not a drawback cause the main purposes is to keep the best performance for your apps and not overusing memory. but golang also have flexible data type called null interface, but you are not recommending to put it in all variable you define, it's only use for Dictionary or JSON values.
Malang, Malang City, East Java, Indonesia

Popular posts from this blog

OpenVPN Alternatif Solusi Menanggulangi Blokir dari KOMINFO

Author Bill Tanthowi Jauhari
Sejak akhir juli 2022 kemaren indonesia di gegerkan dengan tindakan kominfo atas diblokirnya banyak platform digital karna tidak mendaftar PSE, terutama paypal dan plaform game (steam, epic game dll). keputusan ini semakin membuat netizen geram dikarenakan platform judi online malah disetujui untuk beroperasi karna sudah daftar PSE. Jujur menurut saya memang keputusan ini sejak awal saya dengar sudah mengada-ada karna sangat aneh memblokir semua platform digital yang jumlahnya tidak terhitung banyaknya dan hanya membolehkan akses platform yang sudah mendaftar yang jumlahnya hanya ratusan.  saya sebagai developer juga merasa aneh banget ini kebijakan apalagi platform development juga banyak yang di blacklist oleh kominfo seperti, github, gitlab, bitbucket, even website CDN pun di blacklist. astaga wkwkwk. anyway terlepas dari kebijakan konyol ini, saya mau berbagi tips cara agar tetep bisa mengakses semua platform tersebut tanpa ada halangan, yaitu dengan menggunakan VPN. banyak ban...
Read More »

Variadic Function vs Slice Param Function in Golang #GolangDev

Author Bill Tanthowi Jauhari
pixabay.com Hello everyone, good to see you again. I am gonna share about a simple thing in fundamental Golang, this article inspired by a QnA in a website and I think I will tell the answer more flexible and wider in my personal tutorial, so this is about differentiation between Variadic Function and Slice Param in Function. # Variadic Function Variadic function is an unique code, this code is enable us to passing a infinite params in one function, we know that we need to put parameters in function we need to put the space in there, for example : function(param1 int, param2 string), golang absolutely doing that thing too, seems like the other languages, but Variadic function is a something new, you could put many value in function and sapparated by comma, you maybe thing about passing array in parameters but this is something different, you dont need to put parenteses when you call the function, it just like you put regular parameters but have an infinite numbers.  fo...
Read More »

Playing with Hooks in Gorm #GolangDev

Author Bill Tanthowi Jauhari
Pixabay Hello everyone, I would like to share some tricks in gorm, the Idea of this tricks is to execute a command or code statement in the middle of an ORM operation, if you ever know about trigger in the query language, then hooks is just kinda like that. Hooks could execute statement in some events such as: beforeCreate, beforeUpdate, afterCreate,  and afterUpdate . those event is similar as a trigger,  when the trigger is executed in DBMS layer, hooks are executed in the application layer. In my real case, my current company has different convention of naming database column, so when I try to implement ORM, a lot of columns such as created_at, updated_at and deleted_at can't be generated automatically. also if you have a custom UUID you could pass the value UUID generator into hooks before the insert is executed. for more detail let's jump into code : # Explanation Above code containing model struct, and several methods from gorm to serve model, TableName method used to d...
Read More »