> I have no hesitation in recommending Go to displace any programming task which would previously have been targeted towards Java.
Java is faster and has more libraries.
Another go at the Next Big Language
121–125 of 125 posts
Re: Another go at the Next Big Language
#122Earlier quoted context omitted.
My largest Golang deployment is a blender service. That's where I used the Goroutines and protocol buffers I mentioned earlier. Its speed is acceptable. My take on it is that this is a new language. Of course it doesn't have fully mature, fully optimized internals. And certainly part of the problem is that I haven't developed a full mastery of the language (Mastery is not a word i use lightly) so that will improve, t…
I recommend trying gccgo, the Go compiler for the GCC suite. (GCC 4.7.1 and later have Go built in.) In my experience it is (at -O2) much faster than Go's own compiler. GCC, after all, has because a bunch of advanced optimizers with a long history of development behind them, and Go's own compiler does not. My recolleciton is that Go's own compiler was intended as a "suboptimal but correct" reference compiler, but thi…
Appreciate the tip -- sincerely.
Re: Another go at the Next Big Language
#123It's a pity that we are still talking about things like syntax in the context of a next big language. Programs are still full of bugs, especially concurrent programs, lots of time and effort is still spent on testing. At this day and age, the NBL should be a language that helps or guides a programmer write correct concurrent programs with good performance. It should prevent programmers from making mistakes as much as…
Syntax is very important for a programming language. It's in your face all the time. A serious downside to many programming languages is their awful or inconsistent syntax, and that results in code that is hard to read and comprehend even before trying to understand what the code is doing.
It sure is important but who is to say C-style syntax is better than Lisp-style syntax and vice versa. Obviously the NBL should have a sensible and consistent syntax but it has to have a lot more than that to be the NBL. C-style syntax is definitely NOT a must have.
Re: Another go at the Next Big Language
#124Earlier quoted context omitted.
This is the first time I've heard "Java-like verbosity" as a criticism of Go, and I'm baffled by it. Go is generally much more succinct than C++, Java and other similar statically typed languages. Can you expand on your comment?
everything is package prefixed, names are long. Totally minor, but reminded me of my days with java
I guess you could call that "verbosity", but it's very different from what people normally think of when you refer to "Java" and "verbose".
Re: Another go at the Next Big Language
#125This comment is for all those people who have written against Lisp in this thread.
Lisp was designed to represent/design/play with/experiment with advanced and complex algorithms. Now, when was the last time you wrote a code that was algorithmic or was about some new cool algorithm, try to remember, let me tell you the answer: most probably never ever in your life (and there is no hope in future as well). What you people do is stitch APIs, or more precisely, iOS API, Android API, Some web framework API, DOM API, API API API... look at your code and see it is just a bunch of APIs call thrown in a mix. This is absolutely fine because what you guys build is "Application" (not "Technology") which grab some data from here and there, store it in some shiny DB and when user want it show him in a shiny new UI, that all you do and for this purpose go ahead and use whatever language those APIs are in, no problem at all, but please don't rant about something that you don't understand.