twovests

twovests OP wrote

i share this sentiment

i have no qualms against people with spare money shelling it out to scamscams while ignoring the mounting evidence that it's a scam

(i call it a "scamscam" because NFTs are like a scam on top of a scam. fraudulent nfts are a scamscamscam. append an extra scam if u agree capitalism is a scam #scamscamscamscam)

but the space is also filled with a lot of enthusiastic artists, programmers, etc. who aren't just investbros but truly believed optimistically that Blockchain Will Solve Thing. boredape is kind of adjacent to that

on the other hand, a lot of the most vocal people who were blinded seem to be using their fame to promote more coinshit and didn't actually get blinded. so i think actually my sympathies waned over these past few paragraphs #apefest

2

twovests OP wrote

something i love is that NFTs were supposed to provide a way to make a cryptographically timestamped message with verifiable authorship

but nobody is using that, and bored ape's twitter thread about the blinded attendees ended with this message, because NFT threads are full of scamscams

This is the final tweet in this thread. Anything below this that looks like us is spam/phishing links. Do not click on links unless you have determined they are safe. You can also cross-reference with http://crouton.net and official brand communication channels.

lol. lmao.

(editorial note: i added the crouton)

3

twovests OP wrote

every one of my posts is 100% serious and describes something that has happened or is a premonition of something that will happen #apefest

all jokes aside, yeah, the #apefest hashtag on twitter was chock full of people who woke up early in the morning with tweets struggling to make sense of burns on their eyes and skin

now it's full of cryptogrifters saying shit like "When your eyesight returns, come & have a look at our collection. " nft link

5

twovests wrote

ya, what i mean is, i think you gotta:

  1. write val, err := something() and use err to build your own stack trace
  2. make sure something() returns that err in the first place, if you wrote it

otherwise you don't get a stacktrace when something() fails.

i'm not confident about this, because i can't imagine Go reaching any acclaim while being so hilariously designed. but "Errors are values" so maybe we are right and go is bad

2

twovests wrote (edited )

I agree, and feel like Go was meant to solve problems Google had.

You have to explicitly pass and handle your own error stack, you can not have unused code, etc. It's such a pain to write and iterate in.

When I use Go, every weird thing eventually clicks into place when I imagine a first-year Google SWE writing it. It instills cultural values into compilation errors.

With Rust, all the weird things click into place, but in a way that feels empowering and not alienating. The x = match y { Ok(T) => {...}, None => {}} used to feel so alien and weird, but now it feels like a powerful incantation that all my thoughts can fit into.

There's this strange parallel. With Go, all the "clicks" were like the snapping of a bone. With Rust, all the "clicks" were like the popping of an estradiol bottle

6