Archive for Web Libraries

Why it’s not “Just Build a Website”

Hey you know computers right? Can you build me a Website/App?

So how many of the above do you know?
These are all things I worked/work with every day and power much of what you see on the internet.
And how many have you not heard of?
And that is just the top level Web Client side frameworks.
That does not include the working knowledge i need on all of the following just to do my job.

  • Programming Languages
  • Networking and Domains and Protocols
  • Web Servers
  • Web Service Architectures
  • Web Service frameworks
  • Server Integrations and API
  • Operating Systems
  • Hosting Services
  • Software As A Service
  • Platform As A Service
  • Virtual Machines and Integrations
  • MicroServices
  • Database Managment
  • Data Architecture
  • Data Clients
  • Mobile Frameworks
  • Mobile-Web Hybrid Frameworks
  • Development Platforms and IDEs
  • Development methodologies
  • Styling Frameworks
  • Testing Frameworks
  • Deployment Frameworks
  • Design Tools
  • Design Methodologies
  • User Experience and Behavior
  • SEO and Marketing
  • Product Distribution
  • Finances
  • Security and Encryption
  • High-level Math and Logic

Each one of those has a chart like above for them.

But some of those things on that chart are out of date!?


JavaScript in 2017 – Libraries and Frameworks

However, Angular was designed from the beginning to support Web Components. They even ship their own Shadow DOM emulation. In other words, when Web Components are ready, only Angular is specifically designed to use them. This is another reason that we are building many of our own components on Angular’s infrastructure, so that when Web Components are ready, our own leap won’t be nearly as far.

Source: JavaScript in 2017 – Libraries and Frameworks -Telerik Developer Network

Why I’m (Still) Against SASS & LESS

I refuse to use any preprocessors. 

I’ve been creating sites since before CSS was in existence, so I’ve seen a lot of new trends, frameworks and the like come and go in that time. Not all of them have been bad, but a lot of them, mainly frameworks, have only made HTML or CSS even more complicated.

Let me tell you a secret: CSS is NOT a programming language. The beauty of CSS is that it’s so easy for almost any to pick up quickly and read (though it’s very difficult to actually use it properly for the big stuff). Adding a preprocessor on top just needlessly complicates and adds yet another piece of bloat to an already over bloated workflow.

Source: Why I’m (Still) Against SASS & LESS 2D template demonstration is similar to Twitter Bootstrap, but instead of being a framework for building websites, it’s a framework for building apps in 2D (like normal apps) or 3D. The big thing solves is PERFORMANCE for web app development.

via 2D template demonstration – YouTube.

some very cool things happening here and very curious to see what comes out of this.. they have the chops to pull it off… some FAQ answered here


Snap.svg is a brand new JavaScript library for working with SVG. Snap provides web developers with a clean, streamlined, intuitive, and powerful API for animating and manipulating both existing SVG content, and SVG content generated with Snap.

Currently, the most popular library for working with SVG is Raphaël. One of the primary reasons Raphaël became the de facto standard is that it supports browsers all the way back to IE 6. However, supporting so many browsers means only being able to implement a common subset of SVG features. Snap was written entirely from scratch by the author of Raphaël (Dmitry Baranovskiy), and is designed specifically for modern browsers (IE9 and up, Safari, Chrome, Firefox, and Opera). Targeting more modern browsers means that Snap can support features like masking, clipping, patterns, full gradients, groups, and more.

via Snap.svg – Why Snap.