231–240 of 343 posts
Earlier quoted context omitted.
It’s also English. It means the left side page of a book. https://en.wiktionary.org/wiki/verso#English
Still latin…
Earlier quoted context omitted.
> > First off, Swift has both memory & data race safety (as of v6) > But v6 is not released yet, right As of Swift 5 there is zero data race protection and the process model (DispatchQueues if memory serves) is woefully. No advantage over fork and much more convoluted I am well clear of the Apple development world now (thank goodness) but the tools were of very poor quality, albeit very nice looking, as of this time…
Xcode 16 rewrote much of the autocomplete behaviors and the new engine is blazing fast in terms of UI blockage compared with 15, and stable. Everything to do with tagging etc not just completion itself.
We tried and tried but there was nothing we could use amongst the blinking lights and wonderful graphics.
Earlier quoted context omitted.
> wonder if there’s room for a browser engine that ditches performance and just focuses on correctness and safety Isn't this just the noscript, which breaks most sites to a degree where they're impossible to use or load?
That arguably ignores correctness completely
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…
Hi {firstName}
and also requiring double the number brackets
There are modern cleaner markup alternatives like kdl
Earlier quoted context omitted.
Yes, and that's why Chromium moved to allow Rust code (pretty much like they did for Android).
They said some of the code can be rewritten in Rust but majority of the code cannot. Therefore they are stuck with C++ forever. Scary thing to think about.
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…
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…
It's one of the core things that has enabled the web to be as useful as it is. One of the things that draws people in, and keeps them using it.
Yes, there are problems with what we have. But if you break compatibility, you'll either not be adopted, or part of the crowd that the audience yells at for taking away their favourite things. You'll kill efforts and bury knowledge bases.