91–100 of 323 posts
For those that can't stand Twitter's UI: https://threadreaderapp.com/thread/1345146328058269696.html
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.
Earlier quoted context omitted.
It's amazing to me that people find twitter difficult to read... I mean it's not perfect but it's not an ovaltine decoder ring, either. Just ... Scroll ... Down ... Click where it says "read more" or "show more replies" You're human; THE most adaptable creature known. Adapt! I'm not saying that twitter UX is perfect, or even good. I AM saying that it is usable.
Twitter was designed to have 280 characters max per message. This means that for this kind of long format text, the amount of Signal-to-Noise ratio of having a large number of "tweets" is pretty low. The amount of stuff your brain has to filter in the form of user name, user tweet handle, additional tagged handlers, UI menus, UI buttons for replying, retweeting, liking, etc on every single code snippet makes your bra…
> Twitter was designed to have 280 characters max per message.
Twitter was designed to use 140 characters, plus room for 20 for a username to fix in the 160 char budget of an SMS message.
Their upping it to 280 later was capitulating to the fact that nobody actually wants to send SMS sized messages over the internet.
Earlier quoted context omitted.
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.
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.
It’s time for Twitter to evolve in so many ways.
I can appreciate that working well when people are in the office, but I'm amazed that worked out for them when people moved to work from home. I have trouble getting some of my engineers to have a stable connection stable enough for VS Code's remote mode. I can't imagine trying to use a modern GUI over these connections.
Earlier quoted context omitted.
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.
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.
Earlier quoted context omitted.
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.
We are way way past that point. It’s time for Twitter to evolve in so many ways.
Oh man, I wanted this to contain much more details :( Whats the hardware? How much electric energy goes into rendering a frame or a whole movie? How do they provision it (as they keep #cores fixed)? They only talk about cores, do they even use GPUs? What's running on the machines? What did they optimize lately? So many questions! Maybe someone from Pixar's systems department is reading this :)?
They’ve been working on a GPU version of RenderMan for a couple of years.
https://renderman.pixar.com/news/renderman-xpu-development-u...
One of the things they mentioned briefly in a little documentary on the making of Soul is that all of the animators work on fairly dumb terminals connected to a back end instance. I can appreciate that working well when people are in the office, but I'm amazed that worked out for them when people moved to work from home. I have trouble getting some of my engineers to have a stable connection stable enough for VS Code…
Seems very strange to me.