Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ldh
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
91.
▲
by
ldh
14y ago
You can either use the 'W' movement (instead of 'w') or use the 'iskeyword' option to change what is considered a word character. Word movement: http://vimdoc.sourceforge.net/htmldoc/usr_03.html#03.1
92.
▲
by
ldh
14y ago
I don't think I've changed your example, I just don't agree with this: >/orders/groupByCustomer and /orders/groupByDate have the exact same data. The only difference here is representation. Those are two different resources (made plain
93.
▲
by
ldh
14y ago
Ah, you're right.
94.
▲
by
ldh
14y ago
Setting the same Accept header at every request is not difficult or error-prone. But that aside, what happens when you store versioned resource URLs in the client, and then you want to upgrade your client to a new version of the API? Do y
95.
▲
by
ldh
14y ago
I think you're still conflating resource with representation. I would consider /customers/byDate to be a resource. It happens to be a collection containing references to other resources (customers) which you can then navigate to directly if
96.
▲
by
ldh
14y ago
I would say it emphatically is the same resource, in the same way that content negotiation can return you either a JSON or HTML representation of a given resource with the same URL, for example. I don't have a strong opinion on query stri
97.
▲
by
ldh
14y ago
I'm not sure that we're in disagreement here, really. The concrete implementation will change, that doesn't mean the abstract resource changes. If you've got two different resources representing different aspects of customer data, those d
98.
▲
by
ldh
14y ago
In this example, the client knows what version it can handle and should specify that separately than the user providing the URI for the desired resource. Separation of concerns. Why make the end user guess about version numbers?
99.
▲
by
ldh
14y ago
If you're writing a client which is sensitive to the resource representation changing over time and you're using something that calls itself an API, hopefully one would skim the provided docs enough to see that you might want to explicitly
100.
▲
by
ldh
14y ago
I'm not dismissing the idea that resources need to be versioned, certainly a client written against v1 might not be able to handle the v2 representation of the resource. It's just that I think the abstraction the resource is representing ge
101.
▲
by
ldh
14y ago
Sure, if your URIs are versioned those are by definition not going to change. However, I would stress that the 'R' in URI stands for "Resource", not "particular version of an API to request that resource". It seems like your approach places
102.
▲
by
ldh
14y ago
One of the main drawbacks to the HTTP Accept header approach for both versioning and content negotiation is that it makes it less convenient to test from a browser when you can't encode those things in the URL. Personally I feel that using
103.
▲
by
ldh
14y ago
I sympathize, but I'd much rather somebody send me an HTML email than an attached Word document, which is the next likely candidate in most workplaces.
104.
▲
by
ldh
14y ago
This worries me every time I use AOP, but I mitigate that risk by writing integration tests which assert that the aspects are doing what they are intended to, and also to raise an alarm if somebody unknowningly breaks them.
105.
▲
by
ldh
14y ago
That's assuming that there actually is a significant idea bound up in the tiny idea, which is not generally the scenario that the author is complaining about.
106.
▲
by
ldh
14y ago
Ah, right. Thanks for clarifying.
107.
▲
by
ldh
14y ago
I'm not sure it would be such a good idea to implement a hodgepodge of random peoples' mappings.
108.
▲
by
ldh
15y ago
Sometimes it's not. But if you're determined enough to spy on somebody via the audio on their phone, you will likely be persistent and eventually overhear something the person would prefer you didn't. If I were concerned about being spied o
109.
▲
by
ldh
15y ago
Minor interjection: the word you both want is "tic".
110.
▲
by
ldh
15y ago
Honestly perhaps it's partly a defensive reaction about a tool I like. If so, my bad. Maybe I can't help but feel like the "article" could be perceived as saying "see, vim chose these keys simply because that's what the keyboard said withou
111.
▲
by
ldh
15y ago
I worry that the tone of the article seems dismissive of the choice that went into mapping those keys to arrow directions in vi ("That's the whole story"). As if to say it was mere happenstance that vi uses hjkl, and any other outcome was e
112.
▲
by
ldh
15y ago
I wasn't sure how to verify that I recognized my keys at first. To save anyone else a bit of time googling, you want to run "ssh-keygen -lf your_key.pub" against your local copy of the key to generate the fingerprint and compare that to wha
113.
▲
by
ldh
15y ago
You make good points, but I'm not entirely sure that the possibility of someday needing to do analytics on the data precludes one from using NoSQL now. I've heard/read about a good deal of large scale sites running on NoSQL alongside a rela
114.
▲
by
ldh
15y ago
My experience with Homebrew has been a world of improvement over MacPorts. Every time I'd try to update things with MacPorts I might as well have started filing an issue ahead of time. Homebrew rarely requires additional intervention.
115.
▲
by
ldh
15y ago
Well said, thank you.
116.
▲
by
ldh
15y ago
> Civilization hangs on a fine thread of voluntary compliance to the government. That sounds pretty much exactly backwards from any society I want to be a part of. I don't exist in service of a government, but can choose to tolerate a g
117.
▲
by
ldh
15y ago
Does that computer have a network connection? Just store your plugins and settings in a git repo (a good idea anyway) and pull them down on whatever machine you're using.
118.
▲
by
ldh
15y ago
Thanks, I've put that on my reading list.
119.
▲
by
ldh
15y ago
The notion that psychadelics affect a person's outlook is not that great a leap to make, and others have already posted links to studies supporting that. While I'm not asserting that LSD was the lynchpin to his success, I really don't see t
120.
▲
by
ldh
15y ago
> Concluding that he wouldn't been the same successful person without doing LSD. There's no evidence of causation. That's the fallacy. Who's making that conclusion? As far as I can tell, nobody's attributing his success entirely to LSD.
More ›