wincent

14 ms·

91.
by wincent 9y ago
> I do also hope that this iteration brings with it better docs The docs are very minimal this point with some definite gaps (we had a bit of a scramble to get them written in time for F8), but the point is well-taken: Relay docs need to
92.
by wincent 10y ago
Amazing. That is a thing of beauty. Can't believe I've never seen it like that before.
93.
by wincent 10y ago
A made a simple clone ( https://github.com/wincent/corpus ) of nvALT in JavaScript because it was easier for me to make an app from the ground up in Electron than it was to hack on a foreign Objective-C codebase (a littl
94.
by wincent 10y ago
Alternatively: `brew cask install cathode`.
95.
by wincent 10y ago
Wiki for "reference" material, blog for mostly "long form" writing, and snippets as a random grab bag of unorganized content (analagous to gists).
96.
by wincent 10y ago
Missing: Reason ( https://facebook.github.io/reason/ )
97.
by wincent 10y ago
I made an over-engineered, intricate snowflake for it, for fun: https://github.com/wincent/masochist Markdown content stored in Git, custom indexes in Redis/memcached, data fetched via GraphQL, rendered with React
98.
by wincent 11y ago
Looks great but this is not the kind of thing I want to be driving interactively. Rather, I want my interactions with AWS to be automated as much as possible, via a tool like Ansible or similar.
99.
by wincent 11y ago
Guilty as charged. The blog is new (days old), but server rendering will be coming.
100.
Betting on the wrong horse(wincent.com)
42 points by wincent 11y ago|14 comments
101.
by wincent 11y ago
Setting up a gutter-sized band for displaying the column number ( https://github.com/blaenk/dots/blob/d928a76d802159960d8b2768... ) is a pretty neat idea. I'm stealing that, except I'm using the gutte
102.
by wincent 11y ago
I used to know a lot of this stuff. With Puppet, Chef, and then Ansible, I've found myself needing to know less and less of it.
103.
by wincent 12y ago
We have our own parser at Facebook. Our reference implementation will include a parser, and a we'll be releasing a spec as well so it should be possible to build alternative implementations as well, should you wish.
104.
by wincent 12y ago
GraphQL itself doesn't make any assumptions about the storage engine being graph-oriented or otherwise. It's true that the grammar makes it easy to express graph-like relationships (eg. using the notion of one-to-many connections)
105.
by wincent 12y ago
Not really. It's true that those kinds of "components" will usually live on their own routes, but there's nothing intrinsic to the framework that favors that particular kind of app structure.
106.
by wincent 12y ago
I wrote the gist; happy to answer questions (although out and on my phone right now so I won't be super fast).
107.
by wincent 12y ago
Amazon has released packages for their Linux AMIs that deal with both CVEs: https://alas.aws.amazon.com/ALAS-2014-419.html
108.
by wincent 12y ago
There's no normal workload under which Vim should ever slow down noticeably. I routinely have long-lived Vim instances with hundreds of open buffers, and some of the files can be quite healthily sized (tens of thousands of lines). It s
109.
by wincent 12y ago
That's exactly the point: Git didn't handle the rename conflict so well at the time of the mailing list exchange, but it did handle it better by the time the blog post was written. And it may handle it better still in the future,
110.
by wincent 12y ago
I've been using Phabricator for a few months now, and I used Gerrit for over 2 years at my last job. They each have their strengths, but both of them are infinitely preferable to not doing code review. Neither is awful.
111.
by wincent 13y ago
Not to be confused with evil.js: http://andjs.com/code/eviljs/
112.
by wincent 13y ago
"A map to help you find your location" I hope this isn't the start of feature bloat.
113.
by wincent 13y ago
The article says the author doesn't want to depend on something like Ruby. Ruby (or Python) seem a lot more likely to be on a base install than GNU Stow, though.
114.
Managing Side-effects With the Pub-Sub Model(causes.github.io)
2 points by wincent 13y ago|0 comments
115.
by wincent 13y ago
Shameless plug: the scss-lint tool we built at Causes provides you with an automated way of enforcing a consistent style, including a number of details not mentioned in the original article: https://github.com/causes/scss-lint/
116.
by wincent 14y ago
We've used various partitioning schemes at Causes (I'm a coworker of the OP) but for this particular use case the monthly tables weren't a good fit. (Your comment about automatic/transparent makes me think you're probably thinking of merge
117.
by wincent 14y ago
FWIW, we did this in the opposite order (first Rails 3/3.2, then Ruby 1.9). The bigger wins in developer productivity and access to shiny new toys are to be had by jumping to the latest Rails version. Updating Ruby is just the icing on the