As you may know I am a kind of programming language geek. Despite the fact that every software developer uses one or more programming languages most developers do not care much about them. Some are interested in software design patterns, some care more about development methodologies, some are algorithm guys, some like diving deep into databases, many are just interested in technologies and frameworks and there are even those who do not have a real passion but work as developers because this is how they pay the bills. Well my passion are programming languages and while I do not have the opportunity to work professionally on a compiler or even a parser I try to follow the development of popular programming languages and enjoy reading the motivation for language design decisions and compiler implementation decisions that language developers post online. I also like digging in programming language history...

   To fill in the vacuum of technical articles on this no-blog I decided to put in this article about small but interesting problem with LINQ to Objects performance that a guy posted on a developers' forum a while ago. Fear not for I am working on more serious technical article but I am doing it slowly like a glacier moving...

   Happy programmers' day to all programmers, IDE operators and PHP writers. We know that we and not those fancy business guys do the work that makes the world tick. Sometimes we are scared to death by this thought because we have seen it from the inside and we know how fragile our systems are but I am sure that if the giants could see us they would be proud.

   The day of the programmer is getting momentum and this year it has been accepted as an official professional holiday in Russia. Soon in your country!

   Abandon all hope you who read this, for this is where you will find how simple programming problems can turn out to be really hard. For our current project we wanted to implement a seemingly simple functionality – when the user posts a comment via a text area new lines should be converted to "<br />" in the resulting HTML, HTML tags should be encoded so our project would not be vulnerable to script injections and users would be able to post HTML in the comments and finally URLs should be detected and converted to links. Sounds simple? As soon as I was charged with this task I remembered reading a post by the wise Jeff Atwood on his famous blog Coding Horror about how hard URLs can be. The post deals with the issue of a closing parenthesis at the end of a URL and I immediately decided that I was going to ignore this issue like most systems do. However while working on this task I hit many more walls...

   Ever since I asked myself and tried to find out why people tend to hate JavaScript I have been loving the language. My research revealed that JavaScript has many cool features from the very beginning. The reason people are hating it are the sucky browsers. Every browser has its own implementation which causes problems. What is more JavaScript's main use is to deal with the dreaded DOM. Luckily in recent years people seem to discover the power of JavaScript and appreciate the fact that the language is very well suited for the untyped nature of the DOM. As you probably know I do not believe that the Web should be rich and made to resemble desktop applications. Unfortunately this means that I did not have a chance to write complicated JavaScript and use the language to its full potential. The stuff I did was really simple validation and calculations like adding two numbers. However our current project is more user-centric and requires rich UI so it seems like the time has come for me to write some elite JavaScript...