HNHacker News
TopNewBestAskShowJobs

uvtc

88 karma · joined November 30, 2011

John Gabriele

http://www.unexpected-vortices.com/

submissionscomments
uvtc··on The Future of Markdown
I think the reasons for those choices are:

* It's very uncommon to want your output text actually underlined.

* If you really do want underlining, just use <u>this</u>, since it's fine to put raw html in Markdown source.

* The most common way folks express emphasis is probably with ✱asterisks✱ (HN won't let me backslash-escape the *). A less-common alternative is to use _underscores_ (though I rarely see that anymore these days). Maybe the distant third most-common way was with /slashes/. I guess Gruber had to draw the line somewhere and just support the first two most common ways to write it. That seems reasonable.

Another reason to not use slashes for emphasis: using them might interfere (or at least cause headaches) with writing directory names, fractions 1/2, and "and/or" wordings.

uvtc··on The Future of Markdown
I'm not so sure what's needed here is a spec.

What people really want is for all Markdown implementations to be basically the same so they don't have to learn any implementation-specific ideosyncrasies to switch from one to another.

The problem though, as I see it, tends to go away under certain circumstances. And the circumstances, I think, are these:

* If you've got a strong implementation, robust, actively-maintained, and runs fast,

* is easy to obtain, install, and use,

* is well tested and well documented, and

* has just the right blend of sensible additions to the syntax (for example, tables, def lists, LaTeX math, etc.) --- done tastefully,

then folks will just use that, model their own implementations after that, and just overall start considering that to be the standard.

I think this has been slowly and steadily happening with Pandoc.

And, aside from all that, two additional "killer features" that Pandoc seems to have over other implementations:

1. it can convert to/from other doc markup formats, thus making it easy to just convert your existing docs to pandoc-markdown and then use that as your master source format to generate other formats you might need; and

2. with its carefully-chosen set of additional features, it has been slowly proving itself capable of being a replacement for raw LaTeX for certain types of longer technical documents.

My understanding is that there's even some features in the works (for the next release) for converting between markdown dialects --- which would make it even easier to convert markdown files of various flavors into plain standard pandoc-markdown.

So, if you're looking for a standard, I'd suggest that it's for the most part already here. :)

uvtc··on The Future of Markdown
FYI, Pandoc uses ~~two tildes~~ for strikeout syntax.
uvtc··on The Future of Markdown
Using Pandoc, what my habit has become is have the first line at the top of the file be title metadata:

    % Title Goes Here
then make subsequent headings go ahead and start at h1 (rather than h2):

    Some h1
    =======
This puts an `<h1 class="title">Title</h1>` at the top, with regular unadorned h1's further down the page. So, if you like, you can style the title h1 differently from the other h1's.

It breaks the soft rule of having only one h1 on a page, but otoh looks good, and doesn't require me to go to h4 or h5 very often, so I can live with it. :)

uvtc··on The Future of Markdown
I look at it like this: [this] looks a bit like a button you might press (or a link you might click). It looks like what it does.

(this) looks like something you'd whisper off to the side --- to add to the conversation. For example, "That picture is nice (but it needs more trees).".

So links go like: [this is the thing you click](and btw, this is where it leads).

uvtc··on The Future of Markdown
Somewhat related: Pandoc supports delimited ("fenced") blocks as well, but as an alternative allows you to use tildes

    ~~~python
    print "hi"
    ~~~
rather than backticks

    ```python
    print "hi"
    ```
My own 2 cents: I like the more symmetrical tildes.

Anyhow though, yes, I agree; it's great that github supports delimited/fenced syntax-highlighted code blocks and renders .md files there automatically.

uvtc··on The Future of Markdown
Pandoc supports using a backslash at the end of a line to insert a line-break.
uvtc··on The Future of Markdown
I wrote up a little comparison of reST and Pandoc-Markdown, http://www.unexpected-vortices.com/doc-notes/markdown-and-re... , which might be of interest to some.
uvtc··on The World's Lightest Electric Vehicle
Regarding folding bikes, even the smaller ones are still somewhat of a pain to take on the train. But a really tiny one like the "CarryMe" from Pacific Cycles might fit the bill if your "last mile" commute is in the city.
uvtc··on Why Did I Choose Perl When Building Crowdtilt?
Perl 5 has been around for a while and has seen quite a bit of optimization. It's fast.
uvtc··on Ask HN: suggested sweet laptops for running Ubuntu?
[laclinux](http://laclinux.com/gnu/Laptop) is where I got my Lenovo Thinkpad. Recommended.
uvtc··on Debian Now Defaults To Xfce Desktop
I rediscovered it as well, after updating Ubuntu and trying out Unity and Gnome shell.

Xfce does exactly (IMO) what a desktop should do: make me forget what desktop I'm using. It's got all the standard features I expect, and works how I'd expect a desktop to work. Very happy with Xubuntu right now.

Edit: One minor complaint: the default Xubuntu install left me with window borders that were too small to grab onto (for resizing). Had to change some theme or other.

uvtc··on Results of the 2012 State of Clojure survey
> I think we just need to push documentation into the community's culture

Yes.

> and I imagine the best way to do that would be to make tools that make beautiful documentation easy.

Well, we've already got "built-in" tools that make handsome docs (maybe not beautiful, but certainly nice enough :) ). That is to say, almost all Clojure projects are on github and github automatically renders .md files into lovely html. With syntax highlighting too, if you label your blocks like so:

    ```clojure
    (some :clojure "code")
    ```
So, just encouraging authors to add a some doc/*.md files to their project would be an excellent start. :)

> In terms of the {snip} discovery problem

I'm hoping [this](https://github.com/uvtc/clojure-dining-car) might help address that, if it gets some more community traction.

uvtc··on Gitit is a wiki backed by a git, darcs, or mercurial filestore.
Gitit is my favorite wiki software. One file per wiki page, and page source is formatted in (pandoc-)markdown [^1]. Also easy to configure and run.

[^1]: Pandoc adds some oft-needed extras to classic Markdown, such as support for tables, definition lists, LaTeX math, and footnotes.

uvtc··on Effective Go
The Go language seems to have some substantial documentation, which is great. Though, throughout, the code snippets would look better with some syntax highlighting.
uvtc··on Ask HN Teachers and Edu Hackers : How do you prepare educational materials?
You mean what tools did I use? LaTeX.
uvtc··on Ask HN Teachers and Edu Hackers : How do you prepare educational materials?
Do your students have textbooks?

Regarding worksheets/quizzes/etc., you usually either write your own, or else --- to get you started --- borrow from other teachers in your school who are teaching the same subject.

uvtc··on Ask HN Teachers and Edu Hackers : How do you prepare educational materials?
When I was teaching, having a detailed lesson plan was the least of my work. Just a handful of bullet points was fine.

What takes the most time when you're teaching is grading.

Also time-consuming: documenting discipline issues and parent contact. And, when you're new: creating worksheets/problem-sets, lab handouts, quizzes, tests, and exams.

uvtc··on Introducing Mozilla Persona, An Identity System for the Web
Simply always refer to the Persona password as "Persona password".

> In a world where every email provider supports Persona natively, Persona truly is a "no new passwords" authentication system, since it delegates to your provider.

I don't know what this means. I won't give Persona my gmail/yahoo-mail email password.

uvtc··on The Caves of Clojure
> please, someone implement libedit or another readline clone in Clojure and put it in the Clojure main distribution so that the 'up' key gives me the last line.

This works fine for me using Leiningen 2. All the usual libreadline functionality is there, and there's tab-autocompletion too.

uvtc··on Canada’s vanishing tech sector
If there's a lot of Java devs there, the poster might also consider using a JVM-based language. No licensing with MS required, and it should be a relatively painless transition for Java devs.
uvtc··on Flask 0.9 codename Campari released today
I'm guessing that this section of the docs http://flask.pocoo.org/docs/advanced_foreword/#the-status-of... will get updated once the status changes.
uvtc··on Ubuntu To Soon Ship On 5% Of PCs
You can get ThinkPads loaded with your distro-of-choice from [Los Alamos Computers](http://laclinux.com/gnu/Start).
uvtc··on Ubuntu To Soon Ship On 5% Of PCs
> Unity has been polarizing, but many users (especially the "normal" people who are likely to buy an Inspiron or similar) seem to like it.

To anyone who doesn't like Unity, I recommend [Lubuntu](http://lubuntu.net/). Still has the Ubuntu user-friendliness, but no Gnome & Unity.

uvtc··on A Brief Beginner's Guide To Clojure
Hi weavejester. Thanks for the feedback!

Regarding Emacs, yes, I guess I'm a bit behind the cutting edge. I'll probably revisit the section of the Guide once I make the upgrade to Emacs 24. Meantime though, I don't think the instructions are too onerous, and --- as I mention at the top --- if you've already got a favorite editor, you safely skip the whole section.

Re. the "Other Libraries" vs. "Finding the Libraries you Want", thanks for pointing that out. I removed some duplicated info and feels better now.

Re. `lein deps`, it could've been clearer, so I made it so. Thanks.

Re. group-id, thanks for pointing that out. I'll get that clarified soon.

Re. lein-clojars, I like the instructions as is, because I think it will give new users a more concrete feel of what's going on when they upload packages to Clojars.

uvtc··on A Brief Beginner's Guide To Clojure
I was joking, and meant "any other OS besides GNU/Linux". Perhaps not perfectly clear though. Removed unnecessary text.

You should've seen it before though! Had to scale it back from "or another OS ({folds arms} {slowly shakes head} [long sigh] tsk tsk tsk)". ;)

uvtc··on A Brief Beginner's Guide To Clojure
Hi. Thanks for the feedback. Please note that the document is a work-in-progress.

I didn't think to mention its roots on that page, given that it's one of the first things mentioned on the main clojure.org page.

Added a note about it being a Lisp dialect.

← PreviousPage 3 of 3