FuzzyDunlop

While the idea of an oath may be flawed, I do think it's about time some segments of the tech field showed a little less contempt towards users. I don't know how that would happen, but launching your own startup shouldn't give you carte blanche to exploit your users however you see fit.

As a programmer, I don't want a bunch of charlatans in SF to give my career an unsavoury reputation because of these antics.

It's a bit of a stretch to complain that so many people 'stole' the game when they put their own cracked copy on BitTorrent.

It's like Chris Morris gave copy/paste the Brass Eye treatment.

I remember Super Mario Sunshine was much lauded in the games press because of what it did with water and the effects. I absolutely loved the game but you don't really hear much about it any more.

Vim and Emacs have had decades to get to that point. ST is a comparative baby. I'd love to see a modern editor that isn't designed around a terminal join those ranks.

I think you win that, with 54 words nobody needed to read.

with the HTML5 option you could just use CSS:

    a[download]:after {
      /* add an icon or something */
    }

Unless it comes from one of a number of journal or research sites, where at least one of those options will no longer work.

I think that if this was done, there'd be a surge of blog posts not long after telling people to just use the original verbs, because everything about them - caching, idempotence, safeness, etc. - is a known quantity and doesn't change based on different interpretations of the same verb. Not to mention ridiculously confusing APIs.

    TWEET /
    GOOGLE /internet/?query=...
    LIKE /friend/jimmy
    GETPUTPOSTDELETE /i-am-too-lazy-to-use-separate-verbs

I suppose British people never really used the chat to talk about paedophiles. At least they looked for actual words rather than any occurrence in the string.

It should change all the vendor prefixes too:

   border-radius-for-all
   border-radius-for-Webkit
   border-radius-for-Opera
   border-radius-for-Firefox

And maybe @summons instead of @import.

I'm not convinced this is a good idea in JS, where the comment will be completely inaccurate. I'm not exactly sure how you'd differentiate something you decided was protected from something else you decided was private.

This isn't to say that having documentation on what you consider to be the API is a bad idea though. Omitting the functions you don't want or expect people to use is good for public facing docs.

This is making a lot of assumptions about the author of the gist, whom we know absolutely nothing about.

They might actually be one of the contributors.

One would associate 'shelter' with the word 'vagrant' more than 'hospice', which also makes it a strange choice.

I remember having to perform some magical incantation to actually pull that off around then. Set up WP, log in, create new user, set it as admin, log in as the new user, try to delete the admin account, log back in as admin because you forgot something, log in as the new user again, actually delete account.

No wonder everyone stuck with 'admin'.

I also think that clicking on the link to an error should go to the debugger panel, rather than opening the source in another popup.

They also look like tabs and I find it frustrating that the tab switching shortcuts don't work on them.

I used Sublime for a while, then switched to Emacs for a while. I ended up switching back because, while I really liked Emacs, I didn't like being stuck in a terminal and I couldn't do effective pair programming.

The best bit about Emacs is the configuration, and I could give or take the awkward keybindings. Maybe if LightTable supported configuration with ClojureScript and offered a comprehensive API for it there'd be a more modern equivalent.

I'd love it if they were stored in dotfiles (something I like about Textmate 2), but at least all your config gets stored in a nice User package.

I think it's fine so long as everyone agrees, or as long as people don't strip the whitespace in the same commit as their actual changes.

Half the time the pointless whitespace is introduced by an editor that auto-indents for you.

mruby[1] is aiming to be an embeddable version of Ruby. Still a massive WIP though.

https://github.com/mruby/mruby

I think it's a shame that something as as unambiguous and nice to work with as, say, the Cocoa framework and MVC (using that example because of familiarity), was available for us web developers without trying to shoehorn it into javascript and the browser environment.

Having had a taste of native app development, it makes client side web development comparatively frustrating. We're continuously getting new features but little in the way of a more satisfying environment that can help bring all these parts together.

The 90s were truly the golden age of the internet.

It was also a wonderful departure from the style of the previous games in the series. I loved sailing about, looking for islands and ships to explore. Easily up there in my top 10, along with similar styled games like Okami.

I presume they valued the terseness of the domain over the brand potential of 'Pages'. I do agree that there is confusion though. You can't possibly know the difference between github.io and github.com until you're actually told.

The problem with loops in javascript is that, once you start doing more complicated things than accessing array indices, you run the risk of introducing bugs that don't exist when using a more functional style.

Once you're using closures in your for-loop to prevent everything referring to the last index in the array, you might as well be using map and reduce and all that. Otherwise you end up wasting a lot of time to come up with stuff roughly like this:

    (function(order) { 
      // do something 
    })(orders[i])

Probably not good for ruby when combinations of the following things can result in deeply nested code:

    module
      class
        def
          if
        class << self
          def

I find it amusing that Dart is apparently bad because it has batteries included, and that the third party ecosystem should be relied on more, yet the author has no trust in third party 'future' libraries and likes that Dart has core support for it.

I think the killer feature of git -- which applies to any other DVCS -- is that you're not dependent on github if you're well prepared. There's absolutely nothing stopping you adding redundant remotes so you always have somewhere to push/pull changes and deploy from.

    git remote add <remote_name> url

Probably because the former article feels relevant to a wider audience here than something about GCC does. There are probably more Americans than C developers on HN.