mkmcdonald

12 ms·

61.
by mkmcdonald 14y ago
Opera has long been the most innovative and standards-compliant browser available. Google and Mozilla may have bigger teams, but the most innovation is still coming out of Norway.
62.
by mkmcdonald 14y ago
Here's a better idea, developers: stop using vendor prefixes. Use the W3C-defined property only. If it isn't standardized yet (i.e. doesn't work), then don't use it. Stop opening your Christmas presents at Easter. (sorry; typed from a mobil
63.
by mkmcdonald 14y ago
That may be, but it's poison for host objects. In older IE and Opera builds, `"[object Object]"` comes up often, even for host methods. This is because there is no defined standard for `toString` results of host objects.
64.
by mkmcdonald 14y ago
Your API will explode violently in IE < 8 || Quirks. This is because of gratuitous use of `setAttribute` along with `Array.prototype.slice.call` (dirty hack)[0]. IE < 8 || Quirks already treats HTML attributes and DOM properties ide
65.
by mkmcdonald 15y ago
> I haven’t found a use for the Properties section yet It displays DOM properties and their current state. That's pretty important to any web developer.
66.
by mkmcdonald 15y ago
JSBin has without a doubt the most annoying and invasive coding interface I've ever used. I find myself often copy/pasting directly from a text editor to avoid the stupid auto-formatting. That said, its easy customization and lack of script
67.
by mkmcdonald 15y ago
CoffeeScript is not a language. It's a compiler to make JavaScript look like Ruby. Just like the superfluous idea of "semicolons are optional because of a design error", it's personal style. Be sure not to whine, though, when the abstractio
68.
by mkmcdonald 15y ago
> If you've got JavaScript disabled, no one is interested in catering to you. I'd hope an amicable, intelligent developer would. Scripts don't always load. Errors happen. > I understand the myriad justifications for disabling JavaSc
69.
by mkmcdonald 15y ago
> comp.lang.javascript was a very inhospitable place. To novices and the weak of heart? Sure. I've yet to find a greater source of technical depth regarding JavaScript. > David Mark's touted his "My Library" as the holy grail of lib
70.
by mkmcdonald 15y ago
> This might go without saying, but simply knowing a JavaScript library isn’t sufficient any more. I’m not saying you need to know how to implement all the features of a library in plain JavaScript, but you should know when a library is
71.
by mkmcdonald 15y ago
So, has anyone actually read the code? I'd guess that these guys have spent a maximum of one month writing JavaScript. It's a giant mess. All flash, no substance.
72.
by mkmcdonald 15y ago
The problem here is you're simply comparing applies to oranges. Internet Explorer 6 was released in 2001. For its time, it was a very nice product. IE 7 may have faltered a bit, but IE 8 was strong. Of course IE versions 6-8 are going to sm
73.
by mkmcdonald 15y ago
s/browsers/platforms/. Don't lump all browser versions into one pile. I can grasp what you're referring to. Bleeding-edge features are tough to support in large part because of Internet Explorer's slow release cycle. However, the decision h
74.
by mkmcdonald 15y ago
It sure does. Developers seem content to keep moving the goalposts and treating "inferior" users as slime.
75.
by mkmcdonald 15y ago
These "developers" would have saved company X a fair bit of money by actually researching IE. Microsoft has graciously provided a massive amount of documentation covering most Internet Explorer variants and their quirks (via MSDN)[0]. One o
76.
by mkmcdonald 15y ago
Twitter is a perfect example of a "thick client". It's slow, bloated and buggy. When one typo is made in the JavaScript "bundle", the whole site implodes, leaving the user with simply the navigation bar. When JavaScript is turned off, mos
77.
by mkmcdonald 15y ago
GrooveShark also overrides the default context (right-click) menu. That doesn't mean that it's a good idea.
78.
by mkmcdonald 15y ago
In my years as a Flash developer, I built many custom scrollbars: each more painstaking than the last. Why build something guaranteed to be lower in quality than something else that's been in place for years? Let the professionals innovate.
79.
by mkmcdonald 15y ago
This should a warning to all over-enthusiastic designers/developers on the Internet. Please stop creating custom scrollbars. Web browsers already provide wonderful scrollbars.
80.
by mkmcdonald 15y ago
> Clearly your opinions differ from the majority of the web community. > Why do you think we now have document.querySelectorAll? This is called "argumentum ad populum" (appeal to popularity). The advent of jQuery caused clueless "de
81.
by mkmcdonald 15y ago
> Are you testing your code on ie6 running on a 486? I test all the way back to IE 5.5. Try browsing a site with a heavy jQuery dependency in IE 5.5 (StackOverflow is a nice example). Those sites tend to implode. > Those 'Frankenst
82.
by mkmcdonald 15y ago
The DOM is not CSS. Please realize this. Your monstrosity of a query illustrates a continued ignorance of the DOM. "event normalization" is another "nice-to-have" that isn't necessary. DOM 0 event handlers (e.g. `node.onclick`) have worked
83.
by mkmcdonald 15y ago
This post is moving towards the right direction, but not far enough I'm afraid. Selectors are completely unnecessary. Class "selectors" are tar pits as they have to search every single node in the current context (usually the entire DOM