zakisaad

I think this is more about workspace state, not saving working data to disk.

On Linux mainly, and almost strictly for compute workloads (not much need to optimize for 3D workloads given the customer base).

Model weights (what is being tested here) don't inherently "access the web" when inference is running. If the model has access to a web search tool, that's a different story.

This is the reason why performant and "safe" systems languages are on the rise and being accepted into foundational areas of our operating systems (such as the kernel). When the attack defense surface is tighter (language, tooling, compiler instead of the actual code itself), the smart folks can stay at that layer, while the masses can write more code at a level of abstraction that nullifies many of these vulnerabilities by default.

Any chance you could drop the set of feeds? Would be very interested!

Turbos have entered the chat

raises hand, but point taken when painting with broad strokes

> I hate spending money on hardware so i'm living with it

This is an odd take to me, as personally I'd be more willing to spend money on well designed and made hardware, than most software.

This is not at all aligned with my experience. Do you have a source for this?

This is a wild take. All cars can perfectly drive around a track, so why would you ever want an F1 car?

This is interesting to me - why'd you go with the 5070 for your 4x build?

At first thought, they are quite skewed toward compute (vs VRAM), which is great for gamers but not so great for running LLMs.

(I run a 5070 in my desktop)

How do you define "correct" code?

I guess my intent was not to point out that it has a mechanical key, rather that the description of the key on the webpage was wrong (it is not hinged).

The mechanical key fallback pattern is standard across the industry for sure.

This was stated about the key: "Folded into the base is a mechanical backup key, a flat metal blade in a hinged housing."

I own a BYD: this is not true. The key is not hinged; rather, the entire mechanical key pulls out when a small clip is unlatched near the top of the assembly (you can see it in the CT). I assume the circular hinge-looking mechanism in the CT is just a by product of the plastic/metal weld process.

Nonetheless: very cool tech demo!

We're currently at this stage with out kids, too.

I think the staunch "no screen" mentality is a broad-stroke lever that non-technical thought leaders in the child wellness space have stuck to, and I understand where they come from.

Though, as someone who owes his livelihood to being able to tinker and experiment with technology as a child, I'm looking toward a more measured approach. I may very well set up an airgapped Linux box (Windows has come a long way since the XP days, and gone entirely the wrong way) and let my kids proverbially "have at it" - this way, they can't get stuck in big tech's psycho-loops or sucked into YouTube's colourful dopamine machine - which I think, is the entire drive behind "no screens".

I think well-measured exposure is imperative.