mkmcdonald

5 ms·

1.
by mkmcdonald 14y ago
Browser elitism benefits no one. The user is left insulted, and the developer strokes their own ego.
2.
by mkmcdonald 14y ago
> [...] the onus is on us as web developers to encourage [him/her] (in positive ways) to upgrade - through better web applications that require new features, better communicating the reasons for upgrading, etc. I disagree. The onus is o
3.
by mkmcdonald 14y ago
You've been misled into thinking that you need features X, Y and Z. Web pages can be functional without flashy new features. Your browser is your choice, and we as developers need to respect that.
4.
by mkmcdonald 14y ago
UserAgent sniffing and Graceful Degradation do not mesh. This sniffing in particular will fail for Opera 6-8, therefore excluding perfectly capable browsers by a very shallow criterion. The sniff serves no purpose, and is furthermore based
5.
by mkmcdonald 14y ago
Oddly enough, I was working on a similar problem earlier today. I've found that collecting the Text nodes and returning them in an Array is preferable. All it requires is some simple traversal. The developer (that should know what text goes
6.
by mkmcdonald 14y ago
> I find that naming things descriptively and an 80 character limit are at odds. I don't. I use descriptive names for functions and short, concise words for variables (sometimes clear abbreviations). > Another nit, Google Style guid
7.
by mkmcdonald 14y ago
I'm pleased that someone else favours a sensible line limit. I stick to 72 columns for width and 20 lines per function body. The result has been very concise code that's easy to follow. Only exceptional cases such as heavy recursion have el
8.
by mkmcdonald 14y ago
I much prefer "responsive" Web pages to "mobile" sites. Many "mobile" sites cram way too many flashy graphics and bloated scripts into the client; compound that with features that disable zooming, and you have a UI disaster. Finally, don't
9.
by mkmcdonald 14y ago
> Web technology is great for many things. Replicating a native app experience is not one of them. Yep. The client-side environment is far too unstable to build a "native app". There's a reason why monumental frameworks like ExtJS barel
10.
by mkmcdonald 14y ago
> If there is something out there that is better by a wide enough margin to justify giving up that established ecosystem, I'd love to hear about it. The ecosystem has plenty of imperfections, but I haven't come across anything yet that
11.
by mkmcdonald 14y ago
You do realize that IE 10 dropped conditional comments, right?
12.
by mkmcdonald 14y ago
I'll play the cynic here and try to diagnose why this is even being considered. jQuery is a very invasive API. Its goal is to steal all the work from the developer, and to "guarantee" what it deems to be "correct" input for a certain subset
13.
by mkmcdonald 14y ago
The browser versions here are never mentioned, which means this is "multi-browser", and not "cross-browser" (a large difference). Furthermore, the following snippets are simply false: > But Internet Explorer is the black sheep of the br
14.
by mkmcdonald 14y ago
Viewed in IE 4 (800px x 600px): http://i.imgur.com/9NZgc.png
15.
by mkmcdonald 14y ago
Please feel free to comment on the project or the Web site. I'll try to field every response.
16.
Show HN: Matt's DOM Utils—a modular HTML DOM library with wide browser support(fortybelow.ca)
6 points by mkmcdonald 14y ago|1 comments
17.
by mkmcdonald 14y ago
I guess my humble iPod Touch that sputters out on bloated sites like GitHub just isn't up to snuff. Try loading a page without script bloat and you'll see a noticeable difference.
18.
by mkmcdonald 14y ago
…which is a façade for the existing CSS engine. Developers clamoured for it (right or wrong), and it was implemented.
19.
by mkmcdonald 14y ago
A massive script such as jQuery does not belong on a mobile device, minified or not. Surely mobile developers would know that minimal script is best.
20.
by mkmcdonald 14y ago
The DOM API is clear enough that silly abstractions like "selector engines" are unnecessary. The C vs. Assembly argument is such a silly non-point; apples and artichokes.
21.
by mkmcdonald 14y ago
What the jQuery team either perceives or peddles as "modules" are simply split files; there's no encapsulation. All that's new is a shiny node.js builder. I am interested, though, that the team has finally noticed that optional code should
22.
by mkmcdonald 14y ago
> I have made every browser crash and become completely non-responsive, many times over. Chrome. Firefox. Opera. All of them. Now, this is mostly through JavaScript, when I do something stupid by manipulating the DOM the wrong way or so
23.
by mkmcdonald 14y ago
> Is [JavaScript] really an issue in 2012? I mean, people can hardly use Twitter.com itself without JS turned on. That's an indictment on Twitter's shoddy front-end code. The clean-up has already begun, but I don't know how much progres
24.
by mkmcdonald 14y ago
> Unless your customers are paranoid computer geeks, you should completely ignore users who disable JavaScript. Hypothetical: CDN X is having problems, and your scripts don't load. Errors pop up everywhere. Do you: a) realize that scrip
25.
by mkmcdonald 14y ago
Of course, the problem with jQuery is that you're required to use an all-or-none approach. Feel free to send me an e-mail (check my profile) if you have DOM questions.
26.
by mkmcdonald 14y ago
> This framework is written to embrace the DOM rather than fight it. And yet three separate libraries with DOM abstractions are required. Why should I trust your opinion of the DOM if you require so much third-party code?
27.
by mkmcdonald 14y ago
Requiring four separate APIs is a client-side dependency nightmare; requiring around 15k lines of uncompressed code is a disaster waiting to happen.
28.
by mkmcdonald 14y ago
[from the link] > Backbone UI depends on Backbone, Underscore, jQuery, and laconic. That's a disaster waiting to happen.
29.
by mkmcdonald 14y ago
Though the GitHub repo was posted, I would prefer visitors to go to the project site, which is linked in the repo description. I wanted GitHub to absorb most of the page hits since I'm only on shared hosting.
30.
Show HN: Matt's DOM Utils—an HTML DOM library with tangible browser support(github.com)
5 points by mkmcdonald 14y ago|1 comments

More ›