bct

38 ms·

331.
by bct 17y ago
Take a look around the site, the guy's a crank. He's been talking about how great COSA is for years, but he's never actually implemented it, or even shown examples of how it's supposed to look beyond a few trivialities.
332.
by bct 17y ago
It looks like you're making requests directly to the online validators (this is a guess based on how slow it is). Why not just run a local copy? The source for the HTML validator is available, I would be surprised if the others were not ava
333.
by bct 17y ago
Why would you attach a CSRF token to a GET request? GET requests shouldn't do things, so they shouldn't need to be protected against CSRF. (I see this is mentioned in the comments there.)
334.
by bct 17y ago
I agree with all your points, but none of them have anything to do with how "REST" something is.
335.
by bct 17y ago
Having a more specific error code/description in the body of the response is fine, it's using yours instead of HTTP's that's a problem. In the Posterous example that was linked, "Invalid site id" sounds a lot like 404, "User does not have
336.
by bct 17y ago
I really hate it when technical discussions devolve into accusations of "religion". You're basically saying that there is no possible rational reason to do things in some way; after that, any disagreement is merely apologetics. What's left
337.
by bct 17y ago
Why is JSON ok, then? Its structure would be just as custom, and a browser can't read it either. (also the entire world does not revolve around browsers)
338.
by bct 17y ago
GET /q 200 OK { 'start': '/q/start', 'end': '/q/end', 'shift': '/q/shift', 'pop': '/q/pop' } POST /q/end x 200 OK Location: /q/some-identifier-for-element-x The queue now contains [x]. POST /q/star
339.
by bct 17y ago
There are projects for which mainstream UI design is unsuited or unimportant, and there are undoubtedly a few people whose egos would prevent it. Apart from those, I would expect most projects would be happy to accept advice if the UID demo
340.
by bct 17y ago
For the same reasons that very few non-open projects have the kind of usability you're talking about.
341.
by bct 17y ago
Truly, this is a novel and intriguing opinion.
342.
by bct 17y ago
That's the conventional wisdom, but I'm not sure I believe it. It takes (much) longer for an app's usability to mature without some central arbiter, but "you need " it is far too strong a statement.
343.
by bct 17y ago
What I don't get is why you'd pay $35+ for an Arduino when you can get an AVR (the microcontroller at the heart of an Arduino) for $5+.
344.
by bct 17y ago
Where do anarchists come into this? I hope you're not using that word as a synonym for "saboteur".
345.
by bct 18y ago
Show new users a fake front page; ones that upvote the content you don't want on the site get dumped. (I'm only partly joking)
346.
Why It’s Worth Fixing HTTP Authentication (and How to Do It)(necronomicorp.com)
3 points by bct 18y ago|0 comments
347.
by bct 18y ago
That would be a lot. Capacitors are generally on the order of pico/nano/microfarads.
348.
by bct 18y ago
It's got no problem with my OpenID, which is delegated < http://necronomicorp.com/bct> .
349.
by bct 18y ago
I'm OK with calling it "piracy", because nobody is in danger of confusing the details and effects of copyright infringement with those of real piracy. This is not the case with the word "theft".
350.
by bct 18y ago
Of course, I don't think that anybody credible disagrees with that. That doesn't mean that REST "does not mean anything concrete", though.
351.
by bct 18y ago
A lot of people don't get the distinction between HTTP and "HTTP as a transport for some ugliness". The cute initialism isn't the point. The paper that coined the initialism (and describes why HTTP was designed the way it was and what you'l
352.
by bct 18y ago
So a stateful RPC system is RESTful, as long as it uses HTTP? Surely that's not what you mean.
353.
by bct 18y ago
I think this is largely a problem of jargon. "Object request broker" may have a useful meaning to you, but I've only got a very vague idea of what it might be. (I could look it up, but what I've learned over the last two days is that it's m
354.
by bct 18y ago
What's hard to grok about the name? It's an architectural style that's based entirely around transferring representations of resource state between client and server. Names are useful. If the name is misused or used to justify silly things,
355.
by bct 18y ago
> Is www.google.com/search a "resource" or a "method"? You can look at it either way, but it's a perfectly fine resource.
356.
by bct 18y ago
Pretty much. It's certainly more fun than DOM for simple transformations.
357.
by bct 18y ago
I agree, which is why I said that people advocating PUT for commenting don't grok HTTP verbs. (I've never seen anybody advocate that.)
358.
by bct 18y ago
> with people arguing that you should PUT comments to a document instead of doing a POST to /addcomment (because add comment is a verb). If people are arguing that, then they don't grok REST (or HTTP verbs, for that matter). But tell me
359.
by bct 18y ago
REST doesn't demand a noun. If they all have the same code backing them, there's no functional difference between: POST /actions/subscribe and POST /subscriptions and POST /abcdef1234567890 The shape of a URL ha
360.
by bct 18y ago
I know that it's perverse, but XSLT's actually kind of fun if you're not doing anything terribly complex.

More ›