The implementation is incomplete, in particular, much of the character encoding logic and IP address parsing is just roughed id at this point.
I’d like to propose a number of changes to the test results; mostly to more closely match existing browser behavior, and perhaps where possible to make the implementation logic less convoluted. Meanwhile, I felt that it was important to have a faithful baseline implemented so that I could experiment with changes and see if there were any unintended consequences to those changes.
More tests! There’s no such thing as too many tests.
Rewrite URL parser. I suspect that the railroad diagrams (converted to bikeshed?) plus the parts of the grammar contained in curly braces expressed in prose would be more comprehensible and maintainable than the current state machine approach.
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.
New laptop for work: MBP 15.4/2.6/16GB/1TBFlash. First time I ever went the Apple route. I did so as I figured with those specs, I could run multiple operating systems simultaneously. So far, so good. I’m using VirtualBox to do so.
Notes for Mac OS X 10.9, Ubuntu 14.04, Windows 8.1, and Red Hat Enterprise Linux 6.5.
Joe Gregorio: But something else has happened over the past ten years; browsers got better. Their support for standards improved, and now there are evergreen browsers: automatically updating browsers, each version more capable and standards compliant than the last. With newer standards like HTML Imports, Object.observe, Promises, and HTML Templates I think it’s time to rethink the model of JS frameworks. There’s no need to invent yet another way to do something, just use HTML+CSS+JS.
I’m curious as to where Joe believes that these features came from.
My current service is “Standard Cable” (70+ channels, no premium ones) and “Standard Internet” (nominally 15 Mbps up, 1 Mbs down). At the end of the month, I will have had basic cable with Time Warner at the same location for 22 contiguous years, and standard Internet for more than half of that.
With that context, today I got in the mail notification that my rates are set to go up by 60% as my “Promotional” rates (Seriously? A twenty two year long promotion?) will be expiring. After spoofing my User Agent as the chat function doesn’t recognize my browser/operating system combination, I verified this is indeed the plan with “Veronica”. I was then provided a transcript and directed to an online survey when promptly logged me off without submitting my feedback once I had completed it.
Based on this idea, I created a Wunderbar jquery filter to “desugar” Wunderbar calls into JQuery calls. The tests show some of the conversions. I also updated my Bootstrap modal dialog directive to make use of this: before => after.
We’re at an inflection point in the practice of constructing software. Our
tools are good, our server developers are happy, but when it comes to building
client-side software, we really don’t know where we’re going or how to get
While I agree with much of this post, I really don’t think the conclusion
is as bad as Tim portrays things. I agree that there are good server side
frameworks, and doing things like MVC is the way to go.
I just happen to believe that this is true on the client too – including MVC.
Not perfect, perhaps, but more than workable. And full disclosure, I’m firmly
side of the fence.