seumars

Wow that's one awkwardly pompous introduction. Nevertheless Zed never fails to impress. Aside from all the AI fireworks it really goes to show how building software "from scratch" pays off in the long run.

Agreed. Come to think of it Homebrew has pretty bad ergonomics in general. What i want is an overview of compiled binaries, where they are, and what their versions are. That’s it.

It seems the "hard way" here is just avoiding frameworks. The real hard part of UI is in fact state management and the myriad of methods for handling state.

Any specific paper or article of his you would recommend?

great quote. swiss german designer perhaps?

Funnily enough the example given of good “L” and “T” kerning in the word SALTY is badly kerned, the letters are kerned too close to each other. The classic trick is to look at 3-letter groups at a time, one word at a time.

This is the only correct suggestion

you can define import maps in a separate <script> tag and reuse the module name elsewhere

Check out the North Paw Directional Anklet. It’s basically a compass that vibrates whenever you face magnetic north. From what I’ve read people seem to develop a sense of direction pretty quickly.

Thank you for sharing! Big fan of Bartosz's articles and somehow didn't think of looking him up on other platforms

Yes, but in this specific case the focus is on the design elements labeled onto the lego blocks.

That's the UI. There's no actual interaction with the screens.

Same here. I also wonder who would even target their political ads at european audiences.

How is htmx low level?

>I enjoy making my own tools and I'm a bit tired of hearing that everything needs to be "battle-tested." So what it will crash? Bugs can be fixed :^)

I love it

Isn't this just an implementation of the Observable pattern? IIRC the difference between observables and signals is that signals don't recompute the value unless any of its sources change, by using a dependency graph. Also, .effect() is just what used to be called .subscribe() in knockout.js and others.

Well it was made nearly 15 years ago.

I’m disappointed in the fact that the main ambition here is only to recreate a browser for the sake of independence. There is so much potential in creating a modern browser that could for instance focus on performance, privacy, access to lower level APIs, etc. rather than carrying the eternal burden of backwards compatibility.

Appealing to different tastes is far from trolling.

My pet peeve with this question is that sometimes it’s completely fair to call a piece of software "finished".

The whole point of this initiative is to stop using out of date float-hacks, or soon-to-be out of date hacks to CSS grid or flexbox. Firefox's masonry layout is in fact implemented in such a way that basically covers all layout cases by simply adding a new attribute that collapses grid rows.

It sounds to me that if your team is relying that much on inspecting values, you're doing the developers (or designers) a disservice one way or another. A well defined set of design tokens is all that's needed, and isn't rocket science either. Not to mention that encouraging developers to copy-paste CSS should be frown upon anyway.

Not in a way that differs from old-fashioned web scraping. If the website you're targeting is built using a framework and is server-side rendered then it'll most definitely also send all the data it needs for hydrating on the client as JSON, usually attached to the window object as "window.__INITIAL_STATE__" or similar. There are no limits :–)

>Jacob Nielson was blowhard even then. His "all links must be blue and underlined" mantra was tired even then. It takes a lot for me to say this, but his pedantry at the time puts peak Richard Stallman to shame!

And that'd be an understatement! I feel Nielsen spent most of his professional career calling himself a guru mostly to boost his consultancy firm. He also reminds me of Norman in the way that their contributions to the field are lofty aphorisms that don't provide any actual solutions.

One can only wonder how much this domain is worth today.

Although the tech behind Figma is nothing but impressive I find that the biggest downside to current collaborative tools is that they're expected to be used collaboratively at all times.

I would say that no more than 10% of the time I spend on Figma is for collaborating with other people in short brainstorming sessions, team workshops, etc. The other 90% is spent by myself working and polishing said prototypes, but still having to deal with the loading times, server hiccups, and so on.

An "offline mode" of sorts would also be a silly feature to expect since their entire stack is built around collaboration. Seems like a difficult balance.

What's the consensus on using custom HTML attributes such as "hx-post", "hx-trigger" and so on, which are "invalid" according to the spec? I don't mind prepending data- to custom attributes but it's still a minor nuisance.

>if you’re anxious about GPT4 its probably because you’re a shitty programmer

surely this is meant partly tongue-in-cheek?

Calling React the next IBM is giving React way more credit than it's worth. Sure, basic knowledge of React will land you a frontend dev job pretty much anywhere in the world. However most of that work will be maintenance. If anything React is the new PHP.