Chris Coyier rounding up recent frontend moves (by Basecamp and React, specifically) back to server-side rendering techniques of old:
So: servers. They are just good at doing certain things (says the guy typing into his WordPress blog). There does seem to be some momentum toward doing less on the client, which I think most of us would agree has been taking on a bit much lately, which asset sizes doing nothing but growing and growing.
Let’s push those servers to the edge while we’re at it.
I agree. Servers are cool. Clients are cool, too. But so are servers.
This is an extended version of my essay “When front-end means full-stack” which was published in the wonderful Increment magazine put out by Stripe. It’s also something of an evolution of a couple other of my essays, “The Great Divide” and “Ooops, I guess we’re full-stack developers now.”
This is a lengthy, sprawling piece on the evolution of frontend development by someone who really gets the web. It also has its own art-direction and design so you’ll want to read it onsite vs in an Instapaper-alike.
You might reach for
<input type="number>when you’re, you know, trying to collect a number in a form. But it’s got all sorts of issues. For one, sometimes what you want kinda looks like a number, but isn’t one (like how a credit card number has spaces), because it’s really just a string of numbers. Even more importantly, there are a variety of screen reader problems.
(We discuss the uncanny valley of
number inputs on this JS Party episode about the stale parts of browsers.)
Turns out the best practice (just use
text inputs) has a twist to it: inputmode!
JAMstack, myself, but I think the
Ajax analogy he quotes is an apt one. Aside: if this trend continues, Chris and the team might need to rename the site to “Jamstack-Tricks” soon.
Oh, and while we’re here: It’s Changelog not ChangeLog 😄
Chris Coyier can’t help but chime in after listening to our recent debate episode of JS Party.
I enjoyed all the stumbling around the terminology of “web apps” and “web sites” (web things!). This is such a weird one. It’s so easy to picture the difference in your head: it’s like facebook versus a blog! But when you start trying to define it exactly, it gets really murky really quickly and the distinction loses any value, if it had any to start with. Here’s more on that.
Chris has a lot of great insights here. Whether you agree or disagree, I think we can all get on board with one thing: we make web things!
This article is Chris Coyier doing what Chris Coyier does best: pulling on people’s views from around the community, then sprinkling in his own take as he goes.
How do you send email from a JAMstack-style site? Chris Coyer writes on CSS-Tricks:
Chris Coyier joins Suz and Jerod to continue the discussion on The Great Divide in front-end-land. We also use this as an opportunity to gush on how much CSS-Tricks has done for the community, get Chris’ perspective on the history of the website, and finish up by sharing some amazing Pens on CodePen.io.
Two front-end developers are sitting at a bar. They have nothing to talk about.
Chris Coyier on CSS-Tricks:
By getting clever with positioning, transforming, and many other tricks, we can make lots of shapes in CSS with only a single HTML element.
Ok, so the first couple ones are easy, but the lower you go on the page, the more complex the shapes become. I had no idea you could do this with just CSS, much less with a single HTML element.
Chris Coyier on CSS-Tricks:
Say you have a very simple CSS grid layout with one column fixed at
300pxand another taking up the rest of the space at
That’s somewhat robust. That
1frcolumn will take up any remaining space left behind by the fixed
300pxcolumn. It’s true that the
autovalue would do the same, but
autoisn’t quite as robust since it’s size is based on the content inside.
Chris explains something here which may look pretty simple, but would’ve taken me hours to debug. The distinction he makes between the
auto defined column is game changing on its own.
I have to agree with this hard-line stance from Chris Coyier on the subject of view source:
I literally don’t care at all about View Source and wouldn’t miss it if it was removed from browsers. I live in DevTools, and I’ll bet you do too.
I want my website to arrive at light speed on a tiny spec of magical network packet dust and blossom into a complete website. Or do whatever computer science deems is the absolute fastest way to send website data between computers.
I’m much more worried about the state of web performance than I am about web education. But even if I was very worried about web education, I don’t think it’s the network’s job to deliver teachability.
What about you? Is view source more important than web performance? Is DevTools a worthy replacement for view source?
Chris also cites comments on the subject from Tom Dale, Jonathan Snook, and Chris Heilmann.