Technology

37750 readers

205 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

Please remind me how we are moving forward. On application responsiveness to user input. (nitter.net)

submitted 1 year ago by [email protected] to c/[email protected]

25 comments fedilink hide all child comments

Nitter thread from Julio Merino on application responsiveness in early 2000's Windows computers versus modern Windows computers. Videos available in linked thread.

Please remind me how we are moving forward. In this video, a machine from the year ~2000 (600MHz, 128MB RAM, spinning-rust hard disk) running Windows NT 3.51. Note how incredibly snappy opening apps is.

Now look at opening the same apps on Windows 11 on a Surface Go 2 (quad-core i5 processor at 2.4GHz, 8GB RAM, SSD). Everything is super sluggish.

For those thinking that the comparison was unfair, here is Windows 2000 on the same 600MHz machine. Both are from the same year, 1999. Note how the immediacy is still exactly the same and hadn’t been ruined yet.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 1 year ago (1 children)

I don't know how some developers manage it. I've written web apps in React and, without even using available optimisations, the UI is acceptably snappy on any modern desktop.

We inherited an application from another vendor (because of general issues with the project) and it's just S L O W. The build is slow and takes several minutes, the animations are painful and even the translations are clearly not available for the first 5 seconds.

My question is, how? I'm not an expert, I generally suck at frontend and I just had to fill in for it. I didn't purposely write optimised code, the applications are similar in the amount of functionality they provide and they both heavily use JavaScript. How do you make it that slow?

[–] [email protected] 2 points 1 year ago (1 children)

Overuse of the spread operator and creating functions inside of functions are two of the biggest culprits of performance issues in modern is

[–] [email protected] 1 points 1 year ago

Yeah, the spread operator is heavy. Admittedly, one iteration of our software abused it and still seemed to run ok. We didn't end up changing that for performance reasons and it was more about code complexity. I wonder how excessive you have to get?