figma-linux VS nixpkgs

After countless hours trying to get Figma Linux running optimally on my machines, I figured out how to get Wayland, Vulkan, and hardware acceleration working on Fedora 39 Workstation without using the web version of Figma.

.net if it uses a version and features that are supported by linux figma can be used in a browser or with an unofficial electron app https://github.com/Figma-Linux/figma-linux no ms-word (you could use a virtual machine with windows, or office 365 web variant, or only office) node was built for linux git was built for linux docker was built for linux oracle was built for solaris/linux mysql was built for linux

you can try this: https://github.com/Figma-Linux/figma-linux

On figma.com as well as in embedded Google Maps views, Ctrl+Scroll Wheel zooms in and out. This works under GDM, but doesn't work in either Firefox or Chrome under Sway. I found this issue which seems to fix the problem for X11 via an imwheel configuration, but I'm having trouble replicating this in Sway.

Hi all. I recently found out about figma-linux on github. I would love to use it on Windows since it has support for themes. Is there any way that I can build it for Windows?

The scene has greatly improved since I ran builds of Figma Linux on my Pi 4 a year ago (you can see the long steps I took to even set up the dev environment, and even then I was only able to build it for Debian and it only worked on Ubuntu 20.10+) to now. Loads of lower level libs have gotten native ARM64 versions, but there are still issues.

Well, a great developer thought of solving this issue by making an unofficial version of Figma for Linux and the best part is that it is open source. See the GitHub Repository here. The app is extremely similar to the Windows version of Figma.

This will drop you into a shell where `tracexec` is installed.

[1]: https://github.com/NixOS/nixpkgs/pull/310158

I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.

As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...

https://github.com/NixOS/nixpkgs/commits?author=neon-sunset

I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors

For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...

For example,

```

Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...

I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...

NixOS uses a monorepo and I think everyone's love it.

I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.

Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.

https://github.com/NixOS/nixpkgs