Github Link

Why would golfscript be more verbose than some others? Isn’t it made for golfing?

With a hash it’s difficult to find a combination that results in this specific hashed password. Think of it like this: you have a biiig prime number and you multiply it by another. Now, that’s easy, but it’s way harder to do it backwards - factorize a large composite number (this is just for illustration). Similarly trying to find a password that works when you input it based on the hashed one is way more difficult than hashing the password in the first place.

Lesson for the future: stop using crappy illegible fonts in a code editor, and use something nice like Fira Code or even Fira Mono or Sans if you don’t like ligatures.

Edit: In the middle of writing this I realized it was a confusion between “1” and “l”, which makes the font choice even more bizarre. What kinda garbage font doesn’t distinguish between the two? I could understand if it was capital “i” and lowercase “l” since they look extremely similar in most sans serif fonts, but “1” and “l”?

Also it takes like 10 seconds to change the name of a variable across the whole file with a modern code editor like VSCode or an IDE for the specific language you were working with. If they were confusing you, you could have just changed “reclst” into “last_record” and that would save you a day of work.

This is coming from personal experience/opinion, but after trying to create a simple app in GTK4 Rust bindings I was so confused because of how alien the programming style was compared to typical Rust programming. After trying Iced it was much simpler and made so much more sense, no silly decorators or anything, you can define the view and the update loop separately, and interactions are handled by messages using pattern matching. The inheritance based OOP doesn’t work well with Rust, and Iced has none of it, because it was made for Rust specifically.

I’m guessing QT bindings are similarly in a different style of programming and can’t imagine that meshing well with native Rust code. Iced has a lot of merits to it and having the opportunity to both help it develop and use a native Rust framework in a Rust project makes a lot of sense.