Kirby703

local clown

  • she/her

speedrunner, tetris player, programmery human, absolute nerd

there is tetris on my youtube and twitch but I continue to not port content between them

You must log in to comment.

in reply to @mcc's post:

To me, Rust feels like the opposite of C in that you are constantly trying to fight the computer preventing you from doing what you want (whereas in C you are constantly trying to fight to prevent the computer from doing what it wants)

I get kinda the same feel :(

As someone who uses python for a bunch of school stuff, I'm kind of interested if maybe Rust is a nice alternative to C for writing Python modules to speed up compute-intensive bits. Sounds like it has pretty good support for that these days. Haven't tried it myself though, but would like to sometime

i have written only a few, but also... yes. although at least they have a greater than usual tendency to keep working once you have gotten them to work.

The amount of time I spend fighting language quirks in Rust is way higher than in any other language. It’s the least intuitive language I’ve ever worked with. Haskell e.g. is for aliens, but once you start thinking like an alien (or if you already were an alien), it all makes sense. Rust is a weird amalgamation of features that don’t make any sense together, and it is somehow still nicer to work with than C++ most of the time.

Haskell e.g. is for aliens, but once you start thinking like an alien (or if you already were an alien), it all makes sense

this is so fucking true. every time we use haskell again we have a time period of being like "how did i ever use this language" until we find our way back into Haskell Mode and it switches to "how did i ever user any other language". it is such a state of mind

Rust feels at the same time mature and "production-ready" in that you can write perfectly fine software in it, and also like it's still trying to rapidly grow and find its final shape. I like writing Rust, but there are so many idiosyncrasies and quirks that I quite like in principle, but which don't build up to a coherent whole in my head.
Personally I chalk it up to my inexperience with "real" system PLs (I've been a Python dev for 10+ years), and I intend to continue to write Rust since I still enjoy it, but I wonder if there needs to be a Py2->Py3 breaking moment in the future (or simply a successor PL) that will take all the lessons from Rust and try to make a more intuitive core with them.

in reply to @Kirby703's post:

The thing about C is that it's a deceiver. You think you've generated the assembly you want. But then you switch compilers. Or the compiler issues a new point and update. And suddenly maybe you aren't generating the same assembly, or you're generating something that doesn't even work because the UB holes are enormous and unmarked and focus around the areas that at first glance look like C's most useful features… I've seen it go wrong. I don't trust it :(

I love hammering my own thumb 👍👍 it works on my machine*

a particular shoutout to reading/writing 64-bit values at odd indices in a 16-bit aligned array, something that feels very legal and stable (although, it did probably double the speed of any alternative approach, so really who's winning)

* for now