What Language was before C

why was i not subscribed to this shit lmao
"doing UI in c to piss off the react devs" instantly and forever converted me to a zizzoding stan

This is the first time I've ever experienced being able to follow chat.

Rust with its year-editions is like C++ with its year-standards. But C++ at least has a justification for this scheisse — it's not developed by a company, who's sucking Big G's D

we demand A

Did you know that most parts of the AmigaOS version 1.x where written in BCPL, the ancestor of B (and Assembler, notably for Kickstart ROMs, and C - mostly for libs)... Rewrite in C occured for v2...

You are at the height of your powers zozin, beautiful stream

You, sire, are the one true Crustacean! 🦞

Crust makes Rust and C look like appealing languages...

missed opportunity to make a function for each character of Hello world! and then main calls each function individually

Rule 0: No Cargo, only rustc

floppy disk for save. like.

A true alpha chad Crust developer would use #![allow(warnings)]

you can also always say as pointer.
let test: &str = "test";
test as *str;

c_size_t in nightly 🤣🤣🤣

1. UNSTABLE FEATURES ARE UNSTABLE BUT MOSTLY COMPLETE there is usually not much reason to not use those.
2. UNSAFE FUNCTION SPECIFIER IS FOR THE CALLER, NOT THE IMPLEMENTER. WHY THE FUCK WOULD EVEN YOU THINK THAT
3. extern "C" functions CAN be implemented (if you want to call rust from C) and those CAN be variadic (unstable under feature(c_variadic) because "feature has not been properly tested on all supported platforms")
after the previous video and half of this one I just can't fucking shut up anymore this is so infuriating how much you misunderstand rust

also want to say that macros are totally not great in rust currently, there is no excuse for that

rust is just masking unsafe code + makes obfuscation wrappers to rape your debugger :)

cannot wait tsoding to program in A

rust < crust < B U S T

Someone mentioned in the context of rust being noisy with warnings (bullshit like camel case, like really who cares and god forbid they make case of the variables part of the syntax) that it's like «-Wall -Wextra by default». It's not at all. -Wall -Wextra warnings in gcc are 99.9% on point. The only thing that I remember being stupid is about ISO C forbidding function definitions inside other functions when I tried to to a little static inline function in other big static function.

--betterB

Make video on linux setup

I have content for the whole day now

rewrite porth in crust

stb + nob

What happens to the sanity of programmers when horrible runtime bugs ensue? :D
It’s a tradeoff - I’d rather have to think harder at compile time than pull my hair off at runtime (or at least less so)

"Rust developers are deranged" - Crust developer

The last ever programming language will be Z(ozinLang)

Hold the phone. Are those dynamic arrays??? 😂😂😂

Disregard ast, generate fasm output directly

IIRC Ken Thompson's (first) B/C-compiler was basically a set of asm macros.

Such great idea that only missta zozin can handle; Writing B compiler with Crost

This chat in subtitles is a genuinely a smart idea

I don't really understand if that rust-hate is trolling or not, but in case if it's not trolling I think I should clarify what rust actually is from a perspective of a developer who can write in dozens of languages and had been writing C++ and other compiled language code in production for a production systems (this is an important part) for almost 10+ years.

Rust is actually a miracle, neither the less. I don't know any other language that can GUARANTEE you that your application will never exit unexpectedly and will never have UBs if it compiles successfully (no unwrap, no except). Yes you will have to write a little bit more boilerplate code, but this is literally nothing compared to situation when you are searching for a segfault conditions in a production system that has more than 100k SLOC for weeks and weeks, trust me this is agony.

I don't even mention here some amazing built in features like no-gc, algebraic enums and compilation speed (10x faster than cmake + ninja for my local machine). Obviously rust has some downsides like lack of proper OOP, and some really complicated boilerplate for async coding, but again, this is simply nothing compared to what you will deal with for a real large production system.

In 2025 if you want to write some serious, mid to large scale system that will work as fast as C\C++ one -- you will choose rust in 99% of cases if you know that language well enough. I will simply never again write a C++ code in any new project, because this is really irrelevant now when i can do that in rust faster (because my app will compile faster), and safer (because if miss something i will not search that bug for hours, my app just't wont' compile)

> 4 hour vod
> begins using stb_c_lexer

big mistake, should have called the compiler "bc", like the cc, or rustc.
then when the code becomes too big, should rename it to "bbc"

Are there people watched the full video?

I'll direct you to Leviticus 20:27 - Necromancy is illegal.

Sick (b)eats

rust is still easier than dealing with my wife ^^

When gbc, blang or tbc?
When B++?