cryo

Yes I meant Wireguard, haha spend too much time working with Wireshark lately.

Ah I see, thanks. I only clicked on the first link assuming this was the project page.

Do I miss something? The site only shows a stream but nothing to describe or show the project.

For personal projects: GIT barebone repositories + Wireguard to access them from all my devices.

OSS work is mirrored to Codeberg and SourceHut. For actions I try to make sure that local builds, and cross compilation to Windows, macOS, armhf and arm64, is always working to not soley depend on Github Actions.

That was a nice read. I didn't know there were vector graphics in these systems. Found Canadian description of the Telidon "Picture Description Instructions (PDI)"

https://publications.gc.ca/collections/collection_2020/isde-...

The Matter specification has a similar touch. The devil is in the details and due clever marketing people don't understand what they are praising.

The real problem here is people who invest money in this anyway.

After a long period of rejecting CMake for "simple" build.sh and Makefile projects, nowadays CMake is my goto choice. Top features:

- supports all kinds of compilers, even Watcom for DOS and Windows <all versions> projects.

- cross platform compiliation inlc. MSVC

- my #1 feature wide IDE support + usage from command line.

Interesting, would be cool to see that applied to a real world rust program.

Today I got rid of libc on the Windows version of a commandline tool to flash firmware via USB, which freed 7 kB of the .exe size.

The original version was done in C++ plus Qt and was ca. 3.5 MB (.exe and dependencies).

The optimized C version is 14 kB compressed with upx.

FYI Code: https://github.com/dresden-elektronik/gcfflasher

This is a nice status page, clear and honest progress updates.

I've made a JSON parser which works like this too. No dynamic memory allocations, similar to the JSMN parser but stricter to the specification.

Always nice to be in control over memory :)

https://sr.ht/~cryo/cj

The video shows Sutherlands Sketchpad from 1963, I highly recommend looking in the related thesis for more details on how it works.

Technical report of the thesis: https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-574.pdf

Love it, just earned a spot in my bookmark toolbar.

I'd love to have him in a team. He truly cares exactly how code works and analyzes/fuzzes the hell out of everything.

I don't agree with all stylistic choices in his code, but the level of experience and skills are far above most C developers.

Reminds me everytime how awesome Torrents are.

I don't always run this one but have multiple backups of the .torrent and the video just in case.

Nice haven't seen this one yet.

The choice of Cap'n Proto seems odd to me

https://veilid.com/framework/rpc

It is an interesting project, but I'm sceptical. Veilid appears to be focused on their implementation in Rust, not so much as reference implementation but as the thing itself. I was hoping for a W3C like definition of a standard, not "bound" to their implementation or Cap'n Proto.

Is BearSSL still actively maintained? My approach is abstracting SSL away so the API can be exchanged wit OpenSSL, MbetTLS, etc.

Same here, every system is different, but my main desktop Arch installation is kicking since 6 years now with absolute minimal maintenance issues. Perhaps 1-2 times per year maximum things need to be fixed manually in super rare cases.

I've recently compiled my JSON parser with Borland Turbo C compiler (from 1989) on FreeDOS. It feels good to see the code builds with compilers covering 34 years. ANSI C is still remarkable.

Hi HN, here is my take for a minimal structured format. It doesn't specify anything other than the structure, and leaves the data type specifics to the application.

Last time I cloned the repository it was already over 20 GB, holy ***.

Having read the spec up and down a few times I think it's sound, my main complain would be the device attestation and blockchain usage for OTA. Also Matter inherited the very same thing that sucked most for Zigbee: manufacturer specific "enhancements" are valid, what could possibly go wrong.

Wow that one was new to me, looks pretty good.

Sourcehut. I like how they approach things there, and am happy to pay for my account to support them.

The Pico runs at 133 MHz. I don't know how the slint-ui works under the hood but the shown demo (with DMA speedup) could be much more snappy imho. For that the code needs to be aligned to what the SPI protocol of the display offers instead of treating it as a general purpose frame buffer. For example while scrolling not sending the whole area but only the part which becomes visible.