Do you have a sense of which aspects are the most resource-intensive? Naively I would guess it's the backdrop-filter.

Comments URL: https://news.ycombinator.com/item?id=44063490

Points: 23

# Comments: 4

We’ve observed that the last few years is a much better indicator of what the weather will be like than most data sources which aggregate from 1900 or even 1950.

We’ve also added tourism stats, and synced it to weather data. This has been particularly eye-opening. It lets us see when a country experiences over-tourism (e.g., Croatia and Austria) relative to its population.

There’s lots more we’d like to build, but we’re releasing it now to get feedback. It’s free and there’s no ads, so if you’re interested and would like to support us, there’s a box to give your email. In the future, we may consider a premium app version or an patreon-like support option.

Thanks for checking it out!

Comments URL: https://news.ycombinator.com/item?id=43864508

Points: 5

# Comments: 0

I was surprised because Cloudflare’s central messaging is that their network is fast, and disappointed becuase I’m a happy user of their other products (domains, DNS, pages, and R2).

I've also wondered about disabling the timer entirely. Have you ever had the experience in real life of being hyper-aware of your own "reply timer" during a conversation?

Getting to speak any time is super interesting feedback, you're the first one to suggest that. It would be really cool if you could even interrupt them! Super mind-bending for me to think of how I'd handle that with prompting and scoring. Thank you for this!!

Yang Li is divisive. You are not alone :-) If it helps, she disappears for quite a while after the intro.

I am impressed you broke it! Not because my code is that robust, but nobody's broken it in a while. I'm sorry about that. Investigating!

1. Exactly yes. The frontend is a light-ish amount of JavaScript + React, with a relatively enormous pile of my own janky CSS on top of (Framer) Motion, DaisyUI, and Tailwind.

2. No plot branching. Would love to add, but focused only on exploring the mechanics of conversational gameplay. Perhaps if it is ever successful enough for a sequel (ha!)

Re: taking too long, I 100% agree. Wrestled with what to cut. Do you think skipping all the setup screens and story intro would have worked well for you, dropping right into Vincent('s missed birthday)?

The tech especially isn't rocket science (first time using Tailwind, FastAPI, and sqlite, which have all mostly delighted). While the game design isn't either, it's been interesting to think about how to do (LLM) conversations as actual gameplay, as opposed to purely ornamental. I think the tasks must feel objective and fair enough to be engaging as a challenge, while still being open-ended enough to reward creativity.

I hope you enjoy, and would love to get your feedback!

Comments URL: https://news.ycombinator.com/item?id=42481249

Points: 144

# Comments: 52

Just to give a bit more meat to my comment: these experiences are really helpful when you're in the position to adopt a potential time-saving (stack-cutting/unifying) technology. I find I get a huge benefit from word-of-moth experiences from others who have tried such frameworks. Specifically compared to takes on the _idea_ of the technology.

Comments URL: https://news.ycombinator.com/item?id=41618452

Points: 2

# Comments: 0

- I use a 3rd party platform

- My maps are generated at runtime

- They looks... let's say vaguely consistent on mobile & desktop

Maps were the most painful and time-consuming part of building a travel blog, but also perhaps the most satisfying.