Not much else to say. An iconic voice inextricably tied to something I love, though her feelings on that were mixed.
RIP Dave Smith
Less than 3 weeks after making an appearance at Superbooth and looking healthy and enthusiastic, Dave Smith is dead at 72.
If you don't know who he is, Smith is a synth pioneer who founded Sequential Circuits in the 70s. They made a lot of iconic synths but were most famous for the Prophet 5, pretty much the first programmable polyphonic synth. It really has yet to be topped, which is probably why the re-built company is still making a Prophet 5.
Then, in the early 80s he conceived of and developed a universal interface for synthesizers from different manufacturers to talk to each other. Whether the fact that it's still in use today is evidence of its effectiveness or of how out-of-date it is now, you can't argue that MIDI is one of the most important things to happen in the world of music since the development of the synthesizer itself. He and Roland founder Ikutaro Kakehashi (also sadly no longer with us) even received a Grammy for the development of MIDI.
For those of us who might never afford a Prophet, MIDI is the great unifier. Since its inception, it has allowed the fanciest Oberheim, the lowliest Volca, your SP-404 loaded with samples of farts, whatever it is, to talk to each other. The standard even continues into the computer, where I can download MIDI files of Clyde Stubblefield playing drums and replace all the hits with sounds of dogs barking or car crashes. I'm sure that's exactly what Smith had in mind.
And speaking of that, one of Smith's other ventures was the first real software synth, Reality. Though he didn't ultimately care for making music inside a computer, it's another project he spearheaded that pretty much changed music forever.
So the only thing left to say is thanks. You'll be missed.
Yes, Virginia, there is a Microsoft version of that
It can be tough when you're stuck in Windows world, with security lockdowns on your computer and a ban on most cloud services. With the notable exceptions of UserZoom, Figma, and Overflow, I'm in MS world and that's been an adjustment after the world of Google Apps and other lightweight, web-based tools.
There's a benefit to being entirely in Microsoftland, or at least in theory there is. Kinda looks like with the advent of Loop they are trying to make good on that theory and put it into real practice.
So to say that Loop is a Notion ripoff seems partially true. But for those of us stuck here in Office 365 with no hope of using the real thing, that's totally fine. Just like Planner is not Trello and Todo isn't quite what Wunderlist was, and Power Automate is far from being as easy to work as IFTTT or Zapier — but they exist. I can imagine a lightweight database table like what Notion employs would be so much easier for many of the small tasks where I'm using SharePoint Lists. But the "components" feature of Loop seems to be where MS are really trying to take it a bit further.
The idea behind components seems to be that the pieces of functionality (like Notion blocks?) are available elsewhere in the Office ecosystem: Teams chats, Word docs, email messages. And that's the kind of interoperability that we really don't enjoy today, even though that should be a prime selling point of Microsoftland. Mail Merge isn't exactly the future. But maybe Loop will be?
Lite XL
Love the contradictory name. I don't necessarily want to get on the Electron hate train, but when you see the speed at which this thing fires up (much faster than VSCode, faster than GEdit, even) you might consider ditching Atom. It strikes a nice balance of features and performance.
Yes, this, etc.
My quest for simplicity has led to some people doing some pretty interesting stuff. Even more appealing to me than Utopia is Every Layout, which frankly seems hard to sum up in an elevator pitch, but like Utopia it aims to get CSS back to declaration and away from prescription. In this case, it seems largely because declarative just works better. My only beef with this thing is the price. It's no doubt that a lot of work went into it but 70 bucks is steep.
The further I read into the sample content, the more I'm standing up, punching the air, screaming. It's that invigorating and it makes that much sense.
Incidentally, one of the authors is responsible for CUBE CSS, which I'm been looking at with interest too. I'm a BEM-head from way back, but this looks like an interesting philosophical take on CSS that embraces a recent trend among true HTML/CSS folks: Stop fighting the cascade. You're speaking my language.
365 days of type 9 from TRU
I don't think much about cool typefaces these days, I'm generally just looking for something readable and pleasant for UIs and websites. But I still get a kick out of my favorite subject from school. This is really beautiful.
Another day, another blog redesign
Been thinking about doing this ever since I did the last one. It never quite came out the way I wanted and frankly, the newspaper-ish feel just didn't work. It worked in my head, and it sorta-kinda worked in Figma, and it just didn't translate.
After reading about Utopia and thinking, hey maybe I should do that, I went a little deeper into the rabbit hole of simplicity.
Some notes:
- There was no Figma phase to the "design."
- I did this entirely live by mounting my website with
rcloneand editing live with GEdit (Atom couldn't browse and edit the remote files fast enough). - There are 157 lines of CSS, un-minified, with a carriage return between each rule. It uses zero media queries. There aren't even any columns, so I didn't get the chance to evolve from flexbox to grid.
- I'm using CSS custom properties for the second time in my life, and though it doesn't give me everything I want from the Sass feature set, it's really great to get variables while staying native.
- I didn't quite leave the HTML unchanged, but I probably could've. I've been using almost the same HTML pretty much since I switched to Kirby many years ago.
- Standard posts have a larger first paragraph. This might possibly be inspired by Lagrange, the nicest Gemini client out there.
I suppose I'll enjoy looking at this for a couple weeks and then off we go again, probably with a pendulum swing to complexity. Or maybe I'll just change that yellow to something else to tide me over for a bit.
Utopian thinking
Now this is something interesting.
Obviously we've gotten pretty far away from the fundamentals of the web. "Text with hyperlinks" is the mission of the Gemini project, something that's described as heavier than Gopher and lighter than the web. So there's an appetite for those simpler days. All the myriad ways we've strayed from Hypertext's light would take quite a few more blog posts and sound like an old man yelling at clouds, but in terms of web design it feels pretty specific. Build tools. Compiled code. Scoping and renaming classes at runtime. Arguments about whether to put CSS in JS. Not gonna belabor that, you get it.
I taught myself to ditch tables around 2002-2003 by reading Eric Meyer's O'Reilly title CSS: The Definitive Guide, which is purely a reference title. It was not what I would call complicated. It probably took me just as long to figure out how to implement Grunt, which was already supplanted by Gulp by that time. Life is complicated, and I guess life in CSS has gotten that way as well. It feels such a long way from the CSS Zen Garden.
I don't necessarily think that breakpoints and media queries are an extreme example of the complication — remember conditional comments? Remember writing separate sites from Netscape and Internet Explorer? But I do think Utopia's authors asserting that their framework is "declarative" instead of "prescriptive" or "instructive" brings it back to the fundamentals of CSS. I find it a bit ironic though that they're using some really complicated calculations to achieve simplicity for the user. I recognize that bootstrap does something similar when calculating the grid, but the deeper the math I don't understand burrows, the more scared I am of relying on it.
I haven't read enough of the material here to understand how they handle anything other than the spacing and typography — and whether they like it or not, there is more to it than that, even if those are the only two things you can't take away. Looks like it may be relying on CSS grids to keep things in one media space. And lord knows I haven't adequately learned CSS grids yet. But I'm going to give this a shot. Maybe the next version of this site will be Utopian.
The FBI Guide to Internet Slang
Pentagram does a snarky thing with a fun type design. Like Bierut, I wonder if any of these terms the FBI notes have ever been used by anyone. The idea of the document reminds me of the old Law Enforcement Guide to Satanic Cults. Link is to the film but its print predecessor baffled me even in middle school.
It speaks to the (uh, problematic) law enforcement mindset that there are dark forces and coded evils working in all corners of the world and they're the last bastion of defense against it. Too often those "evil" symbols are just non-WASP identifiers, and fear of youth comes from the same place — especially when so much of internet slang comes from AAVE and other non-white sources.
Problems I'm glad I'm not dealing with
Eric Meyer on the CSS Working Group's attempts to add conditionals to CSS. My most recent side project uses pure CSS with variables, which is a huge step toward me not caring about preprocessors anymore. With logic, the only things left are concatenation (probably solved already), and nesting syntax, which I find cleaner to go through later on. He's right though, as a Sass user I can easily see both sides of this argument and don't know what's right. But I know it's progress, and in my current way of thinking, more features in CSS is better. Because no matter how "bloated" you think it'll be, it's still better than having to use extra tools that aren't natively parsed by the web browser.
