Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Verso – Web browser built on top of the Servo web engine

github.com

Post reply on HN
Print view View original

301–310 of 343 posts

Re: Verso – Web browser built on top of the Servo web engine

#301

Post by throwaway14356 »

zackbrown wrote: post #227
ksec wrote: post #5

So we will, in ~5 years time have two new browser, one in Rust and one in Swift. I hope in the process of doing it we will find new ways of doing things.

> I hope in the process of doing it we will find new ways of doing things. HTML & CSS themselves have become a major bottleneck to quality and creativity. The arcane layout model, the baggage of backwards compatibility, the cognitive dissonance — played out over decades of design-by-committee — between "this is a document engine" and "this is an app engine." The rendering-thread-is-the-main-thread architecture of JS…

I want to see different file types with their own rendering engines and/or programming languages in the same browsers.

Very powerful but also very limited languages and formats that know what their purpose is.

Re: Verso – Web browser built on top of the Servo web engine

#302

Post by refulgentis »

lnrd wrote: post #261
refulgentis wrote: post #131

Earlier quoted context omitted.

Problem is Swift engineer supply is low, there's not a viable business case to learn Swift because it's not actually viable cross-platform for development unless you have $X00 million to throw at your macOS/iOS team to build it from scratch, platform by platform (to wit, sibling comment re: Arc Browser) So best case we're looking at: Swift isn't ready yet, the next major version will be, and we can't build UI with it…

> Problem is Swift engineer supply is low, there's not a viable business case to learn Swift because it's not actually viable cross-platform for development The Swift business case is that in many situations native is strongly preferable than cross-platform. Excluding some startups that wants to go to market super fast and consulting companies that have to sell the cheapest software possible, usually the benefits of…

Right -- no one read my comment and thought I meant Swift was unnecessary or businesses don't use it. Contextually, we're discussing Swift for cross-platform dev.

Re: Verso – Web browser built on top of the Servo web engine

#303

Post by HeckFeck »

nequo wrote: post #229
azangru wrote: post #32

Earlier quoted context omitted.

Wouldn't dont be even easier?

As an acceptable compromise we can separate all punctuation and put it at the end of the paragraph Although some oldfashioned enthusiasts of the Chicago Manual of Style will object But I think its good to bring some fresh ideas to our old and worn orthographyevery now and again,.-…’—.

Finally, RPN but for natural language!

Re: Verso – Web browser built on top of the Servo web engine

#304

Post by bangaladore »

zackbrown wrote: post #227
ksec wrote: post #5

So we will, in ~5 years time have two new browser, one in Rust and one in Swift. I hope in the process of doing it we will find new ways of doing things.

> I hope in the process of doing it we will find new ways of doing things. HTML & CSS themselves have become a major bottleneck to quality and creativity. The arcane layout model, the baggage of backwards compatibility, the cognitive dissonance — played out over decades of design-by-committee — between "this is a document engine" and "this is an app engine." The rendering-thread-is-the-main-thread architecture of JS…

To me, it seems like you are reinventing frameworks like Svelte while adding the complexity of Rust. I don't see the benefits.

Re: Verso – Web browser built on top of the Servo web engine

#305

Post by bangaladore »

bbatha wrote: post #294
mappu wrote: post #246

Earlier quoted context omitted.

It's hard to summarize like that since Ladybird is still ahead in many individual tests including important ones (e.g. acid3 at https://staging.wpt.fyi/results/acid/acid3/numbered-tests.ht... ).

acid3 isn't particularly important as it doesn't even match modern standards. Modern chrome and firefox only pass 97/100 tests.

Someone reading your comment might infer that Servo is passing 97 out of 100 tests, when in fact, they are passing 86 out of 100.

I don't know enough about browsers to know how vital those tests are, but it is important to note that they are still a ways off of 97.

Re: Verso – Web browser built on top of the Servo web engine

#306

Post by laweijfmvo »

The linux (flatpak) instructions seem to be out of date or at least not working for me on Fedora; but I'm a flatpak noob so maybe I missed something

edit: missed the part where i still need to clone the repo. but also a requirements.txt would be appreciated!

Re: Verso – Web browser built on top of the Servo web engine

#307

Post by themikesanto »

zackbrown wrote: post #275
madeofpalk wrote: post #271

Earlier quoted context omitted.

I think CSS is excellent and pragmatic. Alternate layout engines for the web might be a fun experiment, PhD thesis, or talent retention program, but it's not practical.

> Alternate layout engines for the web might be a fun experiment, PhD thesis, or talent retention program, but it's not practical. Flexbox was once an "alternate layout engine for the web," as was Flash player, as is Figma. Framer, Retool, and Squarespace all offer alternate layout engines tailored for visual building. All of these seem practical to me.

All of the products you described are just tools that build HTML/CSS for you.

Re: Verso – Web browser built on top of the Servo web engine

#308

Post by niutech »

atoav wrote: post #256
zackbrown wrote: post #227

Earlier quoted context omitted.

> I hope in the process of doing it we will find new ways of doing things. HTML & CSS themselves have become a major bottleneck to quality and creativity. The arcane layout model, the baggage of backwards compatibility, the cognitive dissonance — played out over decades of design-by-committee — between "this is a document engine" and "this is an app engine." The rendering-thread-is-the-main-thread architecture of JS…

Care to point us to a better combination than HTML/CSS when it comes to layouting flexible interfaces? Don't get me wrong, I also could imagine better markup languages for that purpose. But everything I have seen in the wild was worse in multiple, show-stopping ways. Maybe instead of coming up with a new thing, we just need a clear way to solve the pain points and put the solutions into CSS4 and HTML6

LaTeX or Tagged PDF are better than HTML for document-oriented content.

Re: Verso – Web browser built on top of the Servo web engine

#309

Post by [deleted] »

Aerbil313 wrote: post #217
jhatemyjob wrote: post #181

Earlier quoted context omitted.

[flagged]

Don’t think this really fits in with HN guidelines. Seriously, check out https://servo.org , they post monthly updates and the progress seems great. And their repo, too - too bad GitHub can’t display code frequency because there’s too many commits in the project.

[deleted]

Re: Verso – Web browser built on top of the Servo web engine

#310

Post by [deleted] »

Aerbil313 wrote: post #217
jhatemyjob wrote: post #181

Earlier quoted context omitted.

[flagged]

Don’t think this really fits in with HN guidelines. Seriously, check out https://servo.org , they post monthly updates and the progress seems great. And their repo, too - too bad GitHub can’t display code frequency because there’s too many commits in the project.

[deleted]
Post reply on HN