jacobian

20 ms·

211.
by jacobian 16y ago
> I genuinely don't know the answers to any of these questions, so I'd really love to know. Well, I don't speak for the project as a whole, so I'm going to just answer personally. I'll try to channel the rest of the core team as best I
212.
by jacobian 16y ago
You're right. I get kinda pissed when people call me "dammed irresponsible" because I can't find the time to solve some technical problems. It implies a sense of entitlement to my time that rubs me the wrong way. You did exactly the right t
213.
by jacobian 16y ago
> It's just damned irresponsible. Since you feel that strongly I can expect to see a patch from you fixing the technical issues I mentioned, right? You write it, I'll commit it. Go.
214.
by jacobian 16y ago
A few things: First, There's no such things as "the django overlords". We're an open source community of thousands. Hundreds contribute. Dozens have commit access. Vry few among these contributors, and none (that I know of) on the commit te
215.
by jacobian 16y ago
I saw a demo of this sort of system c.a. 2000 and it completely blew my mind. Sadly, from what I can see in the video the technology hasn't really changed. This indicates to me that the problems facing car train adoption are the same they w
216.
by jacobian 16y ago
I also suspect — can't prove, but suspect — that there's a higher percentage of "experienced" PyCon attendees than DjangoCon attendees. Most Django developers are fairly new to the platform — heck, the platform's fairly new, relative to Pyt
217.
by jacobian 16y ago
... and then what happens?
218.
by jacobian 16y ago
Let's not. Ideas really are worth nothing when compared to execution. Don't take my word for it: look at successful companies. What're the ideas behind the top 10 Fortune 500 companies? 1. WalMart - a bigger and cheaper convenience st
219.
by jacobian 16y ago
Yes, though only on a single app -- a reasonably high-traffic content site. In this case, PyPy is roughly 10% faster (measured by comparing total view rendering time) but consumes about 2-3x as much RAM. Edit: I should clarify: this site do
220.
by jacobian 16y ago
https://github.com/spacelog/spacelog . -- looks like it's built with Django, Redis, Xapian, and a few other things.
221.
by jacobian 16y ago
Unfortunately right now it is a fork -- django-nonrel makes some internal changes to Django. I'm hoping to reconcile those changes with core at some point so that -nonrel could indeed be just a backend, but we're not there yet.
222.
by jacobian 16y ago
Guh, reading comprehension fail. Thanks for the correction. IANAL either, but I agree that GPL-with-linkage-exception is functionally equivalent to LGPL, so I still think the rest of my comment's correct. Of course, given my track record
223.
by jacobian 16y ago
Sorry, didn't mean to imply that libgit2 couldn't be linked into non-permissively-licensed-code, too (you're right, and it can be linked into any code). I meant to contrast it with GPL-licensed code, which (might) requires re-licensing upon
224.
by jacobian 16y ago
Correction: it's L GPL, with the linkage exception [Edit: I'm wrong. See silentbicycle's comment below]. That's a big difference. Most importantly, it removes any reason to complain about licensing other than dogma, FUD, or ignorance -- li
225.
by jacobian 16y ago
As a Node noob, I have to ask: is the tone of this article indicative of the general attitude and style of the Node community?
226.
by jacobian 16y ago
"Django" doesn't implement new features: people do. In this case, Ben Firshman led a group of about a dozen or more to get generic views refactored, and Carl Meyer took point on the long-requested on_delete work. They had itches to scratc
227.
by jacobian 16y ago
I love SQLAlchemy - it's an amazing piece of software, and I use it often. So why wouldn't I argue for Django to switch? * I love Django's ORM, too. It's far simpler, much easier to teach to new users, and results in code that "scans" b
228.
Buildbot: configuration and architecture(jacobian.org)
4 points by jacobian 16y ago|0 comments
229.
by jacobian 16y ago
Thanks, Ben. I knew there had to be previous discussion that I was missing. Again congrats - this looks like a good thing to me, at least.
230.
by jacobian 16y ago
This looks like good news to me: I've noticed that Pylons and Repoze shared a lot of common ground. Ben and Chris are seriously smart dudes, and I'm excited to see what they come up with when they put their heads together. I am a bit surpri
231.
"Web scale"(jacobian.org)
3 points by jacobian 16y ago|0 comments
232.
by jacobian 16y ago
In my experience with Django, the commit history has been incredibly critical. There's been a good number of bugs that required digging back to nearly the beginning of the public commit history (July 2005). There have even been a few bugs t
233.
by jacobian 16y ago
There's a branch with this feature: http://github.com/goosemo/fabric . The current work's in the "mutliprocessing" branch. I'm using it for a big deploy right now, and it appears to be working well. [edit: fixed my mistake about where the
234.
by jacobian 16y ago
Do you want to legally require that users contribute their modifications back to the project? Then use the GPL. Do you want to encourage the broadest possible use? Then use the BSD/MIT. Please don't choose anything beyond these basic three
235.
by jacobian 16y ago
Like I said, I'm a big PostgreSQL fan. However, I really don't think you're giving the MySQL developers enough credit here. Smart people -- and I maintain that the MySQL developers are a whole hell of a lot smarter than you or I -- can have
236.
by jacobian 16y ago
Studs Terkel's _Working_ is a collection of short essays about people in a whole variety of professions. Most of the writing is people talking about their own jobs in their own words. It -- like all of Studs' work -- is incredible.
237.
by jacobian 16y ago
If you're using Django, and all else being equal, I'd choose PostgreSQL. Nearly all of the core developers (myself included) use PostgreSQL, so Django tends to have better support and we tend to find (and fix) PostgreSQL-related bugs a litt
238.
by jacobian 16y ago
Historically, MySQL has focused on ease of use, speed out-of-the-box, and aimed to be a lightweight, "personal" database (hence the "My"). This fast & light focus meant that certain "BigDB" features (triggers, transactions, ...) fell by
239.
by jacobian 16y ago
I've got to admit to taking a certain guilty pleasure in these numbers after Posterous' last campaign to get switchers. They were pompous, arrogent, and unnecessarily slagged on their competition. I'm pleased to see that such nasty tactics
240.
by jacobian 16y ago
I'm really sorry that you found us to be hostile, and I apologize for any part that I played in that. I hope you believe that hostility isn't at all our intent -- in fact, I try very hard to be open to criticism -- so if you experienced hos

More ›