See Ruby one point nine.
HN user
svoroval
It is written here: https://github.com/slash-lang/slash
I don't understand how you switch from “wow, guy wrote a language I can use in my projects” to “why should I switch from PHP, I need a more compelling reason” and stuff.
And yeah, PHP sucks. And your career path is something you should not think about at all.
Wiki doesn’t download with your repo. I think that’s the reason.
I don’t know. I just don’t feel approriate to use Wiki for projects that are smaller than 6000 LOC, I don’t know.
Maybe you’re right.
Because it is not designed for this purpose?
Sure! You’ve got the idea.
Not really far-fetched. Look at Sinatra README for example: https://github.com/sinatra/sinatra
There are 11 versions of Sinatra’s README which don’t share any general templates. They should be manually edited after each release. This is kind of thing that needs automatization.
Plus, it is much easier to inject badges by a mixin, not by copypasting and manually changing some elements from your old READMEs.
Zero configuration (no config.rb), a lot of preprocessors besides Sass/Compass supported (like LESS, HAML, Slim, CoffeeScript and so on).
Not really.
Just use --compile flag. Here is the issue: https://github.com/somu/sword/issues/7
Yep, fixed now. Thanks.
Yep, just a typo.
Thank you, will fix it.
Got it! Open an issue and describe your thoughts? Will think to add it in the next release.
It is silly and wasteful. It is just possible.
Hey, I am the Sword author. Harp development and Sword development have begun almost simultaneously. You should stick with Harp if you use typical NodeJS tools for templating (like Handlebars and Stylus), and use Sword if you prefer Ruby ones.