Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MY
Posts
4
Comments
179
Joined
2 yr. ago

  • Linux is too much bloat. BSD is also too much bloat. Switch to Temple OS. Actually, Temple OS is too much bloat. Uuh. Did you know that it's possible to use gcc to compile a c or c++ program in such a way that it's bootable? You can make your own shitty command line os in like 100kb that way and still have access to most of the easy QOL libraries and namespaces. That's still too much fucking bloat for me though. The way I do my "computing" is I just draw on my monitor with a dry erase marker instead of plugging it into a pc.

  • In reality, only some Pentium 1 compatible motherboards can support enough ram for you to actually run Linux on a Pentium 1. Even if you don't run into ram problems, you'll run into bios related problems. I would suggest anyone trying this in 2024 to not even attempt it unless you can get a socket 7, and preferably a later socket 7 motherboard at that. The closest thing I can come up with to a reason not to drop support for 486 (the cpu before the Pentium 1) is that a 486 is a lot more possible to put on a custom pcb than a Pentium 1. Some of the more basic arm cpus aren't even as powerful as an upper tier 486 (but better arm cpus aren't that hard for hobbyists to get). Anyone die-hard enough to want to try to run Linux on a fully custom made computer like that would have better results using an arm or risc-V chip instead.

    I am curious why they're dropping support for 486 but not Pentium 1, pentium 2 and anything not capable of SSE1 or later. mmx isn't even that good but I guess gcc does technically support it.

    I wonder if they're going to drop 486 support in gcc as well. It can still compile for 386. You have to seriously strip down the kernel to run Linux on anything that old. Maybe 486 users (all 2 of them) should switch to Temple OS.

  • Open source fpgas cost up to $10 per chip, $17 if you want the big chungus 256 pin one with lots of extra memory and logic blocks. You can get pcb printing services for like $7 per board but I think I paid less than that last time I built something.

    I'm pretty sure custom made ASICs cost orders of magnitude more than that.

  • I evangelize Linux irl by simply keeping my computer always tuned up, up to date and working well. It's inevitable that someone's windows or mac shitbook will do something shitty and people will pay attention to me just for not having the same problems as them. For example the other day by brother wanted to watch spongebob, his macbook wouldn't let him connect to the TV so I plugged it right in to Arch Linux and it worked like a charm. Sometimes the superiority of Linux simply speaks for itself.

  • My brother tried to use his macbook to put spongebob on the TV and it wouldn't let him due to drm reasons. Don't let this shit become the new normal. It's GNU Linux or nothing for me.

  • Probably stable diffusion. You can self host either stable diffusion or easy diffusion. Easy diffusion runs on stable diffusion but its easier to deal with, the only caveat is that it isn't compatible with lycoris models.

  • In my experience they're the same from a reliability standpoint. Stuff on Arch will break for no reason after an update. Stuff on Debian will break for no reason after an update. It's just as difficult to solve reliability problems on both.

    Because Debian isn't a rolling release you will often run into issues where a bug got fixed in a future version of whatever program it is but not the one that's available in the repository. Try using yt-dlp on any stable Debian installation and it won't work for example.

    Arch isn't without its issues. Half of the good stuff is on the AUR, and fuck the AUR. Stuff only installs without issues half the time. Good luck installing stuff that needs like 13+ other AUR packages as dependencies because non of that shit can be installed automatically. On other distros,all that stuff can be installed automatically and easily with a single command.

    I use Arch btw.

  • If they never release the source, including all the fpga verilog files then this is pointless to the open source community.

    Edit: actually I just realized my comment is kind of pointless. Even if he released the fpga source code, a thing a lot of projects like these never do, it still wouldn't be possible to reproduce one of these using only free and open source software. This is because the only fpgas that let you program them using open source software and not a locked-down windows-only bloatfuck program that needs an internet connection and licensing are the lattice ice40 fpgas. Tl;dr this can't be fully "open source".

    I wonder if it would be possible to make an ice 40 based video card that could still do opengl.