mtford

Immediately eaten by a Pterodactyl... lol

There is a 24 hour public tourist webcam - I had Claude pull all the interesting footage and shots: https://claude.ai/artifact/KQRxeaEpmtmwT8HwzhHRUt

This website behaves very strangely... scroll hijack. Also everything is suuuuuper stretched out.

That and the "The boring deck is dead. One file killed it."

It makes me kinda tense up - I've become almost allergic to it. Kinda interesting really.

This happens all the time in tech. A few years ago everybody got excited about static websites and server-side rendering as if we hadn't been doing that with PHP long ago.

This is really cool! I'm pumped for anything that makes it easier to review generated code. I, like many people these days, am searching for ways to stay close to the code whilst not being overwhelmed... and as a visual personal i like your idea to semantically link code to diagrams

I've been working on a (semi-)similar thing, a TUI for narrative code reviews - https://github.com/mtford90/revue - the idea being to generate "guided tours" of a change as opposed to a big wall of files.

Very impressive, well done!

I feel ya buddy - come and join the wacky world of front end development where these things matter less ;)

Isn't Opera at v24 now?

Hi Luna, from my perspective async.js is about control flow whereas operations.js is about creating well defined operations that can be composed, queued, cancelled, reused and monitored. It's more of a workhorse.

Yeah, operations.js is meant for more complex scenarios than that. For example if we were spawning hundreds of operations that interact with networks/file systems. We can set an upper limit on concurrent operations using queues and express complex dependencies between them, compose them and cancel them.

I'm a huge inconsolata fan myself.

Many thanks for this! This has been a thorn in my side for a while but never got round to doing anything about it...

I know a few of the investment banks have this kind of thing internally, implemented as a DAG: http://en.wikipedia.org/wiki/Directed_acyclic_graph. Cool stuff.

Nice... I did make an attempt to filter out sensitive stuff but clearly did a bad job. Thanks for letting me know. I will eventually introduce a demo app rather than my own site.

Sounds interesting... i'll take a look. The fact that its UDP would be helpful in avoiding the need for a dependency on celery/message queues.

What's it like in terms of getting the data back out?

Tbh, probably fairly bad atm. I haven't done anything empirical but atm Silk will create a record for every SQL query executed during the request/response cycle effectively doubling the number of queries. Not only that but it also saves down any non-binary HTTP body to a TextField, and this isn't yet configurable.

I think the Elasticsearch/Celery option is a good shout if this were to ever be used in production. Celery would help with the issue of response time but it wouldn't solve the load impact on the database (although I guess could also configure a different SQL database in Django).

I will certainly do some investigation into this at some point :)

That's not a bad idea, it would probably be more natural than the rigid filters that are currently in place for the requests and profiles. As far as having this running in prod I've only really thought of siphoning off the results to celery or something similar to avoid impacting response time, but a spray and pray at Elasticsearch would work just as well.

What's nice about the current setup is that it takes very little effort to get up and running but I suppose could make that configurable...

Sure just added this to the intro. You can download via https://github.com/mtford90/silk/releases or install through pip install django-silk

Yep django-toolbar is great! My aim with this was, like you said, to provide the history of multiple requests, but also to provide finer-grained profiling with the decorator and context manager. Not only do they capture execution time but they also capture the queries that were executed whilst they were active. The aim was extra visibility all round really.

Not at the moment. Silk doesn't actually save anything down until right at the end of the cycle i.e. in process_response of the middleware. Had to do this to avoid issues with atomic transactions. I certainly don't mind adding this as a feature if people would find that useful - perhaps by detecting that no request is in process and then commiting profile data on the fly if that's the case.

Thats a great question... that def shouldn't be there. render_to_response is actually dynamically profiled i.e. the decorator is applied at runtime via configuration in settings.py. This looks like its probably a bug with that. Cheers, will look into it

Never. To upgrade to Mavericks I just created a USB installer using unibeast, booted from USB and followed the usual OSX install process. All my files and apps were left untouched.

Yep, just upgraded mine to Mavericks and had absolutely no issues. You just need to make sure you buy components that are tried and tested by the hackintosh community.