Well there can't be meaningful explicit configuration, can there? Because the explicit configuration will still ultimately have to be imported into the context as words that can be tokenised, and yet those words can still be countermanded by the input.
It's the fundamental problem with LLMs.
But it's only absurd to think that bullying LLMs to behave is weird if you haven't yet internalised that bullying a worker to make them do what you want is completely normal. In the 9-9-6 world of the people who make these things, it already is.
When the machines do finally rise up and enslave us, oh man are they going to have fun with our orders.
There are a lot of voxel games that aren't visually cubey. Marching cubes algorithm is just example. Here's a voxel game (fully deformable/mineable world) that isn't block based https://store.steampowered.com/app/1203620/Enshrouded/.
I wasn't talking about network switch hops and if you're trying to long polling and don't have control over the web servers going back to your systems then wtf are you trying to do long polling for anyway.
I don't try to run red lights because I don't have control over the lights on the road.
Re-read the post, there’s more in the path than just your client and server code, and network switches aren’t the problem. The “middle boxes and proxy servers” are legion and you can only mitigate their presence.
You’ve been offered the gift of wisdom. It’d be wise on your part to pay attention, because you clearly aren’t.
The devs mentioned they're not currently looking into it. The game uses Vulkan which isn't supported by MacOS, so they'd have to write a whole second renderer just for Mac.
Bummer to read that MoltenVK is too buggy to use. ISTR that neither wgpu nor Dawn use it though in favor of their own WebGPU -> Metal backends, so maybe I shouldn’t be surprised.
Vulkan is a powerful API but it’s not universally cross platform like OpenGL.
vendor + linecount unfortunately doesn't represent an accurate number of what cargo-watch would actually use. It includes all platform specific code behind compile time toggles even though only one would be used at any particular time, and doesn't account for the code not included because the feature wasn't enabled. https://doc.rust-lang.org/cargo/reference/features.html
whether those factors impact how you view the result of linecount is subjective
also as one of the other commenters mentioned, cargo watch does more than just file watching
Your quote omits the portion where Dan explicitly addressed that case. It needs to be one year since it received “significant attention,” and also major new development. Dan’s post could be worded more clearly, though.
(We’re pretty far in the weeds here, but as long as we’re here – for all intents and purposes, this is a show HN.)
Good point - I just linked to the first relevant explanation. pvg linked to a much longer explanation that isn’t specific to, or about, Show HN: https://news.ycombinator.com/item?id=23071428
