zathura or evince ftw
infinite monkey theorem smh?
proprietary sotfware moment proprietary software moment
https://www.f-droid.org/packages/com.aerotoad.thud/
gofumpt's even beter, also golaegci-lint-langserver
just dogsled shit
I left tumbleweed for alpine and artix because even if you always use --no-recommends for package installation it seems to ship just too much bloat and I left it after it shipped some broken software I didn't need anyway but must've affected system stability too severely, iSCSI iirc
CS is also what most problems on leetcode and the like are about. Programming is just application of CS concepts, usually wrapped in several layers of abstraction, to domain specific problems. But I've never seen a job posting for a computer scientist specifically, yet we all know how it often looks like.
depends. Desktop code, sure, reverse engineering from assembly takes some time but some good dissasemblers might be able to produce some C skeleton to start from. Though you might get lucky just exploiting the supply chain of bloated open source with a hellton of vulnerabilities deps/infra like glibc, apache or sudo.
But web code? Sure, minifiers exist but not every website uses them and even if their do, thanks to all the new stuff since ES5 you can for example spend way less time doing something like finding a Math.random() based, ergo cryptographically utterly broken PRNG.
Or for example you can easily rule out whether the website uses header-to-cookie based CSRF protection by just checking the console on any authenticated write-like request. The rest could be automated with things like zaproxy or selenium/curl-impersonate/puppeteer scripts.
piping find to sed with some possible tr, awk or perl sprinkle is your friend*
* not discounting the risk of ending up wasting more time than planned trying to get one complex regex right
ig even more suits pushing back against remote work :(
pkill
0 post score0 comment score
joined 3 years ago
AOSP is not proprietary. Also security is not achieved merely by the merit of being libre, see CVEs for sudo, glibc or Apache HTTP server or even the Linux kernel itself.
And when it comes to proprietary firmware updates, in case of x86 one such notable example is the microcode which is pretty important to keep updated for security.