HN user

huyng

192 karma

http://www.huyng.com

I'm a Biomedical/Software Engineer. Currently exploring the waters of embedded electronics and sensors.

Posts9
Comments9
View on HN

I glanced at this paper, here's my basic understanding:

Given an end goal, and a list of web-services, automatically compose the data "piping" required to reach the end goal. Do all of this using AI.

Can someone confirm this? If so that's pretty amazing and I will be giving this topic a deeper look.

No I don't think so ... I actually found this library as I was watching the GoogleIO Wave Keynote. When I saw what the wave team did with GWT, compiling Java => Javascript became a viable option in my mind. Before the demo, it had always been a mystery to me as to why anyone would want to use such an absurd amount of abstraction.

Agreed, I definitely feel most comfortable with my Python on server-side, but the UI ability on this thing is beautiful. Too bad... I wish I was at JavaOne so I could ask these guys some questions regarding how easy it is to separate the two components.

This experimental search is very well done. Will definitely recognizes a problem a lot of us are having with trivial day-to-day stuff such as looking up documentation for a Django function or class. I know a lot of my time is spent looking up functions.

Because of this, I've been working a light-weight search-engine to sift through the Django source code:

http://www.djangocodesearch.com

Hopefully it'll help you find the code you're looking for, fast.

In regards to vertical search, I feel like the biggest barrier to competing with G/Y/M is the relative difficulty a user has to go through to reach the actual search page before entering in the information. If its more than a few key strokes away, then the user has a natural tendency to resort to the Big 3 engine which are situated conveniently in their search bar.

Adding a Firefox Keyword Search would definitely be a step in the right direction, but unfortunately the other browsers don't have that facility.

This originally started out as my own tool, but I thought you guys might be able to benefit from it. I'm always forgetting how certain functions such as "direct_to_template" are called , so I end up digging through source code to find out.

This lets you find code quickly. No need to dig through documentation to reference simple functions or class definitions.