1171
Brave will not add Web Integration support
(twitter.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Jul 2023
1171 points (96.4% liked)
Technology
59094 readers
3518 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
I don't like it because it's a chrome derivative. Sure, they use Chromium and can edit some things. But at the end of the day, they use the Chrome javascript engine and render the HTML/CSS however Google wants to. Therefore Google more or less defines how that browser represents the web. If Google wants to implement or not implement some web standard, Brave has to follow along whether they like it or not.
I want less power in Google'a hands, not more.
The chrome javascript engine? V8 you mean? That's used in Node, it basically powers most, if not all, of the modern web lol
Node is far from the most popular. Majority of websites run on PHP.
Hence the modern. Most modern websites nowadays don't use php anymore, at least for their FE
Laravel is modern enough. If you're talking bleeding edge web dev, that's actually on elixir with Phoenix
Not sure how you count how "modern" something is considering PHP still has new versions and cut lots of releases
People totally still just output html from PHP in modern websites, not everything is react
Good point, I had forgotten node uses v8. It's powering servers that run node, sure. Not every website uses node. Lemmy I think is rust backend and kbin uses PHP.
But I mean browser specific rendering. They all follow ECMAScript standard but there are things outside of it. In the past __proto__, a way to get an object's prototype, only worked in Spidermonkey. Or how the ECMAScript doesn't specific what order the elements in a for...in loop shows up. Today these are little minor things
They aren't particularly important right now (besides hunting weird bugs) because Google follows the standards more or less. But give Google 100% control and you will start seeing dark patterns slip into the javascript itself
The FE can, and probably, still uses node
Anyway I agree with the sentiment, I use Firefox myself (actually at work I test just against Firefox lol)