And We’re In Business!

By  on  

The blog has been successfully moved to the new domain and theme. Took longer than I wanted, but doesn't everything?

A few of the roadblocks I ran into include:

  • MooTools & Syntax Highlighter didn't cooperate as I hoped. The issue was with Syntax Highlighter, but I've iron out this issue.
  • Problems upgrading WordPress from 2.2 to 2.3. I've stayed with 2.2 for now.
  • WordPress' list-driven navigation. A lot of WordPress revolves around lists, which in most cases is good, but why use UL/OL/LI if you can simply use "display:block;" CSS?

In any event, the new blog is up and I'd love to hear your thoughts on the design and how I can improve the website!

Recent Features

  • By
    Interview with a Pornhub Web Developer

    Regardless of your stance on pornography, it would be impossible to deny the massive impact the adult website industry has had on pushing the web forward. From pushing the browser's video limits to pushing ads through WebSocket so ad blockers don't detect them, you have...

  • By
    CSS Animations Between Media Queries

    CSS animations are right up there with sliced bread. CSS animations are efficient because they can be hardware accelerated, they require no JavaScript overhead, and they are composed of very little CSS code. Quite often we add CSS transforms to elements via CSS during...

Incredible Demos

  • By
    Fix Anchor URLs Using MooTools 1.2

    The administrative control panel I build for my customers features FCKEditor, a powerful WYSIWYG editor that allows the customer to add links, bold text, create ordered lists, and so on. I provide training and documentation to the customers but many times they simply forget to...

  • By
    Camera and Video Control with HTML5

    Client-side APIs on mobile and desktop devices are quickly providing the same APIs.  Of course our mobile devices got access to some of these APIs first, but those APIs are slowly making their way to the desktop.  One of those APIs is the getUserMedia API...

Discussion

    Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!