|// execute a callback when all images have loaded.|
|// needed because .load() doesn't work on cached images|
|// Modified with a two-pass approach to changing image|
|// src. First, the proxy imagedata is set, which leads|
|// to the first callback being triggered, which resets|
|// imagedata to the original src, which fires the final,|
|// user defined callback.|
|String imagePath = "img/desandro-avatar.jpg";|
|float res = 10; // resolution, dot density|
|float zoom = 3.0; // proportion to zoom image|
|boolean isAdditive = true; // true = RGB, false = CMY|
|float offsetAngle = 1; // affects dot pattern|
|0 = no patter|
|0.05 = slight offset|
|1 = slight offset|
I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.
From Require.js - Why AMD:
The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"
I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.
Thanks for getting in touch and for this tremendous invitation. I'm flattered and excited by the offer.
Representation matters to me. I'm curious: How are you aiming to build a diverse speaker line-up this year? Last years's conference only had 1 female and 1 person of color.
My inclusion rider: I'll join as a speaker if the line-up includes at least ██ women and ██ POC.
I realize putting together a diverse line-up is difficult. As a white male, I'd rather not take up a slot that could better feature someone not like me. Here's a list of people I can recommend.