Skip to content

Instantly share code, notes, and snippets.

@Wilto
Wilto / gist:5239409
Last active December 15, 2015 09:38

I talked it over with the BDConf folks, and we’ve put aside one pass to Breaking Development Orlando for someone that needs it.

I didn’t have the easiest time when I was just starting out in this gig, and I sure as hell couldn’t afford to go to any conferences. The only way I ended up in a job with an honest-to-God desk is through tons of help from the people I met along the way. So, fair’s fair, yeah? If you’re in a place where you can’t swing the cost of the ticket, let me know what the deal is and we’ll try to figure something out.

BDConf is a great show. Come learn a few things, meet some people, and land yourself a gig. Buy me a beer there; we’ll call it even.

I’m [email protected].

@Wilto
Wilto / gist:5598218
Created May 17, 2013 10:10
Grunticon.
module.exports = function(grunt) {
// Grunticon
grunt.loadNpmTasks('grunt-grunticon');
// Project configuration.
grunt.initConfig({
[ … ]
grunticon: {
options: {
src: "_tmpl/_css/_img-source/global/",

“Responsive”:

<?xml version="1.0" encoding="utf-8"?>
<!-- Generator: Adobe Illustrator 17.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg"
	xmlns:xlink="http://www.w3.org/1999/xlink" 
	x="0px" y="0px"
	viewBox="0 0 21 8" 
	enable-background="new 0 0 21 8"
@Wilto
Wilto / chili.md
Last active August 29, 2015 13:55
Chili.
  • 2 Tbsp vegetable oil
  • Red bell pepper, diced
  • Yellow bell pepper, diced
  • 4 cloves garlic, minced
  • 2 yellow onions, minced
  • 24 oz. can tomatoes, diced (Pastine 4-LYFE)
  • 24 oz. can tomatoes, crushed (See above)
  • 1 can black beans, drained/rinsed
  • 1 can kidney beans, drained/rinsed
  • 1 can vegetable stock

(Int. Android 2.3 HQ )

“This browser is… it is hot garbage. We have done the worst possible job. We are the worst.”

“Listen, whatever—where we at on removing source elements in weird contexts?”

“Wh… what? Like nothing works—there are so many bugs—why would we spend time on—”

“WE MUST REMOVE SOURCE ELEMENTS FROM WEIRD PARENT CONTEXTS NO MATTER WHAT.”

method: getCandidatesFromSourceSet (0, 18, 18)

images/pic-medium.png is parsed correctly

images/pic-medium.png 1x is parsed correctly

images/pic-medium.png, images/pic-medium-2x.png 2x is parsed correctly

images/pic-medium.png 1x, images/pic-medium-2x.png 2x is parsed correctly

@Wilto
Wilto / thanks.md
Last active August 29, 2015 14:02

Let’s leave aside, for now, the fact that you’ve changed web standards. You’ve been a participant in the first time—in the history of the web, far as I know—that the web development community has taken a feature from an initial proposal to the funding of an honest-to-God native implementation.

Instead, I want you to focus on this: say only ten developers use a native responsive images solution to reduce the weight of just one page apeice by only 500kb, and each of those pages has a barely-significant 5,000 hits per month: those users have been saved almost 24GB of data. A thousand pages saving 500kb apeice, and we’ve saved users an entire terabyte in a month. Now expand that to the entire industry: every web developer; every hit on every page that would otherwise carry with it a huge, wasteful image request, saving megabytes at a time. To those users, the only change is that the web is faster, less expensive, more accessible. For those users, the web is just better.

In helping make the picture element