Congratulations to the Go team! There are many excellent folks working on the Go language and it's been an absolute joy to work with in my experience.
Go 1.6 is Released
131–140 of 367 posts
Re: Go 1.6 is Released
#132Binaries are up but not everything is fully updated yet. Announcement blog post coming shortly. Edit: Blog post up: https://blog.golang.org/go1.6 maybe change the article link to that?
Ok, we changed from https://golang.org/dl/#go1.6 to that.
Re: Go 1.6 is Released
#133Earlier quoted context omitted.
Why GUI though? Go shines for servers, but I would never want to write a desktop application with it though. Especially if I could do it in C#.
The way I see it: 1) Go produces 100% portable code. I absolutely suffered doing the same for a very basic C++ program that used C++11's std::regex. Compiled fine on clang-3.5 on OS X, fails on clang on Linux. It took me hours of searching online to find and install the exact version of GCC that actually fills in std::regex instead of just keeping it empty. Trust me, there are some versions that do that! No errors du…
Go programs can link the Qt library, specifically the GUI components, statically? ... it produces one output binary per target OS?
Re: Go 1.6 is Released
#134Earlier quoted context omitted.
FWIW there have been methods added to the Math class that perform math operations on unsigned integers, allowing a Java int to be treated as an unsigned int (cf long). In addition there have been other libraries such as JFFR and JNA that make it more sane to inter operate with C libraries in a much less painful way. There's even a future enhancement request to add this info a future release of Java.
Yea, I wouldn't read my above list as a list of roadblocks. The JVM is a serious work horse and every year the list of complaints I have shrinks. Go certainly has its own problems as well, and the performance profiles that pain java are probably not going to fare much better under Go. The major win is probably goroutines.
It's not even goroutines. Its the scheduler. I am continuously impressed by the amount of quasi-generic performance they can get out of something so simple. You can understand the entirety of the golang scheduler in minutes, and it works out of the box for most of my golang use cases.
That said, the JVM scheduling is pluggable, so I have options for a much bigger variety of use cases. With go if the default scheduler doesn't do what I want, I'm stuck.
Re: Go 1.6 is Released
#135Earlier quoted context omitted.
emacs is an IDE wrapped inside half an OS
I would like people that keep saying stupid stuff like this to try and compare the size of GNU Emacs to the size of, say, NetBeans, Eclipse or Visual Studio. There is an enormous amount of stuff that "conventional" IDEs to and emacs does not do. Consider NetBeans: there are a lot of people that use the NetBeans platform to create stuff that have nothing to do with programming, the very same way emacs users create mod…
I'll set your less civil commentary to one side and simply ask this:
In what programming language could Emacs possibly not be feasible option for a seasoned Emacs user?
Re: Go 1.6 is Released
#136Earlier quoted context omitted.
For me, I like Go's slim profile. Native compilation, aggressive allocation, low memory usage, static compilation. JVM suffers from slow startup times and tends to eat a lot of RAM, even when the app doesn't technically need it around. It has an object model that spawns a bazillion tiny objects, and much of the JVM's GC design exists to cancel out those tiny object allocations. JVM has many upsides (the portability a…
What's your use cases where you've found startup time to be a significant issue?
Short-lived processes are an issue, because while startup time can be ok, code won't perform well until it's hot enough to be JITed.
Re: Go 1.6 is Released
#137Re: Go 1.6 is Released
#138Earlier quoted context omitted.
Take a look at a curated list of opinionated ecosystems. Hilariously, they contain some of the most popular use-cases going forward, and the price point is good. Genuine question, why all the negativity?
I'm not being negative. I was confused by the unfamiliar anthropomorphic terminology being applied to an artifact. I take away a sense that "opinionated" seems to be an idiom popular within the golang community for a sense of principled design along the lines of Smalltalk's message passing, Lisp's homoiconicity, Haskell's purity from side effects, and so on.
> I'm not being negative.
I was. My previous message is an arbitrary combination of HN clichés, of which "opinionated" is one. It's gibberish, devoid of content but written in a fashionable way. It got zero down-votes so far. Maybe something to think about.
Re: Go 1.6 is Released
#139Re: Go 1.6 is Released
#140Go has a lot going for it. That said, there were a few points I noted, based on a recent go I gave it (pardon the pun), at least in relation to my style of development for this project: 1. It's hard to tinker, mostly because it's fussy about what variables are defined or used. This is a strength in the usual course, but when one is trying to posit what a poorly documented 3rd party API is doing it can be a serious pa…
Doesn't tools like goconvey solve the automated testing side of stuff (at least for running locally)
iirc the workflow with that is change a file and process will rebuild and test it.