> What is the reason that every single recipe site, without fail, follows this same horrible pattern? I.e. the twenty paragraph "When I was a child growing up in Atlanta..." followed by a crappy in-house video player followed by, finally, the actual recipe?
I lived with a food blogger for six years and might be able to provide some more perspective for these types of comments (beyond just SEO).
First, there's actually an audience that _is_ interested in this type of content. Some are repeat readers who want to follow food bloggers' lives, similar to how HN readers might follow a streamer on Twitch. It's a much more rewarding journey if people don't just see you as a recipe database and bounce, but actually engage with you and follow you over time.
Second, a lot of food bloggers simply enjoy writing and see their blogs as a way to express themselves. Some of them write these stories for their family and friends and didn't think they'd be at the top of Google.
Third, it takes a ton of effort to write a single recipe. I can't speak for others, but hers involved multiple days of planning/cooking/shooting, remaking it several times so she knew it'd be consistent for the reader, planning/shooting/editing the photos, and even scrapping recipes altogether if they didn't work out. She also had to deal with the business end of things (like getting a lawyer, accountant, social media manager, and managing contracts with sponsors). Her attitude was basically, "if I'm doing all of these things to provide someone with a free recipe, they can scroll past my story if they don't feel like reading it". (That being said, her site was pretty minimalist compared to other food blogs – she didn't run ads.)
FWIW, I don't have a problem with onlyrecipe.app, I just wanted to share this because I'd be interested if I didn't know already.
I have yet to meet or read about a single person who has ever said "I really enjoy scrolling through twenty paragraphs of backstory and embedded auto-play videos and advertisements while I browse for recipes."
So while I'm sure there exist bloggers who put care into these things, a tiny minority of people seem to find any value there. In fact it now seems that so many people are aggravated by this style that an app to remove them all has been developed.
Also the story is one thing but the painfully verbose explanation of each ingredient is ridiculous. I really don’t want or need an explanation of flour, sugar, salt, etc… That’s the content that really makes me annoyed at a blog recipe.
Like many others I have mostly abandoned blogs in favor of tried and true cookbooks.
If you have an iPhone, you can physically connect it to your computer and inspect its elements through Safari's DevTools. It's a little unintuitive, but I wrote a walkthrough on how to set it up here (see the second section) [0].
> The DX is so good that building things is incredibly fun, intuitive, and headache free. I can’t emphasize enough how empowering it is.
Yes! I've been a full-time React developer for about 5 years, and recently had the chance to try Svelte on a small pet project. I'd written most of the project in React and had a free weekend so I figured what the heck – let's see how it'd look in Svelte. :)
Within a day most of the functionality was in place, and the code just felt _beautiful_. I loved that it removed so much boilerplate (wrote some examples here[0]), and some of the React headaches (like using "Undo" in a controlled <textarea>) were just gone. The ergonomics (especially the built-in stores, error handling, and <svelte:head>) were lovely surprises!
I'm really bullish on it and so happy it's starting to grow.
Really helpful article. Thinking about diving into Svelte. I'm a huge fan of react-query[0] so I was wondering, is there a good alternative for it in Svelte? Would you recommend svelte-query[1]. Thanks.
I'd heard about Millionaire Next Door for years and mistakenly wrote it off as one of those scammy "buy my program" books about visualization.
Then it was gifted to me, and boy, was I wrong! Couldn't put it down. It's packed full of interesting tidbits and data. While I'd highly recommend reading the book yourself, I also wrote some notes on it here [0].
I'd love to see these same studies, but updated to 2021.
I've got good news for you! There was another book written 2 years ago called Everyday Millionaires by Chris Hogan that conducted a new study of millionaires. I think MND studied 100 millionaires, while EM studied 10000.
I use a similar extension for VS Code. My use case is to share certain lines of code with coworkers. I didn't realize it would be so helpful, but I probably use it at least 3 times every day.
Which one are you using? I'd love this. It's usually precisely to reference it in a bug report, to a coworker, in a support case explaining software behaviour, etc.
> Ideally, we'd be able to control opt-outs at the browser level.
We tried it at the protocol level with do-not-track and it just gave them an additional bit of info to track.
But I agree: It would be awesome to have this as a browser option. Just send a list of all the optional things to my browser which responds with the accepted results.
> The second best thing would be a law to prevent consent popups from making it harder to opt-out than it is to opt-in
I wish it was this explicit, but it isn't. EU member states have all interpreted the regulation differently.
Making it harder to opt out than in is explicitly prohibited in the UK and Germany. It is perfectly legal in Italy. In Spain, it is legal to bury the opt out buttons at the end of a 50 page cookie policy.
Full compliance, across the whole of the EU, is exceptionally difficult.
I lived with a food blogger for six years and might be able to provide some more perspective for these types of comments (beyond just SEO).
First, there's actually an audience that _is_ interested in this type of content. Some are repeat readers who want to follow food bloggers' lives, similar to how HN readers might follow a streamer on Twitch. It's a much more rewarding journey if people don't just see you as a recipe database and bounce, but actually engage with you and follow you over time.
Second, a lot of food bloggers simply enjoy writing and see their blogs as a way to express themselves. Some of them write these stories for their family and friends and didn't think they'd be at the top of Google.
Third, it takes a ton of effort to write a single recipe. I can't speak for others, but hers involved multiple days of planning/cooking/shooting, remaking it several times so she knew it'd be consistent for the reader, planning/shooting/editing the photos, and even scrapping recipes altogether if they didn't work out. She also had to deal with the business end of things (like getting a lawyer, accountant, social media manager, and managing contracts with sponsors). Her attitude was basically, "if I'm doing all of these things to provide someone with a free recipe, they can scroll past my story if they don't feel like reading it". (That being said, her site was pretty minimalist compared to other food blogs – she didn't run ads.)
FWIW, I don't have a problem with onlyrecipe.app, I just wanted to share this because I'd be interested if I didn't know already.