arcatek

Not exactly. Buttcracks are gross, and may easily tarnish a community ("hey, look at those fat ass nerds"). I've been at the Utrecht tournament last week: from my seat, I had a direct view on at least two buttcracks, which were both much bigger than in these pictures. Even for the players, it's not a great sight.

However, shaming these guys on social networks is a big no-no. This guy should have went to a judge so that they could talk and educate the concerned people, rather than taking pictures without their consent and posting them online. For this reason, WotC banned this guy from official tournaments for something like a year.

The Magic community (especially the pro community) has a sad habit to publish everything on social networks, even when it should remain out-of-sight (in the past month, two other 'scandals' like this happened, which clearly show that we have something to work on).

You shouldn't use the term "destructor" as an alias of "destructuring expressions" - destructors are an entirely different thing[1], which is not applicable to JS.

[1] http://en.wikipedia.org/wiki/Destructor_%28computer_programm...

The point is apparent is you use actual use cases.

  let {title, content, email} = articles[0];
  let [all, ident, domain] = email.match(/[^@]*@.*/);
  return `<h1>${title} (${ident} at ${domain})</h1><p>${content}</p>`;

Secondly, there is no destructor in JS (because of dynamic memory management), and there will probably never be. Destructuring is nothing like destructors.

Thirdly, the language doesn't have to fork. You can still write ES5 code. But you should probably not because, believe it or not, ES2015 is a really good thing, full of improvements. And syntaxic sugars are part of what makes using it so much nicer than ES5.

Apparently happened with VLC too...

> We also got outed of our +VLC project on sourceforge...

> But it does not matter, we moved to our infrastructure a long time ago to our own, which is better and more powerful!

Previous discussion : https://news.ycombinator.com/item?id=9186246

Looking at every pixel of the image is quite slow (especially if you need to process multiple images, and more so when you're dealing with old devices, such as iPad 2). Resizing them is often "good enough" for the majority of use cases.

I made it too based on a StackOverflow answer a few years ago, but this one is probably much better (I hadn't even put a package.json at the time). However, the SO thread is really interesting, I suggest you give it a look if you're interested in how to solve this issue.

[1] http://stackoverflow.com/questions/13637892/how-does-the-alg...

[2] https://github.com/arcanis/colibri.js

> Using Angular is a bad idea, but lots of companies are using it anyway because The Herd stampeded towards the new shiny thing

The most ironic thing in all this is that your comment is still full of Herd mentality, except that it goes the other way.

Angular is a framework, period. Using it is neither a good or a bad idea, it all depends on the people who actually use it.

Thanks ! Yes, I have a great deal to do as far as documentation is concerned (however, there is some doc about the smartphone-as-a-controller feature[1]). My plan was to focus on this before implementing more features.

The sound isn't yet enabled, I have to resolve some issues with Chrome. Shouldn't be long tho (once the documentation is improved :)

[1] http://start9.io/howto/remote-control

If I may, I'd like to also link my site (http://start9.io) which does this and also work with GB/GBC, and persist your saves online (on top of quite a few other features). The only drawback is that we actually require users to upload their games, for legal reasons.

We're still in beta, and it will probably improve quite a lot in the upcoming months, but I use it myself on a daily basis.

For the record, the emulators are currently based on Emscripten versions of the libretro cores (rather than being a full-JS emulator implementation, like IodineGBA). I'm looking to add more consoles, and the SNES will probably be come soon.

Should you try it, I'd love to hear your feedbacks (my contact is on my HN profile) :)

I've used it everywhere on two production website, and we have had close to no issue with it. I'd say it's quite safe to start using them now.

Funny how Mael has won quite a lot of hype in the past years (it's still a rare name, sure, but it's much more common now than when I first ...acquired... it).

Apparently it simply try to open a bunch of modal window to close. Chrome is smarter enough to figure that out, and there's only about five windows before the script is killed.

the String function is also a nice way to cast a value to a string (using .toString() is unsafe because it may not exist, such as with undefined and null): String(42) === "42".

An other thing that could maybe be covered is this specifity:

    typeof "42" === "string"
    typeof String(42) === "string"
    typeof new String(42) === "object"

Native constructors are ... fun beasts, to say the least.

> "To the women readers/watchers: I apologize for saying "guys" in a few places referring to groups of people"

As a non-native speaker, isn't "guys" a correct term regardless of the gender?

Manually compensating for lags is still interesting :)

Isn't the physical copy already available?

"You'll receive the book in both digital and audio formats, as well as a paperback book that will be shipped to you free, anywhere in the world."

Try doing a parser and you will see why self-closing void tags are generally a good idea.

Anyway, I don't understand this discussion at all. I was expecting something a bit better from the HN community. Since when did we start making strong judgments based on purely esthetical things?

An applicant to a position we offered once submitted a code without <head/> nor <body/> tags, and his justification was totally right: the standard doesn't actually require it[1]. So does that make you a bad programmer for using them? Not using them? I believe nobody really care, and I would have to be a really bad person to judge my colleagues based on that.

[1] http://www.w3.org/TR/2011/WD-html5-20110525/syntax.html#opti...

It's a french standard. Every french/belgian keyboard is AZERTY-based.

You don't HAVE to support it, but accessibility is nice, especially when it comes at virtually no cost except awareness (it is not supported because people don't know it exists).

