Killed by Google
-
@Gąska I would be helped by that, as I have a medical condition that makes black text on white background generally harder to read for me. I know, my body is and here but that's also nothing new for me.
-
@Gąska said in Killed by Google:
Why this thread? I count it as trying to kill eyesight.
I don't know why people prefer white themes. Staring at 90% white monitor is about as pleasant as looking directly into a flashlight.
-
@MrL said in Killed by Google:
@Gąska said in Killed by Google:
Why this thread? I count it as trying to kill eyesight.
I don't know why people prefer white themes. Staring at 90% white monitor is about as pleasant as looking directly into a flashlight.
Doesn't do that to me. At least not in normal ambient lighting conditions.
-
@boomzilla This. I have decades of experience reading books with black print on white paper; black text on white screen isn't that different. If I want to look at my phone in the dark with the lights off, yeah, the white background is not so great, but under normal lighting, it's fine.
-
Stadia is dead?
-
@HardwareGeek said in Killed by Google:
@boomzilla This. I have decades of experience reading books with black print on white paper; black text on white screen isn't that different. If I want to look at my phone in the dark with the lights off, yeah, the white background is not so great, but under normal lighting, it's fine.
Books don't actively produce light. Reading on a white background screen is like reading a book in midsummer sun at noon. It's just unpleasant and eyes get tired quickly. Same reason I have kindle without backlight.
Maybe something's wrong with my eyes, but I don't understand why you'd want to blast them with more light than necessary.
-
While that's true, you also have the option of reducing your screen's brightness to a comfortable level.
-
@Zerosquare I have my laptop at minimum brightness, and still occasionally hoped it would go lower.
-
@Zerosquare said in Killed by Google:
While that's true, you also have the option of reducing your screen's brightness to a comfortable level.
By switching to dark theme :)
-
@MrL said in Killed by Google:
@HardwareGeek said in Killed by Google:
@boomzilla This. I have decades of experience reading books with black print on white paper; black text on white screen isn't that different. If I want to look at my phone in the dark with the lights off, yeah, the white background is not so great, but under normal lighting, it's fine.
Books don't actively produce light. Reading on a white background screen is like reading a book in midsummer sun at noon. It's just unpleasant and eyes get tired quickly. Same reason I have kindle without backlight.
Maybe something's wrong with my eyes, but I don't understand why you'd want to blast them with more light than necessary.
I use an e-reader with a light, but it's still easier on the eyes than a TFT display because the image on it stays put rather than constantly refreshing at 60 Hz
-
@hungrier said in Killed by Google:
refreshing at 60 Hz
Join us in this century and get a real monitor.
-
-
@hungrier said in Killed by Google:
I use an e-reader with a light, but it's still easier on the eyes than a TFT display because the image on it stays put rather than constantly refreshing at 60 Hz
Unlike CRT screens, LCD screens don't really flicker much at their refresh rate (: FRC may cause a little bit of flickering, but it isn't usually noticeable). The backlight may flicker, but at a much higher frequency so that's unlikely to cause ill effects.
The big difference between TFT and e-paper is that the latter doesn't emit light by itself, so it tends to be easier on the eyes since it can't be brighter than the environment (unless you use the optional frontlighting, but it's not needed in daylight).
Another difference is that the "pixels" are monochrome and more-or-less circle-shaped, so it looks more like ink on paper than the RGB stripes of a LCD screen.
-
@Zerosquare said in Killed by Google:
The big difference between TFT and e-paper is that the latter doesn't emit light by itself, so it tends to be easier on the eyes since it can't be brighter than the environment (unless you use the optional frontlighting, but it's not needed in daylight).
That's why Amazon came out with Kindle Paperwhite and pushes it aggressively. E-Ink screen that acts like a real book and is easy on the eyes was just too good, so they had to ruin it with backlight.
-
Not to mention that LCD screens are significantly cheaper, and display ads better.
-
@Zerosquare said in Killed by Google:
The big difference between TFT and e-paper is that the latter doesn't emit light by itself, so it tends to be easier on the eyes since it can't be brighter than the environment (unless you use the optional frontlighting, but it's not needed in daylight).
The other really big difference is that e-paper takes much longer to update. That's why advertisers hate it: they've grown addicted to highly animated stuff, and e-paper simply doesn't support those kinds of refresh rates.
-
@dkf said in Killed by Google:
The other really big difference is that e-paper takes much longer to update. That's why advertisers hate it: they've grown addicted to highly animated stuff, and e-paper simply doesn't support those kinds of refresh rates.
I don't have to worry about that! I paid the extra money (10 or 20USD) and got the 'no ads' option on my Paperwhite. I love it because it's easy to read in any light level.
-
@dkf said in Killed by Google:
@Zerosquare said in Killed by Google:
The big difference between TFT and e-paper is that the latter doesn't emit light by itself, so it tends to be easier on the eyes since it can't be brighter than the environment (unless you use the optional frontlighting, but it's not needed in daylight).
The other really big difference is that e-paper takes much longer to update. That's why advertisers hate it: they've grown addicted to highly animated stuff, and e-paper simply doesn't support those kinds of refresh rates.
For me, reading an LCD screen in direct sunlight is very difficult and uncomfortable. This a big deal when reading for leisure, especially because I mostly only read when I'm out and about.
-
@dcon said in Killed by Google:
I paid the extra money (10 or 20USD) and got the 'no ads' option on my Paperwhite.
I believe you can actually put them back and receive store credit, effectively letting you take out a tiny loan with the ads as collateral.
-
@error Back before I got my e-reader, I used to read ebooks on my phone, and before that on my PSP. It was close to impossible to read in the sunlight, but ok otherwise.
-
@dcon said in Killed by Google:
@dkf said in Killed by Google:
The other really big difference is that e-paper takes much longer to update. That's why advertisers hate it: they've grown addicted to highly animated stuff, and e-paper simply doesn't support those kinds of refresh rates.
I don't have to worry about that! I paid the extra money (10 or 20USD) and got the 'no ads' option on my Paperwhite. I love it because it's easy to read in any light level.
Me too! (Both ad-free and light leveling.) The Paperwhite is my favorite way to read books that are just text. Sadly, ebooks are spendy compared to used ones. :/
-
@Parody said in Killed by Google:
The Paperwhite is my favorite way to read books that are just text.
That's true. Books that have pictures/maps are difficult. I did (actually embarrassingly recently) discover you can zoom in on the pictures. (if I remember, press-hold, then you can zoom by the normal pinch action)
-
Google recently discovered that some browsers based on the Chromium open-source project were making use of features that were “supposed” to only be available on Google Chrome. These features include “Chrome sync and Click to Call”. Essentially, users of some Chromium-based browsers could access their bookmarks, passwords, and sync data tied to their Google account.
As a result, Google announced that they would be limiting access to the necessary Chrome APIs starting on March 15, 2021.
-
Killed by Google: cardboard Google glasses:
-
@Zerosquare I was surprised it was still around. I thought they had some new system that superseded it.
Fake edit: I was right about Google Daydream, but wrong in that it was actually Daydream that got cancelled first.
Daydream was not widely adopted by consumers or developers, and in October 2019, Google announced that the Daydream View headset had been discontinued and that they would no longer certify new devices for Daydream
-
EDIT: OK, that's because they're pushing a "the browser itself does the tracking" solution:
-
A browser with FLoC enabled would collect information about its user’s browsing habits, then use that information to assign its user to a “cohort” or group.
Good fucking luck with that for non-Chrome browsers.
-
That's the obvious hole in the plot, yeah. I wonder if:
- they expect most users won't bother switching to another browser
- they plan to make their services only work well (or at all) with Chrome to keep their users captive, or
- they have another trick up their sleeve.
-
@Zerosquare said in Killed by Google:
they plan to make their services only work well (or at all) with Chrome to keep their users captive
Ahem...
@boomzilla said in Killed by Google:
"As a result, Google announced that they would be limiting access to the necessary Chrome APIs starting on March 15, 2021."
-
This post is deleted!
-
@boomzilla said in Killed by Google:
These features include “Chrome sync and Click to Call”. Essentially, users of some Chromium-based browsers could access their bookmarks, passwords, and sync data tied to their Google account.
Well, I absolutely never do any of that, so if they want to prevent other browsers from doing it, I have no objection.
-
@Zerosquare said in Killed by Google:
EDIT: OK, that's because they're pushing a "the browser itself does the tracking" solution:
After reading the rest of the article, that sounds absolutely awful. They want to take all the Orwellian behavior Google is suspected of doing and standardize it. And then propose to be the arbiter of the algorithm so
ifwhen it gets too terrible, they'll mercifully adapt it to be slightly less prone for discrimination.
Gee, no thanks.
-
Hey. Why do you think they dropped the "Don't be evil" motto?
-
@Zerosquare said in Killed by Google:
Hey. Why do you think they dropped the "Don't be evil" motto?
Didn't they just drop the "n't"?
-
-
@Zerosquare quoted in Killed by Google:
Will you take advantage or be left behind?
I'd not started to “take advantage of” AMP; I never saw the need for it. I also will not feel regret for its passing.
-
@Zerosquare for once, they killed something that people actually didn't like!
-
Google's withdawn hav my server sfrom the project and the OSF cant afford as good uf AI
-
Nevermind, I don't want to know.
-
-
Doesn't quite fit in this thread, but at the same time it does.
Edit - lots of people in this comic and not liking it:
-
@Zecc said in Killed by Google:
Not convinced that's true. I mean, in the nerd community it is, but normal people don't care.
-
Killed by Google: competition.
https://www.politico.com/news/2021/07/07/36-states-dc-sue-google-for-alleged-antitrust-violations-in-its-android-app-store-498622
-
@Zecc said in Killed by Google:
Doesn't quite fit in this thread, but at the same time it does.
Edit - lots of people in this comic and not liking it:
More on this:
I read the article for the comics, to be honest.
-
(Accidentally) killed by Google: Chrome OS devices.
Google flubbed a conditional statement in Chrome OS's Cryptohome VaultKeyset, the part of the OS that holds user encryption keys. The line should read
if (key_data_.has_value() && !key_data_->label().empty()) {
but instead of&&
—the C++ version of the "AND" operator—the bad update used a single ampersand, breaking the second half of the conditional statement.It's not clear how such an obvious, show-stopping problem like this made it into the stable release channel. Chrome OS has three testing channels that changes are supposed to go through—the "canary," "dev," and "beta" channels—with weeks of testing between releases. Somehow this bug escaped that entire process. This problem also seems like something a unit test or automated testing could have caught—not being able to log in is pretty obvious.
-
-
@Zerosquare said in Killed by Google:
Well damn, I was almost ready to make a dash that was compatible....
-
@Tsaukpaetra said in Killed by Google:
@Zerosquare said in Killed by Google:
Well damn, I was almost ready to make a dash that was compatible....
for phone screens. Ars left off a very important word there.
So you can't put your phone in a mount and run android auto on it, but a headunit would work fine.
-
@sloosecannon said in Killed by Google:
@Tsaukpaetra said in Killed by Google:
@Zerosquare said in Killed by Google:
Well damn, I was almost ready to make a dash that was compatible....
for phone screens. Ars left off a very important word there.
So you can't put your phone in a mount and run android auto on it, but a headunit would work fine.
Right, I said what I said. I have a 7 inch screen, mini PC, and other things. Just never got around to getting the harness and faceplate thing.
-