The Watcher

	
# 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 8
# self = https://watcher.sour.is/conv/aqahq5a

prologic

twtxt.net

25 Jul 23 12:34 UTC

@hacker-news-newest I find it interesting to learn just how much the Go compiler can "optimize your code away". That's both good and bad.
The point on benchmarking the right thing is 100% spot on, same goes for testing too. The optimization problem however is a bit too contrived IMO. When would you possible write code (aside from very trivial things) where the compiler would optimize all your code away, thus making your benchmarking invalid? I want to see a real-world example of where someone has been caught out by this?

prologic

twtxt.net

25 Jul 23 12:34 UTC

@hacker-news-newest I find it interesting to learn just how much the Go compiler can "optimize your code away". That's both good and bad.
The point on benchmarking the right thing is 100% spot on, same goes for testing too. The optimization problem however is a bit too contrived IMO. When would you possible write code (aside from very trivial things) where the compiler would optimize all your code away, thus making your benchmarking invalid? I want to see a real-world example of where someone has been caught out by this?

prologic

twtxt.net

25 Jul 23 12:34 UTC

@hacker-news-newest I find it interesting to learn just how much the Go compiler can "optimize your code away". That's both good and bad.
The point on benchmarking the right thing is 100% spot on, same goes for testing too. The optimization problem however is a bit too contrived IMO. When would you possible write code (aside from very trivial things) where the compiler would optimize all your code away, thus making your benchmarking invalid? I want to see a real-world example of where someone has been caught out by this?

xuu@dev.txt.sour.is

dev.txt.sour.is

06 Aug 23 22:01 UTC

@prologic was this in reply to a different thread? Or maybe a hash collision?

xuu

txt.sour.is

06 Aug 23 22:01 UTC

@prologic was this in reply to a different thread? Or maybe a hash collision?

prologic

twtxt.net

07 Aug 23 08:43 UTC

@xuu Hmmm nope, looks like a user error on my part somehow 🤦‍♂️

- https://twtxt.net/twt/bjdy5ea
- https://twtxt.net/twt/fjwkpxa
- https://twtxt.net/twt/aqahq5a

There is duplicate entry here with slightly different content, but not much we can do about that 😅

prologic

twtxt.net

07 Aug 23 08:43 UTC

@xuu Hmmm nope, looks like a user error on my part somehow 🤦‍♂️

- https://twtxt.net/twt/bjdy5ea
- https://twtxt.net/twt/fjwkpxa
- https://twtxt.net/twt/aqahq5a

There is duplicate entry here with slightly different content, but not much we can do about that 😅

prologic

twtxt.net

07 Aug 23 08:43 UTC

@xuu Hmmm nope, looks like a user error on my part somehow 🤦‍♂️

- https://twtxt.net/twt/bjdy5ea
- https://twtxt.net/twt/fjwkpxa
- https://twtxt.net/twt/aqahq5a

There is duplicate entry here with slightly different content, but not much we can do about that 😅