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!
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 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.
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.
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.
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.
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.
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?