Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
aboodman
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
67 ms
·
691.
▲
by
aboodman
16y ago
Go - It's a little thing, but I'm enchanted by its implicit interfaces. Seems like it'd be very nice for testing and for decoupling components.
692.
▲
by
aboodman
16y ago
Thanks for this, I was persuaded by parent's argument, but am a Chrome user.
693.
▲
by
aboodman
16y ago
Also, writing validation code by hand leads to a lot of duplication and room for error.
694.
▲
by
aboodman
16y ago
I specifically chose Chromium (or another browser) because it is one of the few pieces of open source software that normal people would have direct experience using. Seeing your fixes shipped to you and your friends' browsers is an awesome
695.
▲
by
aboodman
16y ago
I think it depends on the kind of person you are. Use what you have. I'm the type that will routinely head off to a restaurant with only vague information about where it is or what its name is. "It's probably down here, this seems like a st
696.
▲
by
aboodman
16y ago
That is the fundamental and sad misunderstanding of this ad. People don't fiddle with their phones while walking because the phones are hard to use. They fiddle because the phone is fun and addicting. There's no desire for a phone that lets
697.
▲
by
aboodman
16y ago
Heh, awesome.
698.
▲
by
aboodman
16y ago
The point that Joe is making is that people can't participate in the official, Google-supported, widely distributed version of the code. They can fork the code and do whatever they want, but that fork doesn't have a lot of value if it doesn
699.
▲
by
aboodman
16y ago
This thread hit close to home, so I wrote a blog post I've been meaning to write for awhile, and framed it as a response: http://www.aaronboodman.com/2010/10/wherein-i-help-you-get-g...
700.
▲
by
aboodman
16y ago
Also, I once worked in an office that I had trouble focusing in. I couldn't figure it out for like months and ended up doing all my work at home after hours. It turned out my office had bad ventilation. Working with the door open fixed that
701.
▲
by
aboodman
16y ago
I used to have something like this problem, and it turned out to be very simple: hunger. I had a bad habit of not eating when I was deeply into something (or deeply stressed), and my body would simply run out of fuel. I think there is somet
702.
▲
by
aboodman
16y ago
Do you only have one computer? Is it a notebook or desktop? It's hard for me to relate to these kind of use cases, because I use many computers, several of which are notebooks. I could never use a workflow like you because I'd always be los
703.
▲
by
aboodman
16y ago
Interesting :) You should start tinkering with the omnibox API and let us know what you think: http://code.google.com/chrome/extensions/experimental.omnibo...
704.
▲
by
aboodman
16y ago
The group is a good place. We read tweets and blog posts too, so that will eventually make its way back.
705.
▲
by
aboodman
16y ago
Thanks for testing out the omnibox API when it is still so difficult to use. We start out new APIs in experimental to get a feel for how they work before becoming stuck with them forever.
706.
▲
by
aboodman
16y ago
A wise man once me taught me that this is the role of culture. You can't be there all the time, and don't want to be: Smart people need to be able to make their own decisions or they get bored and demotivated. A good culture helps them make
707.
▲
by
aboodman
16y ago
In this case it was our (Chrome team's) fault. We broke an API, which we try to never do. The bug is: http://crbug.com/47726 . I actually thought this had already been rolled to stable, but it hasn't yet. I will check if we can get it done
708.
▲
by
aboodman
16y ago
Somebody below said just the opposite. Personally, I find V8 really nice to read and work with. Which part of it do you not like?
709.
▲
by
aboodman
16y ago
V8 mostly follows it: http://code.google.com/p/v8/wiki/Contributing
710.
▲
by
aboodman
16y ago
For some concrete examples of the above: WebKit, Chromium, Gecko, and V8 are all C++. My impression is that there is a very high startup cost with C++ to getting it working on the platforms you want to support and picking the subset that is
711.
▲
by
aboodman
16y ago
Fair enough. I misinterpreted your question to be "So, Mozilla says that this replaces Greasemonkey?", and wanted to clarify the situation (and also snark about the capitalization, a long-time peeve that I should really let go, but never qu
712.
▲
by
aboodman
16y ago
It's Greasemonkey, not GreaseMonkey. Greasemonkey is a third-party extension. It wasn't created and isn't maintained by Mozilla, so it can't be officially obsoleted by Jetpack. That said, if Jetpack supported transparently installing Grease
713.
▲
by
aboodman
16y ago
You are comparing the first mass-market release of Chrome extensions with the first alpha release of Jetpack, which isn't fair. A better comparison would be the first dev channel release of Chrome with support for extensions. That was May 1
714.
▲
by
aboodman
16y ago
* Having users have to configure their popup blocker is pretty weak sauce right? I mean, normal apps don't have to be configured after installation just to be useable. * DOM Storage is not permanent. Browsers can decide to delete it at any
715.
▲
by
aboodman
16y ago
The author works on that :)
716.
▲
by
aboodman
16y ago
The names "web" app and "native" are far too coarse grained to be meaningful. The important parts are the details. Zero install or heavy weight install? Cross platform or single platform? Offline accessible or not? Safe for anyone to use, o
717.
▲
by
aboodman
16y ago
Ah, 3d games and image manipulation. The last resort of all native arguments. This is going to change pretty rapidly with native client I think.
718.
▲
by
aboodman
16y ago
I think in order to make NoScript work you'd also need the ability to block <script> that is inline, not just script that is loaded remotely.
719.
▲
by
aboodman
16y ago
Chrome does this, almost all extensions use it.
720.
▲
by
aboodman
16y ago
Omnibus-response to previous comments: - The ability to intercept and modify requests is indeed missing. We've had some proposals for how to add that to our APIs, but nothing concrete yet. - We're working on the ability to manipulate the co
More ›