Earlier quoted context omitted.
Count me in as well. I only use Google Chrome for Google meet calls, as some feature are not working on Firefox (I'm sure this has nothing to do with the fact that Google makes both chrome and meet ;)
Meet also does not work properly in Safari, each time I have a meet call I need to use Chrome, so Google might using non web standards.
The Ladybird browser project
171–180 of 293 posts
Re: The Ladybird browser project
#172I have hopes it will become a daily usable browser. A new Web engine is great. I hope Servo succeeds at this too. I would consider contributing but development is coordinated on Discord and I avoid proprietary software… [1]. It's a shame. Can't blame them though, they are doing it for fun. [1] https://drewdevault.com/2022/03/29/free-software-free-infras...
I think HN is proprietary.
That would correspond to the NonFreeNet antifeature in F-Droid [1].
They could update the code they released for good measure though [2].
Running Discord is on another level for me. I would consider accessing a Discord using a Matrix or IRC bridge.
Re: The Ladybird browser project
#173Is it just for fun or not? I think it's important to face this question, because users should not trust a just-for-fun browser with their security, and we should not look to Ladybird as a meaningful contribution towards competition in the browser space if it's just for fun. If it's just for fun, we need to temper our expectations accordingly.
"Just for fun" is precisely how Linux started: Hello everybody out there using minix - I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones.
Re: The Ladybird browser project
#174Earlier 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.
Re: The Ladybird browser project
#175Earlier quoted context omitted.
I think their C++ library is one of the reasons they can create capable software so quickly actually. They have jetisoned just a tonne of C++ nonesense and added some really nice modern features such as how they handle memory and errors. Also, you would think that having to implement EVERYTHING themselves ( they are making their own image decoders as an example -- inclding SVG ) would slow them down. However, as it i…
> they are making their own image decoders as an example -- inclding SVG Considering the vast amount of exploits that continually comes out of media decoders everywhere, this basically guarantees I will never ever use this browser.
Re: The Ladybird browser project
#176[flagged]
This mindset is why we now have countless new browsers that all run on Chromium. What's the motivation for those? Also calling the project a "waste of effort" seems a bit out of touch. Effort doesn't have to pay off in any way to be worthwhile. If the act of building is part of the motivation then taking shortcuts at building it defeats the purpose.
To compete on the actual end user experience. Most users do not care at all about the code of the project. They don't care if your layout engine code is completely unique, they care that it does layout for the sites they use correctly. Having a good browser engine to work off of lets people start delivering value to users immediately instead of having to spend a ton of time recreating the parts of a browser that users do not care about.
Re: The Ladybird browser project
#177Earlier 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.
If only Mozilla hadn’t run Firefox into the ground (effectively) we wouldn’t need to reply on Apple.
The performance improvements are nice, but trying to make a Firefox another Chromium skin irks me. Plus I still miss the official compact mode.
Re: The Ladybird browser project
#178Earlier quoted context omitted.
> 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.
We warned people that the government was snooping on everything you transmitted or received. They didn't listen or care.
Re: The Ladybird browser project
#179Love Andreas Kling and the Serentiy OS project. Hate that he's only on Twitter. Mastodon seems like the perfect fit for his audience.
I dunno, he's pretty committed to his positive utlook on things. Mastodon seems to be the far angrier place in comparison to Twitter. Twitter used to be a lot more like that, but it seems like most of the angriest people on twitter moved ot mastodon when Elon took over. It's (IMO) very pronounced and hard to avoid on Mastodon.
Re: The Ladybird browser project
#180Earlier quoted context omitted.
Counterpoint, it would be another release / packaging they would have to build and maintain, unless they find a volunteer that can do it without detracting from their core business, it's not worth the investment (to them). Anyone can set up a pipeline to distribute ISO images though, it's open source.
Sure, if that's the reason, I completely understand. However that's not the reason they stated in their FAQ. It really comes off as gatekeeping
What if the goal is to keep the relevant communication channels populated exclusively with technical users?
I've seen F/OSS projects completely overrun with support requests from non-technical users. Is it wrong to want to avoid this from the start?