Java VS Go

Vicent — Wed, 12 Jun 2019 12:43:51 +0000

At my current job we are going to make a big project that will have a lot of requests from all the country. We don't know if Go is better than Java with Spring for this case. Don't think about knowledge of programmers or experience with that techologies, just think on performance and development speed.

Are you ashamed about your past on twitter?

Vicent — Mon, 03 Jun 2019 18:26:09 +0000

Hi developers!
Are you ashamed about your past on twitter? Would you like to have the silver bullet to all your bad reputation online? Don't worry anymore! Now you can delete all your tweets and favorites just with one program! And it's open source!!! Here you are the link:

https://github.com/llinaresvicent/twitter_deleter

PS: What do you think about the code? Any idea for improving it?

Polymorphism for Go slices

Vicent — Mon, 20 May 2019 17:32:31 +0000

Hi devs!

Today I'm going to show you how to implement polymorphism with slices on golang.

Imagine the situation where you want to implement a similar function on different structs. Interfaces are your best friend! For example, the classic function toString()



//our interface
type Element interface {
    toString() string
}

//our first struct
type MyCustomStruct1 struct {
    prop1 string
    prop2 string
}

//our second struct
type MyCustomStruct2 struct {
    awesomeProp string
}

//abstract implementation of our interface for MyCustomStruct1
func (m MyCustomStruct1) toString() string {
    return m.prop1 + m.prop2
}

//abstract implementation of our interface for MyCustomStruct2
func (m MyCustomStruct2) toString() string {
    return m.awesomeProp
}

At this point, nothing new of interfaces functionallity in golang. Well, now, we could think we can code something like that:




func printElementList(elements []Element) {
    for _, e := range elements {
        fmt.Println(e.toString())
    }

}

//code inside main or another function
ms1 := []MyCustomStruct1{
    MyCustomStruct1{prop1: "foo", prop2:"bar"},
    MyCustomStruct1{prop1: "foo1", prop2:"bar1"},
}


printElementList(ms1)

That may work in other languages thinking on common functionality of hierarchy and polymorphism. However, the compiler will throw us that error:

cannot use ms1 (type []MyCustomStruct1) as type []Element in argument to printElementList

Ok, how can we aboard that problem? At the beggining I thought a map[int]Element could solve the problem, but I don't want to have my slice ordered on a map where I'm not going to use integers.

Well, which is my solution? I surrounded the elements of slice with interfaces just like that:



var elements []interface{Element}

for _, m:= range ms1 {
    elements = append(elements, m)
}

And, of course, I changed the declaration of function and the call:



func printElementList(elements []interface{Element}) {
    for _, e := range elements {
        fmt.Println(e.toString())
    }
}

//code inside main or another function
printElementList(elements)

At this point, we can use printElementList function with an slice of MyCustomStruct2 or another struct that implements Element interface:



ms2 := []MyCustomStruct2{
     MyCustomStruct2{"foo"},
     MyCustomStruct2{"bar"},
}

var elements2 []interface{Element}

for _, m:= range ms2 {
    elements2 = append(elements2, m)
}

printElementList(elements2)

What do you think of that? Is an over complicated implementation?

Here you have the link to full code on play.golang:

https://play.golang.org/p/B88iV16nm4u

From Linux to Mac OS X

Vicent — Mon, 12 Mar 2018 19:43:01 +0000

Hi all!

Recently I started on a new Web DEV job and now, I must code with Mac. I use GNU/Linux on my personal projects so I would like to read some advices from people that "suffered" that change. Software, extensions ... are allowed too :D

PD: sorry for my english level, I'm trying to improve ; )

Forem: Vicent

Java VS Go

Are you ashamed about your past on twitter?

Polymorphism for Go slices

From Linux to Mac OS X