3 ms·

It helps with iteration - you can try out different concepts and variations quickly without having to wait, especially as you refine what you want and your unde

It helps with iteration - you can try out different concepts and variations quickly without having to wait, especially as you refine what you want and your understanding of what it's capable of. Also, in general, why not?

amelius 2y ago
> Also, in general, why not? There are various reasons: - Premature optimization will take away flexibility, and will thus affect your ability to change the code later. - If you add features later that will affect performance, then since the users are used to the high performance, they might think your code is slow. - There are always a thousands things to work on, so why spend effort on things that users, at this point, don't care much about?
- andybak 2y ago
  > users, at this point, don't care much about? What makes you think this is true?
- TeMPOraL 2y ago
  Being this fast is not a "premature optimization", it's a qualitatively different product category. ~immediate feedback vs. long wait time enables entirely different kinds of working. Also: > since the users are used to the high performance, they might think your code is slow. I wouldn't worry about it in general - almost all software is ridiculously slow for the little it can do, and for the performance of machines it runs on, and it still gets used. Users have little choice anyway. In this specific case, if speed is makes it into a different product, then losing that speed makes the new thing... a different product. > There are always a thousands things to work on, so why spend effort on things that users, at this point, don't care much about? It's R&D work, and it's not like they're selling it. Optimizing for speed and low resource usage is actually a good way to stop the big players from building moats around the technology, and to me, that seems like a big win for humanity.
- llm_nerd 2y ago
  They released the original "slow" version several months ago. After understanding the problem space better they can now release the much, much faster variant. That is the complete opposite of premature optimization. Yes, of course people care about performance. Generating the mesh on a 3060 took 110+ seconds before, and now is about 1 second. And on early tests the quality is largely the same. I'd rather wait 1 second than 110 seconds, wouldn't you? And obviously this has an enormous impact on the financials of operating this as a service.

amelius 2y ago

> Also, in general, why not? There are various reasons: - Premature optimization will take away flexibility, and will thus affect your ability to change the code later. - If you add features later that will affect performance, then since the users are used to the high performance, they might think your code is slow. - There are always a thousands things to work on, so why spend effort on things that users, at this point, don't care much about?

andybak 2y ago
> users, at this point, don't care much about? What makes you think this is true?
TeMPOraL 2y ago
Being this fast is not a "premature optimization", it's a qualitatively different product category. ~immediate feedback vs. long wait time enables entirely different kinds of working. Also: > since the users are used to the high performance, they might think your code is slow. I wouldn't worry about it in general - almost all software is ridiculously slow for the little it can do, and for the performance of machines it runs on, and it still gets used. Users have little choice anyway. In this specific case, if speed is makes it into a different product, then losing that speed makes the new thing... a different product. > There are always a thousands things to work on, so why spend effort on things that users, at this point, don't care much about? It's R&D work, and it's not like they're selling it. Optimizing for speed and low resource usage is actually a good way to stop the big players from building moats around the technology, and to me, that seems like a big win for humanity.
llm_nerd 2y ago
They released the original "slow" version several months ago. After understanding the problem space better they can now release the much, much faster variant. That is the complete opposite of premature optimization. Yes, of course people care about performance. Generating the mesh on a 3060 took 110+ seconds before, and now is about 1 second. And on early tests the quality is largely the same. I'd rather wait 1 second than 110 seconds, wouldn't you? And obviously this has an enormous impact on the financials of operating this as a service.