# 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 33
# self = https://watcher.sour.is/conv/tvu2tba
lol re: recent Go telemetry announcement
https://git.sr.ht/~sircmpwn/dotfiles/commit/71c7fe0eb1e502edec3947a06cf84556c80df50d
@abucci ha!
😱 Has telemetry in Go already been shipped? πŸ€¦β€β™‚οΈ
😱 Has telemetry in Go already been shipped? πŸ€¦β€β™‚οΈ
😱 Has telemetry in Go already been shipped? πŸ€¦β€β™‚οΈ
😱 Has telemetry in Go already been shipped? πŸ€¦β€β™‚οΈ
Or is Drew just preparing for this…
Or is Drew just preparing for this…
Or is Drew just preparing for this…
Or is Drew just preparing for this…
@prologic Reckon he's just getting ahead of the game, if that's the flag they proposing for the feature to turn it off.
(#tvu2tba) @prologic Reckon he's just getting ahead of the game, if that's the flag they're proposing for the feature to turn it off.
@eldersnake Ahh I see...
@eldersnake Ahh I see...
@eldersnake Ahh I see...
@eldersnake Ahh I see...
Another commit followed shortly after: export GOTOOLCHAIN=local A complete Go version might be downloaded otherwise, see here: https://github.com/golang/go/discussions/55092 Holy fuck!
@lyse Oh my god! 😱 wut da actual fuq?! Is Russ okay? πŸ€” This is all kinds of nuts really. Can't we just keep Go simple. it happens to be one of it strengths, adding all kinds of "magical"β„’ shit to the Go toolchain is just crazy πŸ€¦β€β™‚οΈ
@lyse Oh my god! 😱 wut da actual fuq?! Is Russ okay? πŸ€” This is all kinds of nuts really. Can't we just keep Go simple. it happens to be one of it strengths, adding all kinds of "magical"β„’ shit to the Go toolchain is just crazy πŸ€¦β€β™‚οΈ
@lyse Oh my god! 😱 wut da actual fuq?! Is Russ okay? πŸ€” This is all kinds of nuts really. Can't we just keep Go simple. it happens to be one of it strengths, adding all kinds of "magical"β„’ shit to the Go toolchain is just crazy πŸ€¦β€β™‚οΈ
@lyse Oh my god! 😱 wut da actual fuq?! Is Russ okay? πŸ€” This is all kinds of nuts really. Can't we just keep Go simple. it happens to be one of it strengths, adding all kinds of "magical"β„’ shit to the Go toolchain is just crazy πŸ€¦β€β™‚οΈ
One benefit you get for this pain is that you can ship scala source code that almost surely compile and run. You don't get into the mess of "oh well this only compiles for scala 2.13" and the person downloading it's like "shit I have scala 2.12 and I don't want to upgrade to compile your code." That issue leads to the world of virtual environments or containers or nix-shells or....which is messy no matter how streamlined people try to make it.

Instead, the person doesn't have to change their scala install or environment in any way, and doesn't have to set up a weird local or temporary environment. They can just compile your code as-is with the tooling they already have, and it'll just work. Part of the build process will grab a shim that lets the scala 2.12 compiler they have compile the scala 2.13 code that your source code requires.

Even with yarn this issue comes up. I had to upgrade the go install on my VPS in order to compile and run yarn, because yarn required a newer version of go than the server came with. In my case that didn't matter because I don't write go and I hadn't set up a special go environment on that server. But if I had set up such an environment, it probably would have been a pain to get yarn to compile. I'm sure there are ways, but the thing is with scala I wouldn't even have to think about it.

Whether go actually needs this though? 🀷
I still don't want my compiler going and automatically downloading a new version. I didn't know Scala does this πŸ˜†
I still don't want my compiler going and automatically downloading a new version. I didn't know Scala does this πŸ˜†
I still don't want my compiler going and automatically downloading a new version. I didn't know Scala does this πŸ˜†
I still don't want my compiler going and automatically downloading a new version. I didn't know Scala does this πŸ˜†
@abucci I get there are situations where this might be helpful, but all the security implications etc. No thanks! It's already kind of bad with dependencies, but the toolchain itself is a whole different level. I've set all the variables already in advance.
@prologic the compiler you have installed is unaffected. The compiler that's downloaded functions as a library that your installed build system and interpreter use to compile other code.
@lyse yeah I think it's dangerous too. I should probably set these variables since I compile yarnd from source.