rix0r

"Constantly pushing updates"

This sounds to me like their plan is to constantly be updating the Lua scripts from their cloud server.

There's no way this would be allowed on iOS right? (Although I can see the comparison with web pages running arbitrary JavaScript, which can also be constantly be updated, but still...)

The author is probably right that there is an issue somewhere, but since I've been using SteerMouse (http://plentycom.jp/en/steermouse/) I haven't had any mouse annoyances anymore.

Not sure what it changed though; I thought it was the acceleration curve but for all I know it could be replacing the entire OS X mouse driver, laggy code and all.

I'm using Vodafone and I'm seeing an "X-VF-ACR" header in my headers that contains a very long base64-encoded string.

Anyone any idea what it is?

(Edit: Looks like a big bunch of binary)

> Don't carry over platform-specific icons

Not in the least because they may mean different things!

As far as I can tell, all icons shown side-by-side for the different platforms perform the same actions, except for the back-arrow.

The Android and Windows icons are for "going back", while the iOS icon shown there is used for "reply".

It also works in Safari 5, surprisingly enough, with ESC to exit fullscreen mode.

f and b will do page scrolling in the man viewer.

I don't know why this is being downvoted -- I guess others are reading something different than I am?

There are three parts to Siri:

1. Speech-to-text (parent has it backwards but that's what he means, obviously)

2. Text-to-intent (referred to by parent as NLP)

3. Intent-to-API calls

Obviously, (1) happens in the cloud and (3) happens on the device. It is still unclear where (2) happens but if the cloud service only responds with text, it seems that (2) happens on the device.

And (2) is still a hard problem by itself.

Another suggestion, similar to the Hand Moldable Plastic: http://sugru.com/

Homebrew will use libraries that are already present on your system, instead of keeping a separate copy of everything.

The downside may be decreased stability, but the reduced compilation times make up for that, to me (and haven't had a problem yet).

We commonly encounter users who believe that searching on two fields can be facilitated by creating two separate indexes on those fields. This example should give you some intuition about why this just isn’t possible.

Not really, as the example only allows a search on ingredient, since it explicitly says the name is not known at all, and hence could never be used for search.

Now let's say we know two things about the unknown recipe: it contains chicken and it's from the Italian kitchen.

Given these two indexes:

  Chicken
    1, 15, 582, 1032

  Italian
    3, 15, 16, 82, 1032, 6821

I could definitely use both to speed up my search by looking only at pages that occur in both indexes (in this case, 15 and 1032). This can be done in O(# of indexes * index length) time if both indexes are in sorted order.

No kidding. The first thing that I tried immediately wasn't supported (capital 'C' to start typing over the first line).

Would be very nice once it gets more mature, though.

I kind of like the "picture password" option. It shows innovation in an area that badly needs some (authentication) and should be easier to remember for many people than a PIN code, I think.

Picture passwords would be harder to write down, but I'm not yet sure whether that's a negative or a positive.

We have that system already (at least, here in the Netherlands), where automated overhead signs urge you to decrease your speed in case of traffic jams.

In my experience, not a single person follows those signs. Everybody just keeps on going at full speed until they're forced to stop.

It would be a lot better (for everyone!) if cars were driven by machines that followed those rules properly.

It recently occurred to me that the icon of a phone is of a type of phone that almost nobody uses anymore. And the icon of a camping site uses a model of tent that nobody uses anymore either.

Our kids will be so confused...

Actually, you just mean the console, not cmd.exe.

cmd.exe is just an command interpreter (like bash) that needs a console/terminal (like xterm) just as any other CLI application does.

In other words, is not cmd.exe that sucks, but the Windows console. If Microsoft improved the console, cmd would immediately become nicer to use (though still hobbled by an inane scripting language).

</pedantry>

For another thing, on WordPress.com the "View Standard Site" button hardly ever works for me.

I keep on trying it, hoping for the better, and cursing every time I'm forced to deal with the OnSwipe theme.

And on Mike Taylor's blog (http://reprog.wordpress.com/), the scroll used to be broken in OnSwipe (it kept scrolling me back to the top). Not sure if it's still the case, these days I just keep to my feed reader instead of visiting his site because I don't want to deal with OnSwipe.

Looks promising!

One question: form rendering, validation and handling are the most important as well as the most annoying things you have to do while writing a web application. Do you plan to incorporate something for that into the framework?

But every hop is also a new attempt... and any variance for a hop could also be encoded using error bars.

Well yeah, but I thought the point was they were equivalent: i.e., one is simply syntactic sugar for the other.

It would be a little more cumbersome to write, but the same effect can be achieved easily:

  A a = new A();
  try {
      B(a);
      return C(a);
  } finally {
      a.cleanup();
  }
 

Transforms into:

  Either<Exception, Result> ret;
  
  A a = new A();

  ret = B(a);
  if (ret.isRight()) ret = C(a);
  
  a.cleanup();
  return ret;

Maybe someone can rewrite this even more cleanly. I can think of an easy-to-generate improvement containing a GOTO.

I thought it was pretty well-known that standard system timers (except the High Performance ones) could/would be inaccurate. I'm actually surprised by how reliable the OS X timers are.

Normally, if you do any kind of benchmarking, you would run the test N times and average the times out.

Escaping the asterisk also works.

  find . -name \*.bar

Also passes the unexpanded argument "*.bar" to find.

From looking at this time lapse I can actually get a sense of the world turning. Very impressive to watch.

Sure, but what I think he meant was: if one work item is very large, it should be broken down to make sure there's no work hiding in there that got overlooked.

I like it, but isn't the approach a little overkill?

If you'd design a declarative systems where you declare your datasets and how they transform into each other, then you could analyze the dependency chain and do the same thing as a library instead of a separate interpreter.

Sprinkle some transparent pickling, hashing and timestamping in there and you get all of the benefits but much more reusable.

Am I underestimating the problem?

True, but the same non-reload could be accomplished with:

  <a href="realurl.html" onclick="javascript_magic(); return false">

And wouldn't break spiders.

I remember hearing in a presentation by Douglas Crockford that the browser will reflow only after the event that triggered the JS has been handled.

So if you do 1 insert or 1000 in response to an event, it should only cause 1 reflow.

Animation on the other hand...

Could you elaborate a little on how matching fonts are chosen? I see delta-VAR and delta-RLW but what do these mean?

If you could use the unique, generated key only once, what would be the harm in not letting them time out?

I guess e-mail sniffing could be a risk... but if that's an issue then we have larger problems.

I like the "history -c" before logging out, while leaving downloaded files and extracted archives all over the place.

Oh yeah, he's really covered his tracks now...