A script to fix EDID problems on external monitors in macOS.
-
Connect only the problem display.
-
Create this directory structure (if it doesn't already exist):
diff --git a/Core/SVGParser.m b/Core/SVGParser.m | |
index a2a3106..7726901 100644 | |
--- a/Core/SVGParser.m | |
+++ b/Core/SVGParser.m | |
@@ -23,6 +23,7 @@ | |
#import "SVGPolylineElement.h" | |
#import "SVGRectElement.h" | |
#import "SVGTitleElement.h" | |
+#import "SVGTextElement.h" | |
var Renderer = function () { | |
var self = this | |
, requestAnimationFrame = window.requestAnimationFrame || | |
window.mozRequestAnimationFrame || | |
window.webkitRequestAnimationFrame || | |
window.msRequestAnimationFrame | |
this.queue = {} | |
requestAnimationFrame(function () { |
Today I had a brief debate on twitter about AMD vs CommonJS, https://twitter.com/TechWraith/status/441387541778808832. It's a debate worth having for sure. But I had to bail out of this one. The thing that annoyed me is that the first argument that people bring up to disquality AMD is "the syntax is too complex". I disagree with this. There are lots of reasons to prefer CommonJS over AMD, but the module authoring syntax is not a very good one. There was also a related statement that AMD authoring introduces more "cognitive overhead". This is absolutely true. But I don't consider this to be synonymous with "complexity" by any means.
So I thought I'd explore some comparable examples. Here's a simple one that was offered up by someone else in the thread. This was on twitter so I can forgive erring on the side of brevity.
AMD
define('myThing', ['some', 'deps'], function (some, deps) {
//my code
return myThing;
import org.zeromq.ZContext; | |
import org.zeromq.ZMQ; | |
import org.zeromq.ZMQ.Socket; | |
import zmq.io.mechanism.curve.Curve; | |
public class Security { | |
public static void main(String[] args) throws Exception { | |
Curve curve = new Curve(); | |
String[] serverKeys = curve.keypairZ85(); |