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

The real meat from the article: https://dev.to/dkechag/how-geekbench-6-multicore-is-broken-b...

First plot really says it all.



The article is probably right about text processing though. It sounds like they took an inherently parallel task with no communication and (accidentally?) crippled it.

I'm not sure what's going on with that subtest, and the lack of scaling is certainly egregious. But we've all encountered tasks that in theory could scale much better but in practice have been implemented in a more or less serial fashion. That kind of thing probably isn't a good choice for a multi-core test suite, but on the other hand: given that Geekbench has both multi-core and single-core scores for the same subtests (though with different problem sizes), it would be unrealistic if all the subtests were highly scalable. Encountering bad scalability is a frequent, everyday part of using computers.

Here we go!

Rough life inside a cave.


Sounds like another win for my gym bros. The science is still catching up.


From the soydev extension.


Next: Palantir thinks high school might be a waste of time, so they are hiring middle schoolers.

Wait...


I have it on my to-do list to install FreeDOS on bare metal to set up a retro gaming box. Tried once, but for some reason the installer failed writing to disk. Anyway, if anyone is making new FreeDOS games, I'll gladly pay for them, and it'll give me an excuse to go down that avenue again.


If enabling CSM in your BIOS isn't an option or isn't enough for FreeDOS, there is a translation layer that can get it to run on UEFI hardware: https://github.com/FlyGoat/CSMWrap


That had not occurred to me and I'm also not sure. FreeDOS was able to boot just fine into the live environment. It was the disk part that failed.


OK, I just posted a comment saying FreeDOS will no longer run on hardware because of lack of BIOS support, but that might change things I guess. Hope it can be made to work.

Another big problem for FreeDOS is the lack of sound card support. I do not know if anyone has solved that yet.


For old DOS games and programs, there is this: https://github.com/crazii/SBEMU


It's so old, that the 3D icons and window borders will be new again when 1.0 is released. Talk about some long-term vision.

But jokes aside, I always enjoy reading about custom OSes.


You joke but the first thing I thought when I saw the icons was that they were nice. Flat everything has run its course.


And the exact same thing can be done in C++.


My Emacs setup typically involves:

- An LSP: https://emacs-lsp.github.io/lsp-mode/tutorials/CPP-guide/ - Neotree to browse the file system: https://github.com/jaypei/emacs-neotree - Awesome-tab for tabs: https://github.com/manateelazycat/awesome-tab

If you want more, look at the extensions section of the LSP page and then go down the rabbit hole.

I likewise do not use Doom or any of the bundled variants because I want full control and understanding of my config. But those variants are still useful to learn what's out there and selectively add things to your mix.


Using tabs requires so much discipline imo. I just end up having 2000 tabs open, and so I chose to not have tabs at all.


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

Search: