News for hackers. Stuff that matters.
Re:iCab: Alternative Browser for macOS by Wowfunhappy on Sunday April 19, 2020 @10:47PM (#22920688)
Presumably because doing anything else is just impossible in this day and age.

There are only two-and-a-half actively-maintained rendering engines in existence: Gecko, and Chromium/Webkit. There's a reason for that. A single person isn't going to be able to maintain their own.

Re:iCab: Alternative Browser for macOS by userbinator on Sunday April 19, 2020 @11:03PM (#22920767)
There's also Netsurf, Dillo, as well as Links and the rest of the text-based ones.

The monopoly should definitely be fought.

Re:iCab: Alternative Browser for macOS by Wowfunhappy on Monday April 20, 2020 @08:22AM (#22923206)
Are those actually usable as a primary/only browser in 2020?

Unfortunately, I think the best way to fight the monopoly at this point is to use Firefox. As bad as 2½ browsers is, I'd much rather have 2½ than 1½.

(On desktop, webkit is also fine, they need marketshare there. Anything that isn't Chromium.)

Re:iCab: Alternative Browser for macOS by tapoxi on Monday April 20, 2020 @12:16PM (#22925294)
I still don't understand the "fight the monopoly" argument. Should I use Windows Server or FreeBSD to fight the "Linux dominance" monopoly?
Re:iCab: Alternative Browser for macOS by Wowfunhappy on Monday April 20, 2020 @12:28PM (#22925433)
The problem is that, the web isn't really an open standard if there's only one implementation of the standard. The standard just becomes "whatever works in Chromium".

It also gives Google the power to unilaterally add or remove anything from the standard as they think will benefit Google. Sure, Microsoft or Brave could choose not to go along with the change, but Microsoft doesn't want to spend resources maintaining a fork, so they're much more likely go go along with whatever Google does.

Re:iCab: Alternative Browser for macOS by alexisread on Monday April 20, 2020 @05:39AM (#22922437)
I think the main problem is that the DOM and javascript are just too large for one person / small team to maintain, so you get feature lag. I'm hoping webassembly and canvas are a small enough target to overcome this, but if we were to look at what could have been, Scheme and something like Tk would've been better
Re:iCab: Alternative Browser for macOS by NaOH on Sunday April 19, 2020 @11:06PM (#22920778)
And this is a developer who also maintains iOS/iPadOS versions along with the Mac version, so not using Webkit on Mac would mean having to maintain and develop for two rendering engines since Apple mobile OSes require using Webkit.
Re:iCab: Alternative Browser for macOS by Wowfunhappy on Sunday April 19, 2020 @11:08PM (#22920794)
Well, you'd still only be maintaining one, since Apple maintains webkit for you.
Re:iCab: Alternative Browser for macOS by NaOH on Sunday April 19, 2020 @11:11PM (#22920807)
True. Bad writing on my part.
Re:iCab: Alternative Browser for macOS by why_only_15 on Sunday April 19, 2020 @11:41PM (#22920913)
Think the chromium one is called "blink"
Re:iCab: Alternative Browser for macOS by Wowfunhappy on Monday April 20, 2020 @09:52AM (#22923791)
It absolutely is and I actually debated which term I should use in my post. Everyone seems to have settled on using "Chromium" to describe browsers based on Google's engine, and I want to use the word that the most people will be familiar with.