Spyke
infosec.pub

If your website only works with Chrome, it’s not a website. It’s a Chrome site.

You didn’t design for the web. You designed for Chrome.

311
lemmy.one

Fuck chrome. Such a dogshit unoptimized spyware browser that now disables ad-blocking plugins

143
Lenareply
gregtech.eu

I agree that Chrome fucking sucks, but it's disingenuous to call it unoptimized. Chrome and chromium-based browsers are as fast as or faster than Firefox. Although I agree that manifest V3 is horrible to the web as a whole and shouldn't have been created.

38

Single browser open? Lemme fire up a dozen .exe processes there.....

5
Lenareply
gregtech.eu

Have you used chrome or chromium in the past few years? Source?

-5

I was exaggerating to make a point. But one of the main reasons why I switched to Firefox (about a year ago) was because it was eating up so much of my CPU.

2

Their plugins were fucked from the beginning. You never had control of your extensions.

7
spookexreply
lemmy.world

The problem for me is that the built-in translator is too convenient

-27
IronKrillreply
lemmy.ca

*For a limited set of languages. Until they add Japanese I won't be getting much use from it, sadly.

5

I use 10ten (previously Rikuchamp) for Japanese. I don't think it does full translation, but it gives thorough dictionary lookups (from WWWJDIC) as mouseover tooltips. Very useful if you're trying to learn the language, but maybe not so much if you just want to read stuff quickly. I think it's now available for every major browser, but I mostly use it on FF.

2

Safari also has it built in. This person is just saying shit to say shit I guess.

9
spookexreply
lemmy.world

AFAIK the built-in translator doesn't support Japanese, which is 99% of translation I need and the extension (which is what is was trying to use before) either requires you to select the text that you want to translate one-by-one or run the whole page through translate.google.com, which doesn't work with any page that requires an account to access or triggers ddos protection on some others.

0

Yeah, I think Firefox's translation feature is technically still in beta.

2
sh.itjust.works

Chrome is awful in nearly every way one can measure a browser. Anyone still using this as they're main driver in 2025 is technologically challenged.

31
borarireply
lemmy.dbzer0.com

It’s wild to see Chrome going from the browser to use if you had any tech sense whatsoever to being universally derided.

33
morrowindreply
lemmy.ml

Universally derided

lol try looking outside lemmy. 90% of people still just use it and don't care

7

At least in my country, google is going balls-to-the-walls mode with the chrome psyop. Like every third ad on youtube is an ad for chrome. And if you're a little older, you'll remember their countless other ad campaigns that propelled chrome into the mainstream. The only reason so many people use chrome is because they're brainwashed into it.

2
Zagorathreply
aussie.zone

That's not necessarily true. Circa 2016–17 I frequented a website that worked in Chrome but not Firefox. This was due to Firefox at the time not implementing web standards that Chrome did. Firefox only got around to it in 2019. So naturally, the developer of the site was telling people to use Chrome.

-12
lemmy.world

I don't know the history of column span but the reason Firefox was "behind" on standards was because Google was pushing new standards through committee faster than competing browsers could keep up. Google would implement a new feature, offer it as a free standard, then get it through the committee. Because Google already had it in their browser, they were already compliant while Firefox had to scramble.

It was Google doing their variation of "embrace, extend, extinguish"

It got so bad that not even Microsoft had the resources to keep up. They said as much when they said they were adopting Chromium as their engine.

92
Zagorathreply
aussie.zone

Google was actually later to implement this particular standard than Edge and Safari, at least according to MDN. And I believe this was before Chredge.

8
Eirireply
lemmy.ca

I'm gonna be honest, if they used a feature that wasn't ready for prime time, it's still on them.

24
Zagorathreply
aussie.zone

It got added because it worked extremely well on browsers that implemented it, and it solved a problem that was needed on the site in question, which was very difficult to solve otherwise. I can't blame a site for using an open standard that works for a majority of its users and which makes the development effort significantly less.

-4
lemmy.ml

This was due to Firefox at the time not implementing web standards that Chrome did.

Uhm, yeah, that's what browsers do. There are somewhere about 150 web standards and some are hard requirement while others are soft. Blink has some implemented that Webkit hasn't but Gecko has and that's true for all three. Same for browsers.

Btw, the one with the most implemented standards is QtWebkit by far. It's still slower tho.

5
Zagorathreply
aussie.zone

