I'd back a bill to ban AI from scholls in many contexts, just like phones I think it's pretty obvious what the result will be.
I guess like with phones we'll all have to pretend it's not obvious for ten years until we have overwhelming scientific evidence, then wait another ten for US policy makers to start talking about making a committee to design a study to develop a plan
I believe the tolerances to the fan housing (which reduces turbulence and thus noise), and the the material stiffness needed for that small tolerance, are the alleged reason there are few copycats. Supposedly getting plastic that rigid is hard. I've tried to find hard numbers and validate that claim, but I wasn't able to. Would probably have to measure an actual noctua fan blade to know. On the other hand, metal printing is attainable now..
While metal printing is attainable..it generally produce shit, surface quality wise. You still need to CNC that if you want a surface roughness not measured in mm
And is not like a 5axis could not produce these fan geometries from a block
These young people have seen less in their life, and a much larger percentage of their life was filled with the advertising of the AI companies. So no wonder that they are a little bit slower seeing the limitations of the AI models.
I don't think so. It's a part of general and wide-ranging technical ignorance.
They know how to navigate through the intricate settings of their favourite social app but debugging connection issues is too much (even on a very basic level, "can my browser access the same site?").
The value of writing is found in the density of information and something harder to define, something like 'art' or 'humanity'.
This post did not have a good ratio of words to those quantities
Pretty sure by devx they mean something like syntax ergonomics. Because otherwise rust's devx first class (cargo, clippy, crates.io) so kind of a nonstandard definition.
I think it's fair to say Java's "syntax ergonomics" are a little below the rest / somewhat manual like rust or C++ by default.
go's type system is significantly more limited in what it can do for you, as opposed to rust or ts. Limited syntax seems to be one of the overarching design decisions for that language, making it more like C with better concurrency primitives. It can feel a bit limiting at times, but at least they have generics now and you can almost do things like union types by constructing interfaces that mimic them, but it isn't exactly ergonomic.
Based on your description, I think a good library for data structures that are intended to be used immutably would help with some pain points. Something with copy on write support or something like that. It's a powerful style, used it in haskell and it prevents a large class of bugs, almost down to just business logic bugs, which is what you want.
I like the style you're describing, thanks for sharing.
This various a lot between compilers. Clang for example treats O3 perf regressions a bugs In many cases at least) and is a bit more reasonable with O3 on. GCC goes full mad max and you don't know what it's going to do.
He's been impeached by the _house_ not by the Senate. The US Senate is extremely complicit with the administration. Something the founders did not intend
I guess like with phones we'll all have to pretend it's not obvious for ten years until we have overwhelming scientific evidence, then wait another ten for US policy makers to start talking about making a committee to design a study to develop a plan
reply