pornel

11 ms·

211.
Rust9x update: Rust 1.93.0-beta(seri.tools)
5 points by pornel 10mo ago|0 comments
212.
by pornel 10mo ago
That's not the spirit Rust wants to have. You can already disable borrow checker selectively by using "raw" pointers in places where you think you know better, and this is used very commonly. Every String in Rust has such raw
213.
by pornel 10mo ago
There is a cranelift backend written in Rust. Rust is pragmatic about its implementation. The goal isn't some ideological purity (despite the reputation Rust has), but to empower users to make safe and efficient systems software. LLVM
214.
by pornel 10mo ago
The compiler has deep assumptions about exclusive ownership and moves, which affects destructors and deallocation of objects. It doesn't actually depend on the borrow checker. All lifetime labels are discarded after being checked. Code
215.
by pornel 10mo ago
You're harshly judging the entire language based on ease of compiling a 3rd party C++ compiler and the C11 code it emits . These gnarly build commands don't even come from the Rust project, and aren't using the Rust language
216.
by pornel 10mo ago
Rust hasn't grown 17 ways to initialize a variable yet. Most projects use most features. When projects choose a subset of language features, it's dictated by their needs (like embedded programs disabling the standard library, or s
217.
by pornel 10mo ago
Bootstrapping of the rustc compiler from scratch is a very different experience than using the language as a user. Bootstrapping requires building a C++ mrustc proto-compiler, which is where the tons of flags are needed. The rustc compiler
218.
by pornel 10mo ago
Having first-party bindings for native extensions written in Rust seems like the least disruptive and most beneficial step. It doesn't require the core to change, but to guarantee support and compatibility.
219.
by pornel 10mo ago
Growth of CUDA gave it a second chance.
220.
by pornel 10mo ago
That's what Golang went for. There are order possibilities: D has `= void` initializer to explicitly leave variables uninitialized. Rust requires values to be initialized before use, and if the compiler can't prove they are, it&#x
221.
by pornel 10mo ago
To me the real horror is that the exact same syntax can be either a perfectly normal thing to do, or a horrible mistake that gives the compiler a license to kill, and this doesn't depend on something locally explicit, but on details of
222.
by pornel 10mo ago
The difference is that it can behave as if it had multiple different values at the same time. You don't just get any value, you can get completely absurd paradoxical Schrödinger values where `x > 5 && x < 5` may be true
223.
by pornel 10mo ago
They're not, but the flaws they found are independent of PGP. Mainly invalid handling of strings in C and allowing untrusted ANSI codes in terminal output.
224.
by pornel 10mo ago
Sequoia is mentioned in only one vulnerability for supporting lines much longer than gpg. gpg silently truncates and discards long base64 lines and sequoia does not. So the vulnerability is in ability to feed more data to sequoia which does
225.
by pornel 10mo ago
I've already been roadtripping across Europe multiple times in an EV that needs 20 minutes to recharge per ~3 hours of driving (e-GMP). To me this is great, and wouldn't be faster in an ICE, since I need the breaks anyway. EV char
226.
by pornel 10mo ago
The old package managers messing up the global state by default is the reason why Docker exists. It's the venv for C.
227.
by pornel 10mo ago
Cargo.lock contains unused dependencies that aren't in the final product. That's because it's a: • union of all deps for all possible target platforms, • for all libraries and all binaries in the whole workspace, • and incl
228.
by pornel 10mo ago
The problem is that these laws were written before automated mass surveillance was feasible.
229.
by pornel 10mo ago
The author is using special prompts exploiting flaws of the old models, and doesn't like that new models interpret the hacks literally instead. The new models have prompt adherence precise enough to distinguish what "British Muse
230.
by pornel 10mo ago
I can't tolerate it. The split between tag and branch pipelines seems like intentional obfuscation with no upsides (you can't build non-latest commit from a branch, and when you use a tag to select the commit, GitLab intentionally
231.
by pornel 10mo ago
In the sidebar of the Amazon website (which may vary by device/locale), I get Prime, Echo, Alexa, Fire TV/Tablets, Kindle, Audible listed before all other product categories. The special treatment so explicit, I didn't think
232.
by pornel 10mo ago
There's also a pure-Rust implementation of a syntax highlighter, which uses TextMate/SublimeText grammars: https://lib.rs/syntect
233.
by pornel 10mo ago
Maybe instead of ad-hoc fear-driven interventions in the market when Chinese companies do too well (TikTok), US should have some general data protection laws, and not allow making surveillance devices that are locked-down and serve their co
234.
by pornel 10mo ago
Amazon wouldn't have kept the manufacturer alive by making Roombas better, but by making it more expensive for other manufacturers to sell their vacuums through Amazon.
235.
by pornel 11mo ago
There's a hybrid approach of C -> WASM -> C compilation, which ends up controlling every OS interaction and sandboxing memory access like WASM, while technically remaining C code: https://rlbox.dev/
236.
by pornel 11mo ago
There's a need for some portable and composable way to do sandboxing. Library authors you can't configure seccomp themselves, because the allowlist must be coordinated with everything else in the whole process, and there's no
237.
by pornel 11mo ago
If a codebase is being maintained and extended, it's not all code with 20 years of testing. Every change you make could be violating a some assumption made elsewhere, maybe even 20 years ago, and subtly break code at distance. C's
238.
by pornel 11mo ago
It can be done in 100% safe code as far as Rust is concerned (if you use `dyn Fn` type instead of c_void). The only unsafe here is to demonstrate it works with C/C++ FFI (where void* userdata is actually not type safe)
239.
by pornel 11mo ago
Many of these mistakes weren't even made by any committee, but were stuff shipped in a rush by Netscape or Microsoft to win the browser wars. There was some (academic) reaserch behind early CSS concept, but the original vision for it d
240.
by pornel 11mo ago
They are wrong, and didn't get the point of separating semantics and presentation.

More ›