Posts by icon_of_computational_sin@mstdn.starnix.network
(DIR) Post #B4SCqXDnKL8PZc4LEe by icon_of_computational_sin@mstdn.starnix.network
0 likes, 2 repeats
I love how Linux kernel code is full of UB and nobody gives a shit. Until the next compiler version breaks something, and then Linus goes to GCC bugzilla and whines about evil compiler authors.
(DIR) Post #B4ZybDltW01qoSVBia by icon_of_computational_sin@mstdn.starnix.network
0 likes, 1 repeats
Finally finished adding a feature to our kernel driver. It took a month to write under 100 lines, for the most part due to the lack of documentation. The only other driver that has this feature is one from a Very Huge Proprietary Corpo, and I had to use it as a reference because there is no documentation for the kernel APIs that I needed.At this point, I'm fully convinced that every Linux vendor has their own documentation repository that they will never disclose, forcing the competition to study shit kernel code while trying to figure things out. Linux kernel development is asinine hell and I hate it, though not as much as writing finance webshit in Haskell.
(DIR) Post #B4mN0zdJQvUdHzpSBE by icon_of_computational_sin@mstdn.starnix.network
0 likes, 1 repeats
Starting with C++26, uninitialised reads are no longer undefined behaviour. Instead, reading from an uninitialised local variable will always result in the same value.https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p2795r5.htmlJust a reminder that even if you remove the ++, the C-like subset of the language is still miles ahead of what backwards C-tards preach.
(DIR) Post #B4zY0jEE3AaExheNCi by icon_of_computational_sin@mstdn.starnix.network
0 likes, 1 repeats
https://blog.djhaskin.com/blog/writing-lisp-is-ai-resistant-and-im-sad/The ultimate irony is that the language once promised to bring the era of AI fails at being processed by AI.
(DIR) Post #B5Js7krIGuayI0ka0W by icon_of_computational_sin@mstdn.starnix.network
0 likes, 1 repeats
With time, I have come to realise that systemd was the best thing to have happened to the L'Eunuchs ecosystem in years, even though initially it seemed otherwise.
(DIR) Post #B5LbQ8lSopJejy7m3U by icon_of_computational_sin@mstdn.starnix.network
0 likes, 1 repeats
https://www.ietf.org/archive/id/draft-thain-ipv8-00.htmlIn the year of the thirtieth anniversary of IPv6 someone finally decided to address to incomplete adoption of the said protocol by... designing IPv8. Now we must just... adopt literally all software on the planet to use it too.If you think about it, the very fact that every piece of code that wants to send data over network must be aware of IPv4/6/8, IPX (lol), etc is just insane. There needs to be some default high-level interface that would be akin to "send data to that fucker, I don't care how". Yup, there are libraries for this, but as far as I'm aware no operating system ships this API by default. Which is totally insane.
(DIR) Post #B5Ld81eii5jJOASaUi by icon_of_computational_sin@mstdn.starnix.network
0 likes, 0 repeats
@phnt no actually useable operating system, I mean.
(DIR) Post #B5O14mTtSWC4fmIkzo by icon_of_computational_sin@mstdn.starnix.network
0 likes, 2 repeats
Pick up the latest BSP for the board. The driver doesn't compile because L'Eunuchs broke internal API again. Typical L'Eunuchs bullshit.
(DIR) Post #B5QsboeA6zw8pff5rk by icon_of_computational_sin@mstdn.starnix.network
0 likes, 1 repeats
RE: https://mastodon.social/@hughsie/116403796692832048Remember, the next time your L'Eunuchs setup shits itself into committing seppuku, it might be because of this. At no point Linux has needed generating more code as quickly as possible. On the contrary, the entire ecosystem has too much code and too few good software engineers capable of designing a coherent system.RT: https://mastodon.social/users/hughsie/statuses/116403796692832048
(DIR) Post #B5t5PYYspTmTIgYU88 by icon_of_computational_sin@mstdn.starnix.network
0 likes, 2 repeats
From: https://lowlevel.fun/posts/tiny-udp-cannon-android-vpn-bypass/The fact that this pretty stupid VPN circumvention exists isn't a big surprise, given how bloated and over-engineered Android (and probably any other L'Eunuchs system) is. The surprising part is these words here:Asked If I am free to discloseWith some uncanny rituals, not at all dissimilar from cults or MLM schemes, big tech corpos have managed to guilt trip a huge crowd of nerds that said corpos are owed the honour of being asked permission to do things. Not because these nerds are paid to do this--most bug bounty programs offer scraps, you can sell these 0days and other secrets to Mossad or CIA for 10x the amount--but because it's somehow "ethical". In quotation marks, because nobody can even tell what ethics system here is usually referred to (deontologists can suck a dingus). All while the same corpos have NO WARRANTY clauses in every single software licence they employ, even in EULAs. And where this isn't possible, they limit the maximum possible compensation to a laughable sum.Remember, boys and girls. You don't owe corpos anything. And you certainly owe their customers even less than that. Full and immediate disclosure is the only way. Let them deal with the consequences of pushing shit code into prod, this isn't your problem.SEE SOMETHING, SAY SOMETHING
(DIR) Post #B5t7v8O5sYdPIXh4Vs by icon_of_computational_sin@mstdn.starnix.network
1 likes, 0 repeats
@phnt you might think so, but it was you who deployed vulnerable software from an untrustworthy vendor. Yes, you. You put your trust in a corporation that leaks (or worse, sells for profit) data left and right, hires subpar engineers, reluctantly spends pocket change on QA, and in a normal world wouldn't be trusted with candy. So called "ethical disclosure" only upholds this status quo of you and your kin pretending everything is fine. It's not fine. It hasn't been fine for a long time now. Full disclosure only reveals this very uncomfortable fact.
(DIR) Post #B5tHjp0uZMwbZE5wMi by icon_of_computational_sin@mstdn.starnix.network
0 likes, 0 repeats
@phnt @mangeurdenuage all it means is that glibc/gcc/whatever need to be killed with fire like the atrocious disgrace of engineering that they are. Same goes for Linux.Actually, it is possible to build secure systems that incorporate Linux. This has been done numerous times and involves isolating different application domains with paravirtualised kernels. A tad bit harder than installing Booboontu or RHELL and calling it a day.
(DIR) Post #B5tO50xFy30APLsFBQ by icon_of_computational_sin@mstdn.starnix.network
0 likes, 0 repeats
@mangeurdenuage @phnt Don’t try to plan for future changes. Focus on the ability to completely rewrite everything from scratch when that change actually occurs.I'm not exactly sure this guy is sane or that his advice on software is to be taken seriously.
(DIR) Post #B63dq47HTJ5GiX3VhY by icon_of_computational_sin@mstdn.starnix.network
0 likes, 1 repeats
I'm still amazed how much kernel development is simpler than most things I have done before. Not in the sense that it takes less skill or experience to get into, but in that the tooling and the development process are much less convoluted.I wish we had this in other areas too.
(DIR) Post #B6I1GYCjFKX0ildnto by icon_of_computational_sin@mstdn.starnix.network
0 likes, 1 repeats
From https://web.archive.org/web/20260514102012/https://thanosapollo.org/posts/bzr-saga/This is the story in which :rms: forced the use of Bazaar for acs development over git for four years. Not because it was better–it was not. Not because it was freer–git was under the GPL from the start. But because it was a GNU project, as in the GNU foundation held the rights over code. Though, at the same time bzr was only developed by Canonical.Four years later, Canonical nuked bzr development and suddenly nobody from GNU expressed the desire to pick it up and continue. And then Emacs switched to git.This tale describes the core of GNU mindset. They will use worse tools developed by someone else, while being incapable of writing a similar thing from scratch or maintaining an existing code base, solely for weird political reasons proclaimed by their deranged cult leader. And then they will happily pat themselves on their backs, while their tooling continues being abysmal piss-flavoured rotting garbage. Until it all breaks apart and then they happily switch to something better, designed and handled by much more competent developers.
(DIR) Post #B6Q9zYO9lGMHDodTGa by icon_of_computational_sin@mstdn.starnix.network
0 likes, 1 repeats
Fun activity of the day:Extracting 1Gb of perf traces over a 115200b/s serial link.
(DIR) Post #B6YUDGLFD0S1eUld7A by icon_of_computational_sin@mstdn.starnix.network
1 likes, 1 repeats
From https://www.freebsd.org/security/advisories/FreeBSD-SA-26:23.bsdinstall.asc:try to install FreeBSDsome asshole neighbour's wifi is called for f in /dev/ad*; do cat /dev/zero > $f; doneoops where did all my data goThis is what FreeBSD developers have been demanding your respect for, all these years.
(DIR) Post #B6YgmCAPv9EwI37u7s by icon_of_computational_sin@mstdn.starnix.network
2 likes, 4 repeats
Daily reminder.We live in the world where most corporate produced pieces of software are indistinguishable from malware from 20 years ago.
(DIR) Post #B6bRdVeHCgHKGbNBmS by icon_of_computational_sin@mstdn.starnix.network
0 likes, 1 repeats
RE: https://wetdry.world/@nelson/116625555245053885systemd is ass, and that's why we're gonna launch it into space. No more systemd will be left on Earth.I'm half serious.RT: https://wetdry.world/users/nelson/statuses/116625555245053885
(DIR) Post #B7Z6JckYlXhFRe1GYi by icon_of_computational_sin@mstdn.starnix.network
0 likes, 2 repeats
UNIX philosophy needs to be killed, dismembered, dissolved in acid, sun dried, mixed into concrete, cast into an obelisk, shattered into pieces, launched into space, and scattered all over the solar system. No other system has done so much harm to the programming world as UNIX had. Bad design with a cult built around it, it needs to just die, whether by Emacs or any other means.