Snark: But why don’t they just contribute to WebP?
Short and to-the-point post on the Adobe Web Platform blog about a cool new proposed CSS3 property: text-align-last. Finally, FINALLY, we can justify the last line of a paragraph tag.
My god, it’s full of stars.
A reasonable, if unscientific, look at the performance of various common CSS methods, comparing things like Attribute .vs. Class-based selectors, box-sizing resets, floats .vs. flexbox .vs. inline-block, and a lot more.
Love that someone took the time to do this so I don’t have to.
Slick technique that is worth looking into for many applications. As someone who deals with a lot of form inputs both as a user and a designer, there are some useful ideas here.
So, we just launched an update to the Structure Sensor homepage, and it features some neat HTML5 / CSS3 tech. I’m pretty happy with it. It required me to learn a few things, which I’ll hopefully have time to write about here soon.
A very well put-together interactive tutorial and examination of drawing using the HTML
canvas tag. Even if you’re pretty up on things, you might learn something new.
A super simple, but super useful, little service that returns various HTTP status codes based the URL called. Helpful tool for testing how your app responds to every HTTP status.
Looks like a handy little tool if you’re in the website business, and it even has a pithy one-line description:
In short, it’s nslookup, if nslookup queried over 1500 servers and collated their results.
Bonus points for being open source and installable via
Imagine you were choosing between PNG or JPEG for an image you wanted to serve. You would simply pick the right format for that use case because web servers support either, you need only drop the file in. That is exactly what Harp does with modern web languages. Want to use Stylus? Just name your file with a .styl extension. Prefer LESS’ syntax? Just drop in the LESS source files and go to work. Or use a combination of both, Harp doesn’t care. Harp knows to compile and serve main.styl when main.css is requested, OR main.less if that file exists instead. It’s that simple.
That’s a hell of a pitch, and it’s only about 1/3 of the whole thing. Read the whole post.
Yet another HTML/CSS/JS framework, but built so that the classes are understandable in english. It’ll create some HTML bloat, but it has a certain Applescript-y charm to it.
The site is pretty snazzy, too. Very readable, very smooth.
Let’s see if they can deliver.
Works in Chrome, pretty cool. A little verbose for my tastes but definitely better than the default.
Been looking for something like this for YEARS now. Hope it’s good.
All too often, technology companies have raced against each other to build restrictive tangleware that suits Hollywood’s whims, selling out their users in the process. But open Web standards are an antidote to that dynamic, and it would be a terrible mistake for the Web community to leave the door open for Hollywood’s gangrenous anti-technology culture to infect W3C standards. It would undermine the very purposes for which HTML5 exists: to build an open-ecosystem alternatives to all the functionality that is missing in previous web standards, without the problems of device limitations, platform incompatibility, and non-transparency that were created by platforms like Flash. HTML5 was supposed to be better than Flash, and excluding DRM is exactly what would make it better.
Adding DRM to HTML5 would absolutely enable new web apps to be made, but guess what: The kind of apps it would enable are across-the-board worse apps than the apps that we already build without DRM. A vote for DRM is a vote for worse in every possible way.