phoenk

Did they not target code tasks for this LLM, or is it genuinely that bad? Pretty embarrassing when your shiny new 400B model barely ties a 32B model designed to be run locally. Or maybe is this a strong indication that smaller, specialized LLMs have much more potential for specific tasks than larger, general purpose LLMs.

The commonly given response to this question is two-fold, and both parts have a similar root cause: smart pointers and "safety" being bolted-on features developed decades after the fact. The first part is the standard library itself. You can put your data in a vec for instance, but if you want to iterate, the standard library gives you back a regular pointer that can be dereferenced unchecked, and is intended to be invalidated while still held in the event of a mutation. The second part is third party libraries. You may be diligent about managing memory with smart pointers, but odds are any library you might use probably wants a dumb pointer, and whether or not it assumes responsibility for freeing that pointer later is at best documented in natural language.

This results in an ecosystem where safety is opt-in, which means in practice most implementations are largely unsafe. Even if an individual developer wants to proactive about safety, the ecosystem isn't there to support them to the same extent as in rust. By contrast, safety is the defining feature of the rust ecosystem. You can write code and the language and ecosystem support you in doing so rather than being a barrier you have to fight back against.

I would assume it just isn't a requirement in the majority of IoT projects, and omitting it saves on cost.

What you're describing is entrapment: https://en.wikipedia.org/wiki/Entrapment

Sometimes its legal, depends where you are and how it was done.

Looks like this is supported: https://support.apple.com/guide/iphone/external-storage-devi...

I plan on buying one, and I have a 3 year old android phone. I would have upgraded sooner, but I basically wanted an iphone 14 but with USB C so I don't have to get new cables. Now I can get that.

USB C is definitely more universal, it is used for laptops and peripherals and other random devices. Qi charging is mostly limited to phones and certain phone accessories, which usually also have USB C.

> Which is generally undesirable for commercial projects; especially early in their lifecycles when bugs may be present and would be best kept private until the project has been more battle-tested.

Copyleft only kicks in on redistribution. If you're only testing internally, you don't need to distribute source code. It's only once you distribute that software that you also need to distribute source.

The desktop application is the easiest way to get up and running on Mac or Windows where a VM is necessary. Of course you can still set up docker engine manually in a VM, but even then it doesn't offer the same level of integration, like host mounts, Rosetta on Mac. Desktop Linux is the only environment where the desktop app offers little benefit over just running the engine.

It isn't official, but headscale exists: https://github.com/juanfont/headscale