nefarioustim

8 ms·

31.
Judging CSS/Spotting Bad Code(css-tricks.com)
1 points by nefarioustim 14y ago|0 comments
32.
Mom Arrested For Hacking School Computers to Change Kids' Grades(abcnews.go.com)
9 points by nefarioustim 14y ago|1 comments
33.
Alleged UK File-Sharers Better Armed and Ready To Fight Ben Dover(torrentfreak.com)
9 points by nefarioustim 14y ago|1 comments
34.
Matt Mills (TED Talk): Image recognition that triggers augmented reality(youtube.com)
3 points by nefarioustim 14y ago|1 comments
35.
Crossdressing, Compression and Colliders: The First Photo on the Web(motherboard.vice.com)
3 points by nefarioustim 14y ago|0 comments
36.
Why showing your face at work shouldn't matter(blog.mikepearce.net)
3 points by nefarioustim 14y ago|0 comments
37.
Handy UI toolkit for just $8(uiparade.com)
5 points by nefarioustim 15y ago|0 comments
38.
New Google PageSpeed(developers.google.com)
3 points by nefarioustim 15y ago|1 comments
39.
A realtime charity thermometer widget in HTML, CSS, JS, and Pusher(blog.pusher.com)
2 points by nefarioustim 15y ago|0 comments
40.
ChuckNorrisException(github.com)
3 points by nefarioustim 15y ago|0 comments
41.
Jwerty - Awesome handling of keyboard events in JS(keithcirkel.co.uk)
2 points by nefarioustim 15y ago|0 comments
42.
by nefarioustim 15y ago
Doesn't work in Chrome 14 or Firefox 6 on my Snow Leopard MBP; just crashes.
43.
Designing Fun(alistapart.com)
5 points by nefarioustim 15y ago|0 comments
44.
by nefarioustim 15y ago
This is a great article. A good portion of my day to day work involves handling JS memory leaks, due to the growing reliance on JS for behaviours, interactions, and application logic (sometimes an over-reliance, IMHO). It's sad that most of
45.
by nefarioustim 15y ago
Your point about pragmatism is valid, but in the way that spjwebster speaks about above. JavaScript is just too fragile to depend on for a truly robust application or website. Lack of JavaScript isn't just about the minor percentage of user
46.
by nefarioustim 15y ago
If only one could rely on JavaScript actually running on a client machine.
47.
by nefarioustim 15y ago
Obviously this doesn't make you a _bad_ web developer, as such, but I'd question your rationalisation here. What capability and resources do you need that you haven't already adopted for cross browser support elsewhere?