That area between 60-120Hz is where the most bass info lies in music today. I feel many subwoofers focus on the lowest Hz number rather than being musical, fast and invisible.
I don't really care if I'm hiring a strong lead for an area if the strategy comes from them or comes from somebody else. I just care that there is a amazing strategy and everyone has bought into it
if you look at it 10 years from now, what are we be the winning company? This is just my personal view. The one that articulate and laser focus on one niche area and also find the right partner and also able to scale the company.
and then the power and the cost and then you can double the performance but you cannot double down on the cost and and area. So those are the thing you have to give give way unless you find some new way of material new way of design.
My opinion is that the least mature area is front end. There have been some attempts to compile Rust to Web Assembly and then run it on the web as a front end as a replacement for TypeScript. But if I was writing a web server, I would totally use Rust for the back end and TypeScript for the front end. I would not really go the web assembly route.
and even if you take a generous interpretation of 128 * 8 gig transfers, you're at 128 gigabytes a second for the same shoreline versus 2 and a half terabytes a second. There's a there's an order of magnitude difference in bandwidth per edge area.
building a third-party client to read and route messages is a gray area in their terms of service, and perhaps only partially supported in their API surfaces.
Big flat toggle buttons under satisfying tension. Clear affordances. You push them down, not in. One click catches, one doesn't. You can use them with bare hands, oven mitts, fingers coated in slippery whatever. Doesn't matter. Plenty of surface area. Outstanding design. It's all been downhill from there.
the coffee bed would act on these molecules by filtering them out a bit like oxygen adsorbers keep oxygen in; it just provides a gigantic maze of free surface area for them to stick on, and hopefully the microscopic fluid velocity is gentle enough to not drag them along.
And if I'm starting to see like more and more experiments that are not statistically significant, that may be a signal to me to say, okay, we might have kind of tried to exploit a little bit too far. Like there might not be as much juice to squeeze.
And actually the reason I think it's exciting is if you look at like the database space right now there's not one database. If you want to do largecale data analytics you'll choose one thing. If you want to do a transactional data store you'll do another. I think we're moving to that area of models
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.