tericho

Thank you, was trying to find where to redeem my pre-order and Paddle was non-responsive.

Hilarious. You probably aren't seeing a huge traffic spike because it's a microsite that hasn't been launched yet. It also appears to be outsourced or in some sort of BETA since the script management is atrocious. Run a Chrome audit - it's only a landing page and still makes 37 different JS file requests & 13 different CSS file requests, none of which are minified. Granted many "professional" sites ignore client-side asset performance but regardless, 120+ HTTP requests for a landing page is laughable.

Edit: Might be same shop as mlb.com, they don't appear to care about asset performance either.

"Nullius in verba"

Submit a PR, Mark seems like a reasonable guy I'm sure he'll oblige.

https://github.com/mdo/wtf-html-css/pulls

Thanks for making the library, glad to see you put lots of time into the docs too. Hopefully the can of worms you've opened doesn't drive you crazy, personally I would've stopped the second I found myself writing something like this...

$($($($('.nH .if').children()[1]).children()).children()[1]).children()[1]

:)

[1]https://github.com/KartikTalwar/gmail.js/blob/master/src/gma...

Just to throw in another point here - while the development tools may be free, licencing SQL Server(s) for production use can be very expensive & convoluted.

Live sports, end of argument.

This is incredible, I'm running 8.1 preview and actually can't find a way to download the release. Just keep getting redirected around to dead links. Another Microsoft stereotype proven right.

*Edit: Switched to IE from Chrome and one of the links opens the native Store app. lol

I'm not advocating the re-emergence of 12px text but the body text for Silvrback is 22px with 1.5 line-height. Medium is 1.45 and I believe 1.2 is normal. I feel like I'm reading a children's book with 2 sentences per page.

As a beta customer I can tell you this (and the inability to custom style anything) is my biggest pet peeve. I can see like 12 lines of text above the fold on my 24" monitor.

Oh look another great free tool and another senseless comment that tries to knock it for no reason. You're just writing over-generalized nonsense for the sake of it, most of which doesn't even make sense...

> Is it okay if I keep writing post in HTML, rather than REST?

What?

Rdio does some fantastic design work. Just a shame their engineering is so bad that I can't even use the app.

His point was that at minimum you still need a GET and POST for read and write. So comparing the numbers against bike-shed implementations is moot. Of course the number of reads will be significantly higher.

This is awesome, I'm wondering how it performs for the average web app. Are there benchmarks load tests anywhere?

While I do agree that copy is an important and valid starting point, don't dismiss the power of images either.

This[1] is a very important and meaningful symbol in any language.

[1]http://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/A14...

Yes, he is an evangelist for WebStorm and is involved in the new Android IDE.

Fantastic! I did hear there were some big documentation updates coming, hopefully this is the first of many. Thanks for sharing.

This is the best post I've ever seen on Hacker News

Go outside dude

This is fantastic, looking forward to promoting it for widespread adoption once it's stable.

Best Ember videos I've seen for clearly explaining each feature and giving alterative ways to conceptualize them. If you set up a page I'll donate a beer for your time, assuming you're not being paid to make them :)

This is the first comment I've read so far that I 100% agree with.

I personally see no reason to keep more than 8-10 tabs open at a given time which doesn't affect my CPU performance whatsoever (running a "standard" dev machine of 12GB+ RAM, i7, etc) so I could care less if FF handles 40 tabs better.

And quickly, some reasons I love Chrome (& Google):

- Accessible nightly builds (Canary)

- AngularJS debug extension

- Built-in bookmark/history/search sync (read something at home yesterday - can easily find it in my history at work or on mobile)

- http://www.googlelunarxprize.org/

I'm by no means an "expert" but I shared the same struggles and after 2 weeks of trying to build a complex app I gave up.

I switched to Angular (which I also had never used before) and got the same app up and running in a couple days with even more functionality because I was able to hash lots of the trickier "outside-the-box" functionality that I could not for the life of me get working in Ember.

That being said I really like Ember's syntax, Handlebars integration, core values (performance & stability specifically) and have the utmost respect for its creators. I'm hoping since it hit 1.0 that lots of new sample apps, blog posts and SO-type Q&A resources will start showing up and actually stay relevant for more than a month.

The biggest concern with JSON seems to be the lack of comments. So what voodoo is Sublime Text 2 performing? Why can't we just use that?

  {
    // Sets the colors used within the text area
    "color_scheme": "Packages/Color Scheme - Default/Monokai.tmTheme",

    // Note that the font_face and font_size are overriden in the platform
    // specific settings file, for example, "Preferences (Linux).sublime-settings".
    // Because of this, setting them here will have no effect: you must set them
    // in your User File Preferences.
    "font_face": "",
    "font_size": 12,

    // Valid options are "no_bold", "no_italic", "no_antialias", "gray_antialias",
    // "subpixel_antialias", "no_round" (OS X only) and "directwrite" (Windows only)
    "font_options": [],

    // Characters that are considered to separate words
    "word_separators": "./\\()\"'-:,.;<>~!@#$%^&*|+=[]{}`~?",

    // Set to false to prevent line numbers being drawn in the gutter
    "line_numbers": true
  }

That's just a standard the team uses, all of the code in the source is formatted that way.

I think you're missing the point. Firefox & IE are browsers, WebKit is a browser engine, market share has nothing to do with WebKit. Chrome gained market share because instead of reinventing the browser engine, they improved on it and re-branded it. John's point seems to be that IE & Mozilla using WebKit wouldn't result in a mono-culture because they could still produce their own features and not worry about reinventing the engine.