ehsanul

However, I am aware that the meaning of AI is always pushed to "whatever we can't yet do". Yet, in this case it's hardly justified to think that these chatbots even slightly challenge Penrose's thesis.

I read the book too BTW, loved it. I'm not sure if he's right, but it's nevertheless a wonderful book and heartily recommend it to all.

It somehow got no attention though, when I posted it to HN a long time back. The title matters a bit too much, I remember keeping the original title for my post.

For my own startup-wannabe, I had to pivot because of the same problem: the app would only be useful if millions of people were using it, the way it was originally conceived.

Graceful degradation is less common for JavaScript now than it used to be though. So if you want a smooth web experience, these days you just can't go without JavaScript. I personally don't think that's a horrible thing, but I guess most people who've disabled JavaScript (or use Lynx or something) would disagree.

    What changed since this article was written:
    1) The Server structure in the unstable branch is finally divided into sections using comments.
    2) The command table is now loaded into an hash table, so the lookup is now O(1) and it is possible to alter the hash table at runtime. This is how we implement ed the command renaming and shadowing in redis.conf.
    3) The shared integers are not used when diskstore is enabled, since we need tha t every object is independent with a different LRU timestamp and so forth. But o therwise using the default mode of operations (in memory) shared integers are us ed.
    4) Databases are now watched for the implementation of "WATCH" using a better AP I, that is signalModifiedKey().
    5) Now we listen to the TCP socket and to Unix socket if configured. The Redis C luster branch (not public) will also listen to an additional TCP port using for cluster message passing.
    7) Loading data from disk to memory is now non blocking, we do this re-entering the event loop while loading data.
    8) Response reading is now faster and cleaner code, thanks to Pieter's work.
    This is a very nice overview. Of course only the surface is covered, there are a lot more things going on in the specific commands, in VM / diskstore command (by far the most complex part of Redis), in specially encoded data types, and in rdb/AOF loading/saving, incrementally expanding hash tables, ...
    In just 30k lines of code there is already a lot to take in mind!
    Basically I and Pieter already reached the point where we are experts in different areas. We both understand the whole Redis codebase, but for instance he is more expert in the sorted sets and special encoding code, I'm more expert in the diskstore things, and so forth.

As an XMonad user with a 15.4" screen, I disagree. For example, when programming, I find it quite easy/fast to alt+1 to my browser for documentation, and alt+8 to go to my 8th workspace, where I usually have a couple terminals open with vim. Or sometimes I'm switching between those two and Gimp on workspace 6.

This doesn't really require XMonad, just having workspaces and quick shortcuts for moving through them is good enough. Most applications are easier to use when you give them the whole screen (at least smaller screens). But yeah, if you're using some sort of taskbar/dock to switch between applications with your mouse, it's probably easier to just have both open together.

[1] http://en.wikipedia.org/wiki/Public-key_cryptography

http://www.mirah.org/

They're only about an hour to 1.5 hours long, and there's only 6 of them. They are supposed to be spread over a 6 week period. So every week for six weeks, you need to find an hour to spend listening to the talk for that week.

You will be meditating during part of the talk. Other days, you will meditate 20-30 minutes. This is not a large time commitment, and since you're on HN, I'm guessing you'd be able to manage.

Good luck! The first two talks have been pretty nice so far.

    heart = (scale,x,y)->
      ctx.beginPath()
      ctx.moveTo(x,y)
      p1 = [x-75*scale,y+20*scale]
      ctx.bezierCurveTo(x-20*scale,y-55*scale,p1[0]-50*scale,p1[1]-55*scale,p1...)
      p2 = [x,p1[1]+60*scale]
      ctx.bezierCurveTo(p1[0]+25*scale,p1[1]+22.5*scale,p2[0]-35*scale,p2[1]-40*scale,p2...)

      ctx.moveTo(x,y)
      p1 = [x+75*scale,y+20*scale]
      ctx.bezierCurveTo(x+20*scale,y-55*scale,p1[0]+50*scale,p1[1]-55*scale,p1...)
      p2 = [x,p1[1]+60*scale]
      ctx.bezierCurveTo(p1[0]-25*scale,p1[1]+22.5*scale,p2[0]+35*scale,p2[1]-40*scale,p2...)

      ctx.strokeStyle = 'rgba(255,40,20,0.7)'
      ctx.stroke()
    
    heart(1.0, 450, 250)

On the other hand, I'm impressed how you just ignored TrollBait's insult and just replied in an absolutely normal manner.

Sounds like they were simply psychopaths, hence lacking most emotion. It seems like that emotion/empathy was selected for in our evolutionary history (or perhaps it's just a side-effect of something else, don't know), so I don't think psychopathic behavior could possibly be characterized as darwinism.

http://www.youtube.com/user/tedtalksdirector#p/u/0/b-iGZPtWX...

If you don't mind me asking, what in your estimation would be an ideal query plan for a join of the type I've described? A hash join? Also, I've left statistics to their defaults and run ANALYZE after bulk data uploads (the only time data is written), but I'll try bumping statistics collection up and running VACUUM ANALYZE again. I don't know what server configuration could be messed up to cause something like this; I have my memory settings (shared_buffers, effective_cache_size) set up fine, and cost parameters have been left alone. Other configuration settings I've changed shouldn't be affecting read queries.