HN user

chungy

6,416 karma
Posts86
Comments1,560
View on HN
86box.net 1mo ago

86Box v6.0

chungy
58pts6
www.mamedev.org 1mo ago

MAME 0.288

chungy
4pts0
ostechnix.com 1mo ago

Linus Torvalds Is Unhappy About the AI Influence in Linux Kernel Development

chungy
17pts6
despairlabs.com 2mo ago

OpenZFS deduplication is good now and you shouldn't use it (2024)

chungy
2pts0
www.mamedev.org 3mo ago

MAME 0.287

chungy
21pts0
sqlite.org 4mo ago

SQLite Release 3.51.3

chungy
5pts4
fossil-scm.org 4mo ago

Fossil Version 2.28

chungy
3pts1
sqlite.org 4mo ago

SQLite Release 3.52.0

chungy
24pts0
forum.lazarus.freepascal.org 4mo ago

Lazarus Bugfix Release 4.6

chungy
2pts0
www.mamedev.org 4mo ago

MAME 0.286

chungy
6pts0
www.mamedev.org 5mo ago

MAME 0.285

chungy
11pts1
www.mamedev.org 6mo ago

MAME 0.284

chungy
15pts3
86box.net 7mo ago

86Box v5.3

chungy
95pts11
virtuallyfun.com 7mo ago

BSD on Windows: Things I wish I knew existed (2023)

chungy
3pts0
www.mamedev.org 7mo ago

MAME 0.283

chungy
4pts1
joelseverin.github.io 8mo ago

Linux/WASM

chungy
10pts0
www.mamedev.org 8mo ago

MAME 0.282

chungy
4pts0
www.mamedev.org 10mo ago

MAME 0.281

chungy
3pts0
www.mamedev.org 10mo ago

MAME 0.280

chungy
8pts0
86box.net 11mo ago

86Box 5.0

chungy
14pts1
zfsbootmenu.org 11mo ago

ZFSBootMenu

chungy
1pts0
www.mamedev.org 11mo ago

MAME 0.279

chungy
3pts0
www.mamedev.org 1y ago

MAME 0.278

chungy
3pts0
www.youtube.com 1y ago

Getting Started with Lazarus 4.0 IDE: IDE Tour and Installing Packages [video]

chungy
1pts0
sqlite.org 1y ago

SQLite 3.49.2 Released

chungy
4pts5
www.mamedev.org 1y ago

MAME 0.277

chungy
3pts0
www.mamedev.org 1y ago

MAME 0.276

chungy
98pts28
chiselapp.com 1y ago

Show HN: Star Trek database, using SQLite

chungy
4pts0
fossil-scm.org 1y ago

Fossil: A Coherent Software Configuration Management System

chungy
3pts1
www.mamedev.org 1y ago

MAME 0.274

chungy
3pts2
86Box v6.0 2 months ago

Different use cases than QEMU, honestly, to the point that there's not much overlap. QEMU is extremely good at running modern operating systems, and not so much at older ones (DOS and Win9x are pretty sore points in QEMU). 86Box is extremely good at running old operating systems (including DOS and Win9x!), but modern operating systems are mostly out of the question (you can run WinXP, but https://86box.readthedocs.io/en/latest/usage/faq.html#can-i-...).

Funny part is, that NFSv4 supports SIDs for user authentication, but the Linux implementation leaves it out (among all the other ACL features) simply on the basis that Linux doesn't support them at all.

The FreeBSD, Solaris, Mac OS X, and Windows (yes, even Windows) implementations of NFSv4 are fully featured with this stuff.

Consider Fossil[1], which packages the entire repository state—code history, wiki, tickets, forum—into a single file, and that state gets cloned.

When/if you need to change hosting providers, you get to lose zero data in Fossil because of it.

[1] https://fossil-scm.org/

It was actually part of Microsoft Plus! for Windows 95. It wasn't directly available for Windows 98 at all, but the Windows 98 install disc does include an INF file so you can install it, provided you have a copy of Plus! for Windows 95.

It was also included with Windows NT 4.0, Windows 2000, Windows Me, and Windows XP (both the original and x64 versions). Finally removed in Vista to never return.

PySimpleGUI 6 3 months ago

Delphi and Lazarus are still kicking, the latter is free and open source.

I know you asked for "the language", but Object Pascal really ain't that bad to get around. If you were proficient in VB6, you should be fine adapting. :-)

