tpict

I’m curious what’s meant by

Designing for bundlers/compilers/typegen (and any pre-runtime static analysis) leads to poor api design that eventually pollutes the entire system

Is this in reference to React Router v7 that just shipped?

I feel insane whenever the Svelte reactivity thing is touted to me as an improvement over React state. Surely it’s not so hard to internalise JS equality rules that such a huge break from convention is necessary?

PS. I looked up the reactivity token docs on the Svelte website to make sure I was remembering correctly, but it repeatedly crashes the latest version of Safari on iOS. Oops!

My dad’s Power Mac running the SETI screensaver is one of my earliest memories of the Internet. Makes me a little sad

I had a similar situation happen with Mercari last year. I bought some used audio equipment and 30 minutes later my account was terminated for "prohibited items or conduct". I still wonder every now and then what part of the listing triggered the banhammer. Guess who never used Mercari again?

On a similar note to the linked article: the low battery alert of the AirPods Pro can be ear-shattering, and there's no means of reducing the volume. I suspect it tries to scale volume with environmental noise because it ranges from "startling" to "painful".

I don’t disagree with the “early TypeScript” comparison, but what’s the issue with args, *kwargs?

I wonder how many millions of lines of shell configuration have died by people switching to asdf. Fantastic tool

I can see how this makes sense for a startup etc that has passed some threshold of operational complexity. As an “indie hacker” there is no way I’d be able to move out of the cloud without my costs going up by an order of magnitude.

did this capture the entire article? I feel like I'm missing something

The GP’s sentiment is common in the comments. I absolutely understand the gut reaction–regional Eastern specialties are rarely presented with the warmth and openness that this article has. I feel like stepping around “Japanese” as a cultural description in this case would only serve to isolate the community in the reader’s mind. As the article says, there is more to Japanese cuisine than seafood. Why should this tradition not be included?

I'm finding the "this is a horrible idea" responses amusing. I don't know if there's something fundamentally different about the way this project works versus Dirac/XT32 or if the naysayers aren't familiar with it. Or maybe there's an anti-room correction sect of audiophiles that have remained hidden to me.

Yep, it will flag any references to variables in the outer scope that it doesn’t know for certain are stable.

Do you have a reduced code sample? I can’t quite picture the stale state issue.

(I suppose this is a good example in favour of the opposing “useCallback is premature optimisation” opinion)

Last time I checked NPM the weekly downloads were still heavily slanted in favour of version 4. I wonder if that plays into perception of it.

At work, an engineer in a different team recently recommended we switch to Vite because it’s “so much faster”. Warm builds are 700ms with our very uninteresting Webpack 5 config. It’s hard to imagine that the cost of reconfiguring our entire build would be worth it.

There’s nothing to read into here. The writers of these shows are chiefly interested in set pieces that will sell CBS subscriptions via dramatic trailers. They aren’t considering the implications for the ST universe any more than they’re considering the internal consistency of any single episode.

It must take an incredibly sheltered perspective to frame goblin mode as something that happens to tech employees who have the luxury of a WFH policy.

It’s almost identical to some of the top comments!

I haven’t been back in a few years, but the selection of onions in my local Kroger would be staggeringly exotic next to the offerings of Tescos of the north-east.

As a British expat, the “yellow onions” you see in US supermarkets are most familiar.

I once had a phone screen for a full stack SWE position where the interviewer was laser focused on the fact that I had previously held the title "web developer". The entire interview was spent defending myself from accusations that web developers "don't write code", or that "they're more about design" etc, while my resume described past job duties that were a 1:1 match with the JD. The canned "we'll be in touch shortly" was said with a chuckle and I never heard back from them.

At the time, I was in desperate need of a new job or else have to leave the country, so it hurt to be dismissed so readily.

These days I'd be more inclined to excuse myself early, but on the other hand, who's to say that this one person is representative of the company and their culture? Maybe they're a recent hire. Maybe I would have enjoyed the subsequent interviews. My only regret is that I didn't share my experience with someone else at that company.

Thanks so much for the comprehensive answer!

Why the separation from Draft.js? What shortcomings of Draft.js are you hoping to address with Lexical?

Really excited for this to be production-ready!

IIRC this is something they’ve investigated for years, but the prototypes didn’t stand up to a simple day/month/year input group in usability testing. Date pickers are hard to do well!

Building one of these is probably easier than wrangling the GitHub notifications settings into having a meaningful signal:noise

I feel like something happened in the past few days that made Google significantly more infuriating to use. I switched my default search engine to DDG after the nth case of Google presenting search results that matched zero of my (fairly mundane) search terms.

The DDG results aren't superb, but they also don't invoke the feelings of communicating with a distracted child or poorly-trained pet.

it was the same author’s “Apple iOS [every version] Has A Nasty Surprise” headlines that made me drop them

I swear that the automatic switching feature was almost flawless when it first shipped, but at some point the "is the user paying attention to this audio source" heuristics were changed. It now seems very eager to switch to my phone and reluctant to switch to my Mac.

There was also a bug for a period of months–I need to check to see if this still happens, I've conditioned myself not to trigger it–where

1. I put in my AirPods

2. I click them in the audio drop-down in the Mac menu bar to connect

3. The "Connect to AirPods" notification appears

4. I click "connect" because I'm already connected and it's the biggest target to dismiss the notification

5. the AirPods DISCONNECT! Come on...

JSX is syntactic sugar for `React.createElement(...)` (most commonly), so React pretty much is plain JavaScript.

I believe "nesting hell" was in reference to obtuse state management architecture rather than DOM structure. It seems like a common misconception based off other comments on this post. Angular inserts a new custom element for every component so it's definitely a problem elsewhere, if not with React.

A React component has no obligation to add a div or any other element to the DOM tree.