Yeah? I'm not saying there's anything wrong with that. I'm saying it's bullshit to say a developer has done a crap job when one browser doesn't implement a web standard that is perfect tailor-made for their site's use case.

4

Still a bad job tho, if his implementation requires things that aren't common and has no workarounds in place.

2

If your job is to make websites and you make sites that don’t work on a browser that has over 100 million users you’re not doing your job.

0
sh.itjust.works

I like this template so much better than the Spider-Man one that people constantly use backwards.

83
lemmy.ca

In the movie the glasses let the wearer see the truth. This template is often used backwards but it's correct in this case.

102
cobysevreply
lemmy.world

"They Live!" A guy finds some strange sunglasses that lets him see the subliminal messages hidden in all our print and media and advertisements. He can also see aliens walking amongst the population, disguised as regular humans!

Turns out, Earth had been invaded by aliens long ago and they've been keeping us under their control with subliminal messages for decades.

45
bluewingreply
lemm.ee

Perhaps the best line ever uttered in any movie. Rowdy Roddy Piper maybe a B movie actor at best, but he was meant to play that role in that movie.

I have often wondered: Who wore a kilt best. Bruce Campbell or Rowdy Roddy Piper. Campbell was a Sharp Dressed Man in his kilt for sure. But Piper wrestled in one for years-- it was his trade mark garb.

11
lemmy.world

My website only works with Chrome, but it has to be a specific old version of it. And you also need to install some extensions. Very specific versions of these extensions. Few of them already removed from the store due to security backdoors.

I have a Docker image you can use to run Chrome though.

77
xiareply
lemmy.sdf.org

What version of Docker do I need to run your container?

36
AeonFelisreply
lemmy.world

You'll need my fork of docker, and you'll need to apply a patch.

46

At that point, just release your website as an electron app.

14
lemm.ee

When developing photon I always end up with more issues on chrome browsers than firefox. and half of those are because of its god awful scrollbar. Please use an overlay scrollbar instead of shifting the stupid page around, chrome.

37

Greatest format ever. I present you with the Demi-God of memes award for best use of THEY LIVE if you originated the template. If you did not originate you get the cool assed dude award for sharing. Many thanks.

15
lemmy.world

I’m going to have to go down the rabbit hole of making my own website soon. Just curious but would there be an easy way to show a pop up just to people using chrome?

No reason in particular… 😏

15
lemmy.world

lol i did something like what i assume your goal is on my neocities when i detect !!window.chrome === true

18
lemmy.world

It's a handy way to convert any value to a Boolean. If window.chrome is defined and done non-empty value, double negation turns it into just true.

12
Fareshreply
lemmy.ml

I've been wondering why not window.chrome == true or Boolean(window.chrome), but it turns out that the former doesn't work and that == has essentially no use unless you remember some completely arbitrary rules, and that JS developers would complain that the latter is too long given the fact that I've seen javascript code using !0 for true and !1 for false, instead of just true and false because they can save 2 to 3 characters that way.

6

== has essentially no use unless you remember some completely arbitrary rules

If you make sure the types match, like by explicitly converting things on the same line on that example, then you can use it just like if it was ===.

In fact, there are people that defend that if your code behaves differently when you switch those two operators, your code is wrong. (Personally, I defend that JS it a pile of dogshit, and you should avoid going to dig there.)

6
ivnreply
jlai.lu

I've never seen the !0 and !1, it is dumb and indicates either young or terrible devs.

Boolean(window.chrome) is the best, !!window.chrome is good, no need to test if it's equal to true if you make it a boolean beforehand.

5

Not sure if serious, but there's a million ways to do this, some that require importing thousands of lines of code and none of which are guaranteed to work in all possible circumstances. But here's a simple one.

15

User agents cannot be fully trusted anymore since every browser puts every possible word in it so they are not excluded by anything.

6

Well, some browsers have made User-Agent strings useless. Technically, it's like this:

Firefox: "Mozilla based browser, Gecko engine, Firefox."

Chromium: "We're totally a Mozilla based browser we swear. Also KHTML, which is like Gecko basically. I guess also a bit like WebKit. Has anyone ever heard of those? No? OK. Fine, here's some actual information then..."

1

Is that http2? Cause http2 allows for reuse of a connection for additional requests.

This caught me out with envoy reverse proxy doing a few subdomains using a wildcard cert.
The browser would reuse the connection cause the cert authority and IP was the same, but envoy couldn't figure out how to route the request correctly. Absolute head scratcher!

8