17,915 karma · joined September 1, 2007
Many years ago, Google Search existed only on http:// and schools used filters to block searches that they didn't like. Then Google shipped https:// for search on www.google.com, upset the schools because they could no longer block just some searches, then moved encrypted search to encrypted.google.com so that the entire domain could be blocked: https://cloud.googleblog.com/2010/06/an-update-on-encrypted-...
Edit: LWN link was changed to this one
1. My brain thinks in terms of editing lines, not s-expressions; I didn't get the hang of paredit, and editing without paredit required really tedious edit operations.
2. Elixir's understanding of types matches Erlang's and the host VM, while Clojure invents its own uni-typed IObj but runs on a typed VM. Interop with Java required adding type annotations. Elixir/Erlang interop seems to be almost entirely pain-free.
3. Elixir has a lot of syntax niceties like triple-quoted strings that automatically remove indents. And pattern matching everywhere.
4. I can feasibly (and in fact, have) audited and built all of my Elixir and Erlang dependencies from git repositories, while doing the same with the Maven dependencies needed for a typical Java project would be almost impossible. I wouldn't even know where to begin with bootstrapping all the necessary Maven plugins.
5. Elixir/Erlang has per-process garbage collection and memory limits, though I haven't taken advantage of these yet.
https://bugs.chromium.org/p/chromium/issues/detail?id=640923
https://bugs.chromium.org/p/chromium/issues/detail?id=639541
My workaround for watching movies with vsync? Use Intel drivers in my main X session, modesetting in a secondary X session just for mpv.
This is not necessarily the case.
> However, in a number of cases involving DVD decryption courts have held that there is no fair use defense in circumvention cases. In Universal City Studios v. Reimerdes, 111 F. Supp. 2d 294, 322 (S.D.N.Y. 2000), the court stated that "[i]f Congress had meant the fair use defense to apply to such actions, it would have said so."[5]
https://en.wikipedia.org/wiki/Anti-circumvention#Fair_Use_an...
As noted in xattr(7), the VFS imposes a limit of 64 kB on the size of
the extended attribute name list returned by listxattr(7). If the
total size of attribute names attached to a file exceeds this limit,
it is no longer possible to retrieve the list of attribute names.