If you don't get your hands slapped at least twice a year, you aren't pushing the boundaries hard enough.
Fly
I went looking for a place to host my ballroom showcase application. I ended up with a job. I start on Monday at [Fly.io](https://fly.io/). as a [Rails Specialist](https://fly.io/jobs/rails-specialist/)
I don't have a firm date yet, but expect to ship a beta in January.
The book will show you how you can largely stay with Rails defaults and can build an application that is roughly 50% HTML, 40% Ruby, 5% CSS, and 5% JS. The resulting application will have the look and feel of a single page web application complete with asynchronous updates.
For those who have not used WSL yet, it is frankly amazing, to this long time Linux user.
Consolidated instructions for running Windows 11 + WSLg + Ubuntu 20.04 + Genie.
Today I recieved a Absentee Ballot application from the [Center of Voter Information](https://www.centerforvoterinformation.org/). It appears legit.
After nearly 20 years away, I found it was surprisingly easy to set up a full development environment on a modern Windows 10 machine. Given a decent browser, terminal, shell, and IDE, the underlying desktop environment turns out not to be much of an impediment.
After nearly 20 years away, I found it was surprisingly easy to set up a full development environment on a modern Windows 10 machine. Given a decent browser, terminal, shell, and IDE, the underlying desktop environment turns out not to be much of an impediment.
Unless I'm missing something, I don't see React often used as middleware. There is a subtle, but important, difference between using React as templates and as middleware.
Chromebook's support Linux now. There are instructions on the web that are incomplete and out of date to switch to Ubuntu. This post pulls much of that information together.
I've migrated my site to [11ty](https://www.11ty.dev/), a static site generator. I've undoubtedly broken many things in the process.
Three mini-demos showing how to implement realtime updates of web pages using WebSockets.
Blending cache and live responses in order to achieve response time goals.
I’m in the process of converting four [Whimsy](https://whimsical.apache.org/) applications from React.js to Vue; and I’m taking a moment to jot down a list of things I like a lot, things I find valuable, things I dislike (but can work around), and things I’m not using.
On balance, so far I like Vue better than React.js (even ignoring licensing issues) or Angular.js, and am optimistic that Vue will continue to improve.
I found myself included in an IBM Resource Action ("RA"). I’m fine, nothing has changed. I’m already working with a non-profit, namely the [Apache Software Foundation](https://www.apache.org/), and find my work there to be very rewarding.
Created by potrace 1.13, written by Peter Selinger 2001-2015 Cache `put` and `match` worked right the first time; cache `keys` not so much. Authentication is a mystery. Outline of future plans, and a call for help.
[Automated Publishing with Instant Articles](https://developers.facebook.com/docs/instant-articles/automated-publishing)
`<description>` A summary of your article, in **plain text** form.
`<pubDate>` The date of the article’s publication, in [ISO-8601 format.](http://en.wikipedia.org/wiki/ISO_8601)
Related: [plaintext](http://www.intertwingly.net/blog/2006/03/28/plaintext), [May Day](http://intertwingly.net/blog/2006/05/01/May-Day), [June Bug](http://intertwingly.net/blog/2006/06/01/June-Bug), [Another Month](http://intertwingly.net/blog/2006/07/14/Another-Month), and numerous others.
the current implementation is a lot more fun to develop and easier to maintain than prior versions. As an example, if it were decided that the moment the secretary clicked the ‘timestamp\` button on the 'Call to order’ page, all comment buttons are to be removed from all windows and all comment modal dialogs are to be closed, this could be implemented using a single if statement as the event is already propagated, and a re-render is already triggered. All that would be required is to change the conditions under which the comment button appears.
The [board agenda tool](https://github.com/rubys/whimsy-agenda#readme) has been tested on Linux, Mac OS/X, Vagrant, and Docker. It contains a suite of tests.
I replaced IE results with Spartan results in my [urltests](https://url.spec.whatwg.org/interop/test-results/). Other than the user agent string, nothing changed.
Following are selected examples where three out of four of the top browsers agree, identified by the odd browser out:
* [Chrome](https://url.spec.whatwg.org/interop/test-results/53d49202f1?select=current&baseline=chrome)
* [Firefox](https://url.spec.whatwg.org/interop/test-results/15341d9fab?select=current&baseline=firefox)
* [Safari](https://url.spec.whatwg.org/interop/test-results/d7d52bebd0?select=current&baseline=safari)
* [Spartan](https://url.spec.whatwg.org/interop/test-results/8bb3c95bce?select=current&baseline=spartan)
I’ve released [Ruby2JS](https://github.com/rubys/ruby2js#readme) version 2.0. Key new features:
* Line comment support. More specifically, comments associated with statements are copied to the output. Comments within statements are still omitted.
* [Source Map](https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit) support. This enables debugging of generated JavaScript using the Ruby source.
The [Whimsy Agenda](https://github.com/rubys/whimsy-agenda#readme) rewrite-in-progress (previously based on Angular.js, now being rebased on React.js) can be used to explore both of these features.
I’ve made a number of updates to the demos. The [tutorial](http://facebook.github.io/react/docs/tutorial.html) demo has been updated to do server side rendering. This means that it is able to be used by clients which either don’t support or have turned off JavaScript.
The second demo is a calendar. Unlike the tutorial which is a single file, this application is organized in a manner more consistent with how I expect projects to be organized.
Nav Bar
-------