mkozlows

37 ms·

421.
by mkozlows 11y ago
Yeah, it'd be a lot more interesting to see results for Linux and Windows, too. The test that'd be the most interesting to me is actually Chrome on ChromeOS vs. Chrome and Firefox on Linux on the same hardware. My subjective impre
422.
by mkozlows 11y ago
Tip: If you want honest answers about how long it took, ask them after they've been hired and working there for a few weeks. Otherwise they will absolutely lie. "That? Oh, it was no big, probably 20-30 minutes."
423.
by mkozlows 11y ago
SQL is actually a pretty terrible syntax, though. Relational algebra is beautiful and elegant, but SQL is a dated, '70s-y syntax on top of that.
424.
by mkozlows 11y ago
Higher-order functions do the same thing.
425.
by mkozlows 11y ago
I've gotta say, I'm somewhat sympathetic to the idea that we'd be better served by a period of focusing on stability and performance over new features... but talking about the IE6 stagnation era as a good thing? Yeah, no, tha
426.
by mkozlows 11y ago
That is a bad definition of "active," particularly considering that the original selling point of G+ relative to Facebook was its privacy controls (circles). I know many people who post to G+, only a few of whom do so publicly.
427.
by mkozlows 11y ago
I agree with this to some extent, but it can be ameliorated a lot with smaller and more frequent PRs. If your PR is enormous and represents a week's worth of work and you end up having to respond to 20 comments, it's going to be a
428.
by mkozlows 11y ago
To make this clear: Productivity is not declining. The growth of productivity is slower than it was in the past, but it's still growing. The first graph here is annualized growth rates, and you'll note they're all positive:
429.
by mkozlows 11y ago
Facebook has, and has long had, a real name policy. If you want a reason why Facebook succeeded and G+ didn't, you'll need something that's actually different between them.
430.
by mkozlows 11y ago
Google Reader never had many users. Feedly claims to have captured 80% of the Reader userbase when it shut down, and they have 15 million users. That is incredibly small by the standards of social networks, much smaller than even the pessi
431.
by mkozlows 11y ago
G+ has not required a real name for a while now. The problem with a profile that spans unrelated services is that your persona on one shouldn't necessarily be tied to your persona on another; Google Accounts with different public-facin
432.
by mkozlows 11y ago
They haven't thrown it away. It's still a shared Google Account For Everything. The distinction they're making now is that they're no longer requiring that account to be tied to a "G+ sharing stream" in a publi
433.
by mkozlows 11y ago
I agree with the VSS-hate, of course, but it's unfair to say that TFS is just as bad. TFS is annoyingly difficult to administer, but it's a zillion times more robust than VSS, and compares favorably to Subversion or Perforce (and
434.
by mkozlows 11y ago
Counter-argument: Old apps, of the sort that are written in COBOL, are often ones that there are good reasons to replace anyway. The reason they tend to still exist, where they do still exist, is that businesses don't want to dedicate
435.
by mkozlows 11y ago
The article is maybe overblown, but I think there's a good point there. A lot of functionality is one-off stuff that doesn't need to be re-used and won't be, and so trying to come up with a name for a little chunk of code jus
436.
by mkozlows 11y ago
My problem with promises is that delivering it without async/await is just awkward. Because, yes, in the ES7 async/await world, you're going to want to use promises heavily because they'll work so great with that. But in
437.
by mkozlows 11y ago
I think it's fair to say that people who want to write object-oriented Javascript are very excited by class. Those of us who have found that the non-OO nature of Javascript is part of what makes it so productive are... much less excite
438.
by mkozlows 11y ago
aria-label is well-supported enough that it's probably better to use that, rather than offscreen text, for most purposes.
439.
by mkozlows 11y ago
Screen readers provide information about headers on a page, and users use that to navigate to the relevant portion of a page. When headers are in sensible hierarchical order, this is easier to do. That said, while it's a best practice
440.
by mkozlows 11y ago
WCAG contrast calculations are designed to account for this: "Color deficiencies can affect luminance contrast somewhat. Therefore, in the recommendation, the contrast is calculated in such a way that color is not a key factor so that
441.
by mkozlows 11y ago
For what it's worth, using the viewport meta element to disable zoom is a WCAG AA accessibility violation: http://www.w3.org/TR/mobile-accessibility-mapping/#zoom-magn...
442.
by mkozlows 11y ago
If you want a11y testing for a CI environment, take a look at aXe, which is designed specifically for that purpose: https://github.com/dequelabs/axe-core
443.
by mkozlows 11y ago
So this is framed as a "things we should have done back then", but I think that the part about case-sensitive filenames show why that wouldn't work: "Of course we tried to be smart in the early days, but if you don’t set
444.
by mkozlows 11y ago
Winning what game? I can't find solid numbers about bug-tracker marketshare, but if I type "FogBugz vs" into Google, it throws up Jira as the first result. If I type "Jira vs", FogBuz doesn't show up -- I get R
445.
by mkozlows 11y ago
But if you're not evaluating the ones who fail, then what's the point of it? you're just grading for style points? What I take away from your article is that being able to solve a FizzBuzz-style problem isn't correlated
446.
by mkozlows 11y ago
Yeah, I share the linked author's opinion of ES6 -- it's good stuff, but it's also a dangerous direction. Part of me thinks that maybe what's needed is an updated version of "use strict" -- "use es6"
447.
by mkozlows 11y ago
That's why I thought this article was honestly the case against TDD. Because the upfront "this method has major problems" stuff rang very true, but then the "this is the correct way to do it" made me wince hard, wit
448.
by mkozlows 11y ago
What I can tell you for sure is that most sites are accessible to the extent that HTML makes accessibility the default, and the instant people start doing stuff that's not accessible-by-default (JS checkbox widgets, for instance), it a
449.
by mkozlows 11y ago
"It's just normal" is a thing that I think is good to communicate. Being able to use Racket to write web apps in ways that wouldn't be unfamiliar to Node devs makes the Lispy thing seem less weird and intimidating.
450.
by mkozlows 11y ago
I think that depends on where you're coming from. If you're a longtime web developer, stateless request/response are in your blood, and stateful, persistent programming is deeply weird.

More ›