News for hackers. Stuff that matters.
Re:Go: Planning the 1.5 release by edwinnathaniel on Tuesday December 02, 2014 @02:54AM (#8686153)
I played with Go a bit and I like the idea of Go replacing C/C++ to write *NIX tools (no, not the GUI ones, the command-line ones, the daemons, the utilities, the server/collectors).
Re:Go: Planning the 1.5 release by waxjar on Tuesday December 02, 2014 @06:33AM (#8686620)
Once Rust is stable, it would be really cool to see these rewritten in Rust.
Re:Go: Planning the 1.5 release by untothebreach on Tuesday December 02, 2014 @07:24AM (#8686744)
Re:Go: Planning the 1.5 release by vezzy-fnord on Tuesday December 02, 2014 @09:33AM (#8687242)
There's still findutils, inetutils, binutils and other collections part of the GNU base system, though. The core daemons are all separate projects, as well.
Re:Go: Planning the 1.5 release by YakovYakov on Tuesday December 02, 2014 @08:26AM (#8686904)
When will it be that Rust is stable? Many moon ago I was of the told that December of 2014 would be the calendar date of the Rust stable version. Yet December is now and I see no Rust stable version. When come it? When?
Re:Go: Planning the 1.5 release by steveklabnik on Tuesday December 02, 2014 @08:31AM (#8686925)
Release candidate around the end of the year. See http://blog.rust-lang.org/2014/10/30/Stability.html and http://blog.rust-lang.org/2014/09/15/Rust-1.0.html for more details.
Re:Go: Planning the 1.5 release by melling on Tuesday December 02, 2014 @11:23AM (#8687854)
If the release candidates are a few weeks out then it must be beta and very close to stable? Can anyone who's using Rust daily discuss performance and reliability. It should be ready for weekend projects.
Re:Go: Planning the 1.5 release by jakevn on Tuesday December 02, 2014 @12:00PM (#8688109)
They have 31 blocking issues to take care of before 1.0 is a possibility: https://github.com/rust-lang/rust/milestones/1.0

The project has 2,100 open issues and 8,500 closed issues.

The stability more or less comes down to the community moving away from targeting nightly, and that can only happen when all of the fires are put out. There are still a lot of breaking changes and clean-up being done in the final hour.

Some people consider stable to mean that the language is "production ready", which often implies a complete set of common libraries. There is still a lot of work to be done in this regard after 1.0. Doing the nightly build whack-a-mole is too frustrating for many, though, so 1.0 will help a lot for developing the ecosystem that a "public ready" language needs.

Re:Go: Planning the 1.5 release by gtani on Tuesday December 02, 2014 @06:14PM (#8690745)
I recommend looking at "This week in" blog and the RFC's also, to form your own opinion of stability

http://this-week-in-rust.org/

https://github.com/rust-lang/rfcs#active-rfc-list

__________________________

discussion re: stdlib and 1.0 https://www.reddit.com/r/rust/comments/2mo0zb/the_race_towar...

Re:Go: Planning the 1.5 release by jakevn on Thursday December 04, 2014 @03:02PM (#8701298)
Thank you for this. I thought this-week-in-rust stopped a while ago. Very useful!
Re:Go: Planning the 1.5 release by kibwen on Tuesday December 02, 2014 @11:59AM (#8688101)
Weekend projects certainly, but I'd still off from doing anything super serious because there are still a few breaking changes waiting in the wings (such as the finishing touches on closure reform), as well as a few potential last-minute syntax tweaks that are still being considered (though if accepted those should be trivial enough to migrate via an automated tool).
Re:Go: Planning the 1.5 release by reflexer on Tuesday December 02, 2014 @12:05PM (#8688138)
It's coming just after Perl 6.
Re:Go: Planning the 1.5 release by StevePerkins on Tuesday December 02, 2014 @07:39AM (#8686779)
By the time Rust is stable, there will be something cooler. And so on, and so on...
Re:Go: Planning the 1.5 release by Arnor on Tuesday December 02, 2014 @11:26AM (#8687877)
Why wait for rust to be stable for something cooler? Haskell is already here :)
Re:Go: Planning the 1.5 release by Animats on Tuesday December 02, 2014 @02:58AM (#8686164)
It would be a big step forward to have everything that runs as root written in something safer than C/C++.

(Screams come from the Old UNIX Admins.)

Re:Go: Planning the 1.5 release by tene on Tuesday December 02, 2014 @03:13AM (#8686192)
The biggest stumbling block there, for me, is that it's impossible to write shared libraries in go. You can't write libraries in go that can be used from anything other than go, so until you've converted everything over to go, you'll still need to write libssl.so and friends in C. Go is a great application language, but it doesn't play well enough with others to really be a systems language as long as you can't write libraries other languages can use in it.
Re:Go: Planning the 1.5 release by colin_mccabe on Tuesday December 02, 2014 @03:43AM (#8686261)
Shared libraries are coming for Go.

https://docs.google.com/document/d/1nr-TQHw_er6GOQRsF6T43GGh...

But shared libraries aren't the only way or even (often) the best way to share code. Especially when we're talking about UNIX tools, it's pretty easy to have one process run another process. Go has a really quick startup time which makes that practical.

Re:Go: Planning the 1.5 release by tene on Tuesday December 02, 2014 @03:58AM (#8686287)
There are absolutely some scenarios that can be adequately (or better) handled by communicating with another process! I completely agree with you. There's still a large volume of use cases where linking code in-process is a very good fit for the problem.

I am looking forward to go someday being suitable for producing native shared libraries. If they ever prioritize and complete that work, that's something I'll absolutely be taking advantage of, and will extend the situations where I'm able to reasonably use go.

Re:Go: Planning the 1.5 release by marcus_holmes on Tuesday December 02, 2014 @04:41AM (#8686375)
I moved from C# to Go, and one of the things I really loved is the sudden absence of DLL-Hell. I never have to worry that installing my program on another machine would suddenly cause it to bork.

I guess I'm happy importing everything into monster huge static binaries and not worrying :)

Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @07:15AM (#8686725)
Coming to C# in the form of .NET Native and vCore on Windows.

Mono always supported static linking.

http://www.mono-project.com/docs/tools+libraries/tools/linke...

http://www.mono-project.com/docs/advanced/aot/

Sometimes I wish people would not mix toolchains with languages.

Re:Go: Planning the 1.5 release by marcus_holmes on Tuesday December 02, 2014 @09:30AM (#8687220)
yeah, I get that. But my actual lived experience of working with C# is Visual Studio, Windows, and DLL-Hell.

Whereas the go toolchain is very much a part of the language. The go team don't tell you whether tabs or spaces are canonical, they tell you to run go fmt on your code.

Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @10:22AM (#8687512)
While I like Go as a better C, I wouldn't use it instead of C#.
Re:Go: Planning the 1.5 release by zak_mc_kracken on Tuesday December 02, 2014 @08:42AM (#8686975)
DLL hell was solved in .net a decade ago. If you need specific versions, ship with your own version in the local directory. Otherwise, .net assemblies solve the problem elegantly.

Go needs to support shared libraries if it wants to move to the next level of adoption.

Re:Go: Planning the 1.5 release by johnny_reilly on Tuesday December 02, 2014 @06:59AM (#8686689)
Marcus, I'm also giving Go a try at the moment (C# is my day job). What are you using tooling-wise? I'm trying out Lite IDE at the moment and that's the best experience I've had yet.

So far my view is that I really like the language but I'm finding the tooling pretty unappealing. Wonder if I'm missing a trick?

Re:Go: Planning the 1.5 release by okatsu on Tuesday December 02, 2014 @07:24AM (#8686743)
I find that Sublime Text with the GoSublime plugin works pretty well. There's "Intellisense" for imported packages and GsLint actively detects syntax errors. Gofmt also takes care of indentation and formatting for you at every save.
Re:Go: Planning the 1.5 release by bkeroack on Tuesday December 02, 2014 @08:21AM (#8686880)
++ to Sublime Text and GoSublime. It's what I use and anecdotally appears to be the most popular Go dev environment.
Re:Go: Planning the 1.5 release by johnny_reilly on Tuesday December 02, 2014 @08:45AM (#8686983)
Thanks both of you - I haven't had a go with GoSublime yet. Now I will!
Re:Go: Planning the 1.5 release by marcus_holmes on Tuesday December 02, 2014 @09:26AM (#8687204)
My experience: you kinda have to rethink what an IDE is. Go comes from the *nix tradition where the "coding environment" is a text editor and a few terminal windows.

I use GoConvey to automagically run my tests and tell me what I broke. I keep this running in a terminal window (so I can CTRL-C stop it) and a browser window.

I have another terminal tab on the same window for godoc, and that's serving another browser window.

I have a terminal tab for git commands and file manipulation (this is the one the terminal window is normally on).

I moved away from SublimeText to Atom (with go-plus) because while the load times suck, the go language support in the tooling is way better. Not that GoSublime is bad, it's not, but Atom just works better for me. I tried vim, and loved it, but the support for the go tools was never quite there, and configuring the bloody thing was a nightmare.

So every time I save a file it automagically runs gofmt, goimports, compiles and runs my tests in goconvey (and tells me what I broke), and colours my test coverage right in the editor.

It's not quite the integrated experience that Visual Studio is, but it's incredibly powerful, and conforms to the unix philosophy of lots of good, small programs working together.

And just for comparison; today I spent 20 mins trying to get a dark theme on VS2010 and had to give up (or hand-pick every colour in what looked like around 100 options)... whereas I have dark themes galore on everything else ;)

Re:Go: Planning the 1.5 release by colin_mccabe on Wednesday December 03, 2014 @05:19AM (#8692870)
There are a lot of good choices out there. Personally, I use vim plus "gocode" to do context-sensitive code completion. gocode is able to parse go, which means that its autocompletion results are pretty good.
Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @10:37AM (#8687595)
VS2010 ?!? We are already on 2013 with 2015 around the corner.
Re:Go: Planning the 1.5 release by vetinari on Tuesday December 02, 2014 @01:08PM (#8688673)
Tell that to Oracle, who hasn't bothered with OCI libs for VS2013 yet ;)
Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @02:46PM (#8689372)
ODP.NET works just fine. :)
Re:Go: Planning the 1.5 release by vetinari on Tuesday December 02, 2014 @05:39PM (#8690512)
Not in C/C++ apps :-(
Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @06:38PM (#8690871)
I see. My employer has abandoned C++ world in 2005, so I only get to play with C++ on hobby projects.
Re:Go: Planning the 1.5 release by marcus_holmes on Tuesday December 02, 2014 @03:00PM (#8689460)
did I mention DLL-Hell? ;)

actually it's because I have a 2010 licence, but none for 2013. Another advantage of Go...

Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @03:35PM (#8689682)
I don't have DLL hell in our applications since years.

- DLLs are distributed with applications

- Dependencies to GAC libraries are enforced with full version

- we make use of application manifests when needed

> actually it's because I have a 2010 licence, but none for 2013.

Express and Community editions?

We just use MSDN subscriptions.

> Another advantage of Go...

I see some good uses for Go as an improved C, but tooling when compared with JVM and .NET eco-systems is not one of them.

Re:Go: Planning the 1.5 release by bkeroack on Tuesday December 02, 2014 @06:24PM (#8690809)
Tooling actually is a huge advantage. I can install the latest Go distribution and get everything I need to work (minus a text editor).

On the other hand, on top of the JDK I have to install, eg, Eclipse, maven, etc. Not to mention all the crazy frameworks I would need to get any real project off the ground.

Similarly with .NET I have to install a whole host of stuff with Nuget, LINQPad, etc.

Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @06:37PM (#8690867)
I rather use VisualVM, Eclipse MAT, dotTrace... offer, not that .ps generated file from Go runtime.

I rather use RAD tooling for GUI design, not spending hours doing design by code.

I also prefer to have visual representation of DB schemas and generate code from it.

I could go on with lots of other examples, Go tooling will get there some day when the language gets enterprise adoption.

Re:Go: Planning the 1.5 release by Dewie on Tuesday December 02, 2014 @12:35PM (#8688399)
> My experience: you kinda have to rethink what an IDE is.

An IDE is an integrated development environment; emphasis on integrated. Having to, by yourself, put together a mixed assortment of tools for your development environment doesn't seem to qualify as being integrated. Though of course someone could come and make a program that bundles a lot of tools together and present them as a coherent, integrated package.

(Personally I'm sceptical of IDEs myself and tend to believe more in being able to make your own work-flow and programming environment, which a lot of loosely coupled (ideally not coupled at all) tools makes simpler.)

Re:Go: Planning the 1.5 release by duaneb on Tuesday December 02, 2014 @01:15PM (#8688726)
Integration is a matter of degrees. The trend with recent editors (textmate, sublime, atom) is that they expose more abilities to integrate with simple editor functions. I don't see how this doesn't qualify as integrated.
Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @03:13PM (#8689538)
They don't offer the developer experience Smalltalk, Interlisp-D, Lisp Machines, Ceres did, nor what modern IDEs are offering.
Re:Go: Planning the 1.5 release by codexon on Tuesday December 02, 2014 @03:44AM (#8686264)
And because everything is statically compiled, go binaries tend to be very large.

Imagine each binary being 5 mb on average and multiply that by 100.

Re:Go: Planning the 1.5 release by dagw on Tuesday December 02, 2014 @05:55AM (#8686534)
I suppose you could work around that by going the busybox route and provide multiple tools as a single binary and then just hard link them to the different command names. But I guess there might be other problems with that.
Re:Go: Planning the 1.5 release by slimsag on Tuesday December 02, 2014 @04:37AM (#8686367)
> And because everything is statically compiled, go binaries tend to be very large.

Are you sure it's because they are statically compiled?

Not because each binary has DWARF debug symbols in it so that there are useful stack traces?

> Imagine each binary being 5 mb on average and multiply that by 100.

I don't think it's a factor of 100 times, that seems a bit outrageous.

Re:Go: Planning the 1.5 release by rurounijones on Tuesday December 02, 2014 @05:16AM (#8686442)
>> Imagine each binary being 5 mb on average and multiply that by 100.

> I don't think it's a factor of 100 times, that seems a bit outrageous.

I think he means 100 utilities all weighing in at 5mb

Re:Go: Planning the 1.5 release by masklinn on Tuesday December 02, 2014 @09:29AM (#8687216)
> Are you sure it's because they are statically compiled? Not because each binary has DWARF debug symbols in it so that there are useful stack traces?

Removing DWARF information with -ldflags -w reduces the size of the binary by 20%. The binary is 1.8MB originally...

    $ go build hello.go            
    $ wc -c hello                  
     1806192 hello
    $ go build -ldflags -w hello.go
    $ wc -c hello                  
     1408880 hello
the rest is pretty much all runtime, the hello world itself should take about 10k, that's more or less the size of the C or dynamically linked Rust versions (Rust also uses static linking by default, and the hello world is 300k in that case)
Re:Go: Planning the 1.5 release by f2f on Tuesday December 02, 2014 @11:18AM (#8687821)
to see how much the runtime contributes to the size of the binary use an empty main. for hello world you bring in the fmt package which is a relative heavyweight:

    $ cat > t.go
    package main
    func main() {}
    $ go build t.go 
    $ wc -c t
      623280 t
    $ nm t | wc -l
        1029
    $ cat > t.go
    package main
    import "fmt"
    func main() { fmt.Println("hello world") }
    $ go build t.go 
    $ nm t | wc -l
        2541
Re:Go: Planning the 1.5 release by grey-area on Tuesday December 02, 2014 @05:36AM (#8686489)
Go binaries start at around 2mb on my machine, so not as bad as 5mb, but still much bigger than similar utils in c. Storage is getting dramatically cheaper all the time though, so the size is becoming less important.

Shared libraries for the std lib would definitely be nice for utils, but they do have drawbacks too (dll-hell).

Re:Go: Planning the 1.5 release by rakoo on Tuesday December 02, 2014 @06:40AM (#8686641)
The problem is not in storing the binary, the problem is that you have to load the binary in memory to execute it. So 5mb you have to transfer from disk to memory and keep it there until you're done (and this is not even counting the runtime memory use)
Re:Go: Planning the 1.5 release by 4ad on Tuesday December 02, 2014 @08:02AM (#8686829)
Not true at all on systems that use on-demand paging (i.e. all systems in the past 30 years). Only what's used is paged-in, and it's paged-in only when it's used. A big part of Go binaries are DWARF info, which are not paged-in in regular operation. Also, much of the code is not paged-in either. The code is currently bloated because the linker can't always statically determine which methods it can elide (it does that for functions), because Go allows to query the dynamic type of an interface at runtime (reflection, type switches and type assertions, and all that). Alan Donovan has done some promising static analysis work that will allow the linkers to elide more code than they do now.
Re:Go: Planning the 1.5 release by grey-area on Tuesday December 02, 2014 @07:37AM (#8686773)
If memory use is a huge issue, you can get down to 400KB or so without using the stdlib - just copy in the isolated code you need if your tool actually requires it. Even with liberal use of the stdlib it's not 5MB on average, more like 1-2MB - where did that 5MB figure come from? It is possible to have smaller binaries with static linking but you have to be careful. Of course it'd be nicer if they were more the size of tiny linux utils (30KB), but they'd need dynamic linking for that, which brings up other issues.

If you are severely resource constrained, and need to have lots of tiny programs resident in memory at once, then go with static linking is not a good choice, but does this preclude using go tools on modern servers, desktops, phones where many binaries are typically > 1MB today and many are only run for short periods anyway?

Re:Go: Planning the 1.5 release by pjmlp on Wednesday December 03, 2014 @07:37AM (#8693370)
> Shared libraries for the std lib would definitely be nice for utils, but they do have drawbacks too (dll-hell).

There is also .a/.lib hell, the only difference is when it gets handled.

In Windows dll-hell is a solved problem since Windows 2000 for any developer that bothers to follow Microsoft guidelines instead of copying dlls into systems directories.

Re:Go: Planning the 1.5 release by grey-area on Wednesday December 03, 2014 @10:33AM (#8694207)
I didn't mean by referencing dlls to imply this was a windows-only problem, just that using dynamically linked libraries shifts the burden of dealing with dependency conflicts to the runtime machine, and away from the developer at compile time.
Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @07:20AM (#8686735)
There is an open ticket planned for Go 1.5.

https://code.google.com/p/go/issues/detail?id=6853

Re:Go: Planning the 1.5 release by TylerE on Tuesday December 02, 2014 @10:47AM (#8687652)
Yea, I mean, that'd cost 20 cents or something to store.
Re:Go: Planning the 1.5 release by Animats on Tuesday December 02, 2014 @01:09PM (#8688684)
Are shared libraries a memory win in production environments? For shared libraries to be a win, you have to be running different executables on the same machine (or VM) which share libraries of significant size relative to the memory use of the program itself. You also have to be using a big fraction of each shared library. With static linking, if you need "cos", you get that loaded; with a shared library, you bring in the entire math library.

Modern production environments often involve only one program per VM, or multiple instances of the same program. In such cases, shared libraries are a lose.

Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @04:00AM (#8686297)
That is a toolchain limitation, not the language.

I think gccgo allows for .so.

And the work for Android is adding .so support to the main toolchain.

Re:Go: Planning the 1.5 release by jzelinskie on Tuesday December 02, 2014 @03:40AM (#8686254)
While totally unsuited for the aforementioned hypothetical situation, Go has also supported SWIG for a few years now.
Re:Go: Planning the 1.5 release by codygman on Tuesday December 02, 2014 @07:25AM (#8686748)
You could write those command line libraries/etc in Ocaml now ;)
Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @03:12PM (#8689526)
Yep

"Unix system programming in OCaml" http://ocaml.github.io/ocamlunix/

Re:Go: Planning the 1.5 release by codygman on Tuesday December 02, 2014 @10:55PM (#8691825)
Oh this looks very interesting. It would be fun to read this and make Haskell versions of the programs as well as learn Ocaml at the same time!
Re:Go: Planning the 1.5 release by luckystarr on Tuesday December 02, 2014 @03:49AM (#8686267)
You mean something like Perl Power Tools from the late 90s? https://metacpan.org/release/ppt :)
Re:Go: Planning the 1.5 release by pjmlp on Tuesday December 02, 2014 @03:20PM (#8689581)
> It would be a big step forward to have everything that runs as root written in something safer than C/C++.

As you know, options have existing since the early days, but mentalities are hard to change.

I came to the conclusion that many issues in computing are only solved with change of generations.

Re:Go: Planning the 1.5 release by zak_mc_kracken on Tuesday December 02, 2014 @08:41AM (#8686968)
Go is never going to make much inroad in that area until it supports shared libraries, and its creators seem to be strongly opposed to that idea (while claiming their goal is to replace C++...).
Re:Go: Planning the 1.5 release by niemeyer on Tuesday December 02, 2014 @09:45AM (#8687303)
There are many different aspects to shared object support, there is support to some of these aspects today (you can link against shared libraries, for example), and there are on going conversations about supporting other models.

This is a recent thread on the subject:

https://groups.google.com/d/msg/golang-dev/0_N7DLmrUFA/qGRb8...