bombela

10 ms·

151.
by bombela 1y ago
This might not seem obvious. So allow me an attempt at expanding a bit. The difference is that a dangling raw pointer to the heap will point to anything that can be modified at any time. But indexing a dynamic array guarantees that every el
152.
by bombela 1y ago
Not op. But my experience is both. It's impossible to get Google to search for a specific region in a specific language. DuckDuckGo is far better on this. You can use add regions to search for, and quickly toggle them.
153.
by bombela 1y ago
It used to be possible to run web pages and applications not full screen. But moderne UIs are so wasteful of space, with massive icons, it has become almost impossible.
154.
by bombela 1y ago
Even doing zcat | grep is faster than journald. I now turn off journald and use rotated pain text log files. It's more efficient in all metrics.
155.
by bombela 1y ago
Why don't your ISPs just use IPv6?
156.
by bombela 1y ago
The removal of the phone jack is so obviously planned obsolescence, it is ironic that this project for sustainability follows the trend. Wired headphones still have better sound quality. Don't need charging. Don't break with softw
157.
by bombela 1y ago
I have never had such a problem. And I have been installing Linux (distros) since 2003.
158.
by bombela 1y ago
I have AT&T fiber 1Gb/s symmetric in the bay area. It is much better than the XFinity coax/cable from before. I still have random slow down and packet loss though. I suspect the shared fiber is oversubscribed one too many time
159.
by bombela 1y ago
Notice how everybody replying says "less than 5s". As if anything done on a machine going through 10_000_000_000 (10 Giga) instructions per seconds should be anything but perceived instantaneous, for it's finite lifetime huma
160.
by bombela 1y ago
Oh yes, it is part of the spec for IPv6 addresses text representation :) https://www.rfc-editor.org/rfc/rfc4291#section-2.2
161.
by bombela 1y ago
Nah I truly do it the wrong way around. Syncthing on the git repos. And one of my device in the Syncthing cluster does btrfs snapshots minutely for recovery and further backups. Because it's at a personal scale, the only time I can cor
162.
by bombela 1y ago
I can forgive exponential as a figure of speech. You missed when they describe using a map for the side effect of [key] dedupliction. Instead of saying "set". The code itself uses the type "strset".
163.
by bombela 1y ago
> Be aware that even with these recommendations, syncing in this way has some risk since it bypasses Git’s normal integrity checking for repositories, so having backups is advised. You may also wish to do a git fsck to verify the integri
164.
by bombela 1y ago
At home, with both ip v4 and v6. For any device exposed on the Internet, I add a static IPv6 address with the host part the same as the IPv4 adress. example: 2001:db8::192.168.0.42 This makes it very easy to remember, correlate and firewall
165.
by bombela 1y ago
dedup on btrfs requires to setup a cronjob. And you need to pick one of the dedup too. It's not completely invisible in my mind bwcause of this ;)
166.
by bombela 1y ago
In 3D printing, I often catch people talking acceleration in kilo-milli-meter/second². Written and pronounced "16k accel". Instead of writing "16m/s²" and pronouncing "16 accel". I have nightmares of
167.
by bombela 1y ago
Why not simply: let mut data = Vec::with_capacity(sz); data.extend(&buf[..sz]); Vec::extend extends a container from an iterable. A Vec/slice is iterable. And from the doc: > This implementation is specialized for s
168.
by bombela 1y ago
And I would sell tickets (at a loss, ). Because whats something cool if nobody witnesses it.
169.
by bombela 1y ago
Rust has succeeded in making us hesitant reaching out to raw pointers. To the point we sometimes forget that we can opt-in into unsafe raw pointers on demand. Unlike C/C++ being opt-in to maybe somewhat safe.
170.
by bombela 1y ago
I usually teach it by translating it to our physical world by way of an object like a book, which I like to think is intuitive. I have a book. I own it. I can read it, and write into the margin. Tear the pages off if I want. I can destroy i
171.
by bombela 1y ago
For me, Comcast only allowed a few models. Because it requires full control. They uploaded a Comcast firmware on it. And they warned me that after that the device is basically stuck to only work with Comcast. This was around 2017.
172.
by bombela 1y ago
Brain was not fully loaded yet, thank you. I don't think the struct in struct is relevant in your example by the way. i32 requires 4-bytes alignment. An array of a struct{3×i32} will be aligned to 12 bytes. Which maintains the 4 bytes
173.
by bombela 1y ago
How could it not be a power of 2? The compiler makes sure to align fields and pad structs to power of 2 anyways.
174.
by bombela 1y ago
protobuf is more friction, and actually slow to write and read. For better or worse, CSV is easy to produce via printf. Easy to read by breaking lines and splitting by the delimiter. Escaping delimiters part of the content is not hard, thou
175.
by bombela 1y ago
What matters in this discussion is the outcome. For the exact same logs: journalctl takes 10s to search through 4GiB. And misses most of the matches. (rip)grep takes (0.1)0.5s to search through 605MiB. In other words. journalctl consumes mu
176.
by bombela 1y ago
The equivalent of the C++ move in Rust are the function take/replace (like mem::replace ajd option::take). And it is fully memory safe. You can build all the ownership you want by using raw pointers in Rust. And there is nothing wrong
177.
by bombela 1y ago
> My results don't match your conclusion. Alright. Let me entertain you. In the data I provided, counting the lines in a big log file was 469.5 times faster than journalctl took to output all the logs. From this information alone, i
178.
by bombela 1y ago
I wouldn't have said it better or more thoroughly.
179.
by bombela 1y ago
journalctl --grep is still much slower than grep on simple files. And if you use ripgrep like I prefer, it's even faster still. No really I don't think journactl makes sense in its current form. It's just broken by design. I
180.
by bombela 1y ago
I find move by default refreshingly simple. I don't even understand what is so hard to understand about move. A move is a simple memcopy + the certainty that the source is unreachable. This is important if the memcopied object holds re

More ›