While developing a macOS app that needed a lot of file & directory access, as well as a number of curl and command line operations, it struck me that integrating the Perfect framework in my app was a no-brainer idea... this is how.
A challenge was issued recently by Sean Stephens, LassoSoft Inc.'s CEO... and it boils down to this: the person who amasses the most meaninful contribution to Lasso on Rosetta Code in the month of November 2013 will win cold hard cash.
Lasso 9's new "web_request->param" behaves quite differently to action_param found in previous versions of Lasso. It's lower-level, and a little more verbose, but significantly faster - which makes it an obvious tool to master.
A while ago my company experienced a weird problem where users were logging into a system we'd built for a client and yet -inexplicibly- then told them they could not view their content because they were not logged in.
The common theme: every affected user was using Internet Explorer, but that wasn't the whole story.
When Kyle Jessup first introduced to me the concepts of Traits in Lasso 9, I thought "cool, that will be really useful", then promptly forgot about the feature amongst all the other awesome new things in Lasso 9. Many months later I was getting tired of adding a delete method to every object on a sizable project, and I remembered traits!
Ever since, I've been writing less and less code to do the same things - face it, every data object has a common set of things it needs to do, and while this is not going to apply to everything some are easy to abstract.
This week we had a significant escalation in traffic on a particular server. It was not unexpected, however we had changed infrastructure between peak periods and I was keen to see how the new network and virtual machine were coping under the load.
It's an easy thing to do to monitor the processing load on a CentOS server in real time, but without access to Webmin or MRTG I was suddenly without a means to easily see what was happening at the TCP/IP connection level.
Today I was reminded again about the quiet revolution for the web - jQuery.
I was reminded because this morning I was looking at the page load times of this blog, and realized it was not set to cache the twitter feed on the right, so it was getting it fresh every time... server-side. That means the server is doing all the work *before* giving the browser the page.
So rather than just turn on the cache, I wanted to add an option to the plugin to get the twitter feed after the page loads.