mianos
It gets so stupid it's frustratingly useless when it does not follow instructions give just a few prompts back.
When you build an LLM, you base it on an immense knowledge base that you didn't create yourself.
It processes that information and, in simplistic terms, constructs its own underlying logic based on what it read. It's once removed from your direct instructions. If you think a human can manually edit or curate all that input content, go for it.
The developer who built the application isn't the author of the output, it is authored by the billions of data points it was trained on. Its choices and biases stem from that training data. No human is writing those billions of logic statements. The LLM is generating its own responses from the input knowledge, not the developer.
Keyboard traffic is plain. Bluetooth access depends on where you are positioned. DVI is not hard to decode for capturing the entire screen. KVMs are so small now that one could easily be snuck in. Even though the motherboard is very compact, there is space above it and near the batteries.
The issue with floating point and aliasing preventing vectorisation was from the late 1980s when early C compilers lacked sophisticated alias analysis and standards were loose. is not a really a thing anymore. C can go as fast, specially compiled with strict aliasing. Maybe more work in compilation.
If you walk into a shop, the US is much more like Australia in terms of service and attitude (even though retail staff are paid vastly differently).
I always thought this was due to TV and Australia having remote branches of many US retail chains.
Outside of California, it's similar but diverges a lot in areas like socialism. In the recent 20 years Australia has pretty much become more like the EU in terms of socialism.
Claude does it occasionally but it's a more a soft landing earlier context seems to be compacted, not completely lose the plot.
I just cancelled my pro subscription. I really wanted it to be good but not yet.
Maybe this might be valid if this was a realistic thing and every bad driver who pulls out of a side street and kills someone suffers serious consequences, but they don't and it's not.
Whether individuals inside the system are true believers or cynical operators, the response to calling out their methods will be identical:
If they genuinely believe the rhetoric: They will simply double down and say, 'Yes, and protecting the children makes this absolutely necessary.'
If they know it is a manipulation tactic: They will still reply with, 'It is for the children,' because they know it is an impenetrable PR shield that gets them their way.
In either scenario, the bureaucracy is entirely immune to the criticism.
Exposing the game might help persuade third-party observers, but it does absolutely nothing to stop the bureaucratic machine from using that exact same line to steamroll the agenda forward.
The immediate reply is the accusational: "why are you trying to trying to prevent safety for kids".
It's a simple next step to accuse you of hiding your own child abuse ring.
This sounds like hype, but it's the normal path here in Australian.
I really like it as I run a webdav service and can read/write and sync notes between multiple Mac desktops and Android. Encrypted while I am at it.
Markdown native.
Anyone smarter than a 10 year old would not we actually know almost everything about car design. How it works is not at all hidden. We have iterated on pretty much the same thing for 100 years. The current state is about efficiency, materials and manufacturing.
When you have deep knowledge and experience in a field you will get near 100%.
- Instant, zero-copy container cloning from images via Copy-on-Write. If you boot a new image like the existing ones it's seconds.
- Atomic, millisecond-level instance snapshots regardless of storage size
- Block-level container migration using native 'zfs send' and 'zfs receive', very short command lines and seems to work perfectly.
- Granular dataset nesting (every instance, image, and custom volume gets its own ZFS dataset). You can see every filesystem even on the host.
- Transparent, inline data compression (LZ4/ZSTD) enabled automatically per dataset. For services that don't change much, you might as well use a compressed image to make them even smaller.
- Mirroring / Raid
- Sub-volume sharing and direct management via native ZFS administration tools. If my home directory has a build area and a million files, I can just save time and put my home, pre cooked into a new machine and not copy or even rebuild on my new machine.
- Dedup keeps blocks with the same data as a reference. This costs a lot of memory and has not saved much for me as a lot of my images are similar and already shared I think, but it's cool.
It's pretty much like any new car as far as entertainment and maps. Plus, it's got physical buttons for everything else. I think recent cars may well be coming back to what I have on my old car.
ps. not mentioned, Anrdoid auto and Carplay are H264, later H265, video players with touch control and buttons in a return channel. The phones render the display internally and project it as video to the display. That's all. This is why much older generation displays with at least reasonable SOCs can run them near perfectly. They are not running Anrdoid themselves. In fact some of them are operating system-less SOCs that have nearly no firmware but a video player and the support for the touchscreen and buttons. Much like that crappy video player built into old TVs ten years ago.
I have them on my motorcycles too. It's way better than a phone, in that the user interface is designed to be less interactive and more focusses with larger buttons.