Charlie Don't Surf
Oh. My. Gawd. @adactio mentioned our in house playbook. runs around, squealing, fists pressed to mouth adactio.com/links/12205
I like it when organisations share their in-house coding styles. This one from Springer Nature not only has guides for HTML, CSS, and JavaScript, but it also has a good primer on progressive enhancement.
Oh. My. Gawd. @adactio mentioned our in house playbook. runs around, squealing, fists pressed to mouth adactio.com/links/12205
Listening to @sonniesedge talk about the excellent Springer Nature Frontend Playbook: adactio.com/links/12205adactio.com/notes/14484
Meeting @sonniesedge and @adactio, even if virtually, was an awesome part of @IndieWebCamp Berlin. Charlie’s wit and style have made me a fan for years. Jeremy Keith been pointing way forward for years. So many perspectives in #IndieWeb community. (quickthoughts.jgregorymcverry.com/s/1MaVr)
Want to use all those great features that have been in landing in browsers over the past year or two? View transitions! Scroll-driven animations! So much more!
Well, your coding co-pilot is not going to going to be of any help.
Large language models, especially those on the scale of many of the most accessible, popular hosted options, take humongous datasets and long periods to train. By the time everything has been scraped and a dataset has been built, the set is on some level already obsolete. Then, before a model can reach the hands of consumers, time must be taken to train and evaluate it, and then even more to finally deploy it.
Once it has finally released, it usually remains stagnant in terms of having its knowledge updated. This creates an AI knowledge gap. A period between the present and AI’s training cutoff. This gap creates a time between when a new technology emerges and when AI systems can effectively support user needs regarding its adoption, meaning that models will not be able to service users requesting assistance with new technologies, thus disincentivising their use.
So we get this instead:
I’ve anecdotally noticed that many AI tools have a ‘preference’ for React and Tailwind when asked to tackle a web-based task, or even to create any app involving an interface at all.
When haters deny HTML’s status as a programming language, they’re showing they don’t understand what a language really is. Language is not instructing an interlocutor what to do in a way that leaves no room for other interpretations; it is better and richer than that. Like human language, HTML is conversational. It is remarkably adept at adapting to context. It can take a different shape on any machine, from a desktop browser or an e-reader screen to a mobile app or a screen reader for the blind (so long as that device is built to present hypertext).
Hell, yeah!
Ultimately, even as HTML has become the province of professionals, it cannot be gatekept. This is what makes so many programmers so anxious about the web, and sometimes pathetically desperate to maintain the all-too-real walls they’ve erected between software engineers and web developers.
Hell, yeeeeaaaaahhh!!!
What other programmers might say dismissively is something HTML lovers embrace: Anyone can do it. Whether we’re using complex frameworks or very simple tools, HTML’s promise is that we can build, make, code, and do anything we want.
React is a non-transferable skill.
React proponents might claim that React will teach you modern UI, but from what I’ve seen it barely copes with modern UI.
autofocus is broken, custom elements don’t work in all but the experimental version, using any “modern” features likedialogor popovers requiresuseEffect, and the synthetic event system teaches you so little about how DOM actually works. This isn’t modern UI, it’s UI from 2013 at its inception. I don’t have the time left in my career to pick up UI paradigms that haven’t evolved much beyond from when Barack Obama was in office.When I mentor early career developers and they ask me what they should learn, I can’t say React, they don’t have time. I mean sure, pick up enough React to land you the inevitable job doing it, but it’s not going to level up your career.
The paradigm shift that web development is entering hinges on the fact that while React was a key enabler of the Single-Page-App and Component era of the web, in practice it normally tends to result in extremely poor products. Built-in browser APIs are now much more capable than they were when React was first invented.
When I was in Amsterdam I was really impressed with the code that Rose was writing and I encouraged her to share it. Here it is: drop this script into a web page with a form to have its values automatically saved into local storage (and automatically loaded into the form if something goes wrong before the form is submitted).
Generating a static copy of The Session from the comfort of European trains.
DOM scripting and event handling.
The behaviour is more consistent now.
Inside me there are two wolves. They’re both JavaScript.
Two JavaScript frameworks—Svelte and Astro—share a philosophy, but take subtly different approaches.
4 Shares
# Shared by Damien Senger • hiwelo. on Monday, November 5th, 2018 at 1:25pm
# Shared by Joschi Kuphal 吉 on Monday, November 5th, 2018 at 1:45pm
# Shared by Accessibility Club on Monday, November 5th, 2018 at 2:10pm
# Shared by Moiety on Wednesday, November 7th, 2018 at 3:13pm