I think this PR is awesome, and I can totally see myself playing around with this at some point. Being able to create DOS executables of SDL projects is just ... cool!
But I do wonder about the practicality. This would, I presume (never done DOS development, never touched a memory extender) only run on 386+ CPUs, and maybe more importantly, probably require a newer CPU than that to run anything non-trivial at acceptable performance. So I wonder how many "real DOS machines" this can practically target.
> "real DOS machines" this can practically target.
Define "real DOS machine".
But I would give you my definition: something with ISA slot so you can hear that awful 2.0 stereo SB Pro-compatible with a hiss what could be almost parseltongue. Video card of choice.
So basically anything between 386sx to P3 Tualatin and some rare and weird cases even P4 and AMD Athlon.
I did testing on a K6-2 300Mhz, and yes it has 2 ISA slot, one of which is where I put the Sound Blaster 16.
Compiling an SDL port of Quake quake gives you 90% performance at 320x200 and 97% at 640x480 compared to the original. That's about 45fps which isn't bad I think.
SDL3 should now work with any i386+ with a VGA and 4MB of RAM which is roughly the requirements of Doom.
A crime?! Please people I don't even know what happened here but removing some bitmap support is a crime now for a maintainer of an open source piece of code?
You are not happy with the project then where is your fork so we can assign some crimes to you and get out of our way to not recommend it?
(Note: I am not affiliated at all with the project and I don't even know what happened but you really need to take a breather, no one forced you to use kitty)
Still improving copper-rs! https://github.com/copper-project/copper-rs a rust first robotics runtime and operating system. It allows you to target your algorithms for both a traditional OS and embedded targets with a perfectly deterministic replay. Our users are from all over the autonomous systems spectrum: AMRs, humanoids, drones, self driving... If you are a rust enthusiast wanting to test the robotics waters or a robotics rust curious. Come and join us!
A trusted website that compiles it from source and a way for you to go to a webpage and flash from there automatically. The FPV community does that all the time with a set of websites for their ESC, flight controllers, radio, all open source. You can add signatures etc but just a trusted website goes a long way vs a random blob preinstalled
That proves that the one they checked, had the correct firmware. It does not prove that the one from the next batch that you bought did. We are all technical people here we and understand that there isn’t really an easy way to do this that a random non-technical person could actually understand and use.
Isn't the person you're replying to suggesting people can update the firmware to the trusted version via a website? So it doesn't matter if you get one from 'the next batch' - provided you're on top of updating the firmware.
If only somebody could make a firmware that claims to have accepted the update, but then proceeds to not actually update itself. Read out the version string from the update and save it. Show that when asked what your version is.
You don't want to add untrusted binary download sources in your Linux system. Your distrib is already doing that. This is not strictly about "downloads from the internet" of course
Here: 20 years of desktops and laptops basically installing the latest kernel asap on Gentoo then Arch. I did break stuff, especially Gentoo, a lot... but out of those I maybe got hit once by a kernel regression?
I don't think people realize how long it takes for the kernel to eventually catch up with your hardware.
My one year old framework laptop motherboard STILL don't have properly implemented usb-c PD apis in the kernel today. Imagine if I took a 5y old kernel?
I'd LoVE to look into it but the news website is pure cancer ads before the video, no sound clock on sound that triggers another ad to you clock back, it restart an ad and you scroll a little bit and a top ad pops up while the bottom one is still there with like 3 words of the article readable.
I clearly remember Cuda being made for HPC and scientific applications. They added actual operations for neural nets years after it was already a boom. Both instances were reactions, people already used graphics shaders for scientific purposes and cuda for neural nets, in both cases Nvidia was like oh cool money to be made.
Parallel computing goes back to the 1960s (at least). I've been involved in it since the 1980s. Generally you don't create an architecture and associated tooling for some specific application. The people creating the architecture only have a sketchy understanding of application areas and their needs. What you do is have a bright idea/pet peeve. Then you get someone to fund building that thing you imagined. Then marketing people scratch their heads as to who they might sell it to. It's at that point you observed "this thing was made for HPC, etc" because the marketing folks put out stories and material that said so. But really it wasn't. And as you note, it wasn't made for ML or AI either. That said in the 1980s we had "neural networks" as a potential target market for parallel processing chips so it's aways there as a possibility.
reply