tomchristie

10 ms·

61.
by tomchristie 11y ago
> you're obviously going to want to trade FIRST on those fundamentals .. right? Cause whoever does is going to win the day If you're only trading long term, then sub-second differences are essentially irrelevant. I think there&
62.
by tomchristie 11y ago
From the source: "CCE agents identified 24 times more mock passengers (66%; 60% at Month 1 and 72% at Month 6) than suspicious signs agents (3%; 6% at Month 1 and 0% at Month 6)" ... "base rates of identification of genuine t
63.
by tomchristie 11y ago
The paper itself: http://www.apa.org/pubs/journals/releases/xge-0000030.pdf
64.
Django REST framework 3.2 released(django-rest-framework.org)
9 points by tomchristie 11y ago|0 comments
65.
by tomchristie 11y ago
> There are already a number of players doing exactly what GitHub does There are folks delivering similar services, but nothing remotely of the same standard. > there isn't that much that ties a project to GitHub They don't
66.
by tomchristie 11y ago
"The problem is scaling your database, keeping your data secure, and iterating to meet business goals with a growing codebase and infrastructure. A mess of stored procedures would restrain you from doing all three." Perfectly expr
67.
by tomchristie 11y ago
> what's the difference? The difference is that when you're behind the wheel of a car your in charge of a machine that can very easily kill other people. > the chance of major injuries is radically lower than when riding a b
68.
by tomchristie 11y ago
> I fall squarely in the camp that says they are just not suitable vehicles to share the road with other occupants Here's the converse: * Bicycles the cause of essentially 0% of road deaths. * Motorized vehicles are the cause of ess
69.
by tomchristie 12y ago
> I-JSON doesn't appear to solve this problem It's not within the scope of what I-JSON is intended to address. This is a more formally specified and slightly more constrained variation of the existing JSON spec. Adding new data
70.
by tomchristie 12y ago
Oh right, writable nested serializations, sure. I won't rehash the reasons that we don't support that in core (ill defined what behavior the user should expect) but yeah it'd still be good to have a third party package that d
71.
by tomchristie 12y ago
Well actually no, it'd be very feasible to re-write Django REST framework as a framework agnostic core. I've done a bit of exploratory work with this and there's nothing there that I think would be particularly fiddly. The ma
72.
by tomchristie 12y ago
At the moment it's on hold - I certainly won't be doing anything with Flask until the Kickstarter work is all complete. I'm undecided after that. It'd be interesting to get your opinion on what your take would be on usin
73.
by tomchristie 12y ago
Thanks Alex, I think that's a great point. Please do feel free to follow this up by raising an issue on the repository - it'd be good to talk through some specifics about areas to improve.
74.
by tomchristie 12y ago
The 3.0 release notes are the place to start for looking at upgrading. They go into quite a bit of detail about this.
75.
by tomchristie 12y ago
Broadly, we aiming for it to be a mature, sustainable and well-supported general purpose Web API framework. We tend to be fairly aggressive about keeping the scope manageable in order to keep to that. For example 3.1 moves some functionalit
76.
by tomchristie 12y ago
Of course you can use many to many fields with ModelSerializer. I'm not sure what you mean here, but I'd suggest opening an issue if you believe there's a problem - we're pretty comprehensive about dealing with incoming
77.
Django REST framework 3.1 released(django-rest-framework.org)
179 points by tomchristie 12y ago|41 comments
78.
by tomchristie 12y ago
Note that the full copy is now available to purchase in both ebook and hardcopy: http://shop.oreilly.com/product/0636920033158.do (No side-interest here, just found it confusing that the page mentioned "hardcopy
79.
Sustainable open source management(dabapps.com)
1 points by tomchristie 12y ago|0 comments
80.
by tomchristie 12y ago
The model / model manager layer is the right place at which to design your state changing API. REST framework absolutely you to work with the grain there. Some good practice I'd recommend... * Write the `create()` and/or `upd
81.
by tomchristie 12y ago
I'm sure they'd appreciate any feedback & examples on accessibility issues. If you've got some time consider raising it on the issue tracker.
82.
by tomchristie 12y ago
Flask API is certainly on pause while 3.1 and 3.2 are addressed yes. After that it depends on what I feel is the most productive use of my time. Perhaps general purpose Python API tooling, that includes Flask as one of the options, or perha
83.
by tomchristie 12y ago
I guess from my side it feels like it's something of a different business relationship to the usual case. There's enough trust from backers that over-funding will ensure a better product, even when the details of that are underspe
84.
by tomchristie 12y ago
Yes it does, but probably best to take this sort of thing onto the discussion group... https://groups.google.com/forum/#!forum/django-rest-framewor...
85.
by tomchristie 12y ago
> Any update on how the money was spent? So this is only 1/3 of the Kickstarter to date. The two stretch goals are planned as releases 3.1 and 3.2. We were significantly overfunded, and I'll treat the extra time/budget fle
86.
by tomchristie 12y ago
I'm not sure at the moment, we'll see once the remaining bits of the kickstarter work (releases 3.1 and 3.2) are done and released.
87.
Django REST framework 3.0(django-rest-framework.org)
255 points by tomchristie 12y ago|30 comments
88.
by tomchristie 12y ago
Personally I think they're going to remain strong. More single page apps? Fine, but they still need to be backed by an API and, in most cases, a relational database. Yes there will be more frontend templating, and yes more mature fulle
89.
by tomchristie 12y ago
So, y'know, raise it on their issue tracker. :)
90.
by tomchristie 12y ago
How would you deal with rendering arbitrary form encodings in the browser? A proposal adding support for form submission of arbitrary encodings could be valid, but it'd have to just be a single form input with the data included verba

More ›