Hacker News new | past | comments | ask | show | jobs | submit | ianbishop's comments login

Isn't that what a traditional co-op is?


Offering equity as well as gadgets is an interesting spin on the co-op model. It works well enough; generally it's chosen for something that doesn't want explosive growth but instead is serving a community -- and that might not gel with the "get rich" urges of some startup types.


It's a query API, no different than any REST API.


But how is authentication and authorisation mapped and passed around and shared between the app server cluster and the db cluster?


Modern CLJS does a pretty good job of guiding you through Clojurescript's tooling:

https://github.com/magomimmo/modern-cljs


There is actually an LRU map implemented in Java, though it is sort of hidden in the LinkedHashMap using a special constructor.

http://docs.oracle.com/javase/1.4.2/docs/api/java/util/Linke...


One issue with that is that it doesn't expel older entries. The capacity specified in the constructor is just the initial capacity.


Is there any way to make it so that the gutter is always present? There's a bit of a noticeable jump to include it when I save a file, it's sort of annoying me.

I tried

  let g:gitgutter_enabled = 1
but that does seem to work.

I'll have a poke through the source.



probably not, the way vim works if there are no more signs attached to a document the gutter goes away. This isn't plugin related, it's just a manner of how vim works.

Although I suppose you can work around this by displaying a fake sign (color match gutter background?), but that has its downsides (depending on colorscheme, the sign can show up. and vim doesn't support whitespace characters for signs, at least not from what I can see).


Yeah, I just noticed that now.

It seems to just grep through the diff itself, so adding a fake sign would be a pain and, as you mentioned, probably not display correctly anyway.

I'm sure my eyes will adjust :).


Why can't you change it if you want to?


I wish it could be made to stand on the right side of a vim buffer. This way it would still be present on demand but would not shift the whole buffer one column to the right.


The named functions were just an attempt at better highlighting what is going on for some readers. Not sure if it worked, but sorry it annoyed you :).


I personally find that creating too many functions makes the code look too different from the "natural", synchronous alternative. But I also hate when people write tons of 1-line methods (Uncle Bob style) so YMMV.


Agh, this is an editing mistake. I re-worded this last minute and reading again next day, it was a mistake.

Really what I meaning to say is that it's much clearer as to what is happening. I was trying to point out that success and error were actually functions on the deferred returned from $.post, not just functions you can pass into $.post (as they once were - hence "circa 2009").


Awesome, I didn't know that such a book existed. Thanks!


This sort of already exists through the service hooks they have, there are 122 services atm.


Good point but improving the presentation there could be great for both GitHub & its users.


I agree, a nice shiny app store with icons could be a great feature for Github users and developers using their APIs. Right now service hooks are pretty buried in the settings panel.




I can't see how to submit stories or post comments with that API


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: