I’ll definitely Open Source it under the AGPL 3.0 when or before it reaches the point of “minimum viable product.”
Which basically means it can technically read see most of the content on the page of what you might consider a “Web 1.0” page. In that state, the layout will be effed, there won’t be any JS, Web Sockets, maybe not even animated GIFs. But you’ll be able to read Wikipedia. (Though, again, it won’t look like it does in Chrome or Firefox or even I.E. 6.0 .)
And then the plan is to evolve it from there, prioritizing roughly the features that most improve the range of sites and features people can reasonably use even if they don’t work “like they do in Chrome/Firefox”.
And if other folks get interested enough to throw labor at it, awesome. If not, hopefully something shiny doesn’t distract me and get me working on something else.
And, mind you, I’ve been working on this for like two-ish weeks. So all I’ve got are some high-level requirements, design, some toy experiments to learn more about how the graphics part is going to work, and some of the infrastructure by which different parts/modules of the browser are going to communicate. There’s kindof nothing to show or update about yet.
If you like, I’ll save your post and when there’s something to show (basically when it’s Open Sourced), I’ll DM you and let you know where the repo is. And you’ll be able to check there for further updates.
And if anyone else wants updates, (and I can’t really promise anything is actually going to come of any of this), feel free to respond to this post.
Oh, also, this might matter to some folks. I’m writing it in Go. Some folks might dislike that because it’s “a Google language.”
I like the “release early, release often” approach. For a curious lay man like observing something from scratch is interesting. This will attract more eyes and eventually more programmers.
You gonna post updates on the project somewhere?
I’ll definitely Open Source it under the AGPL 3.0 when or before it reaches the point of “minimum viable product.”
Which basically means it can technically read see most of the content on the page of what you might consider a “Web 1.0” page. In that state, the layout will be effed, there won’t be any JS, Web Sockets, maybe not even animated GIFs. But you’ll be able to read Wikipedia. (Though, again, it won’t look like it does in Chrome or Firefox or even I.E. 6.0 .)
And then the plan is to evolve it from there, prioritizing roughly the features that most improve the range of sites and features people can reasonably use even if they don’t work “like they do in Chrome/Firefox”.
And if other folks get interested enough to throw labor at it, awesome. If not, hopefully something shiny doesn’t distract me and get me working on something else.
And, mind you, I’ve been working on this for like two-ish weeks. So all I’ve got are some high-level requirements, design, some toy experiments to learn more about how the graphics part is going to work, and some of the infrastructure by which different parts/modules of the browser are going to communicate. There’s kindof nothing to show or update about yet.
If you like, I’ll save your post and when there’s something to show (basically when it’s Open Sourced), I’ll DM you and let you know where the repo is. And you’ll be able to check there for further updates.
And if anyone else wants updates, (and I can’t really promise anything is actually going to come of any of this), feel free to respond to this post.
Oh, also, this might matter to some folks. I’m writing it in Go. Some folks might dislike that because it’s “a Google language.”
Feel free to open-source it already. Even if it’s not a MVP ready
I like the “release early, release often” approach. For a curious lay man like observing something from scratch is interesting. This will attract more eyes and eventually more programmers.