top | item 35741909

(no title)

jsmcgd | 2 years ago

[flagged]

discuss

order

tonyarkles|2 years ago

Heh, nice ChatGPT reply... it's more eloquent than what I was going to reply with, and doesn't start with "Grad school was a long time ago, but from what I recall..."

> To mitigate this, tuple spaces may use locking or transactional mechanisms to ensure consistency and prevent conflicts.

I think I played with some kind of TupleSpace implementation around 2009 or so (as part of a "paradigms of distributed systems" course) and I'm pretty sure it was some kind of hybrid STM (software-transactional memory) / TupleSpace thing that addressed that issue. It was pretty cool... again from vague memories here, I believe it only had tuple-level locking, but you could build a bunch of really neat higher-order synchronization primitives on top of just tuple-level locks.

macintux|2 years ago

Your comment was flagged, I assume for the ChatGPT dump, but that seemed unreasonable to me so I vouched for it.

jsmcgd|2 years ago

Thank you :) Upon reflection perhaps this is fair enough, all Hacker News discussions might descend into ~50% ChatGPT content. I'll endeavour to put what ChatGPT produces through my messy human filter. Humans before bots? Guys before AIs. Ho(mo sapien)s before b(r)o ... doesn't quite work.