Slow Software
inkandswitch.com
Slow Software
1–10 of 272 posts
Re: Slow Software
#2I like how the site is an example of very fast software, such a simple design and it renders immediately; a single file load with the tiniest of javascript to make the videos work. A full page load in 27ms with only 14kb transferred!
Re: Slow Software
#3> Android and iOS both make substantial use of "long press" to access context menus, which require that the user wait hundreds of milliseconds in the middle of their command gestures.
> A related source is delays for disambiguation. For example, on mobile Safari there's a default 350ms delay between when the user taps a link and when the browser begins fetching the new page, in order to tell the difference between a link click and a double-tap zoom.
I really wish mobile devices had one or two modifier buttons on the side. That way you could have "right click", maybe even positioning a cursor without clicking, all sorts of crazy stuff, like being able to "mouse over" a link in a mobile browser.
Re: Slow Software
#4I've said it before and I'll say it again - one of the greatest boons from the new wave of VR is not the tech itself (fun though it is) but the focus on latency as a first-class metric. I've always been sensitive to microstuttering and so find it irritating when a game that's "running at 90fps" (or a document that's scrolling) still has perceptible judders.
Re: Slow Software
#5I think this article places too much emphasis on input devices and hardware constraints, and not enough on software architecture. JIRA doesn't really feel any faster just because your input devices are fast; the application level latency dwarfs the input latency by a large margin.
I would take measurements, but JIRA prohibits benchmarking for some reason... ¯\_(ツ)_/¯ they're probably just trying to save everyone else the embarrassment of seeing how incredibly fast JIRA is compared to their own sluggish offerings, right?
I am confident that JIRA's application latency has nothing to do with Java (backend) or JavaScript's (frontend) garbage collector.
Many companies just feel no impetus to write fast software, or to use commensurately powerful hardware.
Re: Slow Software
#6I like how the site is an example of very fast software, such a simple design and it renders immediately; a single file load with the tiniest of javascript to make the videos work. A full page load in 27ms with only 14kb transferred!
to be fair the site is a html site only and gets served via cloudflare. not a fair metric against a "dynamic" site.
also most webservers/frameworks/whatever will favor throughput over latency.
Re: Slow Software
#7I seriously doubt the vast majority of the population cares.
I mean, I do. I hate websites that take many seconds to completely load when I know they could take less than 1 second without the bloat.
Hardcore desktop gamers and developers usually are also very performance conscious but that is minority.
Sites keep piling hits while adding bloat, and it's totally counterintuitive. Why?
Re: Slow Software
#8I've said it before and I'll say it again - one of the greatest boons from the new wave of VR is not the tech itself (fun though it is) but the focus on latency as a first-class metric. I've always been sensitive to microstuttering and so find it irritating when a game that's "running at 90fps" (or a document that's scrolling) still has perceptible judders.
is 'judder' a synonym for 'jank'?
Re: Slow Software
#9> Android and iOS both make substantial use of "long press" to access context menus, which require that the user wait hundreds of milliseconds in the middle of their command gestures. > A related source is delays for disambiguation. For example, on mobile Safari there's a default 350ms delay between when the user taps a link and when the browser begins fetching the new page, in order to tell the difference between a…
We can't do that. Buttons, and headphone jacks, are so yesterday. /s
Re: Slow Software
#10I like how the site is an example of very fast software, such a simple design and it renders immediately; a single file load with the tiniest of javascript to make the videos work. A full page load in 27ms with only 14kb transferred!
to be fair the site is a html site only and gets served via cloudflare. not a fair metric against a "dynamic" site. also most webservers/frameworks/whatever will favor throughput over latency.
Ok, what about Hacker News? But the article discusses news website like WaPo that really don't need to be very dynamic.