WSSP

this is very cool: https://exhibits.stanford.edu/menuez/catalog/vv758zk7405

I'm curious about: https://exhibits.stanford.edu/menuez/catalog/rw840qg3512 https://exhibits.stanford.edu/menuez/catalog/rd259yj2574

(jogging club?)

the worst thing about all this swatting is the hypocrisy

I was disappointed that refreshing the page didn't regenerate the text

I suppose an infinite scroll _would_ be funnier

> The Google admin tools and process haven’t quite been able to cope with this situation and people have been overly banned with poor information sent to the users.

I can’t recall any success story of Google’s support team or process coping with a consumer’s situation, many have been posted here. this isn’t a new outcome, just a new cause

I do want to understand what’s happening with the $250/mo fees of users caught in this. will it be automatically cancelled at some point?

> American Model trains on public data without a "do not use this without permission" clause.

this is going through various courts right now, but likely not

to be clear I meant emotionally able to move on. burnout is often characterized as being unable to do that, even if the person wants/needs to

but yes I agree anyone who can takes months off work without financial stress should consider themselves fortunate. I know (non-parent) people who did that who were far from multi-millionaires though

I suspect many resignations due to burnout would be better attributed to the company's poor management, culture, lack of opportunities/compensation, etc.

not that I think burnout isn't real; I think the test is if the person can easily move on to their next thing or not

there's a lot of land on the WA/OR coast, but you won't find it cheap in a Seattle suburb, which is where a 30 minute drive along the coastline will take you

> From what I've heard, Swift was also optimized for low memory usage rather than raw speed

at a 1000 foot view, Swift inherits its reference counting system from Objective-C, meaning objects are freed immediately when their retain count goes to zero; vs a tracing GC releasing many objects whenever a tracing cycle runs. maintaining reference counts also adds a cost that a different GC approach could avoid. it's true that Swift will maintain a lower memory footprint, potentially at the cost of lower throughput

I would be a little surprised if that explains the bulk of a performance difference though, vs Swift frameworks being newer and less optimized

out of curiosity what does terrible means relative to other web server frameworks, and any idea what explains it?

I would expect a Swift web framework has at least the potential to be performant

post-ARC, Objective-C and Swift aren't very different in terms of memory management. retain and release are handled for you, and you only need to worry about retain cycles. structs in Swift change things a bit, but not that much

the bait is that reference counting is (often considered to be) a type of garbage collection, and that correction is frequently made in comment threads

and hey, here we are

I love it every time I see it linked

that argument definitely has some truth, but it's worth considering that playing a randomizer is a very different experience than speed running the original game as mxwsn said. I've played a few randomizers and it's a whole lot of fun to dynamically route based on evolving probabilities - vs performing a known route at a hyperoptimized level. randomizers reward adaptation, as well as gameplay and game knowledge that may not matter for the speed run