The existence of LLMs is not the problem. The insane way they've been integrated into society is the problem. Back in 2020, GPT-2 was something novel you'd do random experiments with and something like this would've been cool. As long as it remains a silly experiment, it still is cool.
Every time I see a person leading a model to specialize in a uniquely human endeavour, I think of the last lines of this stanza from Bob Dylan's It's Alright, Ma (I'm Only Bleeding):
Disillusioned words like bullets bark
As human gods aim for their mark
Make everything from toy guns that spark
To flesh-colored Christs that glow in the dark
It’s easy to see without looking too far
That not much is really sacred
The post seems to refer to a very specific subset of demoscene:
> I came across Dwitter.net, which is like Twitter but for 140 character JavaScript demos. They already supported “remix”-ing any dweet so that we can build on top of them.
This person is actually correct. Demos are much more on the art side of coding than most forms of programming, so while LLMs may be up to the mechanical task, they won't produce code with the finesse that a human coder can. That goes double for the art and music. What's more, a demo with AI-gen elements wouldn't be accepted by the community. AI-gen webshit may be embraced by the industry, but the demoscene has different standards: human craftsmanship is the entire point.
Relatedly, I was a bit surprised and delighted to find out that the Sonic (the Hedgehog) community is vehemently rejecting AI recompiles, ports, and fangame projects. Clankers are ok with them when it comes to Dr. Robotnik's evil creations, but not in the real world!
In another decade this headline would be "please let books die" or "please let tv die". Some people are biologically wired to process information in a maladaptive way (so much research about this), and the medium is irrelevant.
I say this that even simple text based sites like hacker news can be used inappropriately.
CD ROM encyclopedias were only really viable when dial up speeds limited the amount of multimedia content on the internet. Both Microsoft and Britannica were victims of internet encyclopedias. And now static internet based encyclopedias are themselves under threat of personalised AI content as well. The pursuit of knowledge keeps changing what knowledge itself looks like.
Britannica actually had a great website during the dot com era - hyperlinked, very browsable, and definitely had that semi-addictive "rabbithole" quality.
The hurt themselves badly by imposing a really annoying paywall just as Wikipedia was beginning to take off. A hybrid model with tiered access (maybe even a limited ad-supported free tier) might well have kept them on top - instead, they offered only a single expensive annual plan priced to compete with the paper or CD editions.
Backwards compatibility has limits. When a piece of software has been abandoned for 30 years, there is very little commercial value in supporting it. Apple, Google and even Linux are more aggressive in dropping support. It's only IBM on mainframes with multi million contracts that is really going for backwards compatibility at any cost.
Doing something that engages your brain in a unique way rewires your brain. I'm currently learning Astronomy and it is changing my thinking already. There are so many academic fields out there that each wires your brain in a unique way. We say were are in the age of AI but human intelligence needs to be studied even more than ever.
I can't even run a binary from one Linux distro to the other, let alone one from a random Unix from the 80s. If a rebuild from source is allowed (which would need to allow modifications to the build system) that's a completely different game.
I had to run a Linux binary compiled for Ubuntu 10.something a few years ago. I couldn't get the drivers to work properly in libvirt and getting the binary to run on modern Linux was practically impossible, even with 32 bit support installed.
The downside of dynamically linked binaries: every tool of medium complexity needs a close-enough version of a common library, and once those get upgraded, the tool dies.
Most statically compiled version should work with a compatible enough libc, but I haven't seen many old programs like that.
Wine, on the other hand, runs tools from the 90s just fine, as long as they're 32 bit.
You don't need to go full static linking. Just bundle every library that doesn't have string backwards guarantees or rather bundle everything except base system libraires. The same is also how things work on Windows (and thus Wine really). Wine won't be able to run a binary that links to some random libpng or whatever that the compiler found in your System32. The only difference is that Microsoft makes an SDK that gives your some idea of whats a system library you can rely on as well as the ability to target older versions than the system you are building on. The latter can be done on Linux as well but there is no-pre made SDK so the easiest solution ends up being a VM or chroot with older libraries.
> Just bundle [...] everything except base system libraires
That means everything above libc. There are no "base system libraries" in the Linux world for GUI. Not even libX11, that has been deprecated in favour of libxcb, which has been deprecated in favour of not having X11 and running Wayland. Some days I am amazed that the ELF binary format hasn't been deprecated yet...
LibX11 is still alive and kicking. It is however possible to bundle libX11 and/or libxcb (libX11 today sits on top of libxcb) because the wire protocol between them and the X server is also backwards compatible.
And of course Wayland has XWayland to continue compatibility. This doesn't give you access to new toys but neither does restricting yourself to a 30-year old Win32 API.
And beyond libc/libX11/libxcb, libasound has also provided good backwards compatibility with newer systems implementing shims to make it work. You can also use libpulse directly if you don't care about old/opinionated systems though.
Many programs are dynamically linked to at the very least, libc. If the system libc is older than what the binary was developed for, it will often fail. Failures going the other direction are less common, but can and do still happen. If the binary was statically linked with everything it needs, you've got a pretty good chance it'll work, but that's a bit harder to do with GUI programs that need to interact with X or Wayland.
It depends. I've found for example, if i compile on Ubuntu or Debian, it will probably work on any Ubuntu, Debian, or Debian-based distro released at or newer than the one I compiled it on. There are other cross-compatible examples.
More broadly, there are things like manylinux and MUSL which allow cross-distro applications.
I agree - the model I use for why containers (Docker etc) exist is to abstract over Linux ABI incompatibility. I don't think they're a great solution, as it complicates software distribution. I should be able to distribute an executable and have it just work.
Linux isn't the source of the incompatibility. The kernel itself is very strict about not breaking userspace. Your userspace is breaking compatibility on its own, containers fix it by shipping the userspace components within the container, which only works because the kernel maintained compatibility. If the kernel broke compatibility you would need to use a VM so you can run a different kernel version.
Hah well yes for Windows. This is a mercy, but my mindset is still "Works on Windows, Linux and Mac". (The last being dropped for anything that requires Cuda...)
From the article, the time to beat is November 16, 1992. This might be possible on one of the BSDs, as FreeBSD and NetBSD both document support for running a.out executables with the 4.3BSD ABI. I guess it would depend on whether anyone had ported X11 to run on a BSD on i386 before then. Alternatively, maybe you'd be able to get something running on SCO OpenServer (if you count that as a current OS, it IS still getting security patches). It documents support for XENIX x.out binaries ( https://www.scosales.com/ta/kb/126704.html ) so you might be able to run software compiled in the late 1980s for XENIX/386.
NetBSD has excellent binary compatible with 80s "unix", the problem is most (all?) of the 80s unix platforms it supports aren't x86.
Current NetBSD still has good support for running SunOS binaries, though, including graphical ones. I'm certain you could get a SunOS 4.x binary from pre-1992 to run on NetBSD/SPARC. I've no idea how far back you could potentially go on NetBSD/m68k -- probably quite a ways, especially if the binaries are statically linked. SunOS pre-1988 was all static linking!
(Running "real" 4.3BSD binaries might be hard -- I think NetBSD/VAX defaults to ULTRIX compat, which is an either/or thing versus strict Berkeley Unix compatibility. Same binary format, similar but incompatible syscalls/data structures.)
Random people that you're expecting to look stuff up for you aren't customer support; they're comparable to 404 Media, except they don't even make a living from views. They're simply random people that you're taking advantage of.
People linked you to lmgtfy because they were saying you were lazy or stupid, not because they weren't going to support their products. They hadn't sold you anything.
I remember having to buy GTA Liberty City Stories to jailbreak the PSP. Then there was the infamous Cubic Ninja jailbreak which caused the game to become worth hundreds of dollars.