121–130 of 280 posts
Earlier quoted context omitted.
So? You should still develop for. Why? For this whole reason. What does it matter? You should target all audiences. Why not?
> Why not? Because it's extra work.
Earlier quoted context omitted.
Oh yes, a MacOS like design but open with Unix, that would be amazing!
macOS is unix... And he seems to not want macOS type design. Unless you mean System 8/9.
Earlier quoted context omitted.
I agree (apart from the popular hate on Firefox). Ladybird is promising and has a much bigger chance to make an impact than SerenityOS. But it's a bit disappointing to see that it's still pretty much a one-man project. Especially to have a chance to get close to the performance of Chrome and Firefox, it will need a large investment. The amount of engineering resources poured into just making JavaScript fast is mind-n…
On recent hardware, how much "performance" do we really need? Wouldn't almost any compliant browser be basically good enough?
Earlier quoted context omitted.
KHTML+KJS released in 1998, via WebKit from 2001, in 2008 it gained the Chrome name, but the code has more than 20 years of legacy.
> KHTML+KJS released in 1998, via WebKit from 2001, in 2008 it gained the Chrome name, but the code has more than 20 years of legacy. Why do you want the oldest code to be less than 20 years old? Why is that "nice"?
Earlier quoted context omitted.
I think the Firefox hate is completely justified. At this point the only positive thing about Firefox is that "at least it's not Chrome".
As a Firefox user, this exactly. The amount of things that now need to be toggled off on a new install are approaching Windows “telemetry” levels: disable sponsored shortcuts on homepage, disable experimental “Studies”, sponsored suggestions in search bar, “suggested extensions”, Pocket, and the list goes on. I really need to look into a privacy friendly fork of FF..
I'd love to make the jump too, just that I rely upon FF sync too much. It's handy getting your bookmarks and other details on mobile devices. The other forks look to be desktop only.
Earlier quoted context omitted.
> KHTML+KJS released in 1998, via WebKit from 2001, in 2008 it gained the Chrome name, but the code has more than 20 years of legacy. Why do you want the oldest code to be less than 20 years old? Why is that "nice"?
Because 20 years is like half the history of modern computing. A lot has changed in a small amount of time
Earlier quoted context omitted.
Because 20 years is like half the history of modern computing. A lot has changed in a small amount of time
So what? Code doesn't rust.
Earlier quoted context omitted.
There’s very little WebKit / KHTML code left in Chrome.
There's very little NT 3.1 code left in Windows, but it's still clear how old that project is.
...ok the /bin /usr/bin nonsense still stays after decades, maybe you have a point