bkardell

Odd, works for me in Firefox, Chrome and Safari. They aren more shapes of text that match the video than images.

From a recent FOSDEM talk https://www.youtube.com/watch?v=cP24XJS8bPg

Last autumn we finally fell to third behind Microsoft, in fairness.. But we're also the second biggest contributors to WebKit (really significant there) and Gecko too, as well as the #1 contributors to Servo, and more - if you're interested: https://bkardell.com/blog/2024-Midseason.html

It's great to see the attention to servo growing - the number of people starring servo on gh just keeps going up! There's a chart on https://toot.cafe/@bkardell/112931971129556513

One big reason to want change is to change the funding model that currently supports the existing browser projects, which isn't great and is threatened too...

Bits of the servo project were integrated into FF/Gecko in Quantum (https://blog.mozilla.org/en/mozilla/introducing-firefox-quan...) - there's shared work where improvements in either end can help either.

Interesting - I had never never seen nyxt - but it doesn't seem to be a new renderer as far as I can tell? I could be wrong! I'm curious if it is though! It seems to say in the FAQ it is agnostic and currently supports a few engines as the renderer https://nyxt.atlas.engineer/faq

Hi, Igalian here. I can tell you that Wolvic does not use Servo nor are there any immediate (or even long term at this point) plans for it to. That's not to say it couldn't happen someday or that it wouldn't be interesting. We are major contributors to a lot of major projects and many of them have something to do with web engines (see https://bkardell.com/blog/2023-Mid-Season-Power-Rankings.htm...) so it's easy enough to see connections, but the connections are mainly often more generally just "we have a lot of interest in web stuff, and a great reputation for contributing".

It seems like some of the work that Igalia did was externally funded, but far from all of it.

Yes, that's right. Very far from all of it, but we're also very appreciative of those who did contribute funding. (I'm from Igalia/the host you're quoting)

about doing some work on MathML in WebKit [sic; Blink presumably

https://twitter.com/webkit/status/756489720893411329?s=20&t=... for example was also Igalia

Wolvic begins its evolutionary fork pretty close to where Firefox Reality left off, so yes, it is Gecko based.

We do right?! Thanks.

Interesting observation. Fwiw, I am definitely very much a native english speaker (in fact, I don't speak any other (non-programming) language very well), and I proposed the name. As the post says at the end - it doesn't hurt that the domains are available if you don't use a "real" world. I guess we'll see if this happens.

I get this take... You might find my post on this topic interesting https://bkardell.com/blog/wolvic.html

I believe this intended to link to https://www.igalia.com/2022/02/03/Introducing-Wolvic.html

Related release news from Mozilla https://twitter.com/mozillareality/status/148924010351593062...

and Igalia https://twitter.com/igalia/status/1489238493981253642

Ah hey thanks for the shout outs :) FWIW Jay Hoffmann has been doin some posts on CSS Tricks https://css-tricks.com/category/history/ and there are some other intersting things in this space too. If you like these, I also do some web history things on our Igalia chats podcasts, often with folks firsthand - one is in fact going to be a chat with Chris Wilson tomorrow at BlinkOn 15.

I really enjoyed watching Simon's talk myself - a slightly different perspective of the last 30 years is also in this talk I gave https://youtu.be/dFsRz1PGjdw?list=PL_BRVuWxk8srToZ69z-_5vBJI... .. It's got no playmobile figures, but a lot of gifs :)

It's part of WebKit itself, so shared by Safari, yes... Igalia is the #2 contributor to WebKit behind Apple with ~16% of all commits (we maintain a few official ports, including the one used for embedded devices, WPE WebKit). Sony are also significant contributors to WebKit. So, it's not an academic exercise, no. Apple WebKit engineers have been quite supportive..

Also the second largest contributor to WebKit after Apple in the same years. I shared a link here in one of the other comments with charts and lots more info from the end of 2019.

Yes, all Igalians receive equal pay and are involved in all decisions!

I'm not entirely sure what you're asking/interested in, but my contact information is on the linked site/my twitter DMs are open and I'm happy to talk more.

Yes! We've contributed loads to each of them. Here's a summary I wrote at the end of last year https://bkardell.com/blog/2019-Wrap.html - #2 contributor to Chromium, #2 contributor to WebKit, top 10 to Firefox last year.

If you can give those users faster performance and lower data usage and opportunities to cash in on the value of their eyeballs, where/when they are willing, it doesn't seem like you even have to 'hate' them, you just have to prefer something with more positive features.

Honestly, I think Brave is good for everyone - including advertisers. There are interesting new patterns to develop here, I'd bet. With every change in tech comes new possibilities, Brave is opening the door to a lot of potentially new ideas/strategies here IMO.

You can also watch and participate in related discussions on https://lists.w3.org/Archives/Public/public-houdini/- I think the article didn't mention IIRC.

I remember hearing about something similar in '08 https://www.youtube.com/watch?v=AMojRXK14jU which became http://www.humdingerwind.com/ - I wonder if they are related? Seems like a really interesting idea.

Send a pull - github for the win! http://darobin.github.io/formic/specs/json/

In fairness, you have to look at how standards get somewhere - this is an editor's draft which is a starting point of an idea rather than a done deal. Don't be surprised if the final product winds up being significantly different than this - even better, get involved in the conversation to make it what we need. That's not to pour cold water on it: It's good as it is, but there are changes which potentially help explain the magic of participating in form encoding and submission which may be better and allow more adaptation and experimentation over time.

I think that at least some of this is historical based on how the capabilities in the platform developed. For example, HTML is declarative and, in theory at least, something all but the purest artist/designer understand. The same is generally true about other traditional communication mediums - Designers for magazines understand magazine printing and often have related tools, for example.

Likewise, CSS is not only declarative, but a rules based DSL for presentation - definitely in the realm of designers (and conceptually an underpinning upon which you could build even simpler tooling).

Where this has broken down and caused the kind of confusion i think the article discusses IMO is that the creation of HTML is very frequently (almost always traditionally) assembled via another system which is less so - asp/jsp for example were Turing complete languages mixed with templating. So it took engineers to make the dom serialization in the first place. Then as things moved client side we had script managing the DOM too. Combined with very limited semantic/expressive powers in HTML and CSS, the marriage between the three often put the two disciplines at odds with one another. I think that new tags, web components/shadow dom combined with new capabilities in CSS like regions, grids and pseudo-elements may put things right and make the web have a much better story for cooperating disciplines of engineering and design/ux.

the info in this piece about Mozilla following safari suit on third party cookies is out dated i think. https://brendaneich.com/2013/06/the-cookie-clearinghouse/

Yes, in layers. The problem currently is that if you want to tweak something you have to basically replicate the entire stack. That sucks - see Yehuda's article linked elsewhere in the comments for better examples. ps, if you want to play with jquery-like selector plugins to prollyfill a proposed feature, check out hitchjs.com

Did you read Yehuda's explanatory post https://medium.com/the-future-of-the-web/2fcd1c1bb32 or the linked readings on the manifesto? It's quite a bit different than today actually.

If you liked this article, you might also like http://news.ycombinator.com/item?id=4887057 which for some reason didn't make the front page when Alex's did and is thus lingering without the attention that this one is getting.