As I take it, it‘s probably a rant about the convolution of programming languages/paradigms and their „unnecessary features for DX“. Also a rant about the community always asking stuff like „do you think X is better than Y because of Z?“ instead of evaluating for themselves, (or maybe at least asking more fine grained questions about some specifics of a language?).
Casey is banging on about the bazillion different languages and frameworks and sheer amount of CRAP that developers these days, have to grapple with! And the more CRAP that we have to navigate, the worse software, as a whole, becomes! There's only a certain amount of CRAP that our puny human minds can deal with at one time!
I legit thought Casey was gonna end his 8th level of sarcasm with "... and that malware recycling your memory is called Windows" and it make me laugh on my own
for best performance in zinc oxide you need to be constantly downloading cracks and torrents to maintain a healthy malware biome in your composted memory bin
He's confusing Mulching, which happens at the top layer, and Composting, which is used beneath the top layer. These are two separate things! Typical zinc oxide programmer. 🙄
I think Zinc Oxide and Stoplang are honestly on to something with MMC (Malware Memory Composting). Most malware doesn't want to be detected, so it tries to avoid heavily impacting its host. This would include freeing up unused memory so as to reduce its footprint. MMC allows us as programmers to never need to care about freeing memory ever again, as when we feed it to malware, it by necessity must handle the freeing that memory in order to keep its footprint low so the host's antiviral systems don't attack it. This is basic evolution. The next step is to integrate and shelter the malware inside of our ZO and SL programs to keep it safe from predatory AV software. Doing so means that it can use the resources it would otherwise be using on evasion and fence instead to better specialize in freeing up memory. In doing so, we create a truly symbiotic relationship with the malware. Our applications run smoother, the malware gets to keep on living, and the user has a better experience using their system and apps. With MMC, everyone wins!
It was a lisp joke indeed, because in lisp you can, instead of composting an old variable, (which would be recycling), pass it along in a function call and upcycle it into a function. Or vice versa, you can give an old function new life as a variable, without completely destroying it in process of recycling. If you end up needing that function again, just call it! It works fine. You can even pass the variable stored on the symbol into the function stored in the symbol, and have it return a closure of itself in itself, starting the cycle all over again. Now that is some environmentally conscious programming, in my view.
you should try sysRPL. A function may pop the _next statement_ of the _caller_ function, inspect it and finally place it back where it was, remove it, alter it, whatever. All this at runtime, obviously.
Casey is always so concerned with generating random numbers. I recommend that you use his leveraging installing all the malware to achieve true ergodicity. Just as it has been shown that seven shuffles will provide significant randomness in a deck of cards, installing more than seven malwares in your composted memory provides only diminishing returns.
At this point, my entire career is about generating random numbers. If I meet Casey in real life, we will have to fight to the death. There can be only one.
People talk about a new language then say batteries included, when we know batteries are not very recycable. We need a solar powered programming language with a highly recycable battery. We are in the 21st century. Why this is not a thing yet?
i dont think prime understands the actual message casey was trying to give, hes basically making fun of all these overcomplicated and useless concepts that programmers make up instead of actually writing code to the computer
I think he's getting sick of people asking about Rust, Zig, Go, and on and on. Maybe he's just sick of language evangelism in general. Which I agree with, except when it comes to Jai. Rewrite everything in Jai.
for the ignorant: rust was not named after a fungus or the product of the oxidation of iron, but is actually an acronym for "Removal of UnSafe Techniques" because of its advanced compiler features that keep you from writing whole types of code that tend to lead to bugs.
Naming this is hard and this is why. They played themselves, at least with langs like PHP it's more apparent it's an acronym not a series of letters forming a very heavily used word creating a stance of elitism self inflicting ignorance in the very name of the thing.
I don't even know what happened to me just now. I usually whatch your videos at 2x speed and would understand every sugondeez joke but now my my brain is in pain. The only thing I got to learn today is zinc oxide is better than rust cuz memory composting
Video cracked me up, but I felt the pain with the Go memory woes. The memory limit added in go 1.19 that ramps up GC the closer it gets to that limit has made some problems I've experienced much less severe. Or, just rewrite in Rust -- works every time.
@@rj7250a You can set the GOGC env to trigger at a specific % of the heap used I believe, and 1.19 added the ability to set a threshold (which appears to just automatically adjust GOGC based said threshold).
Aluminium Oxide would have been a better science joke, because aluminium after interacting with oxygen forms a layer around it to further help any other form corrosion So, AlO>>>>Rust
I know this is joke, but the fun thing is that I keep thinking "what should be good use for memory composting" just to make a language so this rant becomes true haha - Like composting maybe should mean that the language would mix together free/delete operation with allocation! - This would mean that you could either plant into new "memory land" or into some previously occupied location only. - Also this operation would be merged with a constructor. That is constructing of anything would immediately need ot "compost away something else" or multiple other things and the new record or data would live there :-)
I’ll keep with the marketing speak :: - Memory recycling: you zero whole pages of stale memory; - Memory composting: the garbage collector decomposes objects into constituent marts and allows some flagged components to live longer Needless to say, this works best in a purely functional language like nematode.
Probably not as good as the Inert programming language. While Mojo seems to have a stronger positive force and momentum, Inert seems to be taking a slower more lethargic approach to their design, which is what you want from a well-designed language.
as someone learning IA. I have a lot of problems with Python, even if the new language is not the best design or the most suitable for heavy and sensitive tasks, at least I hope it will fix all the weird behaviors of Python, making it faster and safer.
@@Pilosofia I don't think Mojo is a suitable alternative to Python, even for AI. If I were you I'd probably check out HummingBird Lang. While Python is large, slow-moving, and heavy, HummingBird is way smaller, faster, and more agile.
So good but I think the point was that people fixate on these ridiculous things such as what is better programming language but people have to understand that it's not about which is better programming language.
In Casey's world, it makes sense to allocate all the memory up front and have your app run with certain guarantees. Unfortunately, that's not what most organizations do (not sure why this is). For my node/express app, I just deploy to a managed service and hope it doesn't die lol
Thw funny part is that bump allocators actually work very well for most APIs. You can usually just give each request a bump allocator, and reset it once the request is done.
You're DAMN straight! We owe a LOT to C!!! Never forget that! This language IS the Grand Daddy of them ALL! The One Language... To RULE them all!!! And STILL... After all this time... This super small, super fast, super compact and super efficient language is STILL King!!! The only way this language will die out, is when next gen kids are too dumb to use it, and so opt for piss easy slow shite like Python instead or something! But until then, C will rule for a long while yet! It's simply far too important to replace at this time... If ever!!!
