TUSF

12 ms·

1.
by TUSF 9mo ago
> You need to link against the oldest glibc version that has all the symbols you need Or at least the oldest one made before glibc's latest backwards incompatible ABI break.
2.
by TUSF 9mo ago
You shouldn't, cause it's wrong. libwayland is 40k lines of code. wlroots is 60k loc. And just to check, sway is about 49k loc.
3.
by TUSF 9mo ago
I wouldn't call it "tragedy of the commons" because the very idea was coined as a strawman. As far as I'm concerned, the entire concept is a fallacy, and people should stop perpetuating it.
4.
by TUSF 9mo ago
cake[0] might interest you. Basically transpiles C into C89. [0]: https://github.com/thradams/cake
5.
by TUSF 1y ago
As I understand it, WASM GC provides a number of low level primitives that are managed by the WASM host runtime, which would theoretically allow languages like Go or Python to slim down how much of their own language runtime needs to be pac
6.
by TUSF 1y ago
I'm not who you were asking, but my only experiences with vlang was years ago when its marketing was making false claims about what its capabilities were, while pretending to be an already production-ready language. This in turn harbor
7.
by TUSF 1y ago
There's no special tooling to catch this, because nobody catches an error with if-else—it's simply not idiomatic. Everyone uses switch statements in the catch block, and I've never seen anybody using anything other than switc
8.
by TUSF 1y ago
> anti-Rust sentiment I have not seen much of any anti-Rust sentiment in the community. There's a lot of people in the community who do Rust, like rust, and work on rust projects. If the Zig community has an anti-anything sentiment,
9.
by TUSF 1y ago
Qt has no official C bindings. This makes it difficult for a new language to write Qt bindings, unlike for GTK.
10.
by TUSF 1y ago
The negative aspects of Electron have little to nothing to do with CSS, and you're only invoking it here to poison the well by association.
11.
by TUSF 1y ago
> Linux is stupid and sucks. None of this is Linux's fault. I'd argue this is both C's and GNU's fault. The need for a copy of the library, seems to be just a tooling convention. GCC's linker requires it, so othe
12.
by TUSF 1y ago
Zig has a couple of IR layers. Generally, Zig's compiler goes: AST → ZIR → AIR, and from there it'll either emit LLVM bitcode or one of its own, platform-specific "Machine IR"
13.
by TUSF 1y ago
Zig already has an Allocator interface that gets passed around, and the convention is that libraries don't select an Allocator. Only provide APIs that accept allocators. If there's a certain process that works best with an Arena,
14.
by TUSF 1y ago
Breaking changes is just another Tuesday for Zig.
15.
by TUSF 1y ago
I don't think SO's "canonical answer" concept really jives with a pre-1.0 language like Zig that is still in constant flux, regularly making breaking changes. One of the questions the blog brings up as an example, "
16.
by TUSF 1y ago
One idea is to include a bunch of nonsense text into webpages, and use CSS to hide it from browsers. Depending on how aggressively you want to do it, this may affect some accessibility tooling.
17.
by TUSF 2y ago
Zig on Linux already directly interfaces with syscalls,[0] unless your library or application directly links libc. [0]: https://ziglang.org/documentation/master/std/#std.os.linux
18.
by TUSF 2y ago
In Zig, the main function can return either a u8 or void (which always returns 0) or it can return an error union !void , where if you allow an error to bubble up to main, it'll print an error trace and return 1.
19.
by TUSF 2y ago
> What prevents anyone from dedicating a Zig memory allocator to the job (and all of its subtasks), and simply freeing the entire allocator at the end of the job? No baby-sitting needed. Given the whole ecosystem is built around the Allo
20.
by TUSF 2y ago
Yes. In fact, Aro is already in the main Zig compiler's repo, although currently I don't think it actually does any compilation of C (unless you explicitly disable LLVM) and is mostly used for Zig's "translate-c" fu
21.
by TUSF 3y ago
> Is it still so after ditching LLVM? Zig hasn't ditched LLVM, nor does it really plan to. What's planned is for the main Zig executable to not directly depend on LLVM, that way contributors to the compiler can still develop on
22.
by TUSF 3y ago
Yeah, LLVM is here to stay for Zig. The plan is to have a custom backend for fast Debug builds for use during development, while emitting LLVM bitcode for release builds that can then be fed to LLVM. Not linking to LLVM would also make the
23.
by TUSF 3y ago
Does an ecosystem designed with custom allocators (including gc) in mind not count for anything?
24.
by TUSF 3y ago
It's called lobbying, and the courts consider it "free speech". Speech that says "I just spent a million dollars to inconvenience my competitors."
25.
by TUSF 3y ago
By convention, all Zig libraries have functions that take an allocator as input from the user. Your application can use libgc[1] and pass the allocator to any library function you use, and not worry about deallocating afterwards. [0]: http
26.
by TUSF 3y ago
You can always use a garbage collecting allocator with Zig, if you're that paranoid anout it.
27.
by TUSF 3y ago
And most of those were rejected without all that much pushback, as opposed to this one where there's about 100 comments already.
28.
by TUSF 3y ago
This is only still at the proposal stage. The Github issue is mostly for posting usecases for and against, etc… It's not "Accepted".
29.
by TUSF 3y ago
Zig's C/C++ compiler is just clang, but with header files for most major platforms included, and sane defaults, so there's no hassle getting it it to cross-compile. Some companies have been using Zig solely for an easier to u
30.
by TUSF 3y ago
With Zig, you just write something like: const c = @cImport({ @cDefine("SOME_MACRO", "1"); @cInclude("raylib.h"); }); Which translates the header files directly into Zig and allows you to c

More ›