I'd love to see Nim on this diagram: https://talks.golang.org/2016/applicative.slide#13 - it could be close to the top right corner.
Nim is interesting, but in my opinion, it wants to kill to much bird in one shoot.
Program your next server in Go
381–384 of 384 posts
Re: Program your next server in Go
#382There are some questionable statements: > Go differs from Java in several ways > Programs compile to machine code. There's no VM. This tries to imply that having a VM is a bad thing. > Simple, concise syntax The syntax is simple, but not overly concise. For example the lack of generics leads to a lot of repetition. > Statically linked binaries You can have them with Java, too. > Built-in strings (UTF-8) Should this s…
> This tries to imply that having a VM is a bad thing.
What net value add a VM (appart something more to handle) ?
> Should this suggest that Java doesn't have trings?
as long as you stick with basic multilingual plane you can consider that java strings are ok
> It is questionable whether this is good or not. There are a lot of good concurrency libs for the JVM.
Concurrency in the JVM is hard to have right
Re: Program your next server in Go
#383I had a PHP program that processed HTTP requests and stored some data onto a local database, and decided I needed to rewrite it for various reasons so I decided to choose Go. Some points I recall: * Static typing is good. * As I expected, the standard library and other packages available had the http & routing stuff I needed, which is all good. * I like that errors are specified in function signatures, unlike excepti…
memory safety imply that if you do something bad you will be stopped (with "invalid memory" issues for example), not that it is illegal to write something bad
Re: Program your next server in Go
#384I had a PHP program that processed HTTP requests and stored some data onto a local database, and decided I needed to rewrite it for various reasons so I decided to choose Go. Some points I recall: * Static typing is good. * As I expected, the standard library and other packages available had the http & routing stuff I needed, which is all good. * I like that errors are specified in function signatures, unlike excepti…
memory safety imply that if you do something bad you will be stopped (with "invalid memory" issues for example), not that it is illegal to write something bad
Well I am also then interested in it being hard or illegal to write something bad :)