this post was submitted on 27 Nov 2023
1727 points (97.6% liked)
Technology
59282 readers
4451 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's weird how lots of devs treat chrome as a standard, even though when developing I have a lot more issues with Chrome browsers than Firefox browsers
I haven't had any issues with browser compatibility since IE. Occasionally Safari might have some CSS issue, but it's been probably 10 years since I had any major issues with browser compatibility. Html 5 and CSS 3 tend to work across all browsers without issue.
There are some niche features Mozilla refuses to accept like WebSerial and WebMIDI, but they're starting to come around on them.
Across all two of them.
I would really like to see how broken the web would be if someone in theory create a new complete implementation of the basic standards.
Three: Chrome and friends, Safari, Firefox
Well the market share is the whole story when it comes figuring out whats the standard
I think devs go chrome first and then adapt the site to firefox.
Because Chrome rendering and dev tools are effetely superior to Firefox. That's why.
I'd disagree on Dev tools. Both are really great and useful. What I'd say is that Firefox may have less support for external debugging, but that's more others choosing not to do Firefox debugging