Yet Another Chromium Fork. In a way, it's almost a shame Chrome was open sourced through Chromium. Maybe if it weren't, we'd have a healthier, more diverse browser ecosystem.
Show HN: We launched a new web browser
51–60 of 194 posts
Re: Show HN: We launched a new web browser
#52Yet Another Chromium Fork. In a way, it's almost a shame Chrome was open sourced through Chromium. Maybe if it weren't, we'd have a healthier, more diverse browser ecosystem.
As much as I lament the same thing. I think it’s more likely we’d just have nothing.
Re: Show HN: We launched a new web browser
#53I have a question about blockchain DNS's. This might be the time to ask! There is a centralization aspect in any DNS, blockchain or otherwise in that, literally to be useful, there needs to be consensus about which chain operators own which .{name} extensions for a given name. Which makes financial incentive for say an investor to 'bribe' browsers into using their DNS, which then charges money to end users, which er.…
If you are going to use an immemorable hash instead of a memorable name, why not use IP directly?
Re: Show HN: We launched a new web browser
#54Yet Another Chromium Fork. In a way, it's almost a shame Chrome was open sourced through Chromium. Maybe if it weren't, we'd have a healthier, more diverse browser ecosystem.
Writing a browser from scratch is hard.
Re: Show HN: We launched a new web browser
#55I have a question about blockchain DNS's. This might be the time to ask! There is a centralization aspect in any DNS, blockchain or otherwise in that, literally to be useful, there needs to be consensus about which chain operators own which .{name} extensions for a given name. Which makes financial incentive for say an investor to 'bribe' browsers into using their DNS, which then charges money to end users, which er.…
we already have "nameless" IP addresses, in which DNS is built on top of it as abstraction. using SHA256 is no better that using IPv6 IMO
There is probably a decent case to be made for having an indirection layer above IP addresses, even if they are as meaningless and unmemorizable as a hash: for portability (IP addresses are tied to the host infra provider), load balancing, etc.
Re: Show HN: We launched a new web browser
#56Yet Another Chromium Fork. In a way, it's almost a shame Chrome was open sourced through Chromium. Maybe if it weren't, we'd have a healthier, more diverse browser ecosystem.
As much as I lament the same thing. I think it’s more likely we’d just have nothing.
Maybe. There's no way to tell, of course.
Re: Show HN: We launched a new web browser
#57Yet Another Chromium Fork. In a way, it's almost a shame Chrome was open sourced through Chromium. Maybe if it weren't, we'd have a healthier, more diverse browser ecosystem.
Writing a browser from scratch is hard.
Hard is underselling it. At this point it’s borderline impossible. It’s unlikely we will ever see a new browser.
Re: Show HN: We launched a new web browser
#58Earlier quoted context omitted.
> Why are you swallowing "error" from invoking the "reall" tool? That seems like a great way to make contributors really frustrated Glad you're looking at the code! There's still some refactoring needed for butil. It will get more polished soon ;) > This trend of "I'm going to invent some build tool because there are not enough build tools in the world" is evidently leaking out of the node ecosystem butil applies str…
It may be "statically typed" but from a consumer's PoV, 100% opaque. My first question when trying to build any project is "what is this going to do to my machine" and with some golang based build system, you're asking for a lot of trust on two different levels: 1. go install something (so now I need to read its source) 2. oh, turns out it actually delegates to an entirely separate binary that I now need to separatel…
> but I wanted to make sure you were choosing the contribution path you wanted to build upon
> that goes double because it already has tight coupling to GN due to Chromium
Interesting i'll experiment with moving this to GN. I have more high priority things to deal with atm but i'll get to that.
Re: Show HN: We launched a new web browser
#59Re: Show HN: We launched a new web browser
#60DANE is really interesting. Wider adoption would be good for everyone I think. I’m going to have to give this a try.
The problem with DANE is that it doesn't move us away from CAs, it just conflates the role of running a DNS zone with also being a CA. And even CAs may be problematic, the entities running DNS zones are often more so.