alchemio · HackerTrans

8 maanden geledendiscuss

You can use std containers in a no-exceptions environment. Just know that if an error occurs the program will terminate.

alchemio

8 maanden geledendiscuss

checksec is part of the pwntools suite. Along with other tools for finding ROP gadgets and shellcode generation.

alchemio

8 maanden geledendiscuss

The most shocking part is the absence of stack canaries. I know there are issues with them on microcontrollers, but still I would assume they’re enabled by default by the compiler.

alchemio

vorig jaardiscuss

Python, rust and Go aren’t beacons of software stability though.

alchemio

vorig jaardiscuss

Zig’s general purpose allocator might detect use after free in debug builds, however zig appears to be ok with dangling (invalidated) pointers/slices and use after free for stack variables, which is more concerning, especially from a security standpoint.

```zig

const std = @import("std");

fn get_ptr() i32 { var a: i32 = 6; return &a; }

pub fn main() void {

var x: ?*i32 = undefined; { var a: i32 = 5; x.? = &a; } std.debug.print("{} {}", .{ x.?.*, get_ptr().* });
}

``` These are trivial examples that Zig doesn’t even warn about, even though similar code in C or C++ gets a warning in gcc and clang.

This discussion:

https://ziggit.dev/t/what-makes-ban-returning-pointer-to-sta...

indicates that core zig devs aren’t interested in diagnosing such usage.

alchemio

vorig jaardiscuss

But it does. He has to notify R4L of what his changes were and how it broke the Rust driver. Even if he didn’t, he will still be contacted for information regarding these things.

alchemio

vorig jaardiscuss

So they stirred a whole lot of drama for not much, potentially harming R4L.

alchemio

2 jaar geledendiscuss

Flash apps and Java applets (via Cheerp) can run again in browsers thanks to wasm.

alchemio

2 jaar geledendiscuss

Embrace, Extend, Extinguish, Endow

alchemio

2 jaar geledendiscuss

> It is undoubtedly hard work to fix these remaining problems, as they typically require both rust and C knowledge in addition to deep HTTP familiarity. There does not seem to be that many persons interested or available for this challenge. Meanwhile, there is little if any demand for hyper from existing (lib)curl users.

You might as well replace HTTP with OS, hyper with rust and curl with linux, and you get the current situation with Rust adoption on Linux.

alchemio

2 jaar geledendiscuss

RustyBuzz is quite limited when compared with HarfBuzz. The Rust fonts scene also seems to lack the necessary momentum to drive things through. I’m not sure whether it’s because the Rust community is mostly interested in webtech or whether Rust itself makes it hard to solve such complex problems. But I don’t see the sands shifting in less than 10 years to come.

alchemio

2 jaar geledendiscuss

Memory allocation is slow and undeterministic in perf. Some allocations also require a global lock on the system level. It’s also a point of failure if the allocation doesn’t succeed, so there’s an extra check somewhere. Furthermore if every object is a pointer you get indirection overhead (even though small but existent). Deallocation as well incurs an overhead. Without a compacting gc you run into memory fragmentation which further aggravate the issue. All of this overhead can be felt in tight loops.

alchemio

2 jaar geledendiscuss

Which make? I’m guessing you mean gnu make, well there’s several incompatible variants as bsd make and nmake. Also bash is not universally used, not windows, not current macos.

alchemio

2 jaar geledendiscuss

It’s looking like the same fate awaits Rust in the linux kernel!

alchemio

2 jaar geledendiscuss

Exactly

alchemio

2 jaar geledendiscuss

It really doesn’t matter and that’s my point.

alchemio

2 jaar geledendiscuss

It’s something Zig touts when compared to other languages(1). The idea is that in the end it’s a convention that an allocator needs to be passed to indicate that the function allocates, which not even the stdlib adheres religiously to. I’m fine with it since I do believe a library writer should know best what works with their library.

1. https://ziglang.org/learn/why_zig_rust_d_cpp/#no-hidden-allo...

alchemio

2 jaar geledendiscuss

Just a correction: most std C functions don’t allocate. strdup does but it was only recently adopted into the standard, it was previously an extension.

Similarly zig’s stdlib shouldn’t allocate behind your back, except for thread spawn where it does: https://github.com/ziglang/zig/blob/5cd7fef17faa2a40c8da23f0...

Generally speaking, it’s as mentioned just a convention. A zig library might not allow its users to pass allocators for example.

In C++, stl containers can take an allocator as a template parameter. Recent C++ versions also provide several polymorphic allocators in the stdlib. You can also override the global allocator or a specific class’ allocator (override placement new).

alchemio

2 jaar geledendiscuss

So rewrite the browser in Rust!

Rust is 10 years old this year, yet there are no production level browsers or operating systems written in it!

I’m talking about Google. They come up with article after article about the failings of C++, yet would prefer starting their own programming language Carbon, continue using C/C++ for chrome, zircon and android.

alchemio

2 jaar geledendiscuss

I for one appreciate this article. It sheds light on the history of V and its undelivered promises; and save me wasted time trying it or reading their site.

comments