- cross-posted to:
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Zed is a modern open-source code editor, built from the ground up in Rust with a GPU-accelerated renderer.
I thought we were past this as a society 😔
Not until after you convince these projects to stop using discord
As long as they just use it for their community and don’t fucking lock documentation behind discord I don’t really care. But this trend has been so annoying. Due to this I’m in so many servers I have to quit a server just to join a new one
https://zed.dev/docs/linux#installing-via-a-package-manager
ooh, available for “x86_65” on Alpine
(and they’ve fixed that now)
imagine the nightmare of writing a 65 bit instruction set
Now imagine designing a 65 bit computer. The bus, registers, alu…
You’ll probably waste a lotta chips since most of them are designed for working with powers of 2
I don’t think it has to be a nightmare per se if you start from scratch.
Instead of 8-bit bytes, you have 5-bit “bytes” (fyves?) Hoozah! Done.
only if double precision can be called high fyves
This is a mandatory rule now.
Have you really not heard of it? It is a new architecture that is a bit better than x64_64.
Finally. 65 bit processor.
x86_64++
Plus ultra!
It’s made in rust, therefore it must be safe!
A curl piped into a shell or some unofficial packages from various distros.
At this point I don’t get why these projects are not Flatpak-first.
Flatpak is worse for debugging, development, and reproducibility.
Its good for user friendly sandboxing, portability, and convenience.
Is it really worse tho? A single build, against a single runtime, free from distro specificities, packaged by the devs themselves instead of offloading the work on distro maintainers?
Flatpaks are reproducible https://ranfdev.com/blog/flatpak-builds-are-not-reproducible/
You see the conclusion of that article is that flatpaks are not repeoducible after presenting solutions to make it reproducible right?
@ParetoOptimalDev @GravitySpoiled Tusky 25.2
Device:
Fairphone FP4
Android-Version: 11
SDK-Version: 30
Account:
@carrabelloy
Version: 4.2.10
Can’t we basically call this a remote access trojan?
Security wise it doesn’t matter, you run the code they wrote in any case. So either trust them or don’t. Where it matters is making a mess on your computer and possibly leaving cruft behind when uninstalling. But packages are in the works, Arch even has it since before linux support was announced officially.