News for hackers. Stuff that matters.
Re:Chrome Is Bad by vesche on Saturday December 12, 2020 @02:54PM (#25401051)
The author went so far as to create a domain for this rant, and yet didn't even do any performance metrics or basic forensic analysis at all. I'm not saying the author is wrong, but there's a lot of questions here. How does Keystone hide itself from the Activity Monitor? Is there a Keystone process if you run `ps aux`? Did you run dtruss/strace? What is it doing when Chrome isn't running that causes it to degrade performance?
Re:Chrome Is Bad by Etheryte on Saturday December 12, 2020 @03:21PM (#25401333)
Because this sounded outlandish, I decided to have a look on my own system. Since the author didn't give any technical details, I grepped `~/Library` and `/Library` for files containing `keystone` in either name or contents. This yielded the following interesting candidates, along with similar entries for daemons etc:

  ~/Library/LaunchAgents/com.google.keystone.agent.plist  
  ~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/com.google.keystone.agent.plist
  
They all reference the same binary, `~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareUpdateAgent`, and frankly are wholly uninteresting configuration files to integrate with launchd and other stuff.

Looking through a full system trace in Instruments didn't yield anything interesting either (outside of discovering that I forgot to shut down one of my virtual machines).

All in all, this sounds like hot air, and I can't help but wonder what the motivation behind making this page was.

Re:Chrome Is Bad by joshspankit on Saturday December 12, 2020 @03:44PM (#25401537)
Thank you for digging in to it on your machine. That level of forensics is exactly what we need in this issue.

Because there is a rich history of issues that only affect certain configurations, and those configurations are typically only revealed in hindsight: your results have to be seen as a single datapoint and not a nail in the coffin.

To others who are curious about this: please contribute more datapoints

Re:Chrome Is Bad by nostromo on Saturday December 12, 2020 @03:28PM (#25401401)
> I can't help but wonder what the motivation behind making this page was.

Why would you immediately jump to assuming bad faith?

No grand conspiracy required... the author believes that Chrome is slowing down his Mac and decided to share it. The end.

Re:Chrome Is Bad by Etheryte on Saturday December 12, 2020 @03:31PM (#25401425)
I'm not really one for conspiracies, more so I fail to see where the evidence is that Chrome was somehow related to begin with. I do agree my wording could be better there, though.
Re:Chrome Is Bad by edoceo on Saturday December 12, 2020 @03:49PM (#25401567)
Asking the question "wonder" is not really assuming bad faith is it? I don't see any intentional deception there.
Re:Chrome Is Bad by jodrellblank on Saturday December 12, 2020 @04:08PM (#25401731)
The page says "I deleted Chrome, and all the files Keystone had littered on the computer, restarted, and it was so snappy it felt like a brand new computer. Yeah, I realize this sounds like a freakin' infomercial, but it worked so well I spent $5 on a domain name and set up this website even if it makes me sound like a raving nut."

To then "wonder what the motivation is" is to suggest that you don't believe this simple positive explanation, and imply there's something less simple, and more scheming.

Re:Chrome Is Bad by lorenb on Saturday December 12, 2020 @08:40PM (#25403523)
Yeah, there was no super master plan here, just that after dealing with one sluggish computer for days (you name it, I tried it), and another one for 5 years... the fact that it turned out to be slow because of an app that wasn't even running was pretty frustrating.

Filing a bug report that would get "works on my machine"'d and then ignored and auto-closed by a bot in 5 years didn't quite feel worthy.

Auto-updating browsers are a good idea. Keystone is bad auto-updating software. It should probably get scrapped.

Re:Chrome Is Bad by diebeforei485 on Saturday December 12, 2020 @11:11PM (#25404243)
What's a good way to verify that I've removed Keystone completely? Google doesn't provide any sort of uninstaller or uninstall instructions.
Re:Chrome Is Bad by lorenb on Sunday December 13, 2020 @10:20AM (#25407114)
try `mdfind keystone` in terminal
Re:Chrome Is Bad by Aeolun on Saturday December 12, 2020 @04:36PM (#25401948)
And domains are dirt cheap nowadays, so it’s not as if the author is out a lot of money.
Re:Chrome Is Bad by ehsankia on Saturday December 12, 2020 @04:24PM (#25401848)
Well, for one, going as far as buying a domain for a single rant is a little bit suspicious. If at least it was a website dedicated to gathering issues with chrome, but a single issue with zero evidence or research. That's not generally how people "decide to share it".

Sure looks suspicious and not the content I expect to see on HN.

Re:Chrome Is Bad by dang on Saturday December 12, 2020 @04:45PM (#25402018)
"Assume good faith."

"Please don't post insinuations about astroturfing, shilling, brigading, foreign agents and the like. It degrades discussion and is usually mistaken. If you're worried about abuse, email [email protected] and we'll look at the data."

https://news.ycombinator.com/newsguidelines.html

Re:Chrome Is Bad by stjohnswarts on Sunday December 13, 2020 @01:09PM (#25408610)
It's not suspicious, its $5 which is not much to a lot of people in 1st world countries, especially those with at least enough curiosity/knowledge to be able to set one up if he/she has be frustrated a long time by a slow computer.
[dead]
Re:Chrome Is Bad by dang on Saturday December 12, 2020 @04:44PM (#25402014)
Personal attacks are not ok here. Please don't respond to a comment that breaks the site guidelines by breaking them yourself. That just makes the thread even worse.

https://news.ycombinator.com/newsguidelines.html

Re:Chrome Is Bad by _qulr on Saturday December 12, 2020 @04:53PM (#25402088)
This entire submission has been flagged, so it appears that Hacker News itself sees something seriously wrong with the author's web site.

Anyway, FWIW, I was defending the author from the charge of doing something suspicious.

Re:Chrome Is Bad by dang on Saturday December 12, 2020 @11:16PM (#25404267)
> a dude with too much money and self-importance

Personal attacks are not ok on HN. Please don't post like that again, regardless of whom you're defending.

Re:Chrome Is Bad by _qulr on Sunday December 13, 2020 @08:44AM (#25406489)
This is a serious, non-sarcastic response: honestly, sincerely, in my experience as a HN reader off and on for years, a commenter for 6 months, and occasional author of submitted articles (usually submitted by someone other than me) that have reached #1, violation of the HN guidelines is the norm on HN, and abiding by the guidelines is the exception.

I myself have been personally attacked on here, or been interpreted uncharitably, etc., countless times. Mostly with no moderators intervening. In general I have no objection to "policing" the comments, if it is done well, and consistently, but the problem with policing, not just on HN but in general, is the selective, arbitrary enforcement of rules.

Just looking at the current case, for example, why was my reply flagged, but the comment I replied to, which you also cited as violating the guidelines, was not flagged?

Moreover, IMO this whole submission seems to be a strange time to be pedantic about enforcing the guidelines. After all, the submission itself was flagged as very low quality, and many of the commenters were justifiably complaining about the low quality of the submission and wondering why it was #1. The author is deserving of some rebuke, especially for the "nefariously hides itself from Activity Monitor" bit, which is technically false, indeed impossible. The author should know better, being or having been a Mac software engineer himself.

In fairness, HN is no worse off than any other site that allows comments from the general public. HN wants to believe that its comments are higher quality than other sites, but the reality is that it's not really true, and it's hard to see how that will ever become true. Maybe it was true in the distant past when HN was less trafficked, I don't know.

Re:Chrome Is Bad by dang on Sunday December 13, 2020 @04:21PM (#25410404)
There are several points here—happy to respond.

> violation of the HN guidelines is the norm on HN

It happens much more than we'd prefer, but to say "the norm" is a huge exaggeration. I understand how it can feel like the norm—it's common enough to run into frequently, and painful experiences leave a stronger imprint than pleasant ones [1]. But these false feelings of generality are dangerous because they lead to an attitude of why-bother. Current toxin levels, though bad enough to produce symptoms, at least aren't fatal. Why-bother would kill the community if it spread.

> selective, arbitrary enforcement of rules

HN moderation is inconsistent in one way but consistent in another—call them strong and weak consistency. Strong consistency would be "every post that breaks the guidelines gets moderated in the same way". That would require moderators to read all the posts, and there are far too many for that to be feasible. Weak consistency would be "when a post does get moderated, the mods do it consistently and even-handedly". That's at least possible, and what we're shooting for. We don't get everything right but we're open to hearing about and fixing our mistakes.

If you see a post that ought to have been moderated but hasn't been, the likeliest explanation is that we didn't see it [2]. (You can help by flagging it or emailing us at [email protected].)

> why was my reply flagged, but the comment I replied to, which you also cited as violating the guidelines, was not flagged?

Users flagged one more than the other. Your post violated the guidelines worse, so I don't think that was unfair.

> this whole submission seems to be a strange time to be pedantic about enforcing the guidelines

That's not how moderation works. When users break the guidelines and we see it, we ask them not to. Keep in mind that we don't necessarily read the threads in order—sometimes we do, but other times we're looking in via more random-access views. The guidelines don't change relative to the submission, so I don't see why moderation should.

[1] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...

[2] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...

Re:Chrome Is Bad by comex on Saturday December 12, 2020 @03:08PM (#25401197)
Another thing you can do: profile the process to find out what exactly it’s spending all that CPU time on. There are a few different ways to do this on macOS, including the GUI Instruments.app which comes with Xcode, and dtrace. But if you’re the sort who always has a terminal open, the quickest way is to just run

    sudo spindump
Also useful when a process is hung, even if it’s not taking up CPU time.

Sometimes the output isn’t useful due to a binary having been stripped of symbol names, but all macOS system libraries have symbols, so you can usually figure out something.

Re:Chrome Is Bad by z3t4 on Saturday December 12, 2020 @03:38PM (#25401486)
So users are expected to run debugger tools in order to figure out what some hidden program is doing?

Many years back I couldn't sleep and noticed my HDD's was working hard. I checked and it was google updater that was scanning everything...

I will never know why, they might be stealing IP (i was working on OCR at the time) or they just wanted to create a profile to serve better ads...

Re:Chrome Is Bad by ehsankia on Saturday December 12, 2020 @04:26PM (#25401870)
> So users are expected to run debugger tools in order to figure out what some hidden program is doing?

That's like saying "So we're expected to investigate and have a full trial before sending someone to jail?". If you just want to delete it, go ahead. If you want to go as far as creating a whole domain to blame Chrome, yes, you do need more than just "I deleted it and coincidentally my computer got fast".

Re:Chrome Is Bad by Aeolun on Saturday December 12, 2020 @04:39PM (#25401971)
> If you want to go as far as creating a whole domain to blame Chrome, yes, you do need more than just "I deleted it and coincidentally my computer got fast".

I think the fact that the site exists and is a pretty highly ranked story on HN probably proves that incorrect.

Re:Chrome Is Bad by ehsankia on Saturday December 12, 2020 @05:08PM (#25402220)
s/you do need more/you should need more/

Clearly if you read the thread, most people here aren't happy about this being at the top of HN, and it honestly reminds me of reddit where people just upvote things purely based on the headline, without even looking at the content. If anything this is just a sad day for HN.

Re:Chrome Is Bad by tripzilch on Monday December 14, 2020 @05:13AM (#25415330)
> most people here aren't happy about this being at the top of HN

well the ones that comment, at least.

there might very well be a silent majority that is reading these threads with great joy.

like for instance the bit where someone lost it when they got reminded of the site guidelines and felt the need to list their "accomplishments" on HN

you don't get entertainment like that in normal threads.

Re:Chrome Is Bad by _qulr on Monday December 14, 2020 @09:12AM (#25417712)
You're welcome!

Of course your comment also violates the guidelines: "Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith." Reinforcing my claim that violation of the guidelines is the norm here rather than the exception.

My point was that authors of HN submissions are almost always treated with disrespect by HN commenters, and I was citing my repeated personal experience of having been such an author. (I believe the HN moderators are in denial and view the site through rose-colored/orange-colored glasses). I don't view having been #1 on HN to be an "accomplishment". I don't find it useful at all, because I run an independent business, yet being #1 on HN never increases my software sales at all, so it's pretty useless as far as I'm concerned. It just increases my server usage. I've sometimes considered (as I'm sure many people have) simply blocking Hacker News referers on my server. Could still happen...

In fact I finally created an account on HN simply to try to have some "control over the narrative" in HN comments about my own authored articles, because there are often some really dumb misunderstandings in the comments. Not sure it has been worth it though.

Technically, I "lost it" on HN about 3 weeks ago, when I got sick and tired of accurate information being downvoted. The only reason I'm still here now is that I have way too much free time on my hands due to the pandemic/social distancing.

Re:Chrome Is Bad by saagarjha on Saturday December 12, 2020 @04:14PM (#25401773)
How else do you expect to figure out what a program is doing? Should it make a pop up with a stack trace from time to time?
Re:Chrome Is Bad by z3t4 on Saturday December 12, 2020 @09:44PM (#25403859)
Maybe a notification of what it is doing. "We are using your computer for machine learning" or "Currently upgrading Chrome". Or some sort of documentation on what the program is supposed to do.
Re:Chrome Is Bad by franklampard on Saturday December 12, 2020 @03:57PM (#25401645)
There is a GUI program as he said.

By definition, “hidden” programs are not gonna tell you what they are doing up front.

Re:Chrome Is Bad by stjohnswarts on Sunday December 13, 2020 @01:13PM (#25408644)
Yep lots of responsible software companies will tell you what software is doing if it goes outside the parameters of their software. Say if a program is scanning your computer for information when it's really only supposed to be a web browser.
Re:Chrome Is Bad by codetrotter on Saturday December 12, 2020 @03:10PM (#25401218)
Speaking of the GUI Instruments.app. Is there a way to start a process from there, instead of attaching to an already running process? I used it the other day and could only figure out how to attach to an already running process with it.
Re:Chrome Is Bad by arcticbull on Saturday December 12, 2020 @03:15PM (#25401269)
Create a new profiling environment based on the template you're interested in, making sure "Choose a profiling template for:" is set to "Your Computer > All Processes." Next, in the top-left of the window, where it says "Your Computer > All Processes", click on All Processes. Select Choose Target... and navigate to your binary and hit Choose. Then hit the red circle to begin recording. This will launch a new instance of the specified binary and profile it.

This may not work for binaries that set PT_DENY_ATTACH, though.

Re:Chrome Is Bad by codetrotter on Saturday December 12, 2020 @03:15PM (#25401281)
Thanks :)
Re:Chrome Is Bad by comex on Saturday December 12, 2020 @03:16PM (#25401285)
Yes, it’s possible. In the menu with all the processes, pick the option “Choose Target”. It’s kind of an annoying UI, but it works.

Another option is to use `xcrun xctrace` to get a recording from the command line, which can then be opened in Instruments.

Re:Chrome Is Bad by blindm on Saturday December 12, 2020 @03:12PM (#25401231)
> The author went so far as to create a domain for this rant

It's not a 'far' thing to purchase a domain anymore. Domains are cheap as chips, and have gotten cheaper now since the advent of novel generic TLDs where usually the first year is sold cheap but to roll it over into the next few years the price is hiked (which is why so many people now purchase a domain for a year only).

It is common now and expected to see single-serving-sites[0] that are just thinly veiled blogposts.

[0] https://en.wikipedia.org/wiki/Single-serving_site

Re:Chrome Is Bad by SkyPuncher on Saturday December 12, 2020 @03:54PM (#25401623)
A lot of blogging services integrate domains as well.

If you already have payment integrate, adding a domain to a blog is a few clicks - if even.

Re:Chrome Is Bad by Blikkentrekker on Saturday December 12, 2020 @03:00PM (#25401111)
I'm quite impressed by that “chromeisbad” as a domain was not already taken.
Re:Chrome Is Bad by codetrotter on Saturday December 12, 2020 @03:13PM (#25401249)
Yeah. After reading your comment I tried out a couple of similar domains on the form x is bad and x is good and they were both parked waiting for someone to pay whatever ridiculous price the owner is wanting to demand to sell it. I wish it was illegal to do that.
Re:Chrome Is Bad by Blikkentrekker on Saturday December 12, 2020 @03:18PM (#25401308)
If it weren't legal, then someone would simply use it for a trivial website and then sell it.

Perhaps that is the only reason this simple, trivial article exists.

Re:Chrome Is Bad by libria on Saturday December 12, 2020 @03:52PM (#25401599)
With the amount of rebuttals in this thread, I'm impressed `chromeisgood.com` isn't taken.
Re:Chrome Is Bad by artiszt on Saturday December 12, 2020 @04:37PM (#25401958)
right

besides, most probably would learn themselves the hard way when put in the same position the OP detailed

problems with Goo are widely known in circles of the Mac-communities ever since Goo-acc's first became avail in the beginning only by invitation, back then

also worth to look into the history of why, when and by whom LS aka LittleSnitch was developed in the first place -- tho this was more related to issues with that then must-go-to site 'versiontracker' [for all sorts of Mac shareware] and a vintaged firewall [3rd party] product widely used that time that didn't work as advertised

a Mac OS w/out LS these days ? back then very few only were concerned with 'calling-/phoning-home' issues on a scale nobody could imagine, least speak or post about in public, in those pre-iPhone ages

Re:Chrome Is Bad by alfon on Saturday December 12, 2020 @05:45PM (#25402509)
Here you have another one: ilovechrome.com :)
Re:Chrome Is Bad by sroussey on Saturday December 12, 2020 @03:01PM (#25401114)
Possible correlation and hand waving equals causation.

I, too, was hoping for something, well, technical. Considering #1 on hacker news...

Re:Chrome Is Bad by edgefield0 on Saturday December 12, 2020 @03:03PM (#25401142)
Does anyone else see the irony that hand waving is being disputed with hand waving?
Re:Chrome Is Bad by izacus on Saturday December 12, 2020 @03:08PM (#25401196)
No, there's a concept of "burden of proof" which applies here.
Re:Chrome Is Bad by platelets2020 on Saturday December 12, 2020 @03:11PM (#25401227)
You don't get to stack "hand waving" indefinitely. The person who made the original claim is responsible for providing refutable evidence.
Re:Chrome Is Bad by stjohnswarts on Sunday December 13, 2020 @01:15PM (#25408666)
I was reading through the comments and hoping someone would know what keystone actually was and if there was any possibility of the claim in the article :) . I mean there's a lot of stuff in chrome other than this keystone thing, maybe it was one of those other things.
Re:Chrome Is Bad by wnevets on Saturday December 12, 2020 @03:20PM (#25401324)
Hating Google is very fashionable on HN these days, I'm not surprised to see this so highly voted. I also wouldn't be surprised if most of the upvotes are based on the title/domain rather than the actual "content".
Re:Chrome Is Bad by coldtea on Saturday December 12, 2020 @04:14PM (#25401776)
>Hating Google is very fashionable on HN these days

Well, why shouldn't it be?

Re:Chrome Is Bad by wnevets on Saturday December 12, 2020 @05:02PM (#25402167)
Why shouldn't apple? For some reason apple gets a pass on HN for things like fighting to keep forced labor camps open [1]. Lets hate Google AND Apple.

1. https://9to5mac.com/2020/11/23/anti-forced-labour-bill-apple...

Re:Chrome Is Bad by coldtea on Sunday December 13, 2020 @06:05AM (#25405728)
>Why shouldn't apple? For some reason apple gets a pass on HN

Or, you know, Apple gets the same or more kind of criticism, but since you are biased to agree with it, you are blind to it, and only see the praise/defenses.

>for things like fighting to keep forced labor camps open

That's probably because the framing of this by the media is BS, playing into the trade war objectives and narrative of the US foreign policy.

It's just that these companies have a lot of suppliers in those areas, unrelated with any "labor camps", whereas the US/law has put a wide canvas that includes a huge area and all kinds of inoffensive suppliers. Seeing that the companies can't just cut off their supply chain on the drop of a hat, they ask for extention period, better monitoring on which and if any of their particular suppliers might actually involve such labor, etc.

But that doesn't make for good headlines for the masses, or for good propaganda.

Re:Chrome Is Bad by wnevets on Sunday December 13, 2020 @01:28PM (#25408796)
>Or, you know, Apple gets the same or more kind of criticism, but since you are biased to agree with it, you are blind to it, and only see the praise/defenses.

Do you honestly believe if this post was about apple or an apple product with the exact same lack of content, it would have gotten the same number of up votes as quickly as this one did?

Re:Chrome Is Bad by coldtea on Sunday December 13, 2020 @02:04PM (#25409119)
In HN, where every third post is "Why I'm leaving Apple" or such? Yes.
Re:Chrome Is Bad by wnevets on Sunday December 13, 2020 @04:44PM (#25410616)
I dont see any apple related post on the front page, let alone negative ones. Do you see a different front page than I do?
Re:Chrome Is Bad by coldtea on Monday December 14, 2020 @04:46AM (#25415148)
Yes, it's called "bias blind spot" :-)

Here's one in the front page, just a few days ago:

Falling Out of Love with Apple, Part 3: Content and Censorship (hardware.substack.com) 321 points by zherbert 7 days ago | flag | hide | 292 comments

https://news.ycombinator.com/front?day=2020-12-07

Re:Chrome Is Bad by wnevets on Monday December 14, 2020 @01:43PM (#25421378)
Wait, so we went from every third post on HN is a negative post about apple to here is one post from 7 days ago? Talk about "bias blind spot".
Re:Chrome Is Bad by stjohnswarts on Sunday December 13, 2020 @01:22PM (#25408731)
This law is untenable. For one thing outside of companies like Apple or Amazon who -might- be able to negotiate with the Chinese government on audits, middle to small businesses would have no possibility of that because they mean nothing to the CCP. This is a government to government thing, not a company thing and the bill doesn't make sense to make companies culpable for the entire supply chain. It's just punting responsibilities to companies who trade rather the US government whose job it is really to investigate such things. It's just a feel good law to blame corps rather than Congress Critters, which they've been trying to get rid of responsibilities for decades.
Re:Chrome Is Bad by SZJX on Sunday December 13, 2020 @03:44AM (#25405182)
Or, you know, maybe the world isn’t black and white, and you could read the whole linked article to see why Apple might want to reasonably oppose certain provisions of the bill, instead of simply being “evil”, whatever that means:

> However, there is one potential explanation.

> In July, campaign groups called on Apple to err on the side of caution by ceasing using production facilities based in the Uyghur Region of China. The bill as it is currently written might make that the only way that US companies could ensure compliance.

> > One provision in the bill requires public companies to certify to the Securities and Exchange Commission that their products are not made using forced labor from Xinjiang. If companies are found to have used forced labor from the region, they could be prosecuted for securities violations.

> If Apple cannot easily avoid using downstream suppliers based in the region, it may be that it is trying to dilute the provision to something more along the lines of a requirement to conduct audits, investigate claims, and to take all reasonable steps to prevent the use of forced labor.

Re:Chrome Is Bad by mihaela on Monday December 14, 2020 @10:41AM (#25418768)
With Apple you get what you've paid for. With Google you pay for what you've got for "free".
Re:Chrome Is Bad by boogies on Saturday December 12, 2020 @07:00PM (#25402972)
Seriously, why not? And why was wnevets getting downvoted?

The linked article references a source I’m sure most on HN would agree is reputable, to the extent it confirms their biases.

> A report in [The Washington Post](https://www.washingtonpost.com/technology/2020/11/20/apple-u...) claims that Apple is trying to weaken provisions in the bill.

> > Apple lobbyists are trying to weaken a bill aimed at preventing forced labor in China, according to two congressional staffers familiar with the matter, highlighting the clash between its business imperatives and its official stance on human rights.

Re:Chrome Is Bad by coldtea on Sunday December 13, 2020 @09:53AM (#25406928)
Yeah, just bad reporting.

"Apple lobbyists are trying to weaken a bill aimed at preventing forced labor in China, according to two congressional staffers familiar with the matter, highlighting the clash between its business imperatives and its official stance on human rights."

1) The US legislators could not care less about "forced labor" in China (or even in the US for that matter, e.g. penal labor). Same way they don't care when it is their allies doing it (or worse things). It's all about the trade and dominance war with China.

2) Apple and the other companies involved don't care about forced labor either (if they could legally and without media repurcusion use it, they would). But they also don't need and don't seek forced labor. Good old capitalist low wage labor is good enough for them. So it's not like they try to defend China's forced labor because they benefit for it.

3) What Apple and the other companies have is multiple suppliers all over China, including that area. Most of them (if not all) have little or nothing to do with forced labor. But because the law aims to hurt China and not to stop forced labor, it doesn't care about little details, but uses blunt force and a wide net.

4) Understandingly (from a business/logistics perspective) Apple, Google, and co, can't just drop/replace suppliers at the drop of a hat. So they ask for more time for check, and a better look at which suppliers are actually problematic to be added to the bill. So "weaken the provisions" is actually "make the law more accurate and fairer", but they won't say that.

Then the mix of propaganda for foreign policy (as if those legislators care), hypocrisy, business interests (from Apple and co) and extremely bad reporting for clickbait and patriotic reasons, then turns into:

"Apple lobbies in favor of force labor".

It's as if some companies wanted to continue to use some useful drug medically, and e.g. tried to "weaken the provisions" of an strict anti-drug law that forbade it without nuance, and the headlines were like "Company X lobbies in favor of heroin".

Re:Chrome Is Bad by stjohnswarts on Sunday December 13, 2020 @01:25PM (#25408764)
I agree, this is a deal that should be between governments, this is just an attempt of the US government to push responsibility to companies rather than actually acting against the Chinese government to end these labor camps. Whether tariffs or whatever. Few companies have the ability to follow every link of the supply chain for corruption. Most small to mid size to just find a distributer and buy what they need, they don't have the ability or authority to send in a small army of auditers, that the CCP isn't going to allow anyway.
Re:Chrome Is Bad by politelemon on Saturday December 12, 2020 @03:06PM (#25401174)
That this is so high right now is quite reflective of HN.

It's nearly an exact match of the meme like utterance often seen on reddit: "chrome bad".

Re:Chrome Is Bad by dang on Saturday December 12, 2020 @04:47PM (#25402038)
If you're going to credit the community with the problem I trust you'll credit it with the solution as well.

https://news.ycombinator.com/item?id=25402000

Re:Chrome Is Bad by platelets2020 on Saturday December 12, 2020 @03:13PM (#25401252)
There's been a massive influx of reddit-quality comments for quite a while. I guess it was only a matter of time before it was reflected in the submissions.
Re:Chrome Is Bad by stjohnswarts on Sunday December 13, 2020 @01:27PM (#25408788)
So are you also going to point out that the vast majority of other top links are actually quite credible? It's easy to declare a whole site bad over one thing isn't it? Like the author in this article did under similar circumstances?
Re:Chrome Is Bad by Avtomatk on Saturday December 12, 2020 @03:22PM (#25401345)
I think that in HN there is a high quality in the comments and a low quality in the voting of publications, because in the first, people refrain from commenting stupid things because it gets them harsh criticism, but in the second, people can vote for stupid (or low quality) publications because they will not be criticized.

And most of HN (and of social media, and the world in general) is dominated by dumb people.