I am a declarative programmer

I have been always passionate about CSS.
It started in 1997, when I had the chance to taste for the first time CSS. Falling in love with its debilities, caring about its basis, and surfing impatient.

Over those who - pretending to be programmers and becoming, de facto, were just assemblers of eternal libraries - smiled condescendingly upon the routine thatme,  as a declarative programmer, did.

In fact, what I did like more about coding in CSS was not its simplicity, but the fact that It says nothing about the object itself, except some properties, leaving it untouched, unuttered.

If you ever field into the scopes of Logic and Set Theory, you might be aware of what Objects really mean. Something apart. This act of untouching its the most pure example of OOP programming. The object has its sense, and we show its reference through a digital representation.

Why do I write this, you might wonder ? Well, fair to say thatfew days ago, I stumbled upon an interesting article written by Mr. Jonathan Tran.

In his article, entitled "Every time you use CSS, you’re doing Aspect-Oriented Programming"; he brings some light in qualitative aspects of CSS as a programming language, or say, as an Aspect Oriented Language.

Here, an excerpt:

A group of CSS rules is essentially a function. (They even use the same curly-brace and semicolon syntax.) But with CSS, you actually don’t have to explicitly call a function to use it. Where you define the CSS rules (or function), you can use a selector instead of a class name which injects the behavior where you want it. The advantage is that you never have to explicitly reference the CSS rules where they’re used — i.e. you never have to explicitly call the function.

When you write the following CSS statement, you’re injecting the behavior of the rules into your entire site, without touching the code that’s already there.
Worth a read.
Newer Post Older Post Home