kaveri

4 ms·

1.
by kaveri 17y ago
The template system rocks if you like handcuffs on your templates - and for some projects that may be the case. Otherwise it's crippled in comparison to Jinja or Mako - with large amounts of un-Pythonic boilerplate if you want to write temp
2.
by kaveri 17y ago
Good point raised in one of the comments: why not have a giant wind platform out at sea to generate the hydrogen, and have tankers come and offload/replace the hydrogen tanks on a continuous basis ?
3.
by kaveri 17y ago
I think the point being made is that it has an API similar to the Django ORM, not that it is an ORM.
4.
by kaveri 17y ago
Link to petition ?
5.
by kaveri 17y ago
I'm not sure about the causes, but it seems in the UK for example that social mobility has decreased in the past few decades compared to the 1960s. A big part of that has been the disaster of comprehensive education - the old grammar school
6.
by kaveri 17y ago
Absolutely agree with you on most of the points. A couple of quibbles - Django now supports multiple databases (as of 1.2) and South ( http://south.aeracode.org/ ) is more or less the default migration tool nowadays and is OK for most jobs.
7.
by kaveri 17y ago
Who said anything about whining ? It is your duty as a professional to promote what you consider the best tool for the job. A spade isn't much good if your job is to rake some leaves. Of course your advice might be overruled for perfectly v
8.
by kaveri 17y ago
There's still no reason to limit post size because Twitter does - title and shortened URL to the original post works fine.
9.
by kaveri 17y ago
It's a great idea in theory, the problem is that corporate designs go through ten different committees each wanting something different, so you end up with an unusable mess.
10.
by kaveri 17y ago
Very nicely done. I take it this is running on Google App Engine ? (Just a guess, based on the Google Account signup). No need to market it as just for rural locations. In the UK we have Gumtree for example, which is a serious competitor to
11.
by kaveri 17y ago
Django != Python and Rails != Ruby. There are other solutions in either language that might suit your project better.
12.
by kaveri 17y ago
Language is a big factor: English is the first foreign language taught in European schools (and the mother language of most UK and Irish citizens); Americans are traditionally poor at foreign languages, so are less likely to move to a count
13.
by kaveri 17y ago
True, but as a marketable name bluebream leaves a lot to be desired...it doesn't roll off the tongue very well. And what was with the weird YouTube video with the wedding song ? A name change is a good idea - there was too much confusion be
14.
Zope3 renamed BlueBream(pypi.python.org)
2 points by kaveri 17y ago|2 comments
15.
by kaveri 17y ago
At the end of the day you succeed (in the larger world, not the Silicon Valley echo chamber) by having a great (or even good enough) product that hits the market at the right time, and can pretty much grow because you have customers willing
16.
by kaveri 17y ago
Maybe because Luke was so powerful in the Force and Leia wasn't ?
17.
by kaveri 17y ago
Django forms (and their non-Django counterpart, WTForms) are very easy to use, with a declarative syntax. The advantage is that validation is decoupled from models. Often you need to handle validation which doesn't directly involve a single
18.
by kaveri 17y ago
If you are using MVC maybe. ASP.NET WebForms and postback add tons of crap to the HTML.
19.
by kaveri 17y ago
what other technologies are you using apart from MongoDB ?
20.
by kaveri 17y ago
To an American, perhaps. Ask someone from China the same question.
21.
by kaveri 17y ago
Updated my Advent laptop from Jaunty a week ago, no significant issues. Can't say it's massively better than Jaunty in terms of features or performance though.
22.
by kaveri 17y ago
Probably from some idiot MBA. Now there's a commodity.
23.
by kaveri 17y ago
I get the impression Pylons tries to be the "anti-Django" inverting the NIH attitude of Django and trying to be all things to all developers. The end result however is a huge number of dependencies and options that make installation and set
24.
by kaveri 17y ago
That's the problem - when Rails bloggers come across as over-hormonal 15 year olds (as this blogger does) it casts doubt on the maturity of the community as a whole. Why not try dumping this silly, dated "rock star programmer" attitude and
25.
by kaveri 17y ago
I think this points at a general problem with developers. Developers assume that just because "it works" then non-code issues are irrelevant. In truth, people choose frameworks and languages not just because of the code and career opportuni
26.
by kaveri 18y ago
Internet Explorer ?
27.
by kaveri 18y ago
Enterprise applications also have a smaller number of users, so the feedback pool is smaller: you don't get the same number of bug reports feeding back into your development cycle as you would with a widely-used web or shrink-wrap applicati
28.
by kaveri 18y ago
"The investor tells me, "Oh, this is fine. Treat your stock like Monopoly money and give it to the freelancers."" This has happened to me on several occasions. Where do startups get the idea they can rip off freelancers with worthless stock