Better than a small youtube to RSS script that returns the RSS for the channel.

The service don't generate the RSS feed itself, but rely on the server: https://watchrss.de/f/WMMHfSH4PU

A desctructive font editor

The rewrite use FFI instead of a NodeJS subprocess. The rewrite occured component by component compared to Bun.

The agents used most of their time for reading and searching. It costs 120 000$ in tokens.

The rust version takes 55.3ms to create run on turn and dispose a client session; memory peak usage went from 1 383MB to 126 MB.

(from Let's get Rusty - AI loves rewriting codebases to Rust

All comes down to good HTML, CSS and JS

This service provides the RSS feed of youtube channels directly.

Extracts the Channel ID from YouTube's source code

It seems Rust is built for Parse, don't validate. The invariants are encoded in the type system.

• https://docs.rs/nonempty/latest/nonempty/ crates ensure .first() always return
• AbsPathBug is useful because Subsequent code doesn't have to validate the the path is absolute. The type enforces it.
• NonZero ensure the 0 value doesn't exist on the number type. Rust cam also optimize the memory used for Option<NonZero> by using the zero value as None.

How to test load you own application? and use of K6 for it.

I personally always use and recommend FROM scratch images. It not only saves storage, traffic and reduces deployment times, but it also removes most, if not all, lateral movement avenues that attackers could use to escalate after an initial exploitation.

The only situations where you would want to reach for alpine or debian base images is if you need external tools and programs that can't easily be compiled and embedded in your FROM scratch image (e.g. chromium, ffmpeg, pandoc...). In this situation, I will always prefer alpine images because packages are more up-to-date and generally work without any problems.