Unsure whether you’re using the <article>
element correctly? Wonder no longer, there is a tool to help you out: waterpigs.co.uk/services/test-article #html #web #dev
Unsure whether you’re using the <article>
element correctly? Wonder no longer, there is a tool to help you out: waterpigs.co.uk/services/test-article #html #web #dev
New in this version of #taproot:
The local maximum has been overcome, for now. There is still much to do.
psysh.org is the #php REPL shell we have been waiting for. How to start an interactive shell with a given context:
<?php
require 'vendor/autoload.php';
$app = require 'src/app.php';
Psy\Shell::debug(['app' => $app]);
Supports readline, pcntl, registering custom commands, automatic semicolon insertion, clean+concise string representations of evaluated values. Amazing work Justin Hileman!
Had many basic software development lessons hammered in by personal experience over the last couple of years: hierarchy bad. side effects bad. many moving parts bad. undue complexity bad. inconsistency bad. SQL databases fragile. always be reducing.
It’s amazing just how seductive complex, unproductive tools can be. Successfully overcome+abandoned:
PHP remains productive and speedy (with composer, delightful dependency management), python nice with some irritations. jQuery useful when absolutely necessary, plain #js with small libraries loaded via requirejs handle most progressive enhancement concisely. node.js nice for some things, preferring go’s approach to async programming but still not much everyday need for it.
Avoiding middlemen: LESS, SASS, Coffeescript. Unnecessary for most of my work, and more moving parts is bad.
Now bothering me is the frameworky nonsense accumulating in #taproot. Need to cleanse.
Cut a process which was taking 20 mins down to 40 seconds — moral of the story is: building systems which allow you to see the system work in real-time and get an intuitive sense for how long things take is more effective than poring over SQL logs trying to figure out what on earth’s going on in retrospect.
@w03_ recursive functions are fun. Once you’ve figured them, closures and first-class functions out you’re pretty much there :)
.@john_nye all the stores I’ve submitted extensions to do manual reviews. Mozilla:
Safari and Opera have fairly basic, boring forms for uploading stuff, and are extremely picky and unclear about exact image sizes for screenshots and icons. There’s also no “review in progress” page, but otherwise acceptable.
Obviously I’ve not been able to actually submit an extension to the Chrome store, but I’d hope that it’s a damned good experience for $5. If they are doing automatic reviews, then the price becomes even more counter-intuitve. If they’ve automated it, surely it’s cheaper and quicker for them?
.Jack Way no other extension store (mozilla, apple, opera) demands payment, or requires it for verification. Also, Mozilla offers a far superior extension upload experience. Google has no excuse :)
And the #js lesson of the day is: bean.fire(el, 'click')
doesn’t work in Firefox Nightly, but turns out it’s unnecessary, because HTMLElement.click()
does exactly the same thing and already works cross-browser. Always use the browser-native APIs if you can.
I get a little annoyed at #python every now and again (grr package management) but then I come across things like nested tuple unpacking which are just so lovely they make up for it:
for i, (key, value) in enumerate(list_of_tuples):
print i, key, value
I just faked having a task queue for #taproot #indieweb note posting tasks using Symfony HttpKernel::terminate()
and it was the easiest thing ever.
Instances or subclasses of HttpKernel
have a terminate($request, $response)
method which, if called in the front controller after $response->send();
triggers a kernel.terminate
event on the app’s event dispatcher. Listeners attached to this event carry out their work after the content has been sent to the client, making it the perfect place to put time-consuming things like POSSE and webmention sending.
Once you’ve created your new content and it’s ready to be sent to the client, create a new closure which carries out all the the time consuming stuff and attach it as a listener to your event dispatcher, like this:
$dispatcher->addListener('kernel.terminate', function() use ($note) {
$note = sendPosse($note);
sendWebmentions($note);
$note->save();
}
Then, provided you’re calling $kernel->terminate($req, $res);
in index.php, your callback will get executed after the response has been sent to the client.
If you’re not using HttpKernel and HttpFoundation, the exact same behaviour can of course be carried out in pure PHP — just let the client know you’ve finished sending content and execute code after that. Check out these resources to learn more about how to do this:
fastcgi_finish_request()
flush()
HttpFoundation\Request::send()
as a sample implementationFurther ideas: if the time consuming tasks alter the content which will be shown in any way, set a header or something to let the client side know that async stuff is happening. It could then re-fetch the content after a few seconds and update it.
Sure, this isn’t as elegant as a message queue. But as I showed, it’s super easy and portable, requiring the addition of three or four lines of code.
Having fun with tour.golang.org/#35
MDN says FF has “implemented” the SVG text module, then goes on to list 13 presentation attributes which “don’t work”. How exactly does that count as implementing the module? Grr. This is why @supports
is doomed.
Are there any languages with datatypes with built in version control? Would be pretty great for debugging.
Just in case anyone was wondering, the “HA HA HA SOUP” bookmark in those gifs is this bookmarklet:
document.createTreeWalker
is actually pretty great.
Musing on why we only turn to natural language for defining the behaviour of out applications instead of the business logic itself.
Rough ideas: gist.github.com/barnabywalters/6188240
git pull origin hamster
For the tenth time today.
@briansuda just playing around with SimpleCV, looks like working with Kinect depth data is extremely easy! tutorial.simplecv.org/en/latest/examples/kinect.html