Could you please support ZQSD (azerty keyboards)? You just have to alias Z=W, and Q=A.

It's a very simple thing, but almost no web game does it, which makes them unplayable on many computers. I shouldn't have to switch my keyboard layout to use a website :(

Probably the same feeling that when you lie to someone, see your lies being slowly exposed, and there's nothing you can do about it. Happens a lot when we are teenagers :)

Webpack is a very good solution too. I really like jspm, and especially the dedication of its main developer, but I found much easier to integrate webpack in my build process than jspm. More features, a bit less bugs.

Yeah, no, you don't make a project open-source and expect people to improve it as much as you will. It just doesn't work like this.

An open-source project is a burden, you probably won't gain anything from them, and will probably lose a lot of time. Almost all of my projects are OS, but I don't do it expecting people to come over and help (even if it is sure nice when they do).

> "You don't have to care if you don't have anything to hide"

I never quite understood this argument. We have something to hide, that's the whole point. I don't want somebody to look at my phone messages. I don't want to share with the government every sily joke that I may say at home.

Should I work on secret businesses, I certainly wouldn't want any random agent to read about what I'm working on. We all have something to hide, the whole argument is bogus ...

I guess that capitainetrain is too much "France-centric" to be listed on businessinsider, despite it being a really clean product.

I used to work at Sketchfab, which is another really interesting french startup which raised a few millions in the last past year (plus, they work with pretty cool technologies). Incidentally, I think that they are currently hiring.

To be honest, a simple Makefile is very simple to write and efficient once you know the syntax fairly well. Then you add more and more things as the time pass, and it starts to morph into a giant huge monster that eat puppies.

I'm not quite sure to understand what this repo is for. Can you explain?

A good thing would probably to have a way to see the requests triggered by installed extensions. Even checking this list once in a while and manually reporting the suspicious ones with a "report" button would make these rogue extensions almost worthless.

Maybe something like Wisembly[1] ? I worked there as an intern a few years ago, and the product (and team) was great.

[1] http://wisembly.com/fr/

I made a voxel engine without using Three.js a few years ago[1] (well, the engine is rendering-agnostic, so I actually used Three.js, but only the really basic primitives, such as BufferGeometry).

The issue wasn't so much WebGL performances (especially since WebGL is actually hardware accelerated), but rather the CPU cost required to rasterize a real-time voxel world into a polygonal geometry. I wasn't able to generate geometry chunks fast enough to match the player speed (so the player was always able to catch up with the rendering). Even using workers wasn't improving the perfs so much (but I think could have improved that by changing the update heuristic a bit).

But it was pretty fun nevertheless! I'm proud to be one of the few JS voxel engine using marching cubes, which look much better than usual cubes :)

[1] http://arcanis.github.io/voxplode/ (may take a while to load, may be a bit buggy, especially if you move before the chunk underneath has been loaded)