1,144 karma · joined August 17, 2012
It seems kind of odd to do this so late in the patents' life, though. I understand the general theory behind a last-minute cash grab, but you generally can't take "last-minute" quite this literally. Why wait so long?
The US government generally does not claim copyright on its works. However, the Trump name is more likely to be tied up in trademark law than copyright law, and this muddies the waters considerably. It works to your advantage in some ways, but against you in others. Be careful.
But there's one thing I've found interesting. I'm still stuck in Chapter 1.2: the infamous Mathematical Preliminaries section. I am not proud of this. From what I can tell, the various aborted liveblogging attempts I've seen also all get stuck here. Knuth himself recommends skipping it if you get stuck.
But even though I haven't yet managed to finish that single part of the book -this part which comes before any actual computer stuff- I STILL come out of it a much better programmer. Every. Single. Time. I haven't yet written a line of MIX or MMIX, and I have STILL been able to use this book to level-grind, just by getting further in 1.2 than I was able to get before. It's awesome. Even when I fail, I come out stronger.
I do eventually plan to blog my own attempt. My plan, though, is to not actually blog 1.1 and 1.2 live: I will do these chapters, write the articles on them to give myself a buffer, and only put up the blog once I'm already through The Big Filter. I figure this will give me a much better chance of actually succeeding once I start.
France is a civil-law system, so case law is in theory irrelevant. In practice it isn't so irrelevant these days, but it still doesn't carry nearly the same weight that it does in common-law systems (like most of the US, though not Louisiana). On the one hand, this makes it much easier to ignore previous rulings by clearly corrupt judges. On the other hand, it makes consistent interpretation of the law much harder to achieve. It's a tradeoff.
In other words, Nexedi knows that case law is against them in the US, so they cherry-picked a location for the lawsuit that would allow them to circumvent this obstacle.
On the other hand, removing an emoji does not, in any way, prevent expression of the concept it describes. It leaves a very bad taste in my mouth, particularly when justified by what amounts to magic-bullet media theory, but to call it censorship is frankly absurd.
Instead, the argument goes, one should load the JSON, walk the redulting structure, and use it to build your native data structure/objects/whatever. Similarly, when the time comes to save, you crawl through your native structure to build a dict/array/primitive structure, then call JSON.stringify() (or the analogous function) to serialize that.
Uncoupling your data structure from the serialization format, though, is really just basic good software design anyway, is it not? Does anyone argue in favor what this article calls "JSON-driven development" as a design principle? Or is it just a shortcut that developers -and I am no less guilty of this than anyone else- sometimes take in the interest of getting a quick-and-dirty solution out the door?
Yes, working directly on the output of JSON.parse() is a code smell. But I'm not sure that claiming there's a rising trend of "JSON-driven development" is entirely founded. It's just people taking shortcuts.
Site seems to be dead already. This seems awfully fast, given that they only ceased operations yesterday and still have a couple of things left to do, so the site might come back up for a bit. But here's a link to a snapshot just in case.
Ultimately, this. You can test for very, very small numbers, but you can't test for zero. This is why, for example, even though lead has no biological function, extremely small "acceptable levels" are specified in regulations rather than simply saying zero lead. You can prove that, for example, lead levels in the air are less than 0.15 µg/m^3, or that they are not. You cannot do that for zero (nonzero is easy to verify, but zero is not).
There is also, of course, the fact that no food is safe in all scenarios. Even pure water is toxic at high enough doses. For that reason, it makes no sense to hold GMO food to even higher standards than non-GMO food: equal standards certainly make sense, but not higher.
Anti-poaching methods are obviously needed to fill in the gaps while technology catches up, and should be continued or perhaps even escalated. But the most effective weapon against poachers could prove to be the very markets that draw people to poaching in the first place. Remove poaching's feasibility as a lucrative profession, and the profession dies.
[1]: http://pembient.com
If it's still in development, then in what way is it "more mature" than asm.js?
You don't hear much about graphical browsers anymore, not because they died out but because they became such an overwhelming majority that it no longer made much sense to make any distinction. But a few non-graphical browsers are still in development; Lynx is probably the most famous of them.