stutter

6 ms·

1.
A node.js library for Mandrill...that works(github.com)
5 points by stutter 14y ago|0 comments
2.
by stutter 14y ago
I agree that saying it's "too hard" is a cop out. But Microsoft doesn't provide the proper tools, that's not a cop out. I don't want to support IE6, but I know that if I don't put effort into it - customers will complain. When customers
3.
by stutter 14y ago
Point conceded. Though, certainly a +1 for choosing Mac as your primarily development environment; as it can run all the other operating systems you'd care about (:
4.
by stutter 14y ago
> Which they do, they've been offering complete VM images with various combinations of Windows and IE for some time, the current offering is XP + IE6, Vista + IE7, Win7 + IE8 and Win7 + IE9 I've used the IEVMs project on github to insta
5.
by stutter 14y ago
Macs run Windows, Windows don't run OSX. This is why I develop on Mac; it's more versatile. (For web development)
6.
by stutter 14y ago
You don't have comments on your blog, so I'll comment here: IE testing is "hard" on a Mac because of the vm requirement, yes. However, that's not even my main issue. If Microsoft facilitated having VMs of each windows installation + brows
7.
by stutter 15y ago
Boxee Box
8.
by stutter 15y ago
Profiling PHP with PHP is kind of humorous, I'll concede. But it can certainly help alert you to slow-running pages, queries, and steps. Which should at least give you a starting point or prompt you to dive deeper with a stronger/more rob
9.
by stutter 15y ago
I also use XDebug + kcachegrind, but I wouldn't consider that a 'quick' way to identify slow-ups (mainly because of how my set-up looks). I'll agree that manually creating steps around code you suspect to be an issue could be a pain in the
10.
by stutter 15y ago
Both are valid points (editing code in order to profile), and you're absolutely right regarding blindly adding profiling wrappers "just because." You can certainly do that, but it's likely to be far too granular in a lot of places. The pr
11.
by stutter 15y ago
Though according to the manual short_open_tag is true by default, this is a valid point. The safer way to write this would have been to open all tags with <?php instead of <?. I'll update that. thanks for the feedback!
12.
by stutter 15y ago
as the other two stated, the sleep calls just simulate actual code running, so the profiler produces some output other than 0ms for everything.
13.
PHP Profiler to optimize & speed up your applications(github.com)
56 points by stutter 15y ago|20 comments