HumanCoder - Latest Comments

Re: A zope.component introduction – Part 2

Nam — Fri, 12 Oct 2012 04:44:40 -0000

Interesting, I'm working with Zope and still don't know why I need it, it's imposed by the direction, waiting for your next tutorial!

Re: Fabric pygments lexer

Antoine — Tue, 24 Jul 2012 04:14:33 -0000

Nice post !

Re: Go pathfinding

Zippoxer — Fri, 06 Jan 2012 15:35:02 -0000

I never thought googling "golang pathfinding" would work.

Re: Make your own Wikipedia dictionaries for Kindle

Isopor — Thu, 20 Oct 2011 21:36:02 -0000

Great idea! Could you do one for the IT subject?

Re: Go pathfinding

alexplugaru — Wed, 19 Oct 2011 03:17:51 -0000

You're right Chris, I did verify this and the maps are extending once I assign new values, I guess I misunderstood how 'make' really works and how builtins are allocated. However you do need make/new to initialize/allocate the map to be able to use it. I'll modify the post and the code once I have the time.

Re: Go pathfinding

Chris — Tue, 18 Oct 2011 19:57:38 -0000

Why on earth are you resizing map? It resizes itself during runtime when you add new keys, even if you've specified an initial size. Simply using yourMap[newkey] = newData is more than sufficient. No need for make and no need for append.

Also, doing a linear scan of your closed list in O(n) time is silly. The map will give you expected (or perhaps guaranteed, I haven't looked to see if it does perfect hashing) O(1) time assuming you've come up with sensible unique keys for your nodes. Absolutely do not use slices for potentially large datasets you plan on searching through them.

Exchanging proper data structures for syntax is absurd. You absolutely need maps for a closed list because it can grow to enormous sizes and your pathfinder shouldn't wait all day just to verify that shiny new node n isn't a duplicate. Implement your scheme of astar for Vacuum Robots (Russel & Norvig's AIMA book) with a sufficient size world and you'll crash and burn.

Re: Go pathfinding

sasha — Wed, 17 Aug 2011 01:09:41 -0000

The copy builtin is very powerful, but I think your missing the point here. What if I have to perform some operations with val and then assign to s11? I'll still have to use make to allocate and them to loop over.

Btw I could have used append to copy like so:
var s11 []int s11 := append(s11, s2...)

Re: Go pathfinding

Kahvi — Tue, 16 Aug 2011 17:22:08 -0000

After "s11 := make([]int, 5)" you can use "copy(s11, s2)" built-in function instead of looping. :)

Re: Make your own Wikipedia dictionaries for Kindle

sasha — Sun, 14 Aug 2011 16:44:23 -0000

I've put a link there buddy.. that's credit in my universe.

Re: Make your own Wikipedia dictionaries for Kindle

anon — Sun, 14 Aug 2011 16:38:26 -0000

XKCD is licensed under http://creativecommons.org/...

Give credit where credit is due
http://xkcd.com/license.html

Re: Go and Python

Uriel — Sun, 14 Aug 2011 10:20:56 -0000

gofix is much more effective than you might think, and it is able to do a much better job in a language that is statically typed and has a simpler syntax than Python, it can't handle *everything*, but the comparison with 2to3 is not fair either.

Also the APIs in the Go stdlib are much nicer, cleaner and more consistent than the tangled and often redundant mess in the Python stdlib, in part because they are not afraid to clean stuff up, if you leave old cruft alone, it just builds up and it becomes even harder to fix.

Ogle is on its way out, but a new debugger is in the roadmap, in the meantime gdb works well, and to be honest IMHO print() is always the best debugger.

Re: Go and Python

sasha — Sun, 14 Aug 2011 05:15:41 -0000

gofix will not work in all cases. It's not obvious. How about new added parameters? Manual work is still required. Personally I didn't have a good feeling about 2to3 either. It can go wrong on so many levels.

Re: Go and Python

obvious — Sun, 14 Aug 2011 04:51:44 -0000

gofix?

Re: Go and Python

sasha — Sun, 14 Aug 2011 02:16:23 -0000

As I stressed out, changing API often makes people nervous.. when you have a lot of code upgrading to a new golang version would be a real pain in the ass if the API changed in 50 different places. Again.. go is a young language so I guess it's better now or never right? I used gdb, but I want something like python's pdb. I guess ogle would be that.

Re: Go and Python

Jesse McNelis — Sat, 13 Aug 2011 22:49:59 -0000

1. stabilizing APIs can be a terrible thing. Python has some real problems in it's standard library that have been there for decades but nobody want to break the API to fix them.

2. There is gdb support and the ogle debugger is on it's way at http://golang.org/pkg/exp/o...

3. There was a proposed "bike/shed" package but too much discussion eventually lead to the proposal being dropped.

Re: Go pathfinding

sasha — Sat, 06 Aug 2011 02:39:07 -0000

Certainly! Take a look at the updated post.

Re: Go pathfinding

Patrick — Fri, 05 Aug 2011 15:06:38 -0000

It would be helpful if you could explain how you arrived at the first two "lessons learned." Thanks. :)

Re: Make your own Wikipedia dictionaries for Kindle

sasha — Fri, 05 Aug 2011 02:26:11 -0000

Thanks! I'm glad you appreciate it! You can get your physics dictionary here: http://blog.hiresasha.net/w...

Enjoy!

Re: Make your own Wikipedia dictionaries for Kindle

stehk — Thu, 04 Aug 2011 20:47:20 -0000

That's really cool
I'd be greatly interested in the physics related wikipedia, so if you could put your version online onec it's finished that would be great:

I've been using an old german wikipedia version which is a single file of about 324 MB. (http://www.axelschaefermdb....
My kindle 2 occasionaly (or rarely) crashes when i use it- so this file size seems to be on the verge.

Back in the mobipocket days someone wrote a script to create a wikipedia from a html-dump. The files where split up into 40 mb pieces with an index file with hyperlinks- but the hyperlinks between the books don't work on the kindle (though I think generally they would be possible)
http://fbo.no-ip.org/cgi-bi...

anyway, thanks a lot for this post