1,637 karma · joined February 22, 2008
Not really. What the British called "free trade" seemed pretty much like piracy to the Egyptians, the Indians and the Chinese they imposed it on.
And lest you think trade has become more civilized since the nineteenth century: I'm sure farmers in Jamaica are none too fond of having their livelyhood destroyed because their country imports cheap European dairy in the name of free trade. Which is just one example out of many.
Heck, even free trade loving Americans complain about their country getting swamped with cheap Chinese products.
As with most things, it's complicated.
The moral of the story being, I guess, that improvements in science and technology, do not necessarily go hand in hand with improvements in living standards.
But you do, of course, need to block some time every now and then to take a bird's eye view of where your projects stand.
This works for my, but YMMV of course.
I hacked up (and I do mean hacked up) two python scripts that add two bits of functionality that are essential for me:
- Timed tasks: add a date to a task and when that date rolls around, the task gets assigned top priority.
- Repeating tasks: add a human readable marker to a task that indicates it needs to be repeated every X days and every X days a copy of that task is assigned top priority. Another copy of the task is set to pop up in the set X number of days.
For me, these make the rather simple todo.txt the perfect todo list / note keeping setup. Unfortunately the todo.txt Android app doesn't work with my extensions so I have no use for it (I just look through the txt file in the Dropbox app if I need to see it on the go).
Gem issues aside, which Perl doesn't tend to have because CPAN is so rock solid, that was exactly the reason I didn't continue with Ruby when I checked it out, somewhat in depth, a few years ago: Ruby is Perl with OO done right, which is nice, but if you use Perl professionally, Ruby will not provide you with an alternative way of thinking the way Python does.
And with Python, BTW, it's a lot easier, probably because of all the batteries that are included.
but
to me it was news. So as far as I'm concerned the Polish government raising a stink about this, however much a symptom of Polish persecution complex it is, is a good thing. I learned something today (among others, after a few diversions on Wikpedia, about Wojzek the Bear - how cool is that?)
Tried this and gave it up. Your shell may be (somewhat) vi compatible but the applications you use mostly are not so you'll have to break out of the vi mindset at all sorts of inopportune moments. That, and modal editing, while perfectly alright for text editing, maps rather lousily to command line operations. You're much better off getting used to some basic Emacs-style key bindings that work consistently across a wide number of applications (including OS X text fields, IIRC).
If you want the health benefits of fruit, eat a piece of fruit.
Allow what you want to allow and disallow everything else.
That's not version control, that's an export function.
Scaling to Whitehouse.gov is not impressive at all. Like a 16 year-old's shared-host fanfiction site whitehouse.gov really is nothing more than a content site, albeit a very large one.
The problem is Drupal isn't content to simply be a CMS. It has to pretend to be a framework for developing web apps as well, and for that it's just plain terrible.
"Configuration lives in configuration tables" : the OP's point exactly. Configuration should live in a VCS
Bear in mind also that "configuration" van be so complex with Drupal it's often more along the lines of being "an application". A non-trivial view is hugely complicated and yet all its settings and code live in the database entirely, with no way to either back it up in a VCS or deploy it from a development environment to a live environment without manually copying the settings from one to the other.
Bolting a template engine on top of that makes no sense whatsoever.
A lot of things stink about this story, but this isn't one of them.