postfuturist

Java 6 did not break backward compatibility (code written for Java 5 generally runs fine on Java 6).

"One of the great strengths of Python 2 is the long tail of 3rd party libraries" does not imply it is the "only measure"

Did you read the article? The long tail is the critical collection of libraries and most of them will never be ported. People write new Python 2 libraries every day, actually--the list is getting longer, not shorter. That said, gevent is an extremely critical library for a lot of production Python 2 code. There doesn't even seem to be a roadmap to port it to Python 3.

Python 2 has unicode literals and utf-8 available if you declare them at the top of your file. You don't need Python 3 for that.

I'm the author. I've never worked at Microsoft (where did you get that?). I'm a Linux guy.

The "lazy people" you refer to is 98% of the Python community.

Python 3 didn't "gain" static type checking. You can (and I do) run pylint against Python 2 code which is just static analysis, not full type checking. The situation here has not changed between Python 2 and 3.

Python is glue code. You write a small piece of Python to tie together external libraries. Moving a smallish piece of Python code from Python 2 to Python 3 often means porting several 3rd party libraries. If you were to move to Ruby, all you'd need to rewrite is your own code, as there are likely already 3rd party libraries which need no porting.

> No one expects an app written for OSX 10.4 Tiger to work on OSX 10.8 Mountain Lion.

That's truly sad.

json.org/license

That's just a license for software available on json.org, so no impact at all.

OK, I'm moving to Finland.

I like Prolog

Also, I have a love/hate relationship with a lot of these langs, so votes go in both categories, I suppose.

It's a common technique to serialize arbitrary data into blob fields in SQL databases--I've seen it for years. Usually, it is considered an anti-pattern. Postgres 9.1 doesn't do much other than verify the JSON data is valid JSON and then stores it unchanged, though successive versions are adding more first-class JSON support.

It will probably be available here forever: http://web.archive.org/web/20130806152657/http://blog.jgc.or...

> They are a data structure invented by Rich Hickey for Clojure

It is an implementation of a data structure invented by Phil Bagwell: http://lampwww.epfl.ch/papers/idealhashtrees.pdf

Edit: he should have escaped the $title and $body.

This isn't a search for SQL injection, its a search for a couple things that you often find in older PHP code that is generally hacked together and likely to have SQL injection vulnerabilities for historical and cultural reasons. However it's perfectly easy to avoid SQL injection even using these things.

    $id = mysql_real_escape_string($_GET['id']);
    $res = mysql_query("SELECT foo FROM bar WHERE id='$id'");

That may be ugly, but it's bulletproof regarding injection.

"... antioxidants, probiotics, and nootropics. It's everything the body needs." - Soylent video

"It's a single cell protein combined with synthetic aminos, vitamins, and minerals. Everything the body needs." - from The Matrix

People are working on this very problem: http://ecozoomstove.com/

I enjoyed using an earlier version of Linux Mint, but the default gnome-shell UI had a massive memory leak ( https://bugs.launchpad.net/linuxmint/+bug/930402 ) which was never fixed and "upgrades" to the next version are wipe-and-reinstall. So, I wiped it and installed Ubuntu 12.10 which I dist-upgrade to 13.04 without incident.

With no support and no upgrade path, I don't see what the draw is.

1. Does being a cretin or a jerk or whatever mean it is OK to be imprisoned for non-crimes?

2. He wasn't the one who started the comparisons with Aaron Swartz, from weev's tweet: "CNN is also sitting around calling me a meanie. I'm a bad troll, and no Aaron Swartz, the outraged masses cry!" Then he goes on to continue differentiate himself from Aaron, he never created or invited a positive comparison.

3. The article said he was sending messages to another person who was tweeting on his behalf. Why would he lose his right to free speech just because he has been convicted of a crime? Why wouldn't he be able to tweet (by proxy)?

EDIT s/charged/convicted/

"automatic merging" upon consensus -- had to laugh at this idea, the ratio of merge requests that would merge cleanly, automatically is low. Generally they have to be rebased against the exact branch they are to be merged against with human intervention to rectify not only merge conflicts and broken tests but possible interaction issues with recent changes on master branch. In any case, arbitrary changes can (and sometimes should) be made to bring the branch in line with the main code. So branch merges that were "voted in" still need human intervention to merge. Should that then be re-voted on, given that merges and conflict-resolved rebases/merges can include arbitrary changes? Obviously, but what if more changes go into the target branch while folks are getting around to ratifying the rebased merge branch? There still needs to be trusted "merge officers" or whatever who can and will clean up, test, and merge popular branches which were voted on. You can't get around that.

Rosetta Code has Hello World in only 245 programming languages (but a huge corpus of other examples in various languages). http://rosettacode.org/wiki/Hello_world

Perseverence. Time and exposure is all you need. Eventually you will be comfortable with it. I know I am, and it probably took about a year.

Cookie handling needs to be visible, not just for devs, but normal users. Maybe a little bar that shows that first party and 3rd party domains are offering cookies and users can allow them as needed or set defaults they are happy with (like having to white-list third-party cookies on an as-needed basis instead of allowing everyone to track you by default). Not only would these cookie controls allow for easier development, but they would make it obvious that sending cookies back to a site is something that the browser (as an agent for the user) is doing voluntarily on behalf of the user, so we can do away with "cookie laws". The fact that cookie laws exist is related to the fact that nobody understands that accepting/using cookies is perfectly voluntary. Nobody knows this because cookies management is insanely obscure and difficult in all browsers Firefox inclusive.

Quick Ubuntu Guide (tested with 12.10, should work with 12.04):

    sudo apt-add-repository ppa:efl/trunk
    sudo apt-get update
    sudo apt-get install e17 libedje-bin

Log out, select Enlightenment from menu, log in, enjoy!

There's nothing in the LGPLv3 that prevents you from charging money, or distributing through app stores, so long as you comply with the requirements of the license.

"Similarly, if an employee smuggles in GPLv3 code in to the company's codebase then the company can't just shrug that off, and must release their proprietary source code as GPLv3."

No, assuming the company was in violation of the GPLv3, they would probably need to stop using it, and potentially pay damages if sued by copyright holders, but would be under no compulsion to release their own proprietary source code. Unless, of course, they wanted to comply with the terms of the license and continue using it. However, the GPLv3 alone wouldn't even require that unless they were selling or making available copies of the software.

Financial incentive is good, the developer is encouraged to continue maintaining and supporting the project and make it even better, listen to users, pull in useful features from popular forks, fix bugs, etc. The way to have the most popular open source project is to have the best one.

It was a little rough at first, but it has smoothed out. I like it.

What about Firefox which has shipped with Google search default since forever, which Google pays Mozilla for, which Google makes money on? Will you never use Firefox again?

This is just a light lisp-like syntactic layer, as the docs say "LispyScript is not a dialect of Lisp. There is no list processing in LispyScript ." It's just enough to allow nice macros, which adds quite a bit, IMO. There's no CONS, etc. It adds a couple nice things, like an "each" function that does the right thing, and (= foo bar) becomes foo === bar.