480
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 12 Mar 2025
480 points (100.0% liked)
Technology
66584 readers
3675 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 other!
- 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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
That’s not holding back browser development, that’s just holding back browser usage.
That’s definitely not the same thing.
Kind of a strange semantics argument at that point. Saying you can only build with X tools certainly impacts development. Why develop something that would never be allowed to be released?
That’s the exact argument you’re making: that X tools are the only way to develop a browser. Ignoring the entire world of other devices available.
If you are only allowed to use internal combustion engines how do you expect to get an electric car?
If you have no where to sell your product, why develop it?
We got electric cars when all we had was the internal combustion engine. What a silly metaphor.
But it’s nice to hear you admit that I was right, and that the browser could definitely still be developed. The proof, of course, is that there are dozens of web browsers out there in active development.
No you just don't understand the metaphor.
If electric cars cannot be sold, If for example they were actually illegal, then how do you sell electric cars? If
If you have to use the Safari engine for everything and the Safari engine doesn't support a particular feature, then there is no way to use that feature on iOS. You can't develop a workaround because the work around would require you to have access to arbitrary system commands, and that's not how web development works.
For example, there is absolutely no way to implement notifications on iOS without iOS support for web notifications, without that API there is no way to interface with the operating system. There is no way you can build workaround code for that.
I actually didn't mention my preference of web browser, I just commented on how obviously stupid you were being due to your being unable to decipher pretty simple comments. Interesting assumption to make though.
Sorry I wasn't granular enough for you I figured you'd get the whole thought - if I am not allowed to sell anything but ice cars ( can only use WebKit on the largest group of consumers) what would be the incentive for me to create one unless I can also afford to create a platform or brand to release them on (nobody with the capital to do this is going to make something to the benefit of the users)
That maybbe true but feel free toTell me what is then. Developers are less interested in developing for a platform with heavy restrictions. If you have some sort of alternate take on that I'd like some of whatever you are smoking.
It’s not my job to think for you. I already explained this more than once. You have trouble understanding it, have someone else explain it to you.
It has nothing to do with usage. It's a restriction that's imposed on the browser developers.
Mozilla themselves claim that this makes development harder for them.
By forcing developers to have the same limitations as their own browser, apple has made it difficult for competitors to gain an edge over safari.