News for hackers. Stuff that matters.
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.