Mike Amundsen: I have the even greater privilege of working with Leonard and Sam on a new book - “RESTful Web APIs”. It’s scheduled for completion by the end of Q1 2013 and should be available soon after.
While I’m formally on this project, I’m not planning on doing any writing beyond possibly an introduction. As Mike put it, this book isn’t merely a 2nd edition, but rather more of a “follow-up” seven years on. I’m very much looking forward to seeing where Mike can help Leonard take this work.
Peter Linss: I really want to see the TAG be more involved with the rest of the working groups at the W3C
I’ll come out and say it. I’m a skeptic. I’ll note that the three out of the four of the “TAG reformists” statements do NOT list getting involved with the rest of the working groups at the W3C as a goal. What am I missing?
It started with two notifications we received via postal mail. First Time Warner was going to start charging us rent for an outdated cable modem. Second they were going to drop a number of cable channels, but if I acted now, I could request a digital adapter which would allow me to watch these channels on exactly one TV.
This process has turned a fairly complacent Time Warner customer into one that is actively seeking alternatives. In looking around, I see plenty of promo offers of more service than I have (basic cable and basic internet) for considerably less than I am currently paying. I am OK with waiting an hour or more for an answer, but I am not OK with having to be on hold for that entire time. And I’m definitely not OK with renting a separate box per device simply to get access.
This process has turned a fairly complacent Time Warner customer into one that is actively seeking alternatives. So I am beginning my research: starting with looking for alternatives to cable TV. What I want is a single plan that allows me to watch whatever I want wherever I want. I am OK with upgrading my devices as long as we are talking about a purchase not a lease.
Any pointers people might leave in comments would be appreciated.
It makes sense for authors who may produce a handful of pages to be processed by an uncountable number of imperfect tools to agree on restrictions that may go well behond the minimal logical consequences from normative text elsewhere if those restrictions increase the odds of the document produced being correctly processed.
Such restrictions are not a bad thing. In fact, such restrictions are very much a good thing.
Doug Sheppers: WebPlatform.org will have accurate, up-to-date, comprehensive references and tutorials for every part of client-side development and design, with quirks and bugs revealed and explained. It will have in-depth indicators of browser support and interoperability, with links to tests for specific features. It will feature discussions and script libraries for cutting-edge features at various states of implementation or standardization, with the opportunity to give feedback into the process before the features are locked down. It will have features to let you experiment with and share code snippets, examples, and solutions. It will have an API to access the structured information for easy reuse. It will have resources for teachers to help them train their students with critical skills. It will have information you just can’t get anywhere else, and it will have it all in one place.
Robin Berjon: Looking at it in terms of rebounds, plot twists, nurtured healing and abandonment, love and betrayal, strife, toil, stunning victories, dispersions and last minute rallies the only thing that distinguishes HTML’s history from a charts-topping teenage fantasy saga seems to be the lack of vampires. And even then, were vampires around I’m not sure we’d notice them for all the action.
Bill McCoy: EPUB in effect takes the Wild, Wild Web and tames it. EPUB for example requires use of the XML serialization of HTML5 (XHTML5), rather than “Tag Soup” aka “Street” HTML. This means that EPUB content, unlike arbitrary web pages, can be reliably created and manipulated with XML tool chains. EPUB defined Reading System conformance more tightly than HTML5 defines for browser User Agents, pinning down things that are under-specified in the union of W3C standards. [via Patrick Mueller]
Dan Webb: The first thing that you might notice is that permalink URLs are now simpler: they no longer use the hashbang (#!). While hashbang-style URLs have a handful of limitations, our primary reason for this change is to improve initial page-load performance.
Usage: add wunderbar and nokogiri to your Gemfile and run bundle install. Template extensions supported are _html and _json. Examples: view, layout, json.
Note that as Rails layouts and views are predicated on the assumption that output is produced by concatenating text, one must use _ yield instead of simply yield. On the plus side, Wunderbar will note when the first argument to a call which creates an element is html_safe? and will treat it as markup.
The result is a lot like Markaby, except you get to be/have to be explicit when you are creating a tag. In this demo, there is no logic, so the benefits of doing so are less clear, but include you being able to use tags that aren’t known to Markaby, like the ones that were added in HTML5. Both inline and views are supported, but support for layouts has yet to be added.
This site was hacked. A reader of the site noted that Google’s index of this site had been co-opted by dubious pharmaceutical offerings. I’ll gladly thank that individual publicly if they give me permission to do so; but my email reply got bounced as spam.
The immediate culprit was the addition of the following lines to a number of .htaccess files
I’ve integrated jbuilder like functionality into Wunderbar. Key differences? A DSL that doesn’t suck, and output that isn’t ugly.
To harsh? You be the judge. Compare jbuilder ("json dot bar json bar json dot child bang") vs Wunderbar ("underbar underbar underbar underbar").
As to the output? Don’t be fooled by the jbuilder readme. In actuality is no unnecessary whitespace in the output. That’s good if you are bandwidth limited. Not so good when viewing the XHR traffic via firebug...
I now have an open fit hearing aid device for my left ear. That ear has experienced tinnitus for approximately 10 years. An ABR test given at that time found nothing. My hearing loss is primarily in the 2000 Hz and above.
Last night, I went to dinner with my wife in a noisy restaurant and I could hear every word she said.
I added a simple wiki as a demo for WunderBar. It demonstrates shelling out to handing multiple URIs, handing get/post, dealing with both unescaped text and markup, shelling out to commands, AJAX, CSS, jQuery.
The demo relies on git and rDiscount to do the version control and markup processing. It also doesn’t have all the features that you would expect from a wiki, such as conflict detection and resolution.
Jeni Tennison: it became clear that there were several places where having some kind of standard method for building a tree from non-well-formed XML would be beneficial...So the XML Error Recovery Community Group has been set up for this purpose.
Intertwingly.net is moving to DreamHost. I’m sure that every one of my scripts has hard coded paths or depend on the server being in EST/EDT or will otherwise break for unanticipated (but in retrospect entirely obvious) reasons. I don’t believe that I will lose any email in the process, but you never know.
My @apache.org email address will not be affected by this move.
Alex, I think you need to move up the food chain a little.
The root-cause is vendor-driven advocacy directed at content producers which encourages them to produce compelling content using experimental features. Everything else is consequences. If you believe that those consequences are CRAZY, then you must conclude that the root-cause is CRAZY.
Clearly if you want to develop a real web application, you need a router, a templating language, ability to separate out your model, view, and controller, scalability, and much more.
However, at times this is both too much, and yet not enough. I find that I write a lot of scripts that do report generation, execution of shell commands, and the like, and in many cases would like to present a richer output than plain text: things like tables, fonts, and most importantly hypertext links. I’ve been extracting some of the common logic from these scripts out into a library, and recently have started refactoring that library.
Nat Torkington: Don’t wait for the time machine, because we’re never going to invent something that returns you to 1965 when copying was hard and you could treat the customer’s convenience with contempt.