"… this would have also been the first keynote by a person of color at #RustConf …" #Rust
The scandal around the misbehaving against @thephd is rightfully exploding in the hands of those responsible for a non-inclusive environment. I still hope that society learns from this.
What are the benefits of using C over C++ for greenfield projects, setting aside build times and such.
In other words, is there anything that can be done in C that cannot be done at least equally well in C++? Is there something that can be done in C that just can't be done in C++? What are the dealbreakers?
(No language wars please.)
Boosts appreciated: my sphere of influence is quite small. 🙏
「 Not differentiating between C and C++ also has the side effect of ostracizing new users. Many beginner programmers are lead by the term “C/C++” to think that they’re basically the same language. In fact there are many tutorials out there that are advertised as “C/C++ tutorials”, continuing the confusion. This can also scare away C beginners by making them think that understanding the complexities of C++ are required to understand C 」
via brycevandegrift.xyz
'I live in #Alberta in a very #UCP town. I ordered a NDP sign and I was shocked to see the volunteer who delivered it today. It was someone who I know was pro UCP. What was the trigger that made them shift to NDP??'
👉 "Danielle Smith alluding to take over the Canada Pension Plan."
Was C++ always super annoying to work with, or did I just grow dumber with age? Was Visual Studio always so fragile and error-prone, or did I just get used to good IDEs?
Confusingly, VS Code seems massively better than Visual Studio. Intellisense handling for TypeScript in VSCode seems so much more stable than it does for C++ in VS.
Wasn't VS supposed to be an upgrade from VSCode?
Wasn't C++ supposed to be more type-safe than TypeScript?
#MacOS inspired application packaging format for #cuteOS.
I finnaly come up with a nice and clean format, and will publish these docs when all of the job will be done.
For running cuteOS app bundles I've made a little program in #cpp called "cute-exec". That will parse the app.json file, locate the executable, and run it.
It'll be better in the future, with bundle scan and bundle verification support.
@mousebot but here, I'll give it a shot based on vibes
Plato: #Agda (the Idea of the Good, proto-Maoist non-conformists)
Aristotle: #C (arch reactionary)
Duns Scotus: #ASM (simple brittle concepts but with plenty of haecceity)
Spinoza: #CommonLisp (OG that everyone thinks is fresh bcs its dynamic)
Descartes: #MLIR (ghost in the machine)
Kant: #CPP (critique of Pure C)
Hegel: #Genera (the absolute Idea as self-reflective system)
Nietzsche: #Scratch (the primacy of appearances)
Marx/Lenin: #ML (self-explanatory)
Freud: #GDB (not phil, but rather the original debugger for all the problems of phil)
Heidegger: #forth (the anti-technology technologist's lang of choice)
Wittgenstein: #Prolog (all there is are the facts)
Stalin: #Haskell (forces you to do things "correctly" even when its neither the best option for the situation nor the most performant; the extreme ML)
Lacan: #rr (meta-debugging, non-linear retroactive causality of the signifier, on top of gdb)
Deleuze: #MaxMSP (thinks programming should be art, thinks art is about infinite flows, elaboration of Nietzsche)
Federici: #SpritelyGoblins (super witchey)
Derrida: #AWK (theres nothing outside the text)
Malabou: #Python (everything is neurobiological including language itself)
Badiou: #Scheme (the generic is the Idea of the Good)
Butler: #Rust (the new generation of Kantians doing things right, performatively)
Programming tip:
When facing an inscrutable memory bug, intuition is your enemy. The bug probably makes no sense because you're thinking about it wrong, or looking in the wrong place!
I usually start with where I think the bug is, but sometimes I spend way too long making no progress. When that happens, I take a break, forget my assumptions, and start over by systematically commenting out code until I find the offending line.
Has any of you #gamedev people ever had issues with negative scale in an #animation? Our #3D#artist loves to flip things by just applying negative scale, but it makes it into the animation #keyframes. That means the entire #geometry is flipped, including the #triangle winding order. This ultimately turns the mesh inside-out. I wonder if anyone ever came across this?
Today I learned that llvm-mca exists. It's a tool that annotates assembly with instruction latency and throughput information, as well as estimated utilization of various CPU resources.
Today I also learned that the godbolt.org Compiler Explorer has support for llvm-mca.
This means, if one ever needs to micro-optimize some code snippet taking latency/throughput into account, one can simply do that directly in the browser. Amazing.
Are there any #llvm contributors/reviewers on here? I'm making some changes to improve Windows (CodeView) debug info and would love for someone to have a look. First change is here: https://reviews.llvm.org/D148761 #rust#clang