jrpelkonen

10 ms·

91.
by jrpelkonen 3y ago
Unrelated, but this reminded me of this old chestnut that still makes me smile. It is from comp.lang.c FAQ, e.g. < https://www.cs.rpi.edu/courses/fall96/netprog/cfaq.html >: The cost is $130.00
92.
by jrpelkonen 3y ago
I skimmed thru the post, and did not find the arguments convincing. For instance, the example seems to be watered down from the Linux mmap man page. Thus it appears that awareness of mmap and it's man page makes one a "C ace"
93.
Cat,cp,mv,dd,install,split: set the default IO size to 256KiB(git.savannah.gnu.org)
16 points by jrpelkonen 3y ago|1 comments
94.
by jrpelkonen 3y ago
Looks interesting. I just wonder if there will be Rust native TLS options available in the near future.
95.
I'm eating raw chicken every day for 100 days – or until I'm hospitalized(nypost.com)
13 points by jrpelkonen 3y ago|49 comments
96.
by jrpelkonen 3y ago
Using math/rand seeded with a timestamp to generate crypto materials does not instill high confidence in the skills of the team. But their lack of interest in addressing the issues raised here is perhaps even more worrying. If I was a
97.
by jrpelkonen 3y ago
Brings back memories from time when printed documents were still the norm. A coworker used to call it my "seal of approval" if a document was on top of my desk long enough to accumulate a hefty dose of coffee stains.
98.
by jrpelkonen 3y ago
Very prudent of them to not hand those addresses out like candy. They don’t want to wake up one morning and realize that they’ve run out!
99.
by jrpelkonen 3y ago
From the linked thread: > The most difficult issue to get right is cache invalidation. For sure, right up there with naming things and off-by-1s.
100.
by jrpelkonen 3y ago
This is a good point: there are many niche architectures where Rust is not a viable option. But in this specific case, I don’t see these system benefiting from h3/Quic. HOL blocking etc. will rarely, if ever, be a limiting factor for t
101.
by jrpelkonen 3y ago
I really don’t want to criticize anyone or their hard work, and appreciate both curl and OpenSSL as a long time user. That said, I personally find it disappointing that in 2024 major new modules are being written in C. Especially so given t
102.
by jrpelkonen 3y ago
Personally, I’d like to see the data/research behind the “3x” claim to buy it. Especially when it is hard to imagine Sam Altman as an unbiased observer when it comes to benefits of AI.
103.
by jrpelkonen 3y ago
Maybe so, but pretty much all cryptographic primitives have to be written in assembly anyway to achieve constant time operation. Furthermore, it has a ring compatible API, and it is evidently faster than ring itself[1]. [1] https:/&#x
104.
AWS Libcrypto for Rust(github.com)
91 points by jrpelkonen 3y ago|26 comments
105.
by jrpelkonen 3y ago
In this particular case the change required (K&R to ANSI C) is such a mechanical exercise anyone with a modicum of C experience can perform successfully. We’re not talking about decades of taxation rules encoded with COBOL here.
106.
by jrpelkonen 3y ago
I switched to fish a few years ago as well. Great productivity boost for very little fuss. I still write my scripts in bash, though. I feel it’s counterproductive to expect the script user to download fish when bash is already preinstalled
107.
What Unsafe Rust Can Do(doc.rust-lang.org)
2 points by jrpelkonen 3y ago|0 comments
108.
by jrpelkonen 3y ago
Implementing the comparisons by hand seems difficult and primitive. May I suggest introducing some helpful sub-packages and building the solution on top of those. For instance, is-odd would be implemented by using is-one, is-three, is-five,
109.
by jrpelkonen 3y ago
Cargo makes it rather seamless to include the async runtime that best suits your needs. I am curious why do you think this is a major issue?
110.
by jrpelkonen 3y ago
DRM already uses a trusted execution environment (TEE), which provides more robust isolation than a VM. Thus I doubt needs of video streaming apps are the main motivation.
111.
by jrpelkonen 3y ago
Sure, Artifactory, etc. have their places. But I am objecting to your "no true scotsman"[1] type of argument. Furthermore, the most bizarre setups I have seen have been in "serious" enterprises. Hardly an endorsement. 1:
112.
by jrpelkonen 3y ago
Great quote and so true in the general case. Unfortunately, I have seen some database designs that have left me more mystified than I was before.
113.
by jrpelkonen 3y ago
Segfaults are not actually even the worst outcome, corrupting the program state yet still trucking along can lead to far worse consequences.
114.
by jrpelkonen 3y ago
This is an excellent post about the evolution and the milestones that lead to the current async Rust approach. I thought the technical arguments were clearly articulated, dispassionately responding to the recent critical viewpoints regardin
115.
by jrpelkonen 3y ago
Smart move? He was not offered a plea bargain, so going to trial was the only option.
116.
Zngur: A C++/Rust interop tool(github.com)
2 points by jrpelkonen 3y ago|0 comments
117.
by jrpelkonen 3y ago
Same. We could both be weird. Or not.
118.
by jrpelkonen 3y ago
True, but git also has pretty simple means to fake committer identity, rewrite commit history etc. Storing it to GitHub was definetely a major faux pas. However, it seems that the FTX people were not really bothered to cover their tracks.
119.
by jrpelkonen 3y ago
It is possible that this is not a fault of the parser or tooling. In some cases, specifically when the video file is not targeted for streaming, the moov atom is at the end of the mp4. The moov atom is required for playback.
120.
Why Not Rust Crypto?(briansmith.org)
4 points by jrpelkonen 3y ago|0 comments

More ›