niggler
Joined 14 years ago
Karma
4,711
Submissions
1,709
Member since
Sep 5
Recent submissions
Comment · 13 years ago
Now TSLA is up 21% (67.90 last trade)
Comment · 13 years ago
What happened to the original title "Unreal JavaScript"? The biggest focus of the article is emscripten, not asm.js.
Comment · 13 years ago
Retina macbook pro early 2013, chrome 26. Zooming some of the plots is noticably slow (and zooming out of the Hopf Bifurcation plot occasionally causes chrome to stop responding)
Comment · 13 years ago
How does this compare to raphael (http://raphaeljs.com/) ?
Comment · 13 years ago
None of your statements contradicts points from my comment, my post, or the coding horror post. If you are releasing code and not putting in a license or doing so improperly, don't expect others to use it. CH focused on one facet (missing a license) while I focused on a different facet (how to add a license properly)
Comment · 13 years ago
"... will we have to endure over the next month"
So long as people click on those pages, everyone with even the most minute point will write to their hearts' content. I'm surprised that this page didn't have a million ads on it
Comment · 13 years ago
There are proper keyboards for the ipad (this is being typed on a logitech ultrathin keyboard ipad cover)
I haven't tried the surface version of office, but the web versions of office definitely lack features compared to the desktop versions (for example, array formulae)
Comment · 13 years ago
It's better to be safe than sorry, as the saying goes. I've never been burned personally. I'm also pretty sure that anyone working for a large software company is warned about using third party code or snippets found on expertsexchange or stackoverflow or random blogs.
Normally people are well intentioned, but sometimes you stumble upon repos with very strange licenses (for example, a javascript repo that has operating system restrictions https://github.com/stephen-hardy/xlsx.js/issues/8 ).
It's usually not of a concern for most people working on small projects (after all, another party has to notice and then decide to take action), but if you are trying to enter an industry with a highly litigious incumbent then you should make sure your ducks are in a row first.
Comment · 13 years ago
I wish licensing was emphasized more in this discussion.
Including a license is the #1 reason myself and many other people stray away from code on the internet. I won't touch a project if it's not stated properly.
And to be clear, just writing that your project is MIT licensed or sticking it in a package.json or making a small remark in your README doesn't cut it. You need to follow the terms of the license you wish to use (my comment on the matter: http://blog.nig.gl/post/48848761220/just-saying-something-is...)
(always a good read: http://www.codinghorror.com/blog/2007/04/pick-a-license-any-...)
Comment · 13 years ago
Unfortunately, the situation has only gotten worse in 2013
Comment · 13 years ago
set -o vi