Disqus - Latest Comments for binerdog

Re: The TCK Trap

Brian McCallister — Tue, 04 Apr 2017 23:14:19 -0000

Yeah, the OpenJDK TCK access rules have changed since then, so is very good to point out :-)

Re: Using the Real Network with Docker 28 Mar 2016

Brian McCallister — Tue, 28 Mar 2017 14:49:08 -0000

So hosts set up this way can communicate without any problems. They are on the same network.

Re: Using the Real Network with Docker 28 Mar 2016

Brian McCallister — Tue, 28 Feb 2017 13:27:24 -0000

Sure, just do it per-host, or are you talking something with swarm?

Re: Making Really Executable Jars

Brian McCallister — Wed, 21 Oct 2015 12:54:46 -0000

It should work as normal -- it is still a normal jar, just with some ignored stuff at the beginning.

Re: Setting up a Go Development Environment 24 Mar 2013

Brian McCallister — Tue, 25 Aug 2015 18:14:59 -0000

I no longer do this :-) See later comments (further down the page).

Re: Setting up a Go Development Environment 24 Mar 2013

Brian McCallister — Tue, 25 Aug 2015 18:13:52 -0000

There are a few tools, Godep ( https://github.com/tools/godep ) is probably the most common, and the one I use by default now.

Re: In Clauses

Brian McCallister — Thu, 06 Aug 2015 14:53:31 -0000

I don't understand your statement here -- the sql statement is not actually created until execution time.

Re: Java URL Handlers

Brian McCallister — Fri, 27 Mar 2015 16:08:38 -0000

I don't think you can unregister one from the JDK once registered, need to look up details again. It is a WEIRD early-JDK design.

Re: Java URL Handlers

Brian McCallister — Fri, 27 Mar 2015 16:07:22 -0000

Yes!

Re: Setting up a Go Development Environment 24 Mar 2013

Brian McCallister — Fri, 30 Jan 2015 17:44:21 -0000

Then don't do it, give them names per project!

That said, I finally succumbed to GOPATH=~/ and use a tool per-project to make sure the right versions of dependencies for that project are checked out.

Re: Setting up a Go Development Environment 24 Mar 2013

Brian McCallister — Sat, 05 Jul 2014 00:12:58 -0000

Thanks!

Re: Setting up a Go Development Environment 24 Mar 2013

Brian McCallister — Sat, 05 Jul 2014 00:10:44 -0000

Idiomatic go has you check out your project *into* a workspace, not check in your workspace.

Personally, I use a workspace per project, a la https://github.com/brianm/a which uses a Makefile to manage the workspace and project, but is otherwise idiomatic (and "go get"-able!)

Re: Library Versioning

Brian McCallister — Thu, 12 Jun 2014 12:27:59 -0000

Update for 2014 -- use Semver instead of APR versioning. Semver is mostly a superset of APR versioning, but is more tightly defined.

Re: First Steps with Apache Mahout14 Feb 2013

Brian McCallister — Fri, 21 Jun 2013 15:29:02 -0000

The code isn't online anywhere. Type is completely safe to remove.

Re: First Steps with Apache Mahout14 Feb 2013

Brian McCallister — Fri, 21 Jun 2013 12:48:13 -0000

`type` there is the content type (ie, blog post, comment, etc) not the ham/spam label. The ham/spam is only recorded on the NamedVector name attribute.

Sorry for the confusion!

Re: Making Really Executable Jars

Brian McCallister — Tue, 11 Jun 2013 08:31:19 -0000

I do not believe so, the actual binary (the jvm executable) needs to read the jar file.

Re: Making Really Executable Jars

Brian McCallister — Fri, 07 Jun 2013 20:00:58 -0000

It needs to be readable as well as executable

Re: First Steps with Apache Mahout14 Feb 2013

Brian McCallister — Sun, 17 Feb 2013 18:16:52 -0000

Happy to, but I would be even more happy to contribute "real documentation" rather then a wiki.

Re: Java URL Handlers

Brian McCallister — Fri, 04 Jan 2013 21:03:04 -0000

The source is linked from the post.

Re: Making Really Executable Jars

Brian McCallister — Mon, 19 Nov 2012 21:41:17 -0000

There is no shell script created, that is the point. It makes the jar file executable.

Re: Go is PHP for the Backend18 Nov 2012

Brian McCallister — Mon, 19 Nov 2012 19:28:12 -0000

Good examples, Mike. The existence of make() for the "our language is not powerful enough for us to express our language" tops the list for me. A couple more off the top of my head:

- Stack allocation is quietly converted to heap allocation iff a pointer to the stack allocated object escapes.

- Maps, channels, and slices are non-pointer reference "special" types.

- Struct literals require a dangling a comma, but you cannot use dangling commas elsewhere.

- make(), new(), and import() all look like function invocations, but are also syntax(ish) (and have special support in the parser). In the case of the first two, they even return values.

These inconsistencies are just inconsistencies, not value judgements. To some folks they will be damning, others won't care. In case you didn't finish reading the article, I personally fall into the "don't really care" category.

Re: Making Really Executable Jars

Brian McCallister — Sat, 16 Jun 2012 17:51:30 -0000

Yes, it still needs the normal manifest entry for Main-class so it knows which main(...) to invoke.

See http://stackoverflow.com/qu... for discussions of the standard way to do it.

Personally, I generally use the Shade plugin though: http://maven.apache.org/plu...

Re: Making Really Executable Jars

Brian McCallister — Sat, 16 Jun 2012 09:30:22 -0000

Right, it doesn't create a seperate shell script, it prepends it to the jar file. Try running:

$ ./target/mything-0.0.1-SNAPSHOT.jar

after the build completes (change jar name to match yours, of course).

Re: Learning to Code

Brian McCallister — Mon, 21 May 2012 16:46:23 -0000

I actually believe that programming will become something everyone does every day, but we won't think of it as programming. It will be embedded in the normal usage patterns of how we interact with computation and we'll think of it as training, configuring, or personalizing. It will in effect be very high level programming and those who can reason more precisely about what they are doing will achieve better results.

Re: Learning to Code

Brian McCallister — Mon, 21 May 2012 16:42:36 -0000

LOL, long gone -- this was in the 90s and I didn't keep a copy. Basically "choose your own adventure" epic where teams of students round robin-ed each others previous sections to write the next. Epics have a very rigorous form so the general shape of what needed to happen next was known, the details could vary widely though. "Interactive" is a bad term for it, given it was really "wend your path through the maze, adding as you go."