3 ms·

Jekyll is too complicated. First, it requires a .yml config file, which is unused outside of the Ruby community. So this fails my "you shouldn't have to know wh

Jekyll is too complicated. First, it requires a .yml config file, which is unused outside of the Ruby community. So this fails my "you shouldn't have to know what language it is written in requirement". Personally I don't think there should be any config files at all, but if you're going to require a minimal one at least pick something universal and easy to understand, like an rc file or maybe json. Secondly it has the weird _ naming thing. Jekyll was clearly made for Ruby developers, which is fine I just think the world needs something much simpler than that.

eropple 13y ago
YAML is unused outside of the Ruby community? Wacky. I guess all my YAML configuration files in C++ and Java and .NET aren't a thing.
- MatthewPhillips 13y ago
  YAML is unused as a configuration file for end users. Or at least it should be.
  - reinhardt 13y ago
    I'm curious who are these end users that would be scared / turned off by yaml but are totally cool with markdown.
  - trvrprkr 13y ago
    YAML was crafted to be usable by most mere mortals. Whether or not it achieves that in practice is another issue ... but I think most people who find themselves using a static-site generator could find their way around a YAML config file just fine.
sneak 13y ago
YAML is a much better choice than the two you suggested. "rc file"s have no defined format, and json is a poorer choice than YAML. I loathe ruby and still use Jekyll because I never have to touch ruby code to use it. I use it specifically _because it is dead simple_. You're making stuff up.
- dasil003 13y ago
  YAML is okay when used in a simple manner such as for a basic configuration file, but it has a seriously fucked up spec with all kinds of landmines waiting to blow your legs off. If you aren't generating your YAML with @ruby_object.to_yaml then sooner or later something bad will happen to you. That's why I prefer TOML. I wish more projects would pick it up for config. https://github.com/mojombo/toml https://github.com/mojombo/toml
- MatthewPhillips 13y ago
  > "rc file"s have no defined format Why does that matter in this case?

eropple 13y ago

YAML is unused outside of the Ruby community? Wacky. I guess all my YAML configuration files in C++ and Java and .NET aren't a thing.

MatthewPhillips 13y ago
YAML is unused as a configuration file for end users. Or at least it should be.
- reinhardt 13y ago
  I'm curious who are these end users that would be scared / turned off by yaml but are totally cool with markdown.
- trvrprkr 13y ago
  YAML was crafted to be usable by most mere mortals. Whether or not it achieves that in practice is another issue ... but I think most people who find themselves using a static-site generator could find their way around a YAML config file just fine.

sneak 13y ago

YAML is a much better choice than the two you suggested. "rc file"s have no defined format, and json is a poorer choice than YAML. I loathe ruby and still use Jekyll because I never have to touch ruby code to use it. I use it specifically _because it is dead simple_. You're making stuff up.

dasil003 13y ago
YAML is okay when used in a simple manner such as for a basic configuration file, but it has a seriously fucked up spec with all kinds of landmines waiting to blow your legs off. If you aren't generating your YAML with @ruby_object.to_yaml then sooner or later something bad will happen to you. That's why I prefer TOML. I wish more projects would pick it up for config. https://github.com/mojombo/toml https://github.com/mojombo/toml
MatthewPhillips 13y ago
> "rc file"s have no defined format Why does that matter in this case?