Ahhhahaha, ahhhahahahahahahahahaha! Good lord I wish this was true!
4,122 karma · joined December 8, 2008
Ahhhahaha, ahhhahahahahahahahahaha! Good lord I wish this was true!
That is, if you can use Python 3, you should: it's the future of the language, and it feels it. I find Python 3 significantly more pleasant than Python 2; nearly all the bits that annoy me about Python are fixed in 3. Python 3 is cleaner, the standard library is de-crufted and easier to navigate, and (most important to me) handling unicode doesn't suck.
However, as others in this thread note, significant parts of the Python ecosystem haven't finished porting yet (Django, Twisted, yada yada yada). If you rely on one of those things, then stick with Python 2. If that code lives fo a long time you will have to face a porting effort later on, but that's improving somewhat as the community discovers new techniques and creates new tools.
The situation hasn't changed. If you want to work with Django on Python 3, go ahead; the code's right there for you. We need the help: it's going to take a lot of burn-in to make sure we get everything right.
If you're waiting for it to hit trunk, fair enough I guess (though it's a purely arbitrary decision on your part; the only difference between the branch and what'll hit trunk is the URL). That should happen shortly after 1.4 ships, so quite soon now.
However we decided not to merge this in for 1.4 for a couple of reasons:
1. As you might imagine, it's a big patch, and potentially destabilizing. Although it's in a good state now, it go there fairly late in the 1.4 cycle. If we'd merged it there wouldn't have been enough time to be sure we didn't break anything for 2.X users. So we held off the merge to make sure that 1.4 was as stable as possible.
2. The approach Vinay took (and the one we're sticking with) is a single-source approach. That is, a single source tree to support both Py2 and Py3, no 2to3 translation needed. The difficulty of this approach is directly proportional to how far back in the 2.X line you want to go. We promised that Django 1.4 would support Python 2.5, but single-source including 2.5 is a lot harder (and makes MUCH uglier code) than single-source for 2.6+. So we made the call to make the Py3 support depend on dropping support for 2.5, which we'll do for Django 1.5.
So, all in all, time timing wasn't right for Py3 support in 1.4, but it is right for Django 1.5. Which is why I expect to see this branch merged shortly after the final 1.4 release.
If there are attacks that we should be aware of please be a good open source citizen and report them to `security@djangoproject.com`. We take security reports very seriously, and want very much to fix any issues that're disclosed!
[edit to clarify: I'm one of the lead developers of Django, and one of the members of the security team that gets emails sent to the `security@` alias.]
When I heard the news, my immediate reaction was not positive. [...] No one I know is filled with joy when using Adobe products...mostly the opposite. Typekit is a great service; I hope Adobe keeps it that way.
(http://kottke.org/11/10/adobe-acquires-typekit)
This sums up my reaction, as well: I use Adobe products because I have to, not because I want to.
I assume you'd disagree with folks like Jason and I about the joylessness of Adobe products, but I'd guess that we'd all agree of the importance of keeping TypeKit simple and elegant.
So what safeguards, if any, have you been able to put in place to ensure that TypeKit maintains its je ne sais quoi as it becomes an Adobe product?
As a very happy user of some of Python PaaS services [1], there are a few reasons why I don't see myself switching to Heroku:
* These services are written by our community, for our community. The principles at most of these companies are people I've known for years. I've reviewed their code; they've reviewed mine. We'd argued, commiserated, and bought each other whiskey. They've helped shape the Python/WSGI/Django ecosystems. Their tools embody the best practices from our communities because they were there when those practices were debated and determined.
This is by no means a slight on Heroku's staff: I've met people from their team, as well, and they're wicked smart, very motivated, and highly focused on delivering an awesome product. Which it is! But as a company, Heroku is going to have to do some work to get to the same level of trust as the companies that have grown organically out of our community.
* Deploying a Python stack on Heroku is something of a small pain: there are few defaults, so you're left to do most of it by hand.
Take, for example, the bits from the Heroku/Django tutorial about configuring Celery. Not a lot of work, to be sure, but it is some work, and the result won't perform well at all (it uses a database for message transport instead of something that'll perform better). On mot Python-specific PaaS offerings, a single line in a config file (or checkbox in a web UI) gets you a fully-configured, optimized, ready-to-roll Celery setup.
I'm pretty damn good at deploying Python setups. I'm not going to use a PaaS offering unless it provides similar features to a hand-rolled setup for less work/money.
* On Heroku, I'm a small fish in a large pond. I'm the weird customer doing Python, but the bulk of their cash (presumably) comes in from their Ruby customers. Deploying Python on Heroku feels rough around the edges. A trivial example is the broken links in the Python documentation: it's no big deal, and easily fixed, but the many similar rough edges send the message that Python support is a hobby project, a sideline to the main business.
This will probably be fixed with time, I think, but again: it's going to be quite a while until I feel I'll get the same level of support on Heroku as on a tool that comes out of the Python community.
* Finally, Heroku really expensive compared to most of the Python-specific offerings. Maybe a typical Django site features more "pieces" than a typical Ruby one (???) -- a standard "smallish" site of mine will consist of Django, a task queue (Celery), a search server (Solr), a non-relational DB (Redis), and a relational database (PostgreSQL).
On Heroku, this will easily run me $100/mo. By comparison, I'm paying between $15/mo and $50/mo for sites of similar size on some of Heroku's competitors.
So all this to say: I welcome Heroku to this space; more competition is awesome. It'll really make life better for every Python web dev. But it's going to take some serious work to convince me to switch.
[1] I'm really sorry to be obtuse here, but I'm trying to be careful not to write anything that might be construed as an endorsement. As a Django core dev I don't feel comfortable playing favorites (just look at the drama that ensued when GvR had the temerity to say that he liked Django...)
But as the back pain kept getting worse, I finally decided to give the standing desk thing a try about 3 weeks ago. I expected my back to start feeling better, and it did -- great! But the unexpected benefit has been vastly increased focus: I somehow feel much more motivated standing than sitting. There's something that feels incredibly silly about watching YouTube or reading Hacker News while standing, and so I just don't do it. I've been more productive these last 3 weeks than I've been in a long, long time.
Perhaps it's just the novelty of a new situation; who knows. But I'm going to stick with it, for now.
Hopefully over time Fulcrum can differentiate itself and compete on features, not on price.
Good call - I just did. There's a "download" link in the sidebar now.
My brain's having a lot of trouble with this. I'd be really interesting in the reasoning that went into re-mapping a color usually used for "stop" or "delete" or "danger" onto "create".
I'm certainly not going to speak on behalf of every open source project. But the ones I work on? This couldn't be farther from the truth.
If you're a designer and want to contribute to Django PLEASE hop on django-developers or get in touch. I would love to have you.
[I think there's a kernel of truth in iamcalledrob's comment. Designers and developers often speak different languages, and I think this can often make designers feel unwelcome. I've neither the space nor the time to expand on this thought, however.]
Password reset is here: https://www.djangoproject.com/accounts/password/reset/
Thanks for clarifying; the pricing page made it seem like you'd need to upgrade to get SSL, hence my rant. I'll edit the parent a bit to make it less hostile. Sorry about the misunderstanding!
I'll try to explain:
I'm a reasonably skilled ops guy, so for big stuff I'm still going to want the control that running my own stack gets me. I suspect most larger customers will be the same: the advantage of a hosted platform over one I design and build isn't proven yet.
But I also have a bunch of tiny one-offs that need homes, so a PaaS offering is super-attractive. I can pretty easily deploy a couple-three of those things on a EC2 or Rackspace instance, so once you factor in my time I'm probably looking at $5-10/mo per app being an attractive price point. So it's damned hard to argument with free!
But — and here's the big thing that'll keep me off Dotcloud — if those small apps get a bit bigger, then what? Well, on my hand-rolled VPS my cost'll double or maybe triple, so I'm looking at say $30/mo. On Dotcloud? I'd jump right to $100/mo.
I suspect this "jump" — and the unknown and likely huge jump that follows when I go from "pro" to "enterprise" — will keep most casual, smallish hobbyest or lifestyle businesses away.
So if large projects stay away, and small projects stay away... what's left?
My guess is over time we'll discover that utility-based billing is going to be the model that makes the most sense for PaaS and that artificial tiers will go the way of the dodo.
[Edit: the following "PS" was a bit hasty; I misread the pricing detail page. Leaving it here because otherwise the discussion below doesn't make sense, but I'M WRONG and THE FOLLOWING DOESN'T APPLY TO DOTCLOUD.]
PS: Oh yeah, one other thing:
Given all we know about web security, having SSL as a value-add makes you look irresponsible at best, and manipulative, opportunistic, unethical, and idiotic at worst. SSL isn't optional, people, and I won't give my patronage to anyone who doesn't get that.
We're workin' on it, though, so if you'd like to help out I'd really appreciate it!
[] The length has nearly doubled in the last two years.
And, of course many, many said similar things about AirBnB -- "couldn't a thief just book a room for the night and then make off with the TV?" -- and that's proven not to be much of an issue in practice.
Ugh, that's a shitty attitude. I think one of the good things about HN is that people here usually give each other the benefit of the doubt and assume good intentions. Lobbing accusations of bias around are a good way to kill that friendly tone. Unless you've got actual proof of bias perhaps you could keep your accusations to yourself next time?
In the first instance, the person in question was my direct boss and was responsible for reviewing my code. He'd routinely call me an idiot, a retard, etc., and during meetings he'd often say things like "no, we can't give that to Jacob - he'll just fuck it up." Now, in his defense I was a pretty shitty developer at the time, but I do believe there are more constructive ways of reviewing code than calling the author a retard. I dealt with it for a few months, and finally asked his boss to transfer one of us. When I explained the reasons, this person was fired.
In the second case, my coworker was showing up to work drunk, yelling and cursing at coworkers, and routinely threatened violence -- "I'm gonna beat your ass if you don't shut the fuck up" was, I believe, a common line. Once he threw a chair through a window halfway through a (technical) meeting. Again I was too much of a coward to call him on his behavior directly, but yes I spoke to first my boss, then his, then the owner of the company. Nothing changed, so ultimately I quit.
In retrospect I certainly didn't behave perfectly: I should have confronted the behavior directly, and I should have made clear what my expectations were with regard to a professional working environment. But I was young, and all in all I'm proud of myself for not tolerating abuse (even if I didn't go about it quite right).
I will call out antisocial behavior, enforce professionalism in the communities where I have the power to do, and leave the communities that cannot at least offer civility.
In other words, if someone's being a jerk, we should call them on it. I didn't mean to suggest dividing the world into "assholes" and "good people" — clearly there's a spectrum, and clearly even saints have bad days. And I certainly didn't mean we should ostracize people at the first sign of shitty behavior.
But if someone's abusive, and they refuse to moderate their behavior, then either they need to leave or I will. I just can't accept that allowing abusive behavior is the price we have to pay for good code.
You bet your ass I asked for him to be fired. He wasn't, so I quit.
I'm very sorry that my post rubbed you the wrong way. My intention is simply to suggest that we shouldn't tolerate antisocial behavior in our communities, and that we should ask those behaving badly to stop. Do you disagree?