The only downside is that it won't stop UDP packets from getting to a UDP listener. There will not be a response but the application will still see it.
Try:
ip route add src ${net} blackholeHN user
The only downside is that it won't stop UDP packets from getting to a UDP listener. There will not be a response but the application will still see it.
Try:
ip route add src ${net} blackholeThe OS is a thin layer providing an abstract and consistent interface regardless of the hardware configuration.
This is called a hardware abstraction layer, not OS.
System WebView but Electron is now the system
The operating system has historically trusted the applications not to do dumb things too much.
Only now we're witnessing the consequences much more frequently thanks to accelerated slop.
(zenzi)³
I mean zenzi-cubic
China has proxies that sell cheaper access to frontier models in exchange for permission to train on your data.
Right.
As an example: Oracle and PostgreSQL don't have dirty reads: READ UNCOMMITTED does nothing. MySQL's concurrency model depends on the engine.
What keeps users themselves from vibe-coding their own software?
If you don't own quality, why should I pay? You're just a middleman at that point.
If you squint hard enough, you'll notice your bank account serves as an IPC semaphore replenishing API credit balances.
Your wallet is now a real-time communication channel.
With consent, yes.
No, "virtual machine" alone doesn't make things safer.
Shrink your attack surface.
Use a completely locked down seccomp. Use nsjail or gVisor for containers. Use microvm or libkrun for full OS.
Lesser attack surface is what matters. Virtualization is only half of the story.
Avoiding problems outside your business problem domain, and can therefore guide the AI more effectively towards building the right thing.
(Note that this still assumes that each biased-coin toss is i.i.d.)
They are orthogonal.
Suppose you have 100ms audio latency and no wait time. Then, natural pause will trigger response immediately but you won't notice it has started until after ~200ms (round-trip time). Twice as annoying.
But it's still a bit more difficult to sue them for leaking your company's data.
At least for now.
You can write unambiguous (UB-free) code and the compiler's output will be deterministic. There will even be a spec that explains how your source maps to your program's behavior. LLM has neither.
Also, if you need to control performance, you still need to know how CPU cache and branch prediction works, both of which exists at the abstraction level of assembly.
How can you read a language you didn't learn?
PatchGuard would like to have a word with you.
Ironic, since Unix is itself an embodiment of "worse is better."
I used floating timestamps as some kind of an identity. If there is ever a conflict, I just increase it by 1 ulp until it doesn't collide with anything. Sorry.
In Python, `shlex` has utilities for quoting and tokenizing strings for POSIX shells.
Documentation: https://docs.python.org/3/library/shlex.html
(Windows users: CMD is hopeless. Sorry. Try powershell.)
Finally, a DOOM download that bypasses captive portals
There are better techniques for hyper-parameter optimisation, right?
There always are. You need to think about what those would be, though. Autoresearch outsources the thinking to LLMs.
This is exactly what subinterpreters are for! Basically isolated copies of Python in the same process.
https://docs.python.org/3/library/concurrent.interpreters.ht...
If you want a higher-level interface, there is InterpreterPoolExecutor:
https://docs.python.org/3/library/concurrent.futures.html#co...
why we keep trusting venture capital to be the community's stewards I have no idea.
They bought the trust.
Well, tell that to OP, not me.
Does appending "/genq" work?
Or use the /btw command to ask only questions
It was kind of an experiment from start. Some ideas turned out to be good, so we keep them. Some ideas turned out not to be good, so we fix them with extensions.
if your framework's value can be replicated by targeting its test suite,
Side note: this is also why SQLite's full test suite is proprietary / private
Except that merely surfacing them changes their behavior, like how you add that one printf() call and now your heisenbug is suddenly nonexistent