rgrove

34 ms·

151.
by rgrove 17y ago
Not really sure why this is newsworthy. It's a very common thing in the tech industry, and Yahoo! has been strongly encouraging employees to take time off during the holidays for years. The only difference this year is that the time off is
152.
by rgrove 17y ago
That takes care of JSMin, but what about JSLint?
153.
by rgrove 17y ago
The point isn't whether it's right or wrong. It's that Google made a rule (no JSMin/JSLint on Google Code), then (unintentionally) broke it themselves with Etherpad and a few other projects, and must now deal with the consequences. To their
154.
by rgrove 17y ago
Much better, thanks.
155.
by rgrove 17y ago
This headline is misleading taken out of context, and is not the headline of the linked blog post (I'm the author). JSMin isn't "banned software", it's just not allowed on Google Code.
156.
by rgrove 17y ago
Your question presupposes that the search results from a given search engine tend to remain static over time, but they're actually in constant flux. All the major search engines make frequent tweaks (sometimes small, sometimes large) to the
157.
by rgrove 17y ago
The tech press hasn't done a very good job of being clear about the details of the deal, which is unfortunate, since it's left many people with an inaccurate picture of what it entails. A modern search "engine" is really many, many engines.
158.
by rgrove 17y ago
Didn't mean to scold; was just explaining my terseness. :)
159.
by rgrove 17y ago
I do. That's a pretty broad (and off-topic) question. I can't speak for everyone at the company, but if I had to sum up how I personally feel: hopeful.
160.
by rgrove 17y ago
Yahoo! Search had lockable SafeSearch settings long before either DDG or Google (although, like Google's new implementation, it's cookie-based).
161.
by rgrove 17y ago
YUI Compressor is not a simple obfuscator. It does quite a few safe optimizations, but it doesn't do anything that could break your code.
162.
by rgrove 17y ago
IE8's IE7 compatibility mode is not perfect, especially when it comes to JavaScript. If it really matters that your site work in IE7, you need to actually test it in IE7.
163.
by rgrove 17y ago
IETester can't be trusted. It's prone to strange bugs that don't appear in the standalone versions of IE.
164.
by rgrove 17y ago
Are there any screen readers that support Flex content? (that's not rhetorical; if anyone knows of one, I'd like to know)
165.
by rgrove 17y ago
Interesting. I pointed my iPhone 3GS at my (pretty neat) digital watch and tapped the shutter release the instant I saw the seconds display change. I did this 5 times. Each time, the seconds display in the photo was from just before it ch
166.
by rgrove 17y ago
Be careful with Mozy. If you haven't done a test restore, I strongly recommend you try one now. The Mozy restore process is extremely broken and has been for years. You can read about my horrible experience with Mozy (and the horrible exper
167.
by rgrove 17y ago
CrashPlan. I've got it backing up all my machines to a Drobo on my LAN as well as remotely to CrashPlan's servers, encrypted before it crosses the wire, and it costs me $5 a month. Been using it for years and have done several very large re
168.
by rgrove 17y ago
There's no need to change JSON. This is a non-issue if you adhere to a few basic security practices: 1. Use crumbs to protect against XSRF. 2. Responses that should not be cached by proxies should have a "Cache-Control: private" header. The