Live data from Hacker News

Test your product on a crappy laptop

css-tricks.com

231–240 of 321 posts

Re: Test your product on a crappy laptop

#231

The point they make is more than valid. I don't like the attitude calling them craptops. A Gigabyte of memory and 10 Mbit/sec are enough to meet 99.9% of the user needs for Web browsing. If sites were implemented in a resource-aware manner of course. Instead of looking down at craptops I would look down at people introducing 4K and using many Gigabytes of memory for personal computing. Even worse making masses use it…

10Mbit/s is actually bit high in my mind... 256kbit/s should be reasonable.

Re: Test your product on a crappy laptop

#232
post #97

Earlier quoted context omitted.

What condescending bullshit.

What do you even mean? A website has no business to have minimum system requirements. It's a hypertext document with some optional macros here and there.

Absolutely trivial to demonstrate to be false.

I can use websites to videoconferencing. Streaming considered video and audio comes with non trivial loads.

I can use websites to compress images, to compute tabulated data on various Excel clones, remotely control devices or play games.

This isn't 1995 and we're way past indulging user lazy choices which have us a decade of internet explorer nightmares. Web is much more than that, and one need to know where to draw the line where their products minimum requirement lies.

Re: Test your product on a crappy laptop

#233
post #203

Earlier quoted context omitted.

> 2) People cannot afford good computer usually also cannot afford to pay for the game. I wonder if they had any kind of proof of this. I would think that there are plenty of kids who could get their parents to pay five bucks for the game, but not 500 bucks to buy a fancy new computer.

If you look at the flip side people who can afford an expensive gaming pc can probably also afford a game which isn’t nearly as expensive

Willingness and ability to pay for one thing doesn't mean willingness to pay for other things. There are plenty of cheapskate rich people and people who consider themselves poor on six figure salaries.

Re: Test your product on a crappy laptop

#234

It's not just developers, and it's not just about speed, it's also designers / UX bods who need to heed this. My decently powered work laptop from job 1 has a fairly rubbish screen, which means that a lot of the subtle hover effects, 1 pixel light grey on lighter grey divisions and skinny fonts either aren't visible or are incredibly difficult to see. A good trick if you're working on a large, hi res screen is to hav…

This is one area that really grinds my gears: the trend in UI design to reduce contrast because full black on full white text is too contrasty. Whatever minor improvement in readability on their quality 3000:1 contrast ratio monitor pales in comparison to the loss in readability on a 200:1 trash TN display. Even on a good display at low brightness low contrast design choices can be infuriating (e.g. phone at min brightness in pitch dark room)

Re: Test your product on a crappy laptop

#235
post #5

Any recommendations for a solid, representative crappy laptop? $100 xSomething Thinkpad off Ebay? Or is there something more representative of today.

Try the shittiest laptop at Walmart. Like an HP stream. Remember the low res 1366x768 screen.

Trying small displays is essential!

My software engineer teammates get specially approved 4K displays and “engineering” laptops. People who use the apps are often restricted to “business” laptops. Conference rooms still use old projectors that are even lower resolution. We have no control over the displays our customers use.

I’ve been teaching my engineers to use the responsive design tools in their browsers. For UI components that render differently based on @media queries, it’s been helpful to add stories for those breakpoints to our Storybook component library.

Re: Test your product on a crappy laptop

#238
post #235
post #5

Earlier quoted context omitted.

Try the shittiest laptop at Walmart. Like an HP stream. Remember the low res 1366x768 screen.

Trying small displays is essential! My software engineer teammates get specially approved 4K displays and “engineering” laptops. People who use the apps are often restricted to “business” laptops. Conference rooms still use old projectors that are even lower resolution. We have no control over the displays our customers use. I’ve been teaching my engineers to use the responsive design tools in their browsers. For UI…

When preparing to present to a remote audience, check how the slides will look for people connecting with a phone.

When recording a demo video, try to record at a lower resolution like 720p to save bandwidth and make it easier for people with small screens to watch.

Re: Test your product on a crappy laptop

#239
post #14

I believe that most of the "web developers" have absolutely no idea of how to build a website using bare html+css. Actually, I worked with "web developers" that are basically not touching code much, but using all sorts of tools and framework - without fully understand what they are doing. And that's also why website looks like each other more and more. And that's the silent majority of the industry.

There is no way to be a modern web developer without knowing everything you need for raw html/css unless you are talking about square space or basic Wordpress work. Things like react are purely extra knowledge needed over the top of the basic website building blocks.

ok, html maybe, because html if anything is easier than the one in 90/00s (no more tables, or divs everywhere)

But in my experience 80% react developers could not layout a page with raw css. I am not even talking anything "fancy" like transitions or animations. They just import libs and frameworks and customize a bit.

Re: Test your product on a crappy laptop

#240

> British soldiers in World War I were equipped with a Brodie helmet, a steel hat designed to protect its wearer from overhead blasts and shrapnel while conducting trench warfare. After its deployment, field hospitals saw an uptick in soldiers with severe head injuries. > Because of the rise in injuries, British command considered going back to the drawing board with the helmet’s design. Fortunately, a statistician p…

Taking the train over the Rockies they tell a story about Westinghouse[1] inverting the logic on the pneumatic brakes. When first introduced they failed open, meaning the train could move. This was convenient on the flats, but if the train was stopped on a grade and the pressure failed... down the hill you go. So Westinghouse made them fail closed: no pressure, no rolling down the hill. IIRC it saved lives.

[1] https://en.wikipedia.org/wiki/George_Westinghouse

Post reply on HN