640 karma · joined August 15, 2012
Imagine how much wailing and gnashing of teeth there will be if Go 2 delivers generics but with triple the build time and +50% binary size... if you thought the minority was vocal now, wait til you see that!
Case in point: the original plan for the NBN was vastly preferable to this scandal ;)
But my main question about the moon was quite serious - how would you access the moon with this? I couldn't quite understand how this part from the executive summary would translate to an actual DNS request:
"One special GeoRegistry must have a server assigned to every cell on the planet. This GeoRegistry will be called the default GeoRegistry named "earth." (The names of the other planets will be reserved for interplanetary geodata.) The default GeoRegistry will be used when client queries do not specify a GeoRegistry name, or when the specified GeoRegistry does not have an assigned cell server."
Kinda cool that .geo predates Google Maps by about 4 or 5 years!
.aero may be questionable, but surely the boundless usefulness of .ninja or .moe isn't in dispute?
I couldn't agree with this more. Also undotree [1] should be built into Vim as well. Vim represents undo/redo under the hood as a tree, which is absolutely incredible once you have a plugin that unlocks it, but the built-in facilities for traversing that tree could be charitably described as "dismal".
Vim's undo tree makes a solved problem out of the old "undo undo undo undo undo... ok what did this file used to look like... redo redo y... oops did I just press 'y' by accident instead of redo and blow away a bunch of my later edits... next time I should remember to commit before I do that (even though I totally won't)" situation, but without the plugin, it's effectively inaccessible.
[1] https://github.com/mbbill/undotree"Don't be evil" is deprecated, Mozilla Manifesto #4 will be too, soon enough.
! medium dickbars and other bullshit:
##.u-clearfix.metabar
##.metabar
##.js-stickyFooter
##.highlightMenu
I have not limited it by domain so I can catch all the other Medium-based blogs that use other domains (hackernoon, etc). This raises my risk of false positives but that doesn't bother me anywhere near as much as all the extraneous garbage on their site does. YMMV.If only Firefox would hurry up and integrate tree styled tabs without requiring one of several now-obsolete extensions, the experience of using a computer might become marginally less terrible. But of course I'm not holding my breath waiting for anyone in this sorry saga to do something that actually helps until I'm forced to read every single website one 200-word line at a time.
Leaving fantasy-land aside for a moment, this morning you woke up in the real world. In the real world, that tool does already exist, and it's called Mercurial.
If you try command-line Mercurial for long enough to get past the initial "oh no Windows/macOS/Linux got updates and moved all my icons" muscle-memory-refresh phase (and especially if you last long enough to get into revsets and templates), you'll find it extraordinarily difficult to go back to using command-line git. Your power grows with Mercurial as you learn more about it because you aren't constantly fighting the complete absence of idioms and opaque "man-page" style of documentation that puts a slab of inscrutable text front and centre and neglects to provide simple examples for common problems (apparently we have a perfectly good Stack Overflow for that).
The git boosters will respond to this by saying, as they always do, "yes, but the real power of git is in the model of the information under the hood. The CLI is just an interface, if you don't like it you should spend months studying the internals and build your own workflow on top of git". Again, back in the real world, who has time for that? Or the interest? Especially when, as I already mentioned, that tool does already exist and it's called Mercurial and you can get started with it right now.
Both tools can do close to exactly the same things under the hood with differences that won't make a lick of difference to the vast majority of users. The user-facing differences are where it really matters: one tool has an excellent CLI which is clear, concise and discoverable; the other has github. Damn. Lousy network effects.
[1] http://www.freelists.org/post/nanomsg/New-fork-was-Re-Moving-forward [1] http://nanomsg.org/
[2] http://libmill.org/
[3] http://libdill.org/ [1]: https://sourceforge.net/projects/javampeg1video/