panzi's comments

On: XML Is a Cheap DSL

[panzi]

That's the biggest problem with DSLs: debugging!

On: XML Is a Cheap DSL

[panzi]

Without namespaces it would be just ML, and that already has another meaning.

[marcosdumay → panzi]

The "extendable" part is about accepting unknown tags. The namespaces expansion is responsible for destroying this, not for creating it.

[panzi → marcosdumay]

I mean I guess one can look at it like that. One could also say that namespaces make it clear what extension it is and resolve name conflicts.

On: PgAdmin 4 9.13 with AI Assistant Panel

[panzi]

Yeah, no thanks. I switched to dbeaver already anyway, because pgadmin was annoying about to which postgres versions it could connect. Too much of a hassle to setup a new version from source back when I tried. With dbeaver I just run ./dbeaver from the extracted .tag.gz. dbeaver is also not a web interface, but a real desktop application (Java, though).

[forinti → panzi]

I run pgAdmin with docker and there's almost nothing to it.

When a new version comes out, I just update the image version on the stack yml.

[panzi → forinti]

The fact that you need Docker to make it easy is already a mayor failure. What happened to single binary programs that you can just run? I don't want a whole virtualized OS installation just to get a desktop application to work.

On: The hidden compile-time cost of C++26 reflection

[panzi]

Is there an implementation that does that?

[dataflow → panzi]

With std::nullptr_t on MSVC, it's always there without any includes.

On: System76 on Age Verification Laws

[panzi]

Exactly. Except this way you can't build a complete biometric database if all citizen! Since it's so obvious how to do it correctly without creating such a database one could make the assumption the creation of such a database is the actual goal.

On: Zed will require age identification for its services

[panzi]

Definitely worth a look!

On: The Xkcd thing, now interactive

[panzi]

Register the mousemove event handler on window, then you will still get the events when the mouse moves out of the window/frame while dragging and it won't be that buggy.

[pierrec → panzi]

Come on, HN, you can't let this information stay under the front page for 13 hours and everyone's like "ah yes of course". Please don't register the mousemove event handler on window, that old school hack never really worked and was obsoleted 10 years ago when the pointer API became standard.

Things are much nicer now and the problem is entirely avoided by using pointer events: https://developer.mozilla.org/en-US/docs/Web/API/Element/set...

[DaanDL → panzi]

Was about to comment the same. It's a common mistake/gotcha.

[benrutter → DaanDL]

Possibly dumb question, but does that still hold inside p5js?

[virgil_disgr4ce → benrutter]

p5 is just a wrapper that adds the setup() and draw() functions, so yes

On: Why does C have the best file API

[panzi]

This is not the C file API, this is the POSIX file API. Doesn't standard C only define fopen() & co? In any case under Win32 this is all different.

On: The Windows 95 user interface: A case study in usability engineering (1996)

[panzi]

2000 was peak except for them still having those tiny non-resizeable dialogs with long lists in them which you have to scroll horizontally and vertically. WTF? Your typical Linux DE was better at that even back then.

On: BarraCUDA Open-source CUDA compiler targeting AMD GPUs

[panzi]

I don't care about anyone seeing or not seeing my unfinished hobby projects, I just immediately push to GitHub as another form of backup.

[bravetraveler → panzi]

I don't care about backing up unfinished hobby projects, I just write/test until arbitrarily sharing, or if I'm completely honest, potentially abandoning it. I may not 'git init' for months, let alone make any commits or push to any remotes.

Reasoning: skip SCM 'cost' by not making commits I'd squash and ignore, anyway. The project lifetime and iteration loop are both short enough that I don't need history, bisection, or redundancy. Yet.

Point being... priorities vary. Not to make a judgement here, I just don't think the number of commits makes for a very good LLM purity test.

[freakynit → panzi]

I literally keep this in my bash history so i can press up once and hit enter to commit: `git add *; git commit -m "changes"; git push origin main;`

I use git as backup and commit like every half an hour... but make sure to give proper commit message once a certain milestone have been reached.

Im also with the author on this on squashing all these commits into a new commit and then pushing it in one go as init commit before going public.

[butvacuum → panzi]

you should push to a private working branch- and freqently. But, when merging your changes to a central branch you should squash all the intermediate commits and just provide one commit with the asked for change.

Enshrining "end of day commits", "oh, that didn't work" mistakes, etc is not only demoralizing for the developer(s), but it makes tracing changes all but impossible.

[panzi → butvacuum]

Yeah, I don't care about that for my tiny hobby projects which are used by no one. XD