Charles Harries

@[email protected]

[Charles Harries @charlesharries]

@dvassallo @nickrw unless you work in corporate advocacy, the paycheck probably isn't for your glowing public opinion—holding your employer to account might be impolite, sure, but not unethical

[Charles Harries @charlesharries]

server-sent events: a trivial websocket replacement for the 80% use case. yeah i said it

https://t.co/3z04JX3iTI

[Charles Harries @charlesharries]

@lowtechmagazine's website is solar-powered, and goes offline in times of bad weather

https://t.co/PxtWXqXajC

[Charles Harries @charlesharries]

a bit of a brain dump in the long wake of a talk on sustainable web development from @HenriHelvetica

https://t.co/cLaw59GF4U

[Charles Harries @charlesharries]

@HenriHelvetica a couple of other projects in the same vein:

sustywp is an attempt to deliver wordpress in as small a package as possible:

https://t.co/E8UM9ngrBZ

[Charles Harries @charlesharries]

@wesbos but wes he's verified, it must be legit

[Charles Harries @charlesharries]

css nesting is great, and we're closer than ever to seeing it implemented! and when it arrives we're not actually going to need it

https://t.co/1BeAPylKbX

[Charles Harries @charlesharries]

boy everyone's verified now eh

[Charles Harries @charlesharries]

@onion2k this isn’t even that impressive, developers have been querying + rendering in the same file since php introduced mysql_query()

i’d say that next’s tools for building, caching, & the Network Request Waterfall are at least a bit more compelling than this

[Charles Harries @charlesharries]

Anyway, it’s nice that we’re finally getting Server Components, and in the right hands, a Next.js application can probably be pretty wicked

Just feels like the baseline’s a little bit off

https://t.co/dZy8eZtPtk

[Charles Harries @charlesharries]

A couple of words on Next.js 13: an exciting release of a well-loved framework, with some eminently hot-takeable features. But…

https://t.co/773hUulWO5

[Charles Harries @charlesharries]

For instance, React now overwrites the fetch() global, opting users into caching (good!) but putting a standardised browser API inside a black box (not good!)

https://t.co/tJeR23xABS

[Charles Harries @charlesharries]

@Hicksyfern @drewhamlett @justmarkup i think that Bundle Size Puritans are less concerned with transmitting 100KB of JS over the wire, and more with executing 100KB of JS in the browser—which is very different from rendering a 100KB image

[Charles Harries @charlesharries]

bit of cheeky wednesday night design inspo, giving off strong blurry gradient blob energy

https://t.co/KO4ryWJxgK

[Charles Harries @charlesharries]

this is a great (if long—in a good way!) overview of the current state of play in crypto, & you should read it if you can find the time

but more importantly, it's written in @sveltejs

https://t.co/zCCrMDYBcp

[Charles Harries @charlesharries]

woof I wish this had been around when I was building new UIs on the reg, woulda saved a lot of head scratching around building accessible accordions &c

https://t.co/yNtwiRi1tL

[Charles Harries @charlesharries]

@varjmes @JoshTumath couching it in language around seo and performance tends to perk up obstinate ears: shiny lighthouse and web vitals scores tend to follow from accessible markup, and proper page structure allows crawlers to index your site more efficiently

[Charles Harries @charlesharries]

@wesbos for properties that involve some expensive logic the first time (e.g. fetch) but that can then returned the same data, but cached:

get smth() {
if (!this._data.smth) {
this._data.smth = expensiveLogic();
}
return this._data.smth;
}