Hacker Newsnew | past | comments | ask | show | jobs | submit | gbin's commentslogin

I don't think it is surprising. Loading entire chrome processes for simple super laggy UIs is just unbearable.

TUI are snappy, accessible over ssh, small screen friendly, easily embeddable in zellij or other multiplexers, easy to copy paste from... Amazing.


Oh no ... Sweet summer child. Whatever the revenue is, whatever profit there is, whatever cash buffer any corporate has, you can be sure of one thing: they need this to go up and to the right...

It became almost a perfect science to optimize your behavior: this is why you end up, bit by bit with enshitiffied products all around you where basically the pain of using that product is just at the threshold of you actually bashing it against the wall.

ChatGPT is just one of them, like Google search, your TV serving ads or ...


What are you talking about. Read part 107. Flying a drone is almost as hard as flying legally a private plane. Fines are huge. They are enforced.


> Flying a drone is almost as hard as flying legally a private plane

What universe are you in?

The FAA can’t even find and identify most of the dickheads flying drones around restricted airspace. You think they give a shit about drones in rural areas around smaller airports? Drones are cheap and easily accessible, orders of magnitude easier to get than an airplane in terms of actual acquisition and the license (spoiler: most drone users aren’t licensed). Compare both of those things with the cost of getting a PPL, to say nothing of how expensive even a small plane is. It isn’t just the US, either - I’ve flown small planes in both America and Australia, and drones are something that both the FAA and CASA clearly aren’t equipped to deal with. Regulations and laws don’t matter if you can’t enforce them because you can’t identify the perpetrator.


You might be right for a limited time only.


The real question is "why not?" :)


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.

Still, it is massively cool.


> "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.

https://theretroweb.com/motherboards?page=1&itemsPerPage=24&...


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 real DOS machine is running on a 8086 (or 8088)

ISA is part of IBM-compatibility.


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)


>where is your fork

Luckily there are better terminal emulators out there, such as foot, so a fork is not necessary.


hyperbole exists


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


Author here, we also have a simple cart-pole demo available https://cdn.copper-robotics.com/demo/balancebot/index.html


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?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: