←back to thread

Pixar's Render Farm

(twitter.com)
382 points brundolf | 3 comments | | HN request time: 2.013s | source
Show context
hadrien01 ◴[] No.25616026[source]
For those that can't stand Twitter's UI: https://threadreaderapp.com/thread/1345146328058269696.html
replies(7): >>25616111 #>>25616482 #>>25616748 #>>25617285 #>>25617838 #>>25618314 #>>25618916 #
nikolay ◴[] No.25616482[source]
It's very painful to follow a conversation on Twitter. I'm not sure why they think the way they've done things makes sense.
replies(7): >>25616558 #>>25616759 #>>25617073 #>>25618707 #>>25619851 #>>25620397 #>>25620402 #
lmilcin ◴[] No.25616558[source]
It was never supposed to support conversation in the first place.

People were supposed to shoot short, simple, single messages and other people maybe react to this with their own short, single messages.

replies(5): >>25616749 #>>25616780 #>>25616785 #>>25616919 #>>25617734 #
nikolay ◴[] No.25616785[source]
Yeah, I've never seen any value in Twitter. They should've called it "Public IM" or limited IIRC and make it function well like IM. Even the poor implementation of threads in Slack is way better than the perverted version of Twitter.
replies(2): >>25618684 #>>25618874 #
1. folkrav ◴[] No.25618684[source]
Apart from being stuck to a single level in depth (which IMHO kind of makes sense in the context of an IM platform), what's that bad about Slack's threads?
replies(1): >>25619098 #
2. nikolay ◴[] No.25619098[source]
Well, literally, you need to move aside - they took the skeuomorphism of people getting aside to discuss a topic without bothering others too far.
replies(1): >>25646430 #
3. folkrav ◴[] No.25646430[source]
Not sure what would you have preferred? I can only think of inline, but I'm not sure how well that would have worked in an IM application, where you'd typically expect things to be in chronological order. You basically described the point of having threads in the first place, and I also cannot think of many other existing implementations, so I'm curious.