hexxington

3 ms·

1.
by hexxington 2y ago
This is the "virtual monorepo", if you want to clone one repo and build the entire SDK product then this is the correct thing to checkout - but development work right now still happens in the separate project repos, of which there
2.
by hexxington 2y ago
Me. I directly refute this hunch. Nothing to do with xbox ever entered the discussion.
3.
by hexxington 8y ago
`dpkg -I foo.deb` tells you which control components are in a package. If it has a postinst, `dpkg -I foo.deb postinst` will show it to you.
4.
by hexxington 9y ago
No. The Winelib implementation fizzled over a decade ago. Mono's WinForms implementation is managed, invoking a cleanroom C libgdiplus.so/dlyib for GDI+ calls
5.
by hexxington 10y ago
> You can use whatever dependencies you'd like with Nix and Guix, that's a big reason for them to exist in the first place. To attempt to translate into Flatpak terms, the "common" runtime would be whatever part of th
6.
by hexxington 10y ago
Guix solves literally zero of the issues I have, including anything I mentioned in my blog post. And you conveniently ignored the real world problems with trusting someone else's dependencies I gave concrete examples of in my parent
7.
by hexxington 10y ago
The thing about dependency bundling is it's the only way to guarantee that the app end users are running is the one your QA team tested against. Minor point releases of seemingly innocent libraries can cripple an application with no vi
8.
by hexxington 10y ago
And the worst damage of the non-runtime components is mitigated via sandboxing.