12 and a half years online
2012
<abbr title="Mar 05, 2012 - Mar 08, 2018 (vallentinsource.com) Feb 03, 2017 (vallentin.io) Mar 08, 2019 (vallentin.dev)">2012\r\n – <span id="year">{{ self::year() }} |\r\n {# <a href="//vallentin.dev">Vallentin -#}\r\n <a href="/">Christian Vallentin\r\n | All Rights Reserved\r\n
\r\n
"; writer.write_fmt(::core::fmt::Arguments::new_v1(&["<div class="footer">\r\n
Copyright ©\r\n <abbr title="Mar 05, 2012 - Mar 08, 2018 (vallentinsource.com) Feb 03, 2017 (vallentin.io) Mar 08, 2019 (vallentin.dev)">2012\r\n – <span id="year">", " |\r\n <a href="/">Christian Vallentin\r\n | All Rights Reserved\r\n
\r\n
"]
March 05, 2012
Happy Birthday - 12.5 Years Online
I have a hard time recognizing webdev anymore...
I know, rough way to start a celebration
Today, my website have been online for 12.5 years.
In Denmark being married for this duration is referred to as "Copper Anniversary", it's also the half-life of tritium.
Overall, I've been doing web dev for a lot longer than 12.5 years. Even the evolution of this website, have gone through many designs, but more importantly many different backends. Over the years it went from complex to simple.
The main difference today, is that common front-end technologies are a lot different, than what I primarily consider web development.
So where do we start?
First of all, one thing that still stands true, is that 12.5 years ago I believed in progressive enhancement of websites, and I still do today.
In short, progressive enhancement implies that CSS and JavaScript are optional, and should only be additive to the experience. They shouldn't be a requirement to consume the underlying data.
The sad truth is however, that a large majority of blog websites, require excessive amounts of JavaScript. Disable JavaScript and you're unable to even read the content of a post.
There's obviously exceptions, e.g. if the services (websites) themselves provide functionality, and isn't just providing data to consume. In short, consider YouTube being able to upload videos, commenting, liking videos, etc. in an interactive manner (without reloading the page), that in itself requires JavaScript. However, I firmly believe (and practice) that being being able to read a blog post, should never require JavaScript (on the client-side).
If the service (website) itself
If the functionality of the service (website) itself, requires dealing with some custom logic, then obviously JavaScript is required. It would be
If the functionality of the service (website) itself requires JavaScript
, e.g. GitHub, Stack Overflow, or YouTube
I've always believed that websites progressive enhancement
progressive enhancement
TODO: Add screenshot how THIS post looks without JavaScript TODO: Add screenshot how THIS post looks without CSS nor JavaScript
TODO: Include screenshots over time
TODO: Forward or backwards?
See all posts