alexrp

5 ms·

1.
by alexrp 23d ago
I think it depends on location. It would be a bizarre approach in Scandinavia because the consensus here is that companies must pay their employees a decent baseline salary -- which unions negotiate across the whole sector -- so there&#
2.
by alexrp 2mo ago
> But you cannot state that people are "welcome to engage and debate the idea on its merits" when that clearly isn't the case. I really didn't think that part had to be stated explicitly; I genuinely don't know w
3.
by alexrp 2mo ago
You don't need to be a Zig expert, but you do need to at least be invested in the Zig ecosystem in some way. I think it's reasonable for any open source project to only be interested in the opinions of its actual users, especially
4.
by alexrp 2mo ago
The Zig issue tracker is for technical discussion; you are more than welcome to engage and debate the idea on its merits. But we do indeed delete meta-commentary, wild speculation, and outright hostility.
5.
by alexrp 2mo ago
This is about a strictly-enforced form of run-time memory safety where there's no `unsafe` escape hatch that a careless programmer can misuse to undermine the memory safety mechanism. Contrasting with Rust is helpful to get that point
6.
by alexrp 2mo ago
> I think the Zig people are really just concerned that maybe Zig itself is a DOA language because it doesn't offer enough over C for any serious use I promise you, hand on heart, that literally no one on the Zig core team is wastin
7.
by alexrp 2mo ago
> NT is optimized, since day one, to swap. I'm not sure what point you're making here. Did you assume we had the page file disabled or something? > This is a feature, not a bug. OOMing when there's tens of gigabytes of
8.
by alexrp 3mo ago
> Both Windows and macOS do so much better out of the box for essentially any workload. We test FreeBSD, Linux, macOS, NetBSD, OpenBSD, and Windows in Zig's CI fleet. Of these, Windows is the only OS that we've had to configure
9.
by alexrp 3mo ago
> Their CI instances are over provisioned and time-out I can't speak to their managed Jenkins offering, but FWIW, we've had no major trouble running Zig's CI on 3 s390x-linux VMs, each with 8x z15 vCPUs and 32 GB of RAM. T
10.
by alexrp 4mo ago
I only started using GPD products with the Pocket 4, so unfortunately I can't speak to your experience with the Pocket 2. I certainly hope the battery doesn't degrade that fast on their newer models... The only thing I can say is
11.
by alexrp 4mo ago
That's fair; the keyboard layouts are definitely an acquired taste. Not that I've quite acquired said taste myself... but for devices that I mainly use when traveling, I just don't particularly care that much. It'd proba
12.
by alexrp 4mo ago
Depends on what you're doing I suppose? I'm able to work on Zig with both of the devices I mentioned. Of course I'm limiting the test cases to the subset that's actually relevant to the area or target I'm working on
13.
by alexrp 4mo ago
The CPU is just too underpowered; I'm sure it's fine for basic computery stuff, but building software and running medium/large test suites on it would be far too slow. Also not enough USB ports; I don't want to carry a
14.
by alexrp 4mo ago
The Minibook X is obviously targeted at the netbook form factor in the traditional sense, i.e. small and cheap. If you're like me and appreciate the netbook/UMPC form factors (for travel purposes in my case) but also need better s
15.
by alexrp 6mo ago
I've experienced multiple instances where (so I heard; I don't use Windows) a Windows Update completely broke a game on Windows for everyone, but Wine/Proton kept running it just fine. So we're already there in some sens
16.
by alexrp 7mo ago
> No shellcode decoding Can't speak to this as I don't RE for security purposes, but: > no plugin support and rather limited IR. this I'm profoundly confused by. BN has multiple IRs that are easily accessible both in th
17.
by alexrp 7mo ago
Binary Ninja deserves a mention in these threads: https://binary.ninja I've used IDA, Ghidra, and Binary Ninja a lot over the years. At this point I much prefer Binary Ninja for the task of building up an understanding of l
18.
by alexrp 7mo ago
It sounds like you expected 1.0 stability from a language that isn't 1.0. > I thought it was stable enough initially but they completely broke fuzz testing feature and didn’t fix it. From the 0.14.0 release notes: > Zig 0.14.0 sh
19.
by alexrp 7mo ago
Just on this point: > You mean like how Rust tried green threads pre-1.0? Rust gave up this one up because it made runtime too unwieldy for embedded devices. The idea with making std.Io an interface is that we're not forcing you int
20.
by alexrp 8mo ago
> You still need a custom distro for Raspberry Pi for example. Are you sure that's still the case? I just checked the Raspberry Pi Imager and I see several "stock" distro options that aren't Raspbian. Regardless, I ta
21.
by alexrp 8mo ago
I'm fairly sure I recall Fedora folks signaling that they intend to move to RVA23 as soon as hardware becomes generally available. It is of course possible that Debian sticks with RV64GC for the long term, but I seriously doubt it. It&
22.
by alexrp 8mo ago
Most people would be better off waiting for the multiple RVA23 boards that are supposed to come out this year, at least if they don't want to be stuck running custom vendor distros. "RVA23 except V" at this price point and at
23.
by alexrp 10mo ago
Our CI workflow literally just invokes a plain old shell script (which is runnable outside CI). We really don't need an overcomplicated professional CI/CD solution. One of the nice things about switching to Forgejo Actions is that
24.
by alexrp 10mo ago
> The reason they move to a lesser known Git provider sounds more like a marketing stunt. We had technical problems that GitHub had no interest in solving, and lots of small frustrations with the platform built up over years. Jumping fro
25.
by alexrp 10mo ago
Worth noting that LLVM has AVR and MSP430 backends, so there's no particular resistance to 8-bit/16-bit targets.
26.
by alexrp 10mo ago
Hug of death followed by a DDoS. At the time of me writing this, it loads instantly again.
27.
by alexrp 10mo ago
> Go's support for NetBSD has been a big boon to the more casual NetBSD user who isn't going to maintain a port. It means a random Go open-source project you use probably works on NetBSD already, or if it doesn't, it can b
28.
by alexrp 10mo ago
As I pointed out in a different comment, even IBM have to maintain a GitHub Actions runner fork with s390x support because upstream just cannot even be bothered to accept the relevant patches: https://github.com/uweigand&#x2
29.
by alexrp 10mo ago
> obscure OS not being supported Believe it or not, there are platforms outside of the big 3. The GitHub Actions runner does not work on FreeBSD, NetBSD, OpenBSD, and illumos, all of which are operating systems we either have existing su
30.
by alexrp 10mo ago
> So much vague outrage over nothing. So you just chose to ignore the technical problems we have with GitHub Actions and then say there are no problems. That's certainly a take. > That CI system created by so called monkeys is th

More ›