Before GitHub 3 months ago

This is a current architectural limitation, manifests (defining check-ins) and tickets are different types of artifacts and you cannot combine the card types into the same artifact. Changing this would likely break backwards compatibility with previous Fossil versions and I'd expect resistance. It may still be worth bringing up on the Fossil forum if you desire the feature.

Personally speaking though, I don't want things automagically closed GitHub-style based on parsing a check-in comment. An issue ought to be closed with intention.

(Of course Fossil actively opposes "pull requests", separate issue)

Not opposition, but very little incentive for the primary developers to implement the feature. Fossil's own developers happen to be the same as SQLite's developers, which doesn't accept outside contribution as a policy. It results in Fossil's features being predominantly, but not exclusively, the same features needed for SQLite and little else.

This thread discusses avenues for implementation: https://fossil-scm.org/forum/forumpost/ce238fccfd6b124d

Other VCSes like fossil store issues alongside the repo.

Technically the issues in Fossil are part of the repository, along with the wiki, code, forum, etc. They come along with every clone and (mostly) cannot be deleted from the historical record.

Items of Fossil that are merely "alongside" instead of actually in the repository include unversioned files, chatroom content, and users and access controls. (Not an exhaustive list.)

What are you really proposing? That a first ".INDEX" entry be made that contains the offsets of all the other members?

That could work in a backwards-compatible way (as long as no standard tar utility makes modifications to the archive...), but it's hamfisted. Just use Zip. It's already a well-known format with numerous implementations and already does the job that you want to do.

There's not a whole lot of interest in making Windows 9x run well on QEMU.

These days especially, it's better to just use 86Box for those operating systems.

Somehow, the bad grammar gives something special by signifying an LLM didn't write it.

Then again, an LLM could probably help clean up the grammar.

Tax Wrapped 2025 3 months ago

I didn't consider that it meant to use the scroll wheel and likewise closed the page before discovering that.

One feature I greatly appreciate is the new default output mode in the SQLite shell in interactive mode. It now defaults to qbox with reflow and line limits enabled, making a fairly pretty output on the terminal. It even does rounded corners. :-)

    sqlite> SELECT 'Hello, world!' AS Greeting, (1+sqrt(5))/2 AS Golden;
    ╭───────────────┬────────────────────╮
    │   Greeting    │       Golden       │
    ╞═══════════════╪════════════════════╡
    │ Hello, world! │ 1.6180339887498949 │
    ╰───────────────┴────────────────────╯

One nit about the site: the screen elements forced me to make my browser window more than half the size of my screen, and I use a 3840×2160 monitor. My windows are normally about ⅕ the size of the screen and roughly 4:3 ratio shaped. It was nearly unusable like that (I don't suffer issues from almost any other site.)

On the game/bracket: it narrowed me down to Noto Sans Mono and I'm honestly not surprised, it's one of the few fonts that comes with my operating system that I find acceptable.

That being said, what I actually have my terminal and Emacs set to is “AcPlus IBM VGA 8x16” from https://int10h.org/oldschool-pc-fonts/. I've always been fond of the VGA font and it tickles all the right usability marks for me.

OpenWrt has a generic x86 PC build that can also be used to turn basically any random PC into a router, complete with an operating system actually designed and developed for that purpose.

Don't confuse "simple and good" with "flawless" :-)

There are indeed only a few private-reserved IPv4 ranges, and almost everyone prefers to keep things memorable and easy to type; you get a lot of 10.0.0.0/24, 192.168.0.0/24, 192.168.1.0/24 as a result. That, and common household routers tend to default to one of these three /24 subnets. (Hardly anyone seems to remember that 172.16.0.0/12 exists, feel free to use that if it happens to work for you.)

IPv6 does solve this issue in a few major ways, one of which is the greater expectation to rely on globally routable addresses, of which every one of your devices will have at least one such address. There's also fc00::/7 which is fairly equivalent to the IPv4 private ranges, though to avoid conflicts in random VPNs you should generate a random /64 prefix inside of this, otherwise you run the risk of everyone picking fc00::/64 because it's easy to remember/type (I'm guilty of this myself, but the VPNs I've configured just go into a random 172.16.0.0/12 subnet and no v6 assigned. I have the liberty that I currently don't need/use any VPNs that I haven't personally configured, and that may not hold true in the future.)