Seriously, what would you think about a language that is weakly typed and uses the same operator for concatenation and addition?
I think it’s insane.
Well, so much for my first encounter with JavaScript. And although I encountered way more problems (most of which were caused by my own stupidity, as usual), the fact that the plus sign (aka +) either adds or concatenates (based possibly on the current mood of the interpreter) struck me as the ultimate wtf.
Luckily, parseInt() comes to save the day. But still, why not rather use some other operator? I don’t really care which… just anything else, mmkay?
When you are creating a design in css, you will often run into various problems. The problem is that you often don’t really know where the problem is. That’s where the problem is.
I was using “border: 1px solid red;” to determine where certain element was. This has several drawbacks… first, it adds 1px on each side of the element, which can cause problems, then it is not too easy to work with (you have to manually add it to every element that you want to highlight).
I have found a much better way to debug css. First, they use outline instead of border (duh), then they make very smart use of wildcard characters, so that out-commenting one thing gets all the css boxes highlighted. Priceless.
Is it even possible that I forgot to advertize my new project on my own blog?
So… here it goes: I created tsumego collections.
Some people obviously like it, as I can see some traffic from sources like something.mail.yahoo.com (someone sending emails with a link to my page?). I wonder if I should write an ad into rgg or godiscussions.
Well, repeating informations that you can find there seems useless, suddenly I don’t really know what to write… hmpfh…
Anyway, big thanks to toxygen for transferring the go fonts from metafont to type1 (in pdf, metafont fonts get included as bitmaps, which sucks big time, and type1 fonts get included as vectors, which rocks).
