Hacker News Reader

Comment by guappa | Hacker News Reader

I would like browsers to have very strict limits on the amount of cycles a page can use, and have some permission like for camera to use more CPU.

View on HN

I would like also that devs run their site/apps on downgraded machine/VM so that they can early detect performance issues.

In my company the frontend team has shiny new powerful machines. I on the other hand don't have enough RAM to compile our server.

Does that create a sort of Conway's law pushing complexity to the FE?

They offset that risk by taking 2 months to design and implement complex features like "add a new text box in the form, to enter an IP address".

I haven't seen them merge a pull request in less than 3 days. However simple.

The team lead, in 2 years, contributed less than 20 pull requests, all of which were 1 to 3 line changes to CSS or similar.

I’ve realized how huge a problem this is by spending time with older relatives recently. Many of them have >5 year old phones (why upgrade?), that current websites and apps often just don’t run on. They SHOULD be able to run - they just don’t.

What a nice idea.

top joke!

Run the browser in a cgroup?

I don't want the whole browser to be stopped or killed. What would that accomplish?

I was imagining for a bad behaved site run it in a cgroup but it would be better if the browser did that per tab

Browsers don't run a process per tab though.

Reply on news.ycombinator.com