I get a lot of questions about how I bought my Kindle and what it cost to get it shipped to the Netherlands. So, for all those Dutchmen (and Dutchwomen) who are considering a Kindle, here’s a short how-to in Dutch:
Our petition aims to unify the voices of concerned Europeans, associations and companies, and calls on our politicians in Europe to stop patents on software with legislative clarifications.
The patent system is misused to restrain competition for the economical benefit of a few but fails to promote innovation. A software market environment is better off with no patents on software at all. Healthy competition forces market players to innovate.
European court decisions still accept in many cases the validity of the software patents granted by national patent offices and the European Patent Office (EPO) that is beyond democratic control. They not only continue to grant them, but also to lobby in favor of them. Despite the current deep crisis of the patent system, they are unable to reform and put at risk too many European businesses with their soft granting policy.
On 2005 the Commission appeared to be more supportive to the interests of major international conglomerates than of small and medium sized enterprises from Europe - who are a major driving force behind European innovation. The European Parliament rejected at the end the software patent directive, but has no rights for legislative initiatives.
We urge our legislators
to pass national legal clarifications to substantive patent law to rule out any software patent; to invalidate all granted claims on patents that can be infringed by software run on programmable apparatus; to also strive to propagate these rules to the European level, including the European Patent Convention. Sign the petition now!
For some time I have been eyeballing Sony’s e-reader in the local bookstore. I tried it a few times, but I didn’t like it - actually I had serious doubts about e-books in general because of the experience. Sony’s e-reader was not really easy to use with only one next-page button in a not-so-easy to access place. It also had a slow e-ink screen. It took a second to a second-and-a-half to show the next page. I didn’t like it and had serious doubts about buying any e-reader at all.
But, reading about all the “epic win”-stories of the Kindle by @johnnybusca I just had to give it a try - I bought one.
Okay, I’ve wanted to make a custom TextMate theme since I first installed the thing on my MacBook in 2006. Today I present you with ‘Epic’.
Grab the theme here: EpicBlue.tmTheme.zip (1.5k). Unzip it and open it with TextMate. That’s all. Enjoy!
There’s bit of a discussion between me and @ludooo about which word has the most significance when measuring the greatness of something.
I say epic is bigger than awesome. @ludooo says awesome is bigger than epic (he’s not right, of course).
Please help us decide!
Which is bigger? Awesome or Epic?(polling)
I just released version 0.4.0 of the IMDB Ruby Gem into the wild. There are only a few minor updates:
Changes in 0.4.0
Updates to the console 'imdb' utility Show the IMDB ID Show the full IMDB URL Installation or upgrade
$ sudo gem install imdb $ sudo gem update imdb Issues, source or contributions
You can find the code at github, as well as the issue tracker.
I haven’t seen a schedule yet, but I’ve been told by Mark that I’ll be speaking at Rails Underground this year.
My talk will be on the topic of Git. In about 45 minutes time I’ll show you all the basic git features you’ll need on a daily basis. Not only that, but I’ll also explain how git manages all those commits and branches so you can be on your way to become a git power user.
Git is quite an awesome version control system. Why? Because it’s lightning fast, even for large projects (among other reasons).
But, how do you use Git effectively for development on a daily basis? Let me explain to you.
With git you normally have a ‘master’ branch. This is also the branch you use to sync your code with other repositories. That is also the reason why you should never code in the ‘master’ branch.
Active Records provides callbacks, which is great is you want to perform extra business logic after (or before) saving, creating or destroying an instance of that model.
However, there are situations where you can easily fall into the trap of creating an infinite loop.
class Beer < ActiveRecord::Base def after_save x = some_magic_method(self) update_attribute(:my_attribute, x) end end The above will give you a nice infinite loop (which doesn’t scale). It’s possible to update your model, without calling the callbacks and without resorting to SQL.
With the release of IMDB 0.3.0, a command-line utility is included!
Why is this awesome for you? Basically, because you can now query IMDB and process the results with any of the great GNU tools available to you like grep.
Let me show you:
$ imdb Star Trek Searching for "Star Trek" 0060028 | Star Trek (1966) (TV series) 0796366 | Star Trek (2009) 0092455 | Star Trek: The Next Generation (1987) (TV series) 0112178 | Star Trek: Voyager (1995) (TV series) 0106145 | Star Trek: Deep Space Nine (1993) (TV series) 0117731 | Star Trek: First Contact (1996) 0084726 | Star Trek: The Wrath of Khan (1982) 0092007 | Star Trek IV: The Voyage Home (1986) 0079945 | Star Trek: The Motion Picture (1979) 0244365 | Enterprise (2001) (TV series) For clarity, only the ten first search results are shown.