This year, I really wanted to work on my output, and I think I’m doing pretty well. Here are some things that I’ve been publishing:
Regular monthly blog posts on yakushima.blog A few posts this year on the Geolonia blog for work However, updates on this personal blog has been not so great – the previous post is the “2023 review” post, after all.
I’ve been updating this blog from 2012, when we officially incorporated Flagship.
I’m sure you have heard of App.net by now. The paid, non-advertisement-supported “live social stream” (read: Twitter). They set a $500,000 goal, and raised more than $800,000 - a clear indicator that some level of demand is there for such a service.
There are two levels of membership, the $50 “User” level and the $100 “Developer” level. A developer account will give you the necessary API keys to build apps that connect to App.
There’s no denying that PHP is not the optimal language. But at least code in good PHP. Here’s my pet peeve for the day:
Relative paths in include(_once)? or require(_once)? statements.
// WRONG require_once("./include_me.php"); // RIGHT require_once(dirname(__FILE__) . "/include_me.php"); Why? Basically, performance. PHP doesn’t look through all its search paths for absolute paths, saving those precious system calls. This effect is compounded when you’re using the APC cache with apc.stat = 0 (it won’t even cache files that are referred to with a relative path)
Basically, do not use text-rendering: optimizeLegibility; with Japanese. At least, not yet. Why not? Here are some examples. The top line has text-rendering: optimizeLegibility; applied, and the bottom line use the browser defaults. As you can probably tell, optimizeLegibility has indeed optimized the legibility, and the type looks much nicer. However, there is a fatal bug in rendering Japanese characters with optimizeLegibility: It seems that the actual optimization is taking
This is what text (more or less) looks like in Windows! Just do: ```css \* { -webkit-font-smoothing: none; } ``` To enable Windows Emulation mode. Great stuff. There’s a few resources about -webkit-font-smoothing in English, but I was wondering what it would look like in Japanese. Here we go. none; おはようございます。僕の名前は敬太郎です
A few days ago, I posted a small JavaScript snippet.
Retina, Please! is that JavaScript snippet on steroids. It is a combination of JavaScript and PHP to allow your Retina users to only download Retina images, while non-Retina users only download the standard-resolution version.
Check it out: https://github.com/keichan34/KKRetinaPlease WordPress Theme Writers: just require it in your functions.php. I may package it into a real plugin later on.
I’ve tested it with CakePHP as well.
Today, we just released the Varnish-ed site I posted about a few days ago. A few things to be careful about in your Varnish deployment (that I had originally overlooked):
Make sure you’re 301 redirecting traffic to your canonical name (http://www.example.com/example to http://example.com/example, or vice versa) Do this redirecting within Varnish! I had strange problems when applying this logic within Apache. If you insist on applying the redirection logic within Apache, you may run into a problem where the Varnish health-check “probes” will fail (and deem your backend “sick”, throwing 503 errors at everyone after the grace period has expired).
Been wondering how to simply retina-ize your website? Put this at the end of your site:
$(function() { try { if (window.matchMedia('(-webkit-min-device-pixel-ratio: 2), (min-device-pixel-ratio: 2)').matches) { $('.autoRetina').each(function(i, e) { var orig_src = $(e).attr('src'); var new_src = orig_src.replace(/^(.*?).(png|jpe?g|gif)$/i, '$1@2x.$2'); $(e).attr('src', new_src); }); } } catch (e) {} }); If you’re on a Retina-equipped device, your images with the autoRetina class will automatically be replaced with their Retina counterparts. If you’re familiar with iOS development, you’ll feel right at home.
TL;DR: Scroll to the bottom for the attached VCL.
No, I’m not talking about the stuff you put on paint to make it last longer.
I’m talking about this amazing piece of software: https://www.varnish-cache.org/
Put simply, Varnish is a “reverse proxy” - a piece of software that goes between the main server and the client. Basically what it does is caches content, so PHP (or whatever backend you’re using) doesn’t need to run for every single request - this makes perfect sense with static content.
As many of you are aware, I have been working for about 6 months now, with 2 other people.
On July 4th, we are pleased to announce that we have officially become a company, Flagship LLC. We have some pretty cool projects lined up in the near future, I’ll be posting updates on our released projects (and maybe if you’re lucky, bits and pieces of unreleased projects) here!
Our goal as a company is multi-fold, but I feel that the most important facet of Flagship is to bring modern web development and standards to Japan.
