I temporarily switched to a Chromebook (Pixelbook) after my main machine broke. Setting up Crostini, the Linux container environment, was a little tricky due to limited information available at the time. The process involved enabling developer mode and then activating the Linux apps option in settings. While the Pixelbook is expensive, Chrome OS is a great platform for web development, allowing me to test on various mobile browsers via ARC and utilize Linux apps like Firefox, vim, and VS Code thanks to Crostini. Although Crostini has room for improvement regarding speed, GPU acceleration, and file integration, and the Pixelbook needs more ports, it's exciting to see this technology becoming available on more affordable devices.
I've been exploring the Amazon Web Service API, comparing its REST and SOAP interfaces. Initial impressions suggest the REST API is significantly faster, especially compared to my experiences using the SOAP API with C# and Web References. However, it's worth noting that these observations aren't based on rigorous testing and the different environments (Windows Forms vs. a Linux server on a fast network) could be influencing the perceived performance difference.
This post, part 8 of a series about my first AJAX application, discusses my return to Perl programming after a year of focusing on C# and .Net. I needed to solve cross-domain scripting issues when calling a web service directly from the webpage. My solution involved proxying the request through a Perl script on my server, which also hid my developer tokens. I found Perl's libraries easy to use and effective for this task. Future plans include more Perl scripting to aggregate data from different blogs and web services, leveraging the proxy to combine multiple calls and enhance functionality. I also learned a valuable lesson about using "content()" methods for POST operations instead of the query string.
