calvin

Look at the healthcare.gov source and you see the following technologies in use:

  - jQuery 1.8.2
  - Backbone 0.9.2
  - Bootstrap 2.3.2

You may need to look inside the all.css and all.js files.

Page Speed: 92/100 YSlow!: C, 76/100

At least on the homepage I don't see Backbone actually being used.

If you offer two-factor authentication for your website, be prepared for a surge in support requests today. When I talked to one of my providers on the phone, they stated they are already getting a surge in calls because of this app update.

Yes, you'll have a cease & desist as soon as Kickstarter sees the URL and site name.

Did Woot get murdered? No.

Did Zappos get murdered? No.

Did Quidsi get murdered? No.

Did Shelfari get murdered? No.

(Note: I'm biased.)

I changed careers five years ago. Up until that point of my life, I'd primarily worked in customer service jobs despite having a B.A.

What I did:

1) found the first job I could in the Seattle area (it was a call center job)

2) attended tech / startup community events (meetups, hack days, etc)

3) got lucky by meeting helpful folks in the tech community

4) worked on side projects on nights and weekends to grow my web development skills

5) found my first paying freelance dev work

6) found more paying freelance dev work

7) took a webdev job at a startup

From there a lot more has happened, but I've been in a webdev role ever since and continued learning new skills and taking opportunities to grow and contribute.

This is only one story and one perspective, but I hope you find a way out of the problems you're facing.

Yes. And DuckDuckGo. And Google.

Why give all your searches to one search engine and one company?

Depending on what you're searching for, Google doesn't always provide the best results.

I like the points made here and the general thrust of the petition; however, the big question I have: where is the data to back up these claims?

The argument would be a lot more convincing if sources or studies were cited for claims such as increased air conditioning costs, etc.

Is $80,000 a realistic amount of money to launch a project as ambitious as this one? With multiple employees and a large need for hardware and manufacturing, I don't see how this is enough to kickstart the product.

Zen coding syntax is fantastic, it makes generating HTML in my editor a breeze.

Stick to ">". That's the standard CSS for indicating a child element.

e.g. "div.myclass > h1" indicates a div with class "myclass" and a child h1 element. In zen, it outputs:

  <div class="myclass">
    <h1></h1>
  </div>

http://www.w3.org/TR/CSS2/selector.html#pattern-matching

I'd explicitly state the license to be blunt, obvious, and avoid any confusion.

Drew's gem doesn't specify a license. It may be open source, but it's not clear what the license is. That doesn't help in this kind of a situation.

Can anyone provide a SFW link for this?

WordPress has BuddyPress (http://buddypress.org/) for social networking. I don't believe it allows interconnecting with other installations.

If 99% of your friends keep their data in Facebook, you're still dependent on Facebook.

What problem is this solving? I know users of social media who are unhappy with what they're using. But I've never heard my mom or any other Facebook user for that matter say: "You know what I want? A decentralized social network where I can own my content!"

For this to get traction, it'll need at least one server with a strong user base.

If so, that would be incredible. More than once I've found myself wanting to search a repository for a specific word or variable without downloading it and acking through it.

Doesn't involving another third-party vendor add an additional point of failure to the system?

It's been long enough since I've been on digg that I don't have the same email address.

I'd much prefer if they provided the data to the internet archive rather than one-by-one providing information to users.

When will the changelog be updated?

https://github.com/h5bp/html5-boilerplate/wiki/changelog

Hence Dalton Caldwell's "Audacious Proposal" and the birth of App.net.

https://join.app.net/

If you have a policy with an insurance company, they should honor it rather than going out of their way to take advantage of a customer. That's the point here.

They've made the build tools modular using grunt.

Considering that they have custom download options for jQuery UI and recently added a tool for jQuery Mobile (http://jquerymobile.com/download-builder/), I expect it won't be many more months before they add one to jquery.com.

The disclosure at the bottom is rather informative:

"Disclosure: Craig Newmark, founder of craigslist, is a member of EFF’s Advisory Board, and craigslist has donated to EFF."

I like the use of colors in the redefined design, but will it work for people with color-blindness?

It's targeted primarily at enterprises and only gets updated (aside from security patches) every 7 releases (42 weeks).

I can't speak to why they upgraded without asking you. However, 3.6 has been end-of-lifed and will no longer receive security updates. You'll be much better off using the Extended Support Release.

Mozilla doesn't make it easy to find the ESR download page. It's here:

https://www.mozilla.org/en-US/firefox/organizations/all.html

Amazon Wireless already exists, but not in the sense you're describing. They sell phones and plans on the existing carriers.

http://wireless.amazon.com/

I can think of a lot of reasons this approach won't work well for most of the sites I work on (other than a few blogs).

1) Combining jQuery with other JavaScript at build time (to reduce HTTP requests). At built-time, we don't know which browser they're using. We'll end up with two assets (the combined version w/ jQuery 1.9 and the combined version w/ jQuery 2.0).

2) Testing costs. For larger sites it's not a trivial thing to test and support two different versions of jQuery. For any site that still needs to support IE8 (and 7 and 6), it will not be feasible to test and support two different versions of jQuery. As such, we'll never get the benefits of using jQuery 2.0 and would not be able to do so for many years.

3) Plugins will be written that only work for one of the two versions (1.9 or 2.0). This will divide the plugin ecosystem. Ideally, plugins should work for both, but many people will only test and support their plugins on one of the versions.

I don't think any knowledgeable front-end engineer would build a page in quirks mode, but a surprising number of existing sites have large swaths of pages without a doctype.

A lot of good changes in here. The modularity will improve usability -- particularly for sites who want the core jQuery features without all the extras. My hope is this will make it easier to use jQuery on mobile -- and more comparable to Zepto in terms of size.

I remember reading somewhere that 1.8 would drop support for quirks mode in IE. Anybody know if this ended up happening? I didn't see any mention in this post.