It’s just data
Automated Publishing with Instant Articles
<description> A summary of your article, in plain text form.
<pubDate> The date of the article’s publication, in ISO-8601 format.
Related: plaintext, May Day, June Bug, 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 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. 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:
I’ve released Ruby2JS version 2.0. Key new features:
The Whimsy Agenda 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 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.
Jeremy Ashkenas: “work towards building a language that is to ES6 as CoffeeScript is to ES5”… close, but—do it for [ES6+HTML+CSS], and you’ll win ;)
It occurs to me that there is a shortcut available. Let a library like React replace [ES6+HTML+CSS]. Then build a DSL for that library.
Brian Leroux: ES6 and Web Components
My take is that this talk lumps React in with others based on when it was introduced; but that it is fundamentally different from, say Angular.js as Angular.js is from jQuery.
I have been telling all non-IBMers to not use my ibm.com email address for years, but this advice is routinely ignored. I’ve repeated the reaons behind why I ask this enough times that it makes sense for me to post the reasons in one place so that I can point to it.
Having determined that Angular.js is overkill for my blog rewrite, I started looking more closely at React. It occurred to me that I could do better than JSX, so I wrote a Ruby2JS filter. Compare for yourself.
URL parsers consume URLs and generate URIs. Such URIs are not RFC 3986 complaint. I’d like to fix that.
I have test results that show that there is much work to be done.
The most likely path forward at this point is to get representatives from browser vendors into a room and go through these results and make recommendations. This likely will happen in the spring, and in the SF Bay Area. With that in place, I can work with authors of libraries in popular programming languages to produce web-compatible versions. This work will take the form of bug reports, patches, or — when required — authoring new libraries.
I’ve downloaded the multi-part zip archive for IE11 on Win10 for VirtualBox on OS/X from modern.ie. I’ve downloaded the single-file archive on both OS/X and Linux. I’ve verified the md5 signatures for each. Yet each time, when I try to unzip the result, I fail.
While I’m clearly late to the party, I’ve already become a huge fan of capybara and phantomjs. I’m now using both with my previously mentioned blogging software rewrite.
My original intent was to aggressively prune unnecessary function with the intent of producing a more maintainable result, but with the ability to have automated acceptance tests, this is now less of a concern.
Looks like Why I quit OS X struck a nerve — it is currently down (see web archive). Also good: Apple has lost the functional high ground.
I particularly like the comment that “It just works” was never completely true. My experience is that when working with open source codebases, doing so on an Linux operating system comes much closer to “It just works” than doing so on any other.
Not rack’s fault, but Sinatra hasn’t released in a while. Problem has been known since July, and a fix was merged into master in August. One possible workaround has been posted. An alternate workaround:
module Rack
class ShowExceptions
alias_method :old_pretty, :pretty
def pretty(*args)
result = old_pretty(*args)
def result.join; self; end
def result.each(&block); block.call(self); end
result
end
end
end
I’ve clearly been neglecting my little spot on the web.
It has gotten so bad that Brendan Eich had to link to a web archive copy of a page of mine. I must say, however, that it is very ironic and amusing that it is was that particular page. General outline of my current approach:
I’ve been having fun working on the URL Living Standard. All good things must come to an end. Now it is time to spell out a path forward.
pegurl.js is the result of two days worth of work. While it is undoubtedly buggy and incomplete, it does pass 255 out of 256 tests and that last test is wrong. For comparison: results from other user agents.
Current work products and future work
I’ve been looking into differences between the WHATWG URL Living Standard and the combination of RFC 3986 and RFC 3987. I’ve come up with an indirect but effective way to identify the differences using urltestdata.txt and addressable.
Dreamhost upgraded my server to Ubuntu 12.04. I noticed things breaking in preparation for the move, and things that broke after the move. If you see something not working correctly, please let me know.