Hacker Newsnew | past | comments | ask | show | jobs | submit | simonbw's commentslogin

A large consumer coming in, driving up demand for water, and being willing to pay for it would be like the textbook example of competing over the water supply.

> "Unless the water providers are selling water too cheaply, what's the problem?"

Do you really not understand how coming in and making a bunch of people's water more expensive isn't popular with those people? You think the problem was that they had it too good with their cheap water and this is fixing that problem?


Now someone's gotta port this version to rust.


Now someone's gotta port this to rust.


I can just imagine the conversation when they came up with that:

Boss: we need to transmit 1 bit of information indicating pressure loss from a spinning rotor blade to the main body of the helicopter. The blade spins too fast for electronics to work properly.

Engineer: What if we make the blades radioactive when they depressurize, then point a Geiger counter at them to detect if that happens.

Boss: ... where did you say you got your degree from?


> is so elegant it’s still being used today

I think it's the "so elegant" part that's wrong. It's not still being used today because it's so elegant. It's still being used today because the old helicopters haven't replaced it.


I think elegance has to do with the technology of the time. Some clever design that is cheaper/better than you would otherwise think possible given the era. There are probably many elegant aspects to Roman aqueduct engineering, but they would still get replaced with modern materials during a retrofit.


if it was less elegant from a function/cost perspective, it would have been replaced a long time ago.


The puzzle pages also give pretty strong AI vibes to me. I think it just reminds me what I've gotten from Claude when I let it decide on design.

Some of the specifics that come to mind:

- the use of emojis instead of icons

- the text content largely sounds like it's written by Claude. This is a big one and it's everywhere: the names of the games, the descriptions, the status texts, basically every single piece of text that I've read.

- the fact that text is being used for some things at all feels a bit Claude-y, like the "Today's result: pending" status or "Vibes are perfected. Well done."

- a lot of the color scheme feels AI somehow. It's interesting, because it's not like the colors are wrong or anything, they somehow just feel like "default" LLM colors

- same thing with the typography


Yeah it's definitely a mix of AI and me haha. The names, color schemes, and status texts are good callouts. The emojis I actually introduced to start to have a theme across games, though I didn't put them in the org chart game. A lot of the copy was written by AI, and then I didn't like the output and changed it.

I appreciate the feedback that it felt off. That's what matters in the end. Thanks for the taking the time to share this.


Does anyone have more context on how this would be used? Is this like an alternative to using a midi keyboard to control synths? Is the appeal of it that it is small and meant to be played one handed while your other hand does something else?


There are lots of pedals these days that are designed as performance instruments in their own right. Check out the Erica Synths Nightverb; it's all chonky knobs and it doesn't even have stomp switches. You'd never put it on your floor.

Storm Summoner takes a pedal with lots of parameters [that would normally be set-and-go] and gives it that missing live performance UX. Singers in particular could use the sensors to modulate their voices.

What excites me is the flag-based system described in the review video at 11:45. You can set up stuff to happen (launch an LFO?) in response to other things that happen, like a value crossing a threshold. That takes it out of the realm of a dumb controller, and we already have enough dumb controllers.


You configure a preset, then touch to change presets while playing instead of kneeling down. Its like a remote control for MIDI effects pedals. Probably more useful if you have complicated live setup with a long setlist filled with a lot of effects.


They've had a preview version of this available as ts-go for a while now, and I've been really happy using it on my projects. I just installed it and changed "tsc" to "tsgo" in a couple places and it just worked. I don't remember exact numbers, but I think an approximately 10x speed up is a reasonable estimate for my build times. They went from noticable-but-not-bad to imperceptibly-fast.


I'm looking not only for better build times, but for lower memory usage - running few LSPs on a large TypeScript codebases currently takes a lot of RAM.


I did not understand why all the commentary in the game was about giant peanuts until I read your comment. Thank you!


You could do some sort of adaptive quality where you spend time incrementally improving fidelity until your frame budget is up. In practice I think that might be trickier than it sounds, but I feel like theoretically there's something there that could get you the best graphics your rig can handle without dropping frames. I've been considering doing something like this when I've been building a game/engine lately.


There's only so high you can go because the game assets have a maximum quality. Maybe you'll be able to max out the 5090 but what about the next flagship GPU?

You're also likely not going to maximize all of bandwidth, compute, etc. because one of them will likely be your bottleneck. And it might be different depending on the GPU, too.


Most games are strictly scaled on resolution due to how deferred pipelines run. This is exactly the slider to max or not max everything on a gpu for games. The more pixels the more memory and the more compute.


If you're rendering at native resolution, which many PC gamers do, going higher isn't significantly better because it just helps with antialiasing via supersampling. There's no point rendering so much more pixels just because you can, that's just a waste of electricity.


The more pixels, the more compute of fragments but not necessarily more memory. A fragment might hit the same texel as an adjacent fragment.

Certainly not more from main memory, and maybe not more from the vram either depending on how the pipeline goes.

It's not a linear slider.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: