111–120 of 293 posts
Great to see some competition still alive in browser engine development. See also Servo (previously part of Mozilla) https://servo.org/ - that and Ladybird are still very underdeveloped compared to every day browsers. It's a huge shame that there are no nightly builds of ladybird to try out but I assume that's because they just don't want the bug reports (if everything doesn't work it's pointless getting random bugs…
Earlier quoted context omitted.
This is where Apple'grip on the iOS browser engine choice paradoxically comes in clutch. It is conceptually despicable, especially for devs, but it prevents Google from completely running the show. Now the European Union is coming after Apple without trying to rein in Google's influence... This seems short-sighted.
The current dispute between the EU and Apple has nothing to do with Safari though and is about the Apple store, not sure how that's relevant?
> In addition, apps that use alternative browser engines — other than Apple’s WebKit — may negatively affect the user experience, including impacts to system performance and battery life.
https://www.apple.com/newsroom/2024/01/apple-announces-chang...
Great to see some competition still alive in browser engine development. See also Servo (previously part of Mozilla) https://servo.org/ - that and Ladybird are still very underdeveloped compared to every day browsers. It's a huge shame that there are no nightly builds of ladybird to try out but I assume that's because they just don't want the bug reports (if everything doesn't work it's pointless getting random bugs…
Don't forget WebKit. It leads to project such as https://surf.suckless.org
(agreed, it is a credible alternative to Blink's dominance)
Earlier quoted context omitted.
See https://awesomekling.substack.com/p/welcoming-shopify-as-a-l... Discussion: https://news.ycombinator.com/item?id=36502433 (246 points | 7 months ago | 66 comments)
We need more companies like Shopify, that actually share some of their revenue with open source projects they benefit from (or even, as in this case, projects that they don't directly benefit from)! But I'm afraid the current financial situation will lead to less, not more, of that...
Step 2: ????
Step 3: Profit.
Earlier quoted context omitted.
It is not any easier, because we still have a monopoly running the show, only it's not called Microsoft anymore. If anyone threatens Google position, they can literally throw money at the problem, invent some overcomplicated standard, implement it in Blink, and have the competition chase them. It doesn't need to go through W3C either, if it works in Chrome, all web developers will adopt it and any smaller engine will…
This is where Apple'grip on the iOS browser engine choice paradoxically comes in clutch. It is conceptually despicable, especially for devs, but it prevents Google from completely running the show. Now the European Union is coming after Apple without trying to rein in Google's influence... This seems short-sighted.
At the very least, if the EU really wants to limit the tech giants' grip on the web, it needs to fund independent open source web engine development handsomely; their pockets are more than deep enough and projects like ladybird and servo can use the extra resources.
"Where are the ISO images?
There are no ISO images. This project does not cater to non-technical users."
This comes off as really abrasive. Wanting an ISO image to quickly test this out is not an indicator of someones technical ability.
I'm sorry I don't want to boot up a linux vm, install a lot of development packages and then build my own boot image just to try this out.
It's been so inspiring to see him and his crew of hackers build a new, independent browser from scratch. I must admit I didn't think it was possible on this small scale in terms of man hours and funding. However, the thought has also crossed my mind if we're finally seeing fruits of browsers being better standardized on "95%"+ of the popular features -- and if writing a browser today is in fact easier than both writi…
It is not any easier, because we still have a monopoly running the show, only it's not called Microsoft anymore. If anyone threatens Google position, they can literally throw money at the problem, invent some overcomplicated standard, implement it in Blink, and have the competition chase them. It doesn't need to go through W3C either, if it works in Chrome, all web developers will adopt it and any smaller engine will…
This is why we, tech nerds who understand the problem, must resist monopolies: object to using such APIs. Chrome wouldn't be in quite this position if, instead of embracing the monopolist, more techies had warned their non-techy friends and family away from it, like they did with IE.
Earlier quoted context omitted.
> No, that feels like living in an imperfect world and trying to make it better. To improve something, you generally need to be part of it and its imperfections. Right, but that's the hypocrisy, no? He's being rude about people who use github, or post an article on HN, but surely most of those guys are doing just the above. When is it OK to use non-free software and when not? Maybe there's a dividing line you can dra…
Are you talking about Drew or "those guys", whoever they are? Let's focus on Drew. I've not seen him mention HN, which by the way doesn't require running non-free software, and he literally runs a free software competitor to GitHub. I've not seen him be rude to people using GitHub. He certainly strongly criticizes them. I assume he uses GitHub to communicate with projects hosted there. If he does, I don't think he co…
Earlier quoted context omitted.
It is not any easier, because we still have a monopoly running the show, only it's not called Microsoft anymore. If anyone threatens Google position, they can literally throw money at the problem, invent some overcomplicated standard, implement it in Blink, and have the competition chase them. It doesn't need to go through W3C either, if it works in Chrome, all web developers will adopt it and any smaller engine will…
This is where Apple'grip on the iOS browser engine choice paradoxically comes in clutch. It is conceptually despicable, especially for devs, but it prevents Google from completely running the show. Now the European Union is coming after Apple without trying to rein in Google's influence... This seems short-sighted.
Earlier quoted context omitted.
It is not any easier, because we still have a monopoly running the show, only it's not called Microsoft anymore. If anyone threatens Google position, they can literally throw money at the problem, invent some overcomplicated standard, implement it in Blink, and have the competition chase them. It doesn't need to go through W3C either, if it works in Chrome, all web developers will adopt it and any smaller engine will…
> if it works in Chrome, all web developers will adopt it This is why we, tech nerds who understand the problem, must resist monopolies: object to using such APIs. Chrome wouldn't be in quite this position if, instead of embracing the monopolist, more techies had warned their non-techy friends and family away from it, like they did with IE.
Elsewhere in this comment section someone literally said they use Chrome because Reddit does not work in Firefox, which is utter nonsense.