Full fathom frontal

It’s been a busy time in Brighton. Last Wednesday’s Skillswap was an excellent affair, with terrific talks about making physical things from Chris Thorpe, Dan Williams, and the lovely young chaps from Mint Digital’s Foundry who were showing their lovely dough globe.

Two days later, it was time for this year’s Full Frontal conference, a highlight of the web-dev calendar. It was really, really good. The general consensus at the after-party was that this was the best year yet. That’s quite something when you consider that in 2009 I said:

it’ll be hard to match the standard set by this year’s conference.

I love it when there are events on in Brighton—dConstruct, Reasons To Be Creative, UX Brighton. It’s great to have geeks come to visit. I always feel like an ambassador and I want the town to be on its best behaviour.

The line-up for Full Frontal was really well curated by Remy. It started with a one-two punch of big-picture thinking, dived into the practicalities of working on the cutting-edge of today’s technologies and then wrapped up with a long-zoom trip down memory lane with Chris.

The one-two punch came from James and John. Like an Oxford debate, they were arguing from opposite ends of a spectrum of opinion. James argued that was perfectly reasonable, even desirable, to make a web app entirely in JavaScript with no HTML in the body element whatsoever. John cautioned against throwing the markup baby out with the web app bathwater, pointing to the robustness of the web stack’s architecture.

The whole point of this opening to the conference was to spark debate and discussion, which it certainly did. Witness this post by Mike Davies in response to James’s arguments.

I’ve seen James present before and, while I certainly don’t agree with what he’s saying, he is a very good presenter. He used a particularly sneaky technique this time. This technical term for this technique is “being reasonable.” Half way through his talk he pointed out that he was taking a deliberately extremist approach and that the truth is that every website sits somewhere on a continuum between document and app (and that websites have had app-like capabilities since the dawn of the submit button). Talking with Mark in the break, we decided we should just get T-shirts with “It Depends” emblazoned on them.

Side note: I’m afraid I must deduct one or two points from James for employing a rhetorical device that really annoys me. At one point (and admittedly just one point) he referred to the “other side” as being dogmatic. Whenever someone labels those they disagree with as “dogmatic” or “purist”, it’s a lazy meaningless barb (like calling someone a hipster). “I’m passionate; you’re dogmatic. I sweat the details; you’re a purist.” Even when I agree completely with the argument being made—as was the case with Andy’s superb talk at South by Southwest this year—I cringe to hear the “dogma” attack employed: especially when the argument is strong enough to stand up on its own without resorting to Croftian epithets.

Anyway, the debate between James and John was a great start to a great day of talks. In some ways, Anna’s excellent talk on the diversity of web browsers on gaming devices was the ultimate rebuttal to James’s argument. “I don’t care about browsers that can’t run this JavaScript,” said James. “This browser basically can’t handle JavaScript,” said Anna. “And here’s the number of young people in the UK accessing the web on this device…”

The Ubelly blog post described Anna’s talk as “One of the best talks of the conference and one of the best talks I have seen this year.”

All in all, a great day which was followed by a whole day of hacking on drones. Clearleft sponsored the event, which means we now have our own flying robot. This could be dangerous.

We’ll be sure to take the drone with us when we head into deepest darkest Dorset next week for this year’s hack farm. But before that I’m in Belfast for the week of Build “don’t-call-it-a-conference” Conf. And you know what I really like? I’m seeing some of the same faces that I saw in Brighton at Full Frontal. Now that’s what I call a balanced conference diet.

Have you published a response to this? :

Responses

Jeremy Keith

@mtheoryx I’m very careful not to label advocates of monolithic client-side architectures as “zealots” or “purists”. It’s just not helpful.

Related posts

Codebar Brighton

Celebrating ten years of the wonderful community event.

FF Conf 2019

A report from Brighton’s unmissable annual front-end gathering.

Indy maps

It’s not the years, honey. It’s the mileage.

Indy web

Maps—they don’t love you like I love you.

Patterns Day videos

The first video is online for your enjoyment.

Related links

A workshop for codebar students: Build a portfolio or blog site | Charlotte Jackson, Front-end developer

Charlotte did a fantastic job putting this workshop together on the weekend. It was inspiring!

Tagged with

With great power, comes great creativity: thoughts from CSS Day 2024 · Paul Robert Lloyd

Here’s Paul’s take on this year’s CSS Day. He’s not an easy man to please, but the event managed to impress even him.

As CSS Day celebrates its milestone anniversary, I was reminded how lucky we are to have events that bring together two constituent parties of the web: implementors and authors (with Sara Soueidan’s talk about the relationship between CSS and accessibility reminding us of the users we ultimately build for). My only complaint is that there are not more events like this; single track, tight subject focus (and amazing catering).

Tagged with

Tagged with

CSS { In Real Life } | Thoughts From CSS Day

It’s clear that companies don’t value CSS skills in the same way as, say Javascript — which is reflected in pay disparity, bootcamp priorities, and the lack of visibility in job descriptions. It’s not uncommon to see front end job specifications listing React, Redux, Typescript and more, with barely a passing mention of HTML and CSS, despite being core web technologies. New developers are encouraged to learn just enough CSS to get by, rather than cultivate a deep knowledge and appreciation for the language, and that’s reflected in the messy, convoluted code, riddled with bad practices, that many of us have to clear up afterwards.

Tagged with

The continuing tragedy of CSS: thoughts from CSS Day 2023 · Paul Robert Lloyd

With new or expanded modules for layout, typography, animation, audio (though sadly not speech) and more, it’s possible to specialise in a subset of CSS. Yet when aspects of frontend development not involving JavaScript are seen as ignorable by employers, few will get this opportunity.

Paul shares his big-picture thoughts after CSS Day:

But one CSS conference isn’t enough. This language is now so broad and deep, its implementation across browsers never more stable and complete, that opportunities to grow the community abound.

Tagged with

Previously on this day

17 years ago I wrote Cascading calendars

Take my style sheet. Please.

22 years ago I wrote Apple Pro Keyboard Redux

I go through keyboards like the Skywalker family goes through hands.