68 karma · joined August 7, 2016
[ my public key: https://keybase.io/georgepantazes; my proof: https://keybase.io/georgepantazes/sigs/_qo_lvYxLy7CJ_IY2QZUbxntRQIBmiNnp3OMJd3-MdQ ]
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
It made me wonder what alternatives there were for adding additional hostnames for the loopback IP.This article on dscl (https://tomafro.net/2009/07/dscl-the-easy-way-to-add-hosts-o...) is one such finding.
If anybody has suggestions about the best way to add hostnames for testing/override purposes, whether that's /etc/hosts or something else, please comment with your favorite.
To be honest, I've never really thought about viewing all tips on the same page, although that is very convenient. A fine feature that should probably be adopted by Duolingo as well.
The convenient one-page format ~~solves~~ mitigates a different issue I've been having lately though. Duolingo doesn't consistently publish (existing!) tips to all Duolingo frontends/apps. Well-supported languages get the best tip-content support, but languages that aren't as supported sometimes don't have tip present even if the tip content exists.
For example:
- Duolingo Web always has tips if tip content exists. This acts like a source of truth, as far as I'm aware.
- Spanish is a language which has tip content both on Web and iOS. I believe this is because Spanish is popular and well-supported.
- Greek is a language where tip content is not accessible via the iOS app, but is present on the web site. I believe this is because incorporating the presentation of tips is probably some hardcoded markup thing (React?) and nobody has gotten around to doing it yet. Also, there's a possibility that the underlying documents need different rendering treatment or style enforcement, and have been omitted from the mobile app on purpose. Still, this is a thorn in my side.
So for me, a one-page-tips fills a gap in the Duolingo UX (which should probably probably be fixed on Duolingo's end since this simply seems to be a prioritization/maintenance/time/effort problem).
As a user, I'd like an easy way to refer to the tips before each lesson without pulling up the actual Duolingo web app - otherwise, why don't I just do my actual lessons on the web app as well? Usually I'm doing lessons on my phone, not my computer, because the phone is not only more convenient (small) but it's easier to change keyboards and type in non-latin alphabets.
Everything after that is finesse, personal effort, and ability to express things succinctly (much like the personalized "headlinese" styles mentioned).
- It uses a human readable text-based file format renderable via the PlantUML jar. Friendly to CLI and git.
- The diagrams are stylable, should you wish to style them.
- There's a PlantUML Integration IntelliJ plugin that's easy to use for preview/rendering[2]
- Overall simple to use, but I imagine it can as robust as you want it to be. For example, the IntelliJ plugin Sketch.it automatically generates PlantUML diagrams from Java source code[3], and the source code for how it works is available on BitBucket if you want to know how it works[4]
I've seen other people suggest Mermaid.JS[5] before, but I haven't used it so I can't say how it is. [1]: http://plantuml.com
[2]: https://plugins.jetbrains.com/plugin/7017-plantuml-integration/
[3]: https://plugins.jetbrains.com/plugin/10387-sketch-it-
[4]: https://bitbucket.org/pmesmeur/sketch.it/src/develop/
[5]: https://mermaidjs.github.ioFirefox and Chrome, and most major browsers can indeed take screenshots from the browser _console_, but taking screenshots from the command line is a separate, interesting concept.