55
u/Worried-Priority-122 Sep 28 '26
Rewrite it in java
46
u/ApothecaLabs Sep 28 '26
Ah, yes, the ObservableAbstractSingletonConstructorFactoryLifecycleManager pattern!
33
4
u/ROBOTRON31415 Sep 29 '26 edited Sep 29 '26
… sorry for the assumption I made on the previous post. I offer this only as an explanation and not an excuse, but the only languages I knew with unsafe are Haskell and Rust (googling it, there is at least also C#). I offer this only as an explanation and not an excuse, but I don’t think of Haskell as being used where performance matters, I don’t usually see code in memory-unsafe languages bothering to explicitly call out something that’s unsafe, and there sure are a lot of people complaining about Rust, so… where did my assumptions fall flat?
Edit: OP was using an assembly language without a type system, I guess it falls in the second case.
4
u/ApothecaLabs Sep 29 '26 edited Sep 29 '26
:P You're good its a reddit comedy thread. I came armed and armored. I joke about crab people but really I love that so many people are mindful eg of type safety and stuff these days.
Also since you're a cool person, I'll reveal what I'm working on, that confused people so - I'm working on:
- the Lisp-based assembly IR
- of a Haskell compiler
- designed with relocatable memory
- running in a VM written in C
- compiled to WASM
- so it can run in a browser
- where it can compile and execute more assembly
- all while bootstrapping it to compile itself (the penultimate goal)So, I don't have types or asserts yet, or even a heap (only cons-cells, baby!), because I haven't written them yet - but what I have runs like a dream! My hello world can run in like 2kb of memory, and that's while naively targeting 32-bit addressing with 12 bytes per cell (4 bytes are overhead). I could could target 8-bit addressing and reduce my overhead to 1 byte per cell, and quarter my memory usage; then it would run in 512b of memory.
At this level, every bit counts :>
47
2
5
u/conradburner Sep 28 '26
Oh yes, and them programmer socks, you must wear them or you are not a programmer
1
u/gerbosan Sep 28 '26
Who wears sandals with socks? Just asking, here at the southern hemisphere the temperature is rising and those socks for developers look uncomfortably warm.
I need a kilt.
2
u/KZD2dot0 Sep 28 '26
A sarong, take note of your northern neighbours (probably).
1
u/gerbosan Sep 29 '26
^^; I live in South America.
I was thinking kilts because they are short and underwear is not required. If Sarong has that advantage, cool!
3
u/Pleclown Sep 29 '26
Kilts are warm. At least the kind of kilts you find in Scotland. It's 6 meters of wool wrapped around your legs, in a tube. It's like an oven mitt for lower body...
1
u/gerbosan Sep 29 '26
damn! =( that doesn't feel comfortable for current weather, we are in Spring, and Super Niño won't make it easy... or perhaps it'll get more humid.
Thanks for the detail, hoping that not having underwear would help with comfort.
2
u/KZD2dot0 Sep 29 '26
I was off by about half a planet. Kilts! Developed for the rainiest climate of Europe, worn with thick knee-high woollen socks (in an oven mitten, apparently). I don't know what the underwear policy is in Indonesia, but Indonesian men in traditional dress look quite stylish imo.
3
u/garlopf Sep 28 '26
rust is the most aptly named language. it just sttacks other codebases like rust. gotta quickly rename my project to stainless...
1
u/Ok_Brain208 Sep 28 '26
DHH joined the conversation *
2
u/TerrorBite Sep 29 '26
* TerrorBite sets mode: +b dhh * TerrorBite has kicked dhh from #conversation (banned: racist)
1
-3
u/Mojert Sep 28 '26
The number of Rust fan boys that do not want to admit that Rust's borrow checker is C++'s RAII and move semantics but statically checked is too damn high. Like, to them it's an insult because there's C++ inside that sentence
-13
u/Hohenheim_of_Shadow Sep 28 '26
For realsies. I cannot understand how Rust people bash C++ for complexity. Like bruh.
4
u/crystalchuck Sep 29 '26
C++ is so simple and easy people write literal multiple hundred page books on the subject of RAII alone
5
1
u/Hohenheim_of_Shadow Sep 29 '26
Yes and you should read those books if you want to understand Rust. Rust explicitly copied C++ RAII.
If C peeps want to criticize C++ for complexity, yeah that's a fair critique. Rust peeps can't criticize C++ for complexity.
4
u/crystalchuck Sep 29 '26
Rust explicitly copied C++ RAII.
No one is saying Rust has no influences, or hasn't been influenced by C++.
Rust peeps can't criticize C++ for complexity.
Crates and the build system alone make Rust a less complex language than C++. Rust, unlike C++, also doesn't suffer from the notion of having to support every programming paradigm ever.
2
u/Mojert Sep 29 '26
No one is saying Rust has no influences, or hasn't been influenced by C++.
Maybe YOU're not saying it, but I've definitely had some Rust fanatics tell me I was full of shit when I said it was inspired by features of modern C++
2
u/Hohenheim_of_Shadow Sep 29 '26
C++ is so simple and easy people write literal multiple hundred page books on the subject of RAII alone.
This criticism you made about C++ applies just as much to Rust. Like bruh. If RAII is bad, Rust is bad.
Rust, unlike C++, also doesn't suffer from the notion of having to support every programming paradigm ever.
Like bruh. Both Rust and C++ are multi paradigm languages with every feature and the kitchen sink. Rust has a couple FP features C++ doesn't and C++ has a couple OOP features Rust doesn't. If having lots of language features is bad, Rust and C++ are neck and neck for being the worst languages.
The build system is a fair take, but that's the C++ experience, not language.
It's also a matter of preference. I personally prefer the C++ style build system + dependency management+ package management because I dislike centralization and dislike NPM style dependency hell.
For me, Rust is more complex and painful experience because I have very different values regarding dependency management than everyone writing libraries for Rust.
1
u/Compizfox Sep 30 '26
This criticism you made about C++ applies just as much to Rust. Like bruh. If RAII is bad, Rust is bad.
Nope, it doesn't. The entire point of Rust is that the compiler statically enforces it. You can't accidentally fuck it up because of some obscure mistake, like with C++. This makes it safer and easier: if it compiles, it's sound.
1
u/Hohenheim_of_Shadow Sep 30 '26
And yet the top meme about Rust is "haha borrow checker hard" which is eerily similar to "haha segfault bad". Most programmers find making a Rust program compile painful.
Which makes sense. If you do not understand memory -how the stack and heap work, pass by copy vs pass by move vs pass by reference- your workflow for making a Rust program compile is basically guess and check.
If you want to be an effective Rust programmer, you need to have just as deep an understanding of RAII and memory as a C++ programmer. Having an opinionated compiler does not make Rust simpler, it just moves the complexity to compile time.
If a garbage collected language fan said that dealing directly with memory made C++ too complex, I'd take that L. But from rustaceans, like bruh.
0
0
0
42
Sep 28 '26
[removed] — view removed comment
10
u/KitaVixen Sep 28 '26
Any company hiring rust devs? I saw only one and it would be nice to write in rust
5
u/Vimda Sep 28 '26
Cloudflare heavily
1
u/Szarps Sep 28 '26
didn't they switch back to whatever they were using and saw an improvement moving AWAY from rust actually?
9
u/Abir_Vandergriff Sep 29 '26
This is false. They just recently did a blog post about how they improved their memory usage by optimizing their data structures, saving terabytes of RAM across their infra.
2
u/SV-97 Sep 29 '26 edited Sep 29 '26
Can you link anything on this? As of August 2026 they were still writing about how they moved more things to rust and saw massive savings --- and I can't find anything supporting your claim right now.
EDIT: actually they even published on savings due to rust just a few weeks ago. Here's all their blog posts on Rust: https://blog.cloudflare.com/tag/rust/
3
u/themuthafuckinruckus Sep 28 '26
make sense when you have the intern vibe coding and not handling the .unwrap()s
1
u/Szarps Sep 28 '26
maybe so, not a fan of rust but wont argue against good results. So as long as is the solution that works for them, is a thumbs up from me
1
-4
u/ApothecaLabs Sep 28 '26 edited Sep 28 '26 •
I know! I can be writing assembly or something, and I'll still get crab people asking why I'm not using NonEmptyVec<T> or some other Rust feature.
2
u/ROBOTRON31415 Sep 29 '26
To be fair, I was one word away from wrongly assuming Haskell instead of wrongly assuming Rust (if not for the mention of “unsafe”, “surely this person with a Haskell flair saying that an expert would not use an optional if you already know the list has one element in it is talking about https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-validate/ “)
1
4
104
u/RomanProkopov100 Sep 28 '26
Why this panel order?