bct

17 ms·

151.
by bct 14y ago
> nothing in the info it gave back looked especially unusual. It doesn't have to be unusual, it just has to vary slightly from machine to machine. It's the specific combination of those slight variations that's unusual.
152.
by bct 14y ago
getmail, fetchmail, etc.
153.
by bct 14y ago
It's a matter of resources. It was a very ambitious project, and they didn't have the funding behind it that Apple and Google do.
154.
by bct 14y ago
A boycott isn't made up out of individuals. Doing this is a waste of your effort unless it's part of a focussed campaign.
155.
by bct 14y ago
No. You're not listening, and you're not arguing in good faith.
156.
by bct 14y ago
> involves being told how to construct a URI The crucial thing that you're missing is that it's being told how to construct that URI in-band . Not in a piece of documentation that has to be hard-coded into the client.
157.
by bct 14y ago
We're talking about two totally different kinds of problems. You're talking about wire formats and structures that feel natural to use for particular kinds of calculations. I'm talking about recognizing properties that we might need a parti
158.
by bct 14y ago
> what resource is it acting on? The distance between the two cities. > You have to come up with some added, unnecessary, implementation-exposing abstraction like "CityPair". This is a really weird thing to say. No, you don't. I hav
159.
by bct 14y ago
No, the problem space being "scalability of component interactions, generality of interfaces, independent deployment of components, and intermediary components". This merely happens to overlap significantly with the requirements of public A
160.
by bct 14y ago
> 1. [send a link for each possible combination] > 2. instruct clients on how to construct appropriate URIs > 3. link a URI for the starting city and then from there link them to possible choices of the second city All three of
161.
by bct 14y ago
The thesis lays out in detail what REST provides: "REST provides a set of architectural constraints that, when applied as a whole, emphasizes scalability of component interactions, generality of interfaces, independent deployment of compone
162.
by bct 14y ago
No, he makes it quite clear that it's a solution designed for a particular problem space. You're debating a straw man.
163.
by bct 14y ago
Nobody ever said that you should use REST if it doesn't suit the problem you're trying to solve.
164.
by bct 14y ago
APIs that ignore the realities of distributed computing and that each have different special-snowflake wire formats requiring tedious documentation: the worst of both worlds.
165.
by bct 14y ago
> Making a call to a server should be like calling a function anywhere else You can make calling a function on a remote machine look and seem (superficially) like calling a local function, but they will never have similar behaviour.
166.
by bct 14y ago
It's worse than that, because sheep don't walk around randomly; they follow repetitive, collectively-defined paths, like most herd animals.
167.
by bct 14y ago
Ha.
168.
by bct 14y ago
> People, you are some of the brightest and cleverest people walking the earth. Oh, please. It's exactly this kind of self-congratulatory bullshit that produces this community's inch-deep intellectual culture.
169.
by bct 14y ago
If you can bring in toads to eat a significant fraction of the beetles that are destroying the sugar cane crops, why wouldn't you do that? (Because: http://en.wikipedia.org/wiki/Cane_toads_in_Australia . These are complex, poorly understo
170.
by bct 14y ago
"The works of the roots of the vines, of the trees, must be destroyed to keep up the price, and this is the saddest, bitterest thing of all. Carloads of oranges dumped on the ground. The people came for miles to take the fruit, but this cou
171.
by bct 14y ago
rm -rf doesn't follow symlinks: /tmp $ mkdir -p a/b/c /tmp $ mkdir -p a/d/e /tmp $ cd a/b/c /tmp/a/b/c $ ln -s /tmp/a/d . /tmp/a/b/c $ cd ../../ /tmp/a $ ls */* b/c: d d/e: /tmp/a $ rm -rf b /t
172.
by bct 14y ago
The secret to understanding HN is that it's not actually a site for hackers. The word "Hacker" in the title bar is written on a board that was nailed up over the word "Startup".
173.
by bct 14y ago
I never said anything about success. We don't need to inject discrimination and close-mindedness, but we do need to counteract it. That means we can't just passively "be open".
174.
by bct 14y ago
> she has nothing to do with the rest of her group. You're wrong. There are lots of things that women experience that men do not (and vice-versa).
175.
by bct 14y ago
> they need only be open to everyone The word "only" makes this sentence completely wrong. In startup terms it's like saying that to make a successful product you need only make something useful and put up a web page offering it for sal
176.
by bct 14y ago
> Therefore, it follows that per capita, it's going to be harder to bring women into the fold. That doesn't follow at all. It could be that the industry has some kind of blind spot that could be easily addressed by e.g. encouraging and
177.
by bct 14y ago
Oh, you're saying that this isn't respectful of him. I thought you were saying that he is not deserving of respect.
178.
by bct 14y ago
I'm supposed to dislike an incredibly prolific and inspiring guy because he took some stuff offline?
179.
by bct 14y ago
It's useful in some contexts but overly broad in others. The differences between a boat and a stapler are readily apparent; the differences between a copyright and a patent, much less so. Imprecise language takes advantage of that.
180.
by bct 14y ago
Yes, I used /dev/null.

More ›