I always rebind it to ^z. Since I never need to put a process in the background (I just open a new screen instead) when running screen, it never bothers me that that combo is a bit harder to type.
When you sign up, they have a question "does your company have less than 10 employees", which is presumably to deal with this issue. Of course, 10 is a pretty low cutoff for this question.
Another alternate moral: Something that seems like a very minor patch-level change which just fixes a bug and doesn't affect your API actually can break running production code.
Many people like to pretend that they can follow a discipline like Semantic Versioning (http://semver.org/). But minor changes like this can cause subtle bugs when you are upgrading between patch-level versions of a component that you're working with.
Ah, yet another CSS extension that adds variables and mixins. At some point, shouldn't some of these projects come together, and say "we ought to standardize this?" I realize that the CSS working group is against adding variables and mixins to the standard, but given that there are now at least three prominent (and incompatible) implementations (Less/Sass/Google Closure), it seems like it's time to fork the standard (like the WHATWG did), standardize something, and then see if you can roll that back up to the W3C (or ignore the W3C if you can't get them to accept it).
Unless it's the standards group that's going to standardize it (which like you say is unlikely), what exactly is the advantage of the projects getting together to "standardize"? It may seem good to the average end developer, simply because there's fewer deliberation to be made, but I suspect the "competition" is probably a net positive for everyone.
The way most of these things go is that over time, either one of the projects becomes the de facto "best one," and the other projects eventually fade away, or two or more projects make some significantly different choices and thus branch off in multiple directions, each with its own community of contributors and users.
I think at this point we really don't need more of these CSS supersets but more comprehensive CSS frameworks like Compass and web framework integration with these CSS frameworks, i.e middlewares and asset management tools. I for once would love to see Compass ported to Less.
Well, yes, that's my point. We don't need more CSS supersets, we need fewer; one standard one, that is called "CSS" (or "CSS4" or whatever). That, then, can be the target for frameworks like Compass, instead of them targeting CSS 2.1/3 or targeting only a single CSS superset like Less, Sass, or now Closure.
Well, to be fair, who is "Academia"? Is it the professors? Is it the administrations? Is it the whole system, including universities (and all of their issues down to football team scandals), publishers, college admissions tests, and so on?
The thing is, there is a fairly substantial system set up around academia. It includes people who run conferences, publishers, school administrators, endowments, students, admissions, government grants, private grants, standardized testing, and more. There is a lot of it that is fairly nasty.
Sure, there can be a few professors who object to some parts of it; but that doesn't mean that the system as a whole isn't sick. Has there been any serious institutional pushback against this prosecution?
I think that part of the the problem is that the people who matter the most in academia (the professors and the students) have lost their voice to the "industry" of academia; the administrations, publishers, the grant funding bodies, and other people who have a vested financial interest in the system, but who aren't the main producers or consumers of the value of academia.
The issue is that they will be releasing the source under the GPL, which requires that you give anyone who receives the code a patent license, but they probably can't give a patent license as they can't sublicense the patent from Creative.
> Sometimes you just have to sue to enforce a contract and your rights.
If you can sue. At my last job, they made me sign a binding arbitration agreement as a condition of being employed. I needed the job, so I couldn't play hardball and refuse.
And $4000 a day can add up pretty quick. 50 days is approximately the average number of days for filming. That's $200,000 per camera. Since you frequently want to do shoot from a few angles, you're talking a half million or more just for cameras.
Now, for a normal Hollywood blockbuster, at $50M, that's significant but not too bad. For an independent film, which will likely have a budget under $10M, and sometimes even under $1M, that's a pretty substantial portion of your costs.
So cameras that cost $10K to buy outright will make a big difference in this space. All of a sudden, things that were prohibitively expensive to independent filmmakers are within reach. Independent films allow people to have more artistic creativity given that there's less at stake; they can also be the "long tail" of filmmaking, covering more niche interests than a big blockbuster is going to have to. So this could be a fairly significant disruptive innovation, if these turn out to be worth it.
Of course, it's not quite as good a deal as it might seem at first, since I believe the price quoted is just for the very core of the camera, containing the sensor, and not lenses, which are where some of the real cost is. But still, these will allow people to do 4K filming who never have been able to do so before.