jedisct1

13 ms·

271.
by jedisct1 2y ago
Even PHP is a perfectly fine, memory-safe language.
272.
by jedisct1 2y ago
"safety" != "memory safety" A formally proven implementation could be called "safe". But code written with checked arrays and without explicit pointers isn't magically safe, and promoting a language or a c
273.
Juice confirms that Earth is habitable(esa.int)
4 points by jedisct1 2y ago|1 comments
274.
by jedisct1 2y ago
Cool stuff, with a very simple API.
275.
by jedisct1 2y ago
Same for me with OVH and Scaleway. Way cheaper than AWS and friends, and they just work.
276.
by jedisct1 2y ago
Do people really care about the engine being used under the hood? From a user perspective, I see no difference between Blink, Webkit and Gecko. And when there is, it's a website that has only been tested on Blink, or uses features not
277.
by jedisct1 2y ago
Also Piknik: https://github.com/jedisct1/piknik The first thing I install on any new computer.
278.
by jedisct1 2y ago
AI for security doesn't work, never will.
279.
by jedisct1 2y ago
Jasmin has largely replaced qhasm.
280.
by jedisct1 2y ago
A Python interpreter has to be written in every language.
281.
by jedisct1 2y ago
clang (just the C frontend, not talking about the backend, not clang++) is an old code base. It's become very complicated to understand, maintain and extend. Zig helps a lot, but in comparison, Aro is small, and simple to understand an
282.
by jedisct1 2y ago
Zig has a built-in test-case reduction command ("zig reduce").
283.
by jedisct1 2y ago
Bun has a built-in Jest-compatible test runner https://bun.sh/docs/cli/test
284.
by jedisct1 2y ago
Zig implementation: https://github.com/jedisct1/zig-aes-gem
285.
by jedisct1 2y ago
This is not a new cipher. The approach is actually very conservative. Moving slow is fine, but the reality is that the current options are not great for today's use cases. They're very easy to use insecurely.
286.
by jedisct1 2y ago
This is a great proposal. It would have been a good opportunity to leverage the AES-PRF construction (see tosc.v2018.i2.161-191 in addition to the original paper), whose overhead is negligible. But unfortunately, FIPS restrictions is why we
287.
by jedisct1 2y ago
Hard to compete with Bellard :)
288.
by jedisct1 2y ago
First thing to check before buying a router: if the firmware can be replaced with OpenWRT.
289.
by jedisct1 2y ago
Congrats for the 1.0 release! doggo has been my main DNS tool for a while, now. Love it!
290.
by jedisct1 2y ago
The Bun team is really good, and Zig is a productive language. But there's also the simple fact that when you reimplement something, it's always going to be easier and faster than it was to write the previous implementation. You k
291.
by jedisct1 2y ago
> "WASM support was just as smooth in Rust as in Zig". There are still way too many Rust dependencies that don't support WebAssembly, and even functions in the standard library that compile but will crash at runtime on Web
292.
by jedisct1 2y ago
Along with Go, it's the most please and most productive language I've used for the past 10 years. And I honestly think I'd have completely stopped writing code if I hadn't discovered Zig, after Rust made me hate what I u
293.
by jedisct1 2y ago
Zig allocators can be composed, so adding zeroization would be trivial.
294.
by jedisct1 2y ago
Not just AES-GCM. The vast majority of encryption algorithms must be used in a nonce-respecting scenario. This is part of the contract to achieve the claimed security properties. Alternatives require multiple passes over the data, which is
295.
by jedisct1 2y ago
On Atari ST, Neochrome was such an awesome pixel art editor. I spent countless hours designing fonts pixel by pixel using it.
296.
Hyper-optimizing the Zig Parser [video](youtube.com)
2 points by jedisct1 2y ago|0 comments
297.
by jedisct1 2y ago
Try Arc. You won't be looking back.
298.
Zignal: An image processing library written in Zig(github.com)
3 points by jedisct1 2y ago|0 comments
299.
by jedisct1 2y ago
It's so sad that DNSCloak hasn't found a new maintainer.
300.
by jedisct1 2y ago
It's convenient, and probably fine when imports are unambiguous. The problem here is that there were multiple possible imports for the same name, and in such situation, the extension picks an arbitrary one. It feels rather like a bug (

More ›