quic5

> At its core, Juno uses the YouTube website itself. No, not scraped. It presents the website as you would load it, but similar to how browser extensions work, it tweaks the theming of the site through CSS and JavaScript.

From the README

> Yes, that is 4 pairs of --s. This is because Bun will pass the first pair to another bun run command, the second will go to tauri dev, the third will go to vite dev, and finally the last set will go to Cargo when running the backend. It's a mess!

You're right we should (ab)use another unicode code point to indicate that this text was scanned using an OCR app /s

It’s still MIT licensed right? Seems like we need a Vscodium for Insomnia

I attempted to delete my Wasmer account a week ago. The button just prompted me to send an email, so I did that, but didn't get response since. Any idea how to enforce GDPR here?

Digging through the source I've found https://github.com/cotes2020/jekyll-theme-chirpy

That is absolutely true. But but you can write memory-bug-free code in Zig but you cannot prevent heap allocations in most of the languages listed in the article, making it outright impossible to write certain software in them.

I don't believe there ever was support for macOS on 32-bit ARM.

That totally misses the point of quality software. What good is memory safety if you medical device crashes because of an out of memory error?

What I'm trying to say: There are use cases where areas of safety are required other than memory safety.

Happens a lot with Zig's builtin functions: See https://github.com/ziglang/zig/issues?q=is%3Aissue+mentions%... for example

> Human beings need spiritual experiences

That is debatable. Spiritual explanations are just easier and we humans are lazy

But there aren’t any guarantees that the file the source map points to is actually the source, right?

Apple already has recent street view of Germany and nobody cared.

Not all that useful but fun: you can implement swizzling with comptime

A good api (like std.debug.print for example) can implement nice compile errors that fail early with readable messages manually at comptime. Still not as convenient as traits though

> Observation: Separating Safari and Web App allows both to run independently. You can open a Web app without opening Safari, you can close Safari without all web apps closing.

The biggest bottleneck in Zig's case is LLVM. That's why they implement fast alternative backends for development. See: https://kristoff.it/blog/zig-new-relationship-llvm/

All because of a single German political party that will struggle to get the required 5% next term. Kinda crazy

Honestly most bad abstraction come from authors thinking they're geniuses (in that moment)

Having spent countless hours in Cities: Skylines I’m a bit worried that I haven’t spotted a single form of public transport nor more bike infrastructure than a painted bike lane. I hope we won’t have to wait for countless DLCs to add more interesting modes of transport that just cars

Yeah because wanting basic human rights is just something "the West" wants

The print function is implemented in the std library[1] not the compiler and Zig does not have varargs

[1] https://github.com/ziglang/zig/blob/f6c934677315665c140151b8...

There's also the compromise of only disabling safety checks per block e.g. in your hot loop with `@setRuntimeSafety`[1] where you are confident that they aren't needed.

[1] https://ziglang.org/documentation/0.10.1/#setRuntimeSafety

Looks a lot like JetBrains Mono but I’m not 100% sure

I've continued to code on my game submitted to the last WASM-4 jam for months and thoroughly enjoyed improving my messy game-jam code. So I'd disagree with the statement that Zig is only good for prototyping.

Then you will enjoy WASM-4 since it handles the glue code for you. There's no JS in you game but the web emulator is written in JS

I can only speak for myself here but of all languages I've tried for WASM-4 (WAT, C, Rust & Zig) it is the most productive one for me.

I really enjoy the balance of safety and control in Zig. I can build using Debug mode during development, turning nearly all my bugs into crashes which are easily fixable using in-browser source-level debugging. But in Release-Small mode the result is fast and more importantly really small since there's a 64kb cartridge limit.

Another factor is the Zig Standard Library which designed to be portable and usable on freestanding targets. I can not emphasize enough how pleasant this is. For example I can just use a `std.heap.FixedBufferAllocator` to back a `std.ArrayList` with no problem.

The comptime feature of Zig also comes in handy when you have to minimize code size.

The seamless C interop furthermore improves my productivity since I can just use any C code I like. I've used a C perlin noise library in a previous game for example, saving me a lot of time.

Plus I've used Zig for the previous WASM-4 jam and just liked it so I didn't bother trying any other language.