Unfortunately it would give me the most day-to-day benefit on OSX, which is probably the place I'm least likely to see it implemented...
1,157 karma · joined September 20, 2012
Unfortunately it would give me the most day-to-day benefit on OSX, which is probably the place I'm least likely to see it implemented...
I suppose there's a scale at which the "gap" becomes too large to call it "physics," but the larger the scale, the stranger it would be to find something irreducible across so many levels.
[(xocalia + a'tl) => chocola-tl => chocolate => choco-] + [(al-kuhl => alcohol) + (-ique => -ic) => -holic] => chocoholic
which, having contributions from Nahuatl, Arabic, and Latin results in a word with morphemes originating in 3 distinct language families.
On the topic of article rebracketing, I also love "an eke-name" (an extra name) becoming "a nickname".
> (The future) (is going to be) (based in (things like (what (Comma.ai) (is building upon) (what (the book) (describes)))))
I interpreted it to mean:
> The future will have many products similar to those made by the company Comma.ai. Comma.ai creates technology on top of the hardware described by this book.
[1] - http://squib.rocks/
(Which is why I've almost exclusively switched to `git checkout -b <newbranch>` for creating. How often do I want to create but not switch to the branch?)
I agree window.opener was a fairly dangerous addition, but it is subject to CORS restrictions. You can't access it from just anywhere.
Also you'd either need a monospace Unicode font (which I don't imagine has anywhere near 100% glyph support) or incorporate spacing and kerning rules...
That said, this tech has been around for years and I still think it's magic every time.
Now if we started talking about "computeless" architecture I'll be confused. (Though maybe that'll be the trendy name for serverless data sources/sinks in a few years...)
That said, I usually prefer subsets, like viridis.
> git commit and git commit-tree issues a warning if the commit log message given to it does not look like a valid UTF-8 string, unless you explicitly say your project uses a legacy encoding.
> git log, git show, git blame and friends look at the encoding header of a commit object, and try to re-code the log message into UTF-8 unless otherwise specified.
I'm not reacting to any offense, as I agree the US has these problems. However this also describes very well my time spent in metropolitan Spain, France, and Italy.
<EOF>
(For very naive definitions of "optimal")
I totally agree that non-communication is a disappointing game mechanic; it almost always ends up being quite... impure design-wise? It still ended up feeling like the most dynamic of the 3 games for me, though admittedly my opinion of El Dorado is only from one play and word of mouth.
Meanwhile, Exit winning the Kennerspiel frustrates me. It's a solid design, and the escape-room-in-a-box can be quite fun, but it's hardly a gamer's game and the other nominees were incredible.
I guess my takeaway is that the SdJ is built up too much and doesn't reflect my segment of the hobby very well.
Plus, improving typography and cohesiveness of design language can aid speed of navigation, when done carefully.
That said, I did think MDN's current design was both usable and modern, so it wasn't high up on the list of sites I was hoping for a refactor of...