The largest money-printing UI element ever made
blog.jim-nielsen.com
blog.jim-nielsen.com
Though we treat small projects far worse because we don't even have the expectation that a large corporate project like Swift gives us individual attention, yet we entitle ourselves to the attention of a free open source volunteer project and then make a loud stink when we don't get it.
Well this seems like the hard part. I think it is actually not easy to get 1% market share, because if you are good enough to hit 1% you are likely to overshoot 1% by a lot, and if you aren’t good enough to make it past 1% you probably won’t make it to 1%. And obviously creating a browser that is good enough to overshoot 1% by a lot is very difficult.
The companies who actually have 1% of a market (for a sustained period of time) are like really weird edge cases.
For selling the search preference it works even better because it instantly adds a bit of targeting information.
Safari can demand such a large price due to the value of their traffic. Size and demographic factors of mobile Safari users really dominates here.
Firefox would probably be worth less than 1/10th of the $400m stated here if Google wasn't constantly looking for ways to 'support' them. It is an open secret that Google actively makes decisions affecting Firefox based on how they believe regulators will view those decisions re: Chrome monopolistic behavior. I have heard direct first-hand accounts of meetings specifically about how to make sure Firefox remains somewhat relevant in the market to counter any regulators that may come knocking. The cash injection is one major factor to make sure they stick around as an 'alternative'
Isn't this what Opera (3% marketshare) and Vivaldi (unknown% since they use Chrome's user-agent) are doing? And yet to make a browser that's good enough to capture this "small" chunk of market share, Opera needs >600 employees, and Vivaldi >50.
it's a victim of "all the ways for all the people", and it can't do either very well.
The optimal middle ground for me was the separation between search query bar and URL bar.
And why did we combine the two? Well, it was to reduce screen clutter and combine features so that we could make room for....
making the URL bar longer, generally far longer than any sensibly human-readable URL. Brilliant!
(the REAL reason was because Chrome wanted to shovel people into Google Search as promptly as possible, and that started a Stupid Browser Trend that firefox got suckered into following.)
The intent was there would be other operators and ways of specifying some sort of resolving agent. It was a pretty interesting idea but Microsoft destroyed internet technology competition for the next 10 years and the rest was lost as the next time someone picked up basic web technology it was a search engine.
On the semantic web thing, in the end, it turned out URLs are useful for everyone — at the very least because a URL is something you can share with other people and be sure they'd reliably end up seeing the exact resource you want to direct them to. Same can not be said about anything that involves web searching. Search results move around all the time for a million different reasons.
I think it was called Ubiquity?
https://web.archive.org/web/20130607000755/http://apple.com/...
Here's a video of IE5 on Windows 98, at 0:45 one of the dropdown suggestions is "search for ...": https://youtu.be/K1OyEMsF9mc?t=45
started with ISP selling your mistyped dns queries to google or whichever search engine they could sign a deal.
from there there was a race to capture as much mistyped domains until google had the end-game idea to pay Firefox to send non-standards domains to google directly, not even wait for it to fail dns resolution.
when later google launched Chrome, initially as a cost saving for the firefox deal, they dialed the dns to search hack so aggressively that they broke the internet (search for chrome type ahead incident).
all search engines (called portals at some point in time) goal was to be the dns replacement. AOL had "keywords" which they advertised heavily in their tv channels like TNT ("we will be back with Terminator. see more at Terminator keyword on AOL")
This is mistaken; Google has been paying to be the default in Firefox since long before Chrome popularized the idea of merging the URL bar and search bar (which, thankfully, you can still turn off in Firefox; I'd prefer not to render my URL bar useless for searching my history).
they darkpatterned the world into using AOL Keywords.
With search suggestions on (the default), they get that even for FF users.
Not only that, but every GET argument on every page is sent to Google as well, since they are perhaps search terms - so as you type your content is being sent; You can imagine the value even BEFORE getting to the fact that it generates more searches.
Which is a shame, since I used to use the URL bar to search my browsing history and the Search bar to search the net, and the whole UI was so much improved, even ignoring all the times I accidentally am sent to a search results page I didn't want.
I am not sure about FF and have no time to test it now.
What would HN folk love in a browser?
A setting to completely disable support for media elements per-origin would be nice. Not this "we try to determine whether a video is eligible for autoplaying" bullshit. I want an "I wasn't asking" approach of the browser literally treating <video> and <audio> as unknown tags when this setting is off.
Native support for Flash via Ruffle would also be nice.
If it's a mobile browser, I really, REALLY want a setting to just completely annihilate all the PWA stuff. No, I don't want to add this random news website to my home screen, thank you very much.
More broadly, I want most of the "progress" of the web platform undone. Sure, new CSS features, like flexbox and grid, are nice. But all those new JS APIs that (try to) turn a hypertext document viewer into a (terrible) operating system? No thanks. I want my clear boundary between the "document" and the "application" back, hence the Flash thing.
Maybe it's no longer possible due to all the click hijacking introduced by web2.