# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 7
# self = https://watcher.sour.is/conv/l7ue64q
movq
www.uninformativ.de
View Thread
So I was writing a little "wordle"-like game in Rust, when suddenly … oops … there’s no rand() … https://www.uninformativ.de/git/rustle/file/src/main%2Ers%2Ehtml#l61 😬
movq
www.uninformativ.de
View Thread
So I was writing a little "wordle"-like game in Rust, when suddenly … oops … there’s no rand() … https://www.uninformativ.de/git/rustle/file/src/main%2Ers%2Ehtml#l61 😬
movq
www.uninformativ.de
View Thread
So I was writing a little "wordle"-like game in Rust, when suddenly … oops … there’s no rand() … https://www.uninformativ.de/git/rustle/file/src/main%2Ers%2Ehtml#l61 😬
movq
www.uninformativ.de
View Thread
I understand that random numbers are much harder than one might think, so they’re probably reluctant to add something to the standard library until it’s “good”. So, for now, we have this:

https://crates.io/crates/rand/

The legend goes that there once *was* a rand() in the standard library:

https://stackoverflow.com/a/29334943

I really wonder how this strategy will play out for the Rust community. How will those external libraries ever be integrated into the standard library? This is going to be a long and painful process, which will involve breaking and rewriting lots and lots of Rust programs. Well, not necessarily *breaking*, because dependencies are pinned by default, but it’s exactly that pinning which makes it easy for software to *rot* (never gets updated, because “it works 🤷”).

Then again, that guy on StackOverflow makes a good point about the sequence of HTTP libraries in Python. 🤔 Python can only grow and, maybe, there’ll be a “clear cut” some day – which will be just as painful.

It all has pros and cons.
movq
www.uninformativ.de
View Thread
I understand that random numbers are much harder than one might think, so they’re probably reluctant to add something to the standard library until it’s “good”. So, for now, we have this:

https://crates.io/crates/rand/

The legend goes that there once *was* a rand() in the standard library:

https://stackoverflow.com/a/29334943

I really wonder how this strategy will play out for the Rust community. How will those external libraries ever be integrated into the standard library? This is going to be a long and painful process, which will involve breaking and rewriting lots and lots of Rust programs. Well, not necessarily *breaking*, because dependencies are pinned by default, but it’s exactly that pinning which makes it easy for software to *rot* (never gets updated, because “it works 🤷”).

Then again, that guy on StackOverflow makes a good point about the sequence of HTTP libraries in Python. 🤔 Python can only grow and, maybe, there’ll be a “clear cut” some day – which will be just as painful.

It all has pros and cons.
movq
www.uninformativ.de
View Thread
I understand that random numbers are much harder than one might think, so they’re probably reluctant to add something to the standard library until it’s “good”. So, for now, we have this:

https://crates.io/crates/rand/

The legend goes that there once *was* a rand() in the standard library:

https://stackoverflow.com/a/29334943

I really wonder how this strategy will play out for the Rust community. How will those external libraries ever be integrated into the standard library? This is going to be a long and painful process, which will involve breaking and rewriting lots and lots of Rust programs. Well, not necessarily *breaking*, because dependencies are pinned by default, but it’s exactly that pinning which makes it easy for software to *rot* (never gets updated, because “it works 🤷”).

Then again, that guy on StackOverflow makes a good point about the sequence of HTTP libraries in Python. 🤔 Python can only grow and, maybe, there’ll be a “clear cut” some day – which will be just as painful.

It all has pros and cons.
lyse
lyse.isobeef.org
View Thread
@movq Oh dear, that's indeed very disappointing to include third-party libraries all over the place. My experience is exactly the same, if it works, it will never be touched again. Regardless of the language.