I 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?
Show HN: We launched a new web browser
171–180 of 194 posts
Re: Show HN: We launched a new web browser
#172Earlier quoted context omitted.
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.
We already have that.
Let's say I have a hosted wordpress blog with a custom domain. How do I get a static IP for it?
Re: Show HN: We launched a new web browser
#173Earlier quoted context omitted.
Why do blockchain-based name systems (or ENS specifically) make you "gag and recoil?"
Proof of stake for one, and the cult it’s built on. Shouldn’t need to be said.
Nobody can engage with your opinions if you don't express them.
Re: Show HN: We launched a new web browser
#174Earlier quoted context omitted.
> I think the ship has sailed and we won't have a new browser from scratch any time soon. I think the big mistake is that we let the HTML spec get so complicated that it's essentially become Google's platform. Although it's technically open, it certainly looks and smells like a monopoly. How do we fix it? Maybe someone could make alternate rendering engines that use Canvas and WASM?
This is a topic dear to my heart. Actually, I'm working on a first-step project to help address this very issue. It's worth reflecting on a few important points. 1. "We" didn't "let" HTML5 become anything. HTML5 reflects whatever browser makers choose to ship, which is why it's un-versioned. The attempt at an industry wide consensus building effort around what HTML should be failed (W3C), largely because it spent mos…
That's why I suggested "Canvas and WASM." It's very trivial to get a "Canvas and WASM" program running in the browser. All you need to do is plan the API inside of WASM very carefully, because...
> That means to make a competitor to HTML5 you need to go outside the browser and build new kinds of browser and document/app technology.
... the next step is to remove the HTML & Javascript adaptors, and "build new kinds of browser"s that are compatible with the WASM API in the "Canvas and WASM" hack!
In this case, the newer browser would probably perform much better than the "Canvas and WASM" hack. :)
Edit: If you read this and want to talk further, my profile has a link to my web page. You can email me or track me down on LinkedIn.
Re: Show HN: We launched a new web browser
#175it's kinda like the old google rss reader and works really really well!
Re: Show HN: We launched a new web browser
#176Congrats on your accomplishment! However, I will never use it because a browser is one of those really important information gateways that I want to be very sure is not compromised.
Your strong wording is interesting here, and I'm curious about what this is implying about how you approach security. The implication here is "not compromised by independent actors that wouldn't already be capable", right? You're delegating trust to closed source megacorp products or open-but-insanely-complex megacorp dependents (firefox/chromium babies?), all of which will naturally create a strong incentive to find…
Basically there are not enough signals here for me to believe they are life-or-death serious about it. I know it sounds dramatic, but people's finances, careers, lives, etc can be destroyed by mishandling the information that flows through the browser. They need to take it that seriously, and signal that to everyone.
Re: Show HN: We launched a new web browser
#177Earlier quoted context omitted.
Hahaha, I don't think a project as monumental as a browser deserves such dismissiveness. Let's not forget that Mozilla's full rust browser has not achieved (and never will) feature parity with safari or chrome either, and they invested far more man power and time into it. The lone effort of a handful of developers that got equally far is worthy of a mention as a "new browser" even if it's not fit for human consumptio…
Yeah I remember the first Mozilla builds in the early 2000s. They were awful. Everything crashed constantly. It was such a memory hog. fast forward twenty years and I use it on a daily basis, and I'm so happy I'm not forced to use Chrome (not to mention some abominations from the past like IE with ActiveX - and at some point such setups were mandatory in order to access some services).
Re: Show HN: We launched a new web browser
#178Earlier quoted context omitted.
> closed-source Aaaand I'm out. Still not over Opera abandoning presto. With open source there's at least a chance it can be continued by someone else.
I would also prefer to see it be open source, but I think in this context that's not the point? My parent was saying that they do not expect to see new browsers from scratch, and this is one. Aside: you could make the argument that both Chrome and Safari are only open source because they were not built from scratch.
Re: Show HN: We launched a new web browser
#179Earlier quoted context omitted.
Web browsers are the most complex codebases in existence. Firefox contains more lines of code than Linux. It would require probably 100 developers just to keep up with new features being added. Then going back and catching up on the already existing components is virtually impossible. Mozilla had a project called Servo which aimed at replacing just a small slither of Firefox and the project ran for years with a huge…
> Mozilla had a project called Servo which aimed at replacing just a small slither of Firefox and the project ran for years with a huge monetary investment and eventually was canceled. Haven't some parts of it been integrated in Firefox? The project does still seem to go on, although outside of Mozilla: https://github.com/servo/servo
Re: Show HN: We launched a new web browser
#180Earlier quoted context omitted.
> I think the ship has sailed and we won't have a new browser from scratch any time soon. I think the big mistake is that we let the HTML spec get so complicated that it's essentially become Google's platform. Although it's technically open, it certainly looks and smells like a monopoly. How do we fix it? Maybe someone could make alternate rendering engines that use Canvas and WASM?
This is a topic dear to my heart. Actually, I'm working on a first-step project to help address this very issue. It's worth reflecting on a few important points. 1. "We" didn't "let" HTML5 become anything. HTML5 reflects whatever browser makers choose to ship, which is why it's un-versioned. The attempt at an industry wide consensus building effort around what HTML should be failed (W3C), largely because it spent mos…
Interesting. Can you elaborate on what some of those academic dreams are/were that derailed things? Did they end up in the spec or were they just bikeshedded to death?