raggi

35 ms·

241.
by raggi 2y ago
I assume this will need to change the shared memory header protocol so either SQLite comes along for the ride or this is an incompatible ABI?
242.
by raggi 2y ago
yep, the iphone is comparably terrible in this area, even with the myshake app
243.
by raggi 2y ago
just wait until you see the real conspiracy
244.
by raggi 2y ago
There’s a one-sentence implied claim in here that raii is the reason for c++ rejection and rejection of c++ implies rejection of raii. The author is clearly unaware of the recent cleanup attribute infrastructure submitted on the c side of t
245.
by raggi 2y ago
This article implies that batch allocations are some kind of panacea and that raii has no place there. Neither of these implications have any case made for them, just links to other publications that do the same. It also alludes to downside
246.
by raggi 2y ago
Read and write a lot of projects. Early career you need to get out there and see things. If you find stuff others are working on too all the better (e.g. OSS but there are other things like charity or public projects too)
247.
by raggi 2y ago
Have the new security and encryption features received review?
248.
by raggi 2y ago
the original had more microsoft smells https://microsoft.github.io/DirectX-Specs/d3d/archive/images...
249.
by raggi 2y ago
Preexisting choice and strong holding bias in the organization
250.
by raggi 2y ago
Same, I work in Go most of the time in performance and memory sensitive areas and the lack of usable abstractions grates so hard. I’m increasingly fed up of long hand everywhere and the bug volume and frequency it inherently produces partic
251.
by raggi 2y ago
I went in half expecting to see another spin heavy solution, so glad to find futexes used properly, cache line sharding and so on. Yay, practically scalable mutexes rather than microbenchmark winning hacks!
252.
by raggi 2y ago
This is less true in "how the language works", and more true in "code I have read in these languages follow these patterns". The latter I agree with, the prior less so. Rust is more type heavy sure, but there are plenty
253.
by raggi 2y ago
It's very probably true in the totality of "as expressed in a real build for all configurations and architectures", too much variation of behavior to have the whole map in mind at once. You can work through it potentially, an
254.
by raggi 2y ago
rustc does not yet no, there's a lot of hope in the gcc rust frontend to help bridge the gap, but also there is increasing support in llvm for more architectures and things like this should drive interest in accelerating those projects
255.
by raggi 2y ago
If you're curious about the RFC IPR: https://datatracker.ietf.org/ipr/2554/
256.
by raggi 2y ago
Yep, I work on low level networking software professionally and this post is largely meaningless dribble and is probably motivated by grandstanding. It’s like an engineer who says “how does a screen show black” and then says “nope” to every
257.
by raggi 2y ago
Very interesting, thank you. We’ll take a look at this!
258.
by raggi 2y ago
this is a bit of a distraction, sure the leaks and some of the deadlocks are fairly uninteresting, but the toctou, overflows, uid race/confusion and so on are real issues that shouldn't be dismissed as if they don't exist.
259.
by raggi 2y ago
https://github.com/tailscale/tailscale/pull/2370 was a practical drive toward this, will not proceed on this path. much more approachable, boats has written about challenges integrating in rust: https:/
260.
by raggi 2y ago
13 CVEs so far this year afaik
261.
by raggi 2y ago
> I don't think io_uring is as complex as its reputation suggests. uring is extremely problematic to integrate into many common application / language runtimes and it has been demonstrably difficult to integrate into linux safe
262.
by raggi 2y ago
we can consider ebpf "a solution" when there's even a remote chance you'll be able to do it from an unentitled ios app. somewhat hyperbole, but the point is, this problem is a problem for userspace client applications, a
263.
by raggi 2y ago
it was originally for the hardware, but it's also valuable on the software side as the cost of syscalls is far too high for packet sized transactions
264.
by raggi 2y ago
UDP offload gets you implicitly today: - 64 packets per syscall, which is enough data to amortize the syscall overhead - a single packet is not. - UDP offload optionally lets you defer checksum computation, often offloading it to hardware.
265.
by raggi 2y ago
There are a number of concrete problems: - syscall interfaces are a mess, the primitive APIs are too slow for regular sized packets (~1500 bytes), the overhead is too high. GSO helps but it’s a horrible API, and it’s been buggy even lately
266.
by raggi 2y ago
No, this idea that unsafe blocks “are not rust” is wrong. Getting unsafe correct is hard, and so needs to be approached with care and first time buyers would do well to get advice from a friendly neighbor, but it’s a normal solution to some
267.
by raggi 2y ago
Brotli and zstd are close, each trading in various configurations and cases - but zstd is muuuuuch more usable in a practical sense, because the code base can be easily compiled and linked against in a wider number of places with less effor
268.
by raggi 2y ago
It’s not prioritization of the code - it’s relatively little implementation and low maintenance but security is critical here and everyone is very afraid of compressors because gzip, jpeg and various others were pretty bad. Zstd, unlike lz4
269.
by raggi 2y ago
Chromies got in the way of it for a very long time, but zstd is now coming to the web too, as it’s finally landed in chrome - now we’ve gotta get safari onboard
270.
by raggi 2y ago
This is excellent marketing material for LLMs!

More ›