Go feels like a beefed up version of C.
Swift feels like a high level language with static typing.
Interestingly, Swift doesn't feel much like Obj-C.
Swift feels like a high level language with static typing.
Interestingly, Swift doesn't feel much like Obj-C.
With Go, I'm never sure what I have (pointer? reference? something other and weird?), and can't cast things that should be castable.
Either way, I'd still rather take Haskell or Common Lisp, but I'd gladly take C over Go after having used Go for a highly multithreaded communications server.
> Interestingly, Swift doesn't feel much like Obj-C.
Not necesarrily a bad thing. However I am the one who does like Obj-C. That said after some time with Swift you do not really want to go back to Ojbective C any more.