Earlier quoted context omitted.
Chrome won because it was more performant (read: only point of interest for Joe Average) and it was modern and cool (read: only point of interest for nerds). Firefox failed because it stagnated on performance and code quality (read: memory leaks for daaaaaaaaays) and ultimately because Mozilla was corrupted by Mitchell Baker and still is to this very day driving away nerds and engineers by the truckload. Lest we forg…
Thanks for the unexpected laugh at the end. Maybe there is a typo in that imaginary world: "Applestantinople". But maybe it is as intended :)
"Begin disabling installed extensions still using Manifest V2 in Chrome stable"
361–370 of 490 posts
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#362Earlier quoted context omitted.
IMO they are still not as good although they have improved. I just develop in chrome and use Firefox for everything else.
I use a little `chrome-new` script to develop (and sometimes take video calls or use buggy apps) against a totally clean fresh Chrome profile, then I use Firefox with uBlock Origin and uMatrix for daily driving. #!/bin/sh [ -z $CHROME ] && CHROME=chromium TMPDIR=$(mktemp -d /dev/shm/chrome-XXXXX) $CHROME --user-data-dir=$TMPDIR --no-first-run --no-default-browser-check "$@" rm -rf $TMPDIR The first line lets me overr…
`export HOME=$TMPDIR chrome `
Will make chrome think that $TMPDIR is $HOME. Keep in mind that means your downloads for example would also be deleted after the rm -rf
This works for most other software too
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#363Earlier quoted context omitted.
I'm not convinced that this is a good idea, but I don't think that's the reason; don't all your dlls come from the internet?
My comment was sarcasm. The difference here is are you downloading a random dll from a well known source or from http://free-vpn-fast-internet.dwnloadfree.ru/free-chrome-vpn... ? My mom isn't going to know the difference and will click the big green DOWNLOAD NOW button blindly.
So here's the dilemma:
- People are afraid of plugins "in the wild". People need some kind of centralized, managed "extension store"
- People complains about store policy like Manifest V3
I don't think a single mechanism can please both crowds.
And what's worse? Google doesn't actually care about the security of the the "store". Scam extensions are everywhere. The "audit process" are minimal, customer/developer service are essentially none, and Google only enforce rules that affect their ads business.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#364There's gonna be a new browser wars. How exciting! Time to do your part. Switch to ladybird! (Insert imaginary we want you for the army poster here)
I realize I'm about to post something that sounds like the most generic HN slop comments... but, considering it's why Mozilla initially made a whole new language in the first place, I hope most can look past what fanatics would normally say and focus on the scenario: I was ecstatic about Ladybird from a "fun NIH project" perspective but once it became "serious" and had a cross-platform daily-driver long term focus it…
My reason for learning Rust in the first place was trying to contribute to the servo engine. But then, Mozilla happened. My hope for servo continues, but it won't go anywhere if it stays in the limbo it has been in after Mozilla ditched it as a project. We need a real browser project, with a full UI/UX and everything, until people take it serious as a base to fork off.
The problem with reality is that almost all software is still built on C. Kernels, userspace APIs, libraries, everything. I just wish that we would've gotten something like C ABIs, but with memory safety and VM-to-VM communication in mind, e.g. for Rust and Go, along the way. WebASM / WASI somehow got there, at least in that direction. But it's never seen as a shared object or dll replacement, and always is just a compile target and nothing more - even when the potential is there.
Something like that would solve so many problems that all kinds of programming language are trying to solve by themselves, over and over again.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#365Earlier quoted context omitted.
Inject dll's from the internet right into the browser. Yes, let's!
I'm not convinced that this is a good idea, but I don't think that's the reason; don't all your dlls come from the internet?
Either from the "wild" internet or manifest v3 intranet.
Or can we do better? For example, a community can maintain an opensource "network control" DLL that allow users to enable/disable tamperscript-like firewall rules from uBlock or such.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#366Can't we avoid the Manifest bullshit altogether? I remember how IE plugins roles: just dll inject into the process.
Chrome tries to block the majority of third-party software from injecting code into it: https://blog.chromium.org/2017/11/reducing-chrome-crashes-ca...
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#367Hopefully this is the inflection point for Chrome. Despite all their made-up "security" reasons, everyone knows this is solely about making adblock less effective. For many users, adblock is what makes chrome bearable - and if they make it unbearable, then those users will leave. Slowly but surely. Google seems much too sure of itself making this change. I hope their arrogance pays off just the same as Microsoft's di…
Agreed on hoping this is the inflection point, but only partial agreement that it's about adblock. For sure Google wants adblock to die, but I think it goes even deeper than that. I think it's part of a much bigger trend in tech in general but also in Google: Removing user control. When you look at the "security" things they are doing, many of them have a common philosophy underpinning them that the user (aka device…
Punching down into a brutal labor environment instead of punching up into a Congress which was blatently bought off to foment this outcome? Odd choice.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#368I've finally switched (back) to firefox today. I switched from firefox to chrome for their superior devtools a few years back, but hopefully firefox has had time to catch up. Everything old is new again!
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#369Earlier quoted context omitted.
I realize I'm about to post something that sounds like the most generic HN slop comments... but, considering it's why Mozilla initially made a whole new language in the first place, I hope most can look past what fanatics would normally say and focus on the scenario: I was ecstatic about Ladybird from a "fun NIH project" perspective but once it became "serious" and had a cross-platform daily-driver long term focus it…
I agree with you there, on all parts. My reason for learning Rust in the first place was trying to contribute to the servo engine. But then, Mozilla happened. My hope for servo continues, but it won't go anywhere if it stays in the limbo it has been in after Mozilla ditched it as a project. We need a real browser project, with a full UI/UX and everything, until people take it serious as a base to fork off. The proble…
Cookie invaders gave me a good shock too :D. As well as the random "bloop" sounds. 10/10
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#370Earlier quoted context omitted.
I agree with you there, on all parts. My reason for learning Rust in the first place was trying to contribute to the servo engine. But then, Mozilla happened. My hope for servo continues, but it won't go anywhere if it stays in the limbo it has been in after Mozilla ditched it as a project. We need a real browser project, with a full UI/UX and everything, until people take it serious as a base to fork off. The proble…
Your personal site is awesome by the way! Though I got too excited about the CV "challenge" until I read on GitHub it really is just a random password you hand out to people and not a "find the secret password somewhere and trigger its" somewhere :p. Cookie invaders gave me a good shock too :D. As well as the random "bloop" sounds. 10/10
PS: The crypto challenge is related to the song that the avatar is humming :)