Skip to content
This repository has been archived by the owner on Feb 7, 2020. It is now read-only.
botanicus edited this page Sep 13, 2010 · 16 revisions

This document is up to date for Rango 0.0.5 (current Git HEAD)

Why we use settings/ instead of config/

It’s kinda convention from Django, but most important is shell completion. In Rango you will probably run config.ru (as executable) pretty often and then it’s pretty tedious when you can’t complete it’s filename on the first time.

You are referring view as template? And action in controller as view? WTF?

Yes, it’s true. It’s Django terminology. Take a look at section Terminology for further explanation.

Seriously, what do you have against RubyGems?

Yeah, it’s true I’m not big fan of RubyGems, you can notice here in wiki. It’s because:

- they are rewriting Kernel#require. It’s fucking stupid idea, it should never happen! The only thing RubyGems should do at runtime is manipulation with $:
- it can’t help me to install packages locally. even if i can use -i parameter, it create some fucking rubygems structure which I don’t care about. I’d like just put vendor to $: and be done!
- people are using require "rubygems" which is bloody bad practice and it really piss me off. Well, it’s not fault of RubyGems, but still …
- And others, as it eats a lot of memory, it’s buggy and too magic, it’s overkill, the manipulation with $: is pretty strange and often works differently than I expect …

It’s basically reasons why I decided to write my own Stupid Package Manager

Clone this wiki locally