Concerning the thing that an os must-have is a browser. But if we do it, we have to do it right. I mean I'm tired of thinking about all the shitty principles I have to follow in order to hope (not to be sure) that my page will render fine. It is sad that I have to care about something that shouldn't cause any problem. There is so much to care about in order to deliver a resource from the internet and that job is poorly done by today's browsers as stated earlier.
As I've mentioned in the thread, I think we could try to tackle a simple browser with some small subset of features but doing a full-fledged browser would not be practical. We could try to simplify an existing browser and we would look into it but my GUESS is that most of the complexity in the browser space is coming from the insane web standards that the browser needs to support, not unnecessary complexity in the browser itself. If people in the handmade community do a clean rethink of what the whole internet stack should look like, I would happily support their web-alternative client on our platform! The most practical thing would be to offer browsers such as chrome via a minimal linux image in the community repositories providing support for running linux applications as they exist today. If we don't have a simple browser or a web-alternative client, we'd probably ship something like chrome out-of-the-box
I think it will be important to ensure consistent metrics for simplicity and making sure that we hit this order of magnitude improvement.
While this is going to be a tough challenge, I think that the killer app might be a phone alongside the laptop.
I think that Apple deserves credit in maintaining simplistic uniformity across their ecosystem.
additionally, I'm wondering how we go about licensing stuff like bluetooth and wifi cards if we want to be as FOSS as possible (idk too much of the business and legal stuff behind this).
Figuring out the exact metrics we'll use to quantify complexity should be decided right away/alongside doing a teardown of a competitors product. I think the best approach would be having brainstorm sessions amongst the team. We'll collect the data for at least one exemplar competitor product, if we aggregate data from multiple products we'll probably want to look at mean, median, mode, std dev, and graphs. Once you've got that we'll just make sure we hit 1/10th those numbers. Another metric to go off of is the 20K OS target Casey Muratori proposed in his 30M line problem talk.
We'll do a phone at some point but definitely not at the same time as the laptop, the team will be small starting out so we don't want to spread ourselves too thin. I think a laptop makes more sense than a phone starting out because unlike a phone, a laptop can be used for real work. Given that doing work from our laptop will be more efficient than using any competitor product, by definition it will accelerate our own ability to make future products
Apple does a lot of things right, they are certainly the closest to what we're going for, I'll give them credit for that!
It doesn't have to be hard-FOSS (although that would be nice!) If we need to license stuff we'll deal with that, I want to get people with business experience on board and we can consult with lawyers as well to make sure we're doing everything properly legally speaking.
This might interest some of you.
While it's still not simple and the processor is slow compared to others, I think it is a good start to have a very open computer architecture. I think the guy also longs for simplicity of computers of the 80's(He made a experimental simple OS: http://dump.mntmn.com/interim-paper/)
Would be awesome if we could get him to work for the company or collaborate with him in some way, taking a note of this to remember to try to contact him at some point!