sstephenson
Joined 17 years ago
Karma
1,066
Submissions
89
Member since
Feb 20
http://sstephenson.us/
View on Hacker NewsRecent submissions
Comment · 6 years ago
When will GitHub terminate its contract with ICE?
Comment · 7 years ago
jwalk parses JSON into a stream of TSV records: https://github.com/shellbound/jwalk/
Comment · 7 years ago
Performance depends on what toolset you’re using and how large your data set is.
For small JSON documents, like a package.json file, jwalk is around ten times slower on my machine: 0.03 seconds, vs 0.004 seconds for jq.
For larger documents, like the 1.5 MB GitHub API response tree.json [1] in the jwalk corpus, jwalk on mawk takes 0.37 seconds vs jq’s 0.11 seconds, but jwalk uses just 1.18 MB of memory, vs jq’s 5.81 MB.
Other interpreted parsers don’t fare as well: JSON.awk [2], which only runs on gawk, takes 0.8 seconds and 27 MB to parse tree.json; JSON.sh [3] takes 201 (!) seconds and 43 (!) MB, and JSONPath.sh [4] takes 7.4 seconds and uses 1.7 MB.
[1] https://raw.githubusercontent.com/shellbound/jwalk/master/te...
[2] https://github.com/step-/JSON.awk
Comment · 11 years ago
Try to imagine yourself in the shoes of someone who doesn't know HTML and just wants to write a message or comment with a little emphasis and maybe a bulleted list. That's the majority of our customer base at Basecamp.
Creating an editor for that does sound like a simple task, doesn't it? Except the tools the browser gives you just don't work, as we've experienced first-hand over the years in the form of customer bug reports.
That's why we built Trix.
Comment · 11 years ago
I was involved with the Wysihat project too. What we found is that its approach, like most other editors', is fundamentally broken. We created Trix to solve the problem. https://github.com/basecamp/trix#different-by-design
I think you'll find Trix's toolbar easy to style however you'd like, but if not, it ought to be straightforward to implement your own using the API.
Comment · 11 years ago
Sadly, while the Scribe developers correctly identified all the various problems with contenteditable (https://github.com/guardian/scribe/blob/master/BROWSERINCONS...), they chose to solve it like most other editors: by using execCommand, waiting for the browser to make a change, and then attempting to clean it up afterwards.
Trix's thesis is that this approach is fundamentally broken. Instead, Trix updates an internal document model on each input event, then re-renders the editor contents in response.
Comment · 11 years ago
Yes, of course we've seen ProseMirror. It looks quite nice.
By the time we first heard of it several months ago, the bulk of Trix had already been written.
Comment · 11 years ago
It is not impossible. It just takes a lot of time and effort. It took two developers around 18 months to build Trix.
The readme explains how our approach is different from other WYSIWYG editors. (Most others are just toolbars that call execCommand.)
Comment · 11 years ago
Trix fully supports file attachments and image attachments, as documented in the readme. It includes an inline caption editor for images.
Trix also supports "content attachments" (currently undocumented) which allow embedding arbitrary HTML as attachments in the document. Basecamp 3 uses this feature to embed @mentions with avatars, and various oEmbed types, in messages and comments.
Comment · 11 years ago
No, it's not distributed as a Ruby gem.
Comment · 14 years ago
"Many of the Ruby version switchers work with '#!/usr/bin/env ruby', but rbenv won't in certain circumstances, so an optimization for it has been built into the framework now."
Incorrect. It is support for an enhancement that rbenv provides.
You often want to invoke an application binstub from another program such as cron, and you want to use the per-project Ruby version specified in the application's root directory. Other version managers require you to spawn a subshell and load the version manager into the shell or otherwise set up the per-project Ruby version environment, then `cd` into the application directory, and finally run the binstub.
rbenv requires an environment set-up step too—set `RBENV_DIR` to the application root—but provides a wrapper that eliminates the need for such gymnastics. When you change a binstub's shebang to `#!/usr/bin/env ruby-local-exec` rbenv automatically searches up the binstub's directory tree to find the right Ruby version.
Comment · 14 years ago
Here's another perspective: http://sstephenson.us/posts/on-configuration