miniblog.

← Back to all posts
Aug 31, 2017 at 19:03
140 chars on Twitter feels so much more limiting after tooting!

Related Posts

Oct 17, 2021 at 00:35
Interesting idea from a discussion around limiting rustc error output: why don't compilers use a pager when there are a lot of errors? Git uses this for large output and it works well there. (origin: https://github.com/rust-lang/rust/issues/27189#issuecomment-291420407)
Add `rustc --fatal` which stops at the first build error · Issue #27189 · rust-lang/rust
Add `rustc --fatal` which stops at the first build error · Issue #27189 · rust-lang/rust
(Should this be an RFC?) Motivation When refactoring, one may have dozens or hundreds of build errors which need to be fixed one by one. Sometimes, a build error is only a consequence of an earlier...
Nov 15, 2020 at 22:20
I'm surprised that "free for OSS" is a common pricing model, without rate limiting the number of free projects/users. Perhaps OSS isn't really that big? Or maybe it drives paid-for adoption sufficiently?
Jun 28, 2020 at 05:23
It's interesting that Twitter sets limits on content size, but not distribution. What if the number of retweets/comments on a tweet was rate limited, or had a cap for new users Would it promote slower or thoughtful conversation? C.f. Stack Overflow limiting new user abilities.