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)
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)
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
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)
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.
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...)
To clarify: it is an excise tax and applies to the _gross sale price_, not the profits (so even if the division runs at a loss, they still have to pay). http://www.irs.gov/uac/Medical-Device-Excise-Tax:-Frequently... I'd agree with your skepticism if it were affecting net (after employee salaries etc).
> And besides, it doesn't invalidate the ethical point that it is right to privide medical insurance, even if true.
Your original point was "There are no good reasons to be against the Act", so my response was pointing to a reason why someone would be against the act: I'm pretty sure that being laid off due to a regulation is a pretty good reason to be unhappy
There are many americans working at medical device companies that will be affected by the 2.3% medical device tax. Zimmer, for example, cited the medical device tax as the reason for firing a thousand workers a few years ago.