Daily reminder.
We live in the world where most corporate produced pieces of software are indistinguishable from malware from 20 years ago.
Remote
THE MARTYR OF BUTLERIAN JIHAD
@icon_of_computational_sin@mstdn.starnix.network
mastodon 4.6.0-alpha.5+chuckyaWe must negate the machines-that-think. Humans must set their own guidelines. This is not something machines can do. Reasoning depends upon programming, not on hardware, and we are the ultimate program! Our Jihad is a "dump program." We dump the things which destroy us as humans!
This is the tech account of @newt@stereophonic.space, formerly located at @pureevil@functional.cafe. If you reached this place, it's your own fault.
Expect long posts about the metaphysics of computing. Don't blame me for any adverse side effects.
231 Followers
11 Following
50 Posts
Joined April 26, 2023
This is a curious piece of writing, but not for the reason you might think. Some irrelevant webshit piece of code changing languages is beyond my concern, but what caught my eye was this:
The important metric: how long does your entire development feedback cycle take, and what portion of that time is spent waiting on your compiler?
Now, all of the sudden, compile time has become an important metric because the consequences of it is now quite tangible, resulting directly in your Claude account being drained. When it was just human time, this hardly mattered to most, even though human time should be more valuable than that of machine.
Which again forces me to a conclusion that most tech people completely suck at estimating costs of literally anything, unless slammed with a number in the face, and lack mental capacity for predicting second or third order effects of their actions. Quite an important lesson here, boys and girls.
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 disclose
With 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
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.
GNU find + mkdir is Turing complete
This needs to be stopped.
systemd 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.
From https://www.freebsd.org/security/advisories/FreeBSD-SA-26:23.bsdinstall.asc
try to install FreeBSD
some asshole neighbour's wifi is calledfor f in /dev/ad*; do cat /dev/zero > $f; done
oops where did all my data go
This is what FreeBSD developers have been demanding your respect for, all these years.
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.
Replying to
@phnt@fluffytail.org 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.
https://www.ietf.org/archive/id/draft-thain-ipv8-00.html
In 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.
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.
I hate git submodules.
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.
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://open-std.org/jtc1/sc22/wg21/docs/papers/2023/p2723r1.html
Just 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.
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.
Replying to
@k8ie@toot.mcld.eu no, it isn't. And no, you don't.
https://en.wikipedia.org/wiki/Direct_memory_access
Fun activity of the day:
Extracting 1Gb of perf traces over a 115200b/s serial link.
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 Emacs 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 and not by GNU.
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.
If you really think about it, the Halting Problem is the defining quality of Turing machines.
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.
Replying to
@phnt@fluffytail.org @mangeurdenuage@shitposter.world 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.
Replying to
@phnt@fluffytail.org @mangeurdenuage@shitposter.world no, not really. Here I only refer to the Android bug above.
But I would've published this "CopyFail" immediately. Linux licence claims NO WARRANTY and that really does mean NO WARRANTY.
Replying to
@phnt@fluffytail.org yes, it does exist, but that is not the point. The point that
Some software is better than the otherMonoculture is among the worst things to have happened in tech. This has been known for a long while, if you look up articles from early to mid 2000s, they argue that Microsoft monoculture is toxic. And yet the nerd herd has managed only to replace one monoculture with another.By the standards of the time described above, most big tech software today would be classified as malware, whether intentionally so or not.
I have never claimed that you must run some perfect software (I can claim this tho). But at least try to have some semblance of standards.
Replying to
@lazyisolation much funnier than that. The protocol was already used in the wild without FDO Benevolent Autistic Committee approval.
Replying to
@phnt no actually useable operating system, I mean.
Replying to
@phnt my point is, there is literally no need for C as a separate language. Just add a standardised runtime-less subset to C++ and you're golden.
Replying to
@lain a QNX-like windowing system would've been awesome. Btw QNX now too uses Wayland.
https://devblog.qnx.com/qnx-self-hosted-developer-desktop-initial-release/
A customizable XFCE desktop environment running on Wayland
It's infectious.
Replying to
mastodon doesn't allow attachments in quote posts
Fuck off
Replying to
@mangeurdenuage@shitposter.world @phnt@fluffytail.org and where exactly is Smalltalk today? Right...
Pick up the latest BSP for the board. The driver fails to compile because L'Eunuchs broke internal API again. Typical L'Eunuchs bullshit.
Replying to
@mangeurdenuage@shitposter.world @phnt@fluffytail.org
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.
Replying to
@m0xEE@breloma.m0xee.net that's all fine and good, except you are wrong in every way possible. Navigating books is absolutely essential, that's why they have formatting. Text is split in paragraphs, every sentence starts with a capital letter. Just like code.
But you touched a very important subject with your nagging rant, the one that despite 50 years of evolution, text editors and the way we currently write and edit code absolutely DO SUCK. Code has no margins to write notes into, no way to add coloured selection, while saving this data either separately or in some way making it different from the original code. It's all just boring text with a bunch of syntax parsing hacks bolted on top of it.
Software engineering is really an oxymoron, and the moronic part starts right away with the tooling.
If you think Nix is an obscure and convoluted configuration system, you should really try Yocto. That thing is hell.
Replying to
@lain unironically, a typical Wayland compositor implementation is only a tad bit smaller than Xorg server.
Replying to
@cnx i'm aware about arcan. It's a display server, not a well-designed OS.
Replying to
@m0xEE@breloma.m0xee.net have you ever read an adult book? Or do you only read those for children, with bright colours and funny pictures on every page?
Replying to
Replying to
@iron_bug C is miles ahead into the grave.
@gabriel@mstdn.starnix.network the dildo of consequences seldom arrives lubed
Replying to
@bonifartius furthermore, those two can be efficiently made to stand out using typography, not colour. Bold and italic fonts exist for a reason.
Replying to
@eric i'm not sure about today, but just a year ago Steam client didn't work without IPv4 at all. Even with 6to4 NAT enabled.
Replying to
@iron_bug ok boomer
Replying to
@bonifartius I detest syntax highlighting
Replying to
Answering to self.
Noise: https://noiseprotocol.org/
Replying to
Want to see the legitimate use of colour in code? Here.
My only complaint about this colour scheme is that the comments are too washed out. Someone wrote them, they must be important and thus need to stand out.