I made it to "Rebranding and the early days of Space Browser" and stopped reading. Why? The article is autobiographical without establishing enough context to keep me interested in you. (In other cases, if you or your product was well known, something autobiographical without establishing context is okay.)
BTW: It's worth trying to disambiguate, early on, if you're building your own HTML rendering engine, or just reusing something else.
Because a browser has so many features at this point that it basically contains an operating system. So to duplicate that its just necessary to start with some existing browser and tweak it.
Out of the thousands of features that enable me to browse across diverse websites, what percentage of those features did you implement in your "new" browser?
What does it actually do that is different from WebKit?
However, listing this as the only difference when asked make it sound like you're selling "spaces" as only a slight performance improvement and nothing else.
However, that aside, it makes no difference whether you have a window, tab, or "space".
- Memory leaks
And so on.
Multi process browsing is fantastic.
So all we really won was performance regressions (the IPC is expensive) and significantly increased resource consumption.
I use bookmarks.
I’m going to give this a try anyway. Maybe the utility of having reference materials on a third screen, that I can glance at without obfuscating my editor behind a browser window will net some productivity gain. When I need copy/paste and codepen-type solutions, I’ll fire the link over to my MBP.
But if I need to add websites to spaces by hand it's not for me as a power user. Make something that will know what websites I often visit and place them automatically in certain spaces. You don't need to stop here! You can go further with this, so if I open 30 tabs of PornHub it will create Adult space for me so I don't need to worry. ;)
To me UI improvements are quite low on the totem pole of “things I wish my browser did/didn’t do”
For one, we still don’t have sufficient privacy on any major browser. Even Chromium, FireFox, and Brave don’t cut it.
> Power Users
Second, scriptability, headless, and Unix-like pipeline integrations without having to use headless chrome and puppeteer. With Phantom gone, it seems we have no choice.
iOS-only WebKit with a neat tab interface doesn’t strike me as a “power user” browser.
But it's a great way to experiment with different UIs.
Maybe if companies won't add that then it's a symptom that we need to combat their browser monopolies somehow.
... wow. Glad you dodged a MoviePass-style bullet on this one.
If it sucks “they’re just 20”
If it’s interesting, they’re precocious
imho if you’re using age as downside protection you’ve already lost
Being really old is a good story – everyone likes to see someone 60+ still fighting[developing], especially because there is a pervasive fear of age discrimination here.
EDIT: I 100% guarantee that even if this project is not successful, if these fellows continue plugging away in the industry, they are going to ship something really awesome.
It’s similar to a bunch of naive HN commenters trivializing work our peers do by suggesting they can build out every startup in a weekend.
The creators of the product have responded in a couple of places about what separates this from a skin, and honestly I think it’s great software design where the complexity is abstracted away from the end user.
And that's why we call them distros instead of separate operating systems.
It would be more interesting to discuss the UX factors and why you think that is a sufficient diffentiator from existing browsers. Just "I wrote a browser and I hope it competes" is a far less interesting story.