←back to thread

Libxml2's "no security embargoes" policy

(lwn.net)
276 points jwilk | 3 comments | 25 Jun 25 19:36 UTC | HN request time: 0.595s | source
Show context
bryanlarsen ◴[25 Jun 25 22:35 UTC] No.44382391[source]▶
> The point is that libxml2 never had the quality to be used in mainstream browsers or operating systems to begin with

I think that's seriously over-estimating the quality of software in mainstream browsers and operating systems. Certainly some parts of mainstream OS's and browsers are very well written. Other parts, though...

replies(2): >>44383097 #>>44384586 #
karel-3d ◴[26 Jun 25 06:01 UTC] No.44384586[source]▶
I have only experience with Chrome codebase and while it's C++ (which I don't personally like) it's pretty solid and most of the weird hairy stuff were the external linked libraries. But I didn't poke around THAT much.
replies(2): >>44384647 #>>44386379 #
1. troupo ◴[26 Jun 25 06:15 UTC] No.44384647[source]▶
Remember "25000 string allocations per each key stroke"? https://groups.google.com/a/chromium.org/g/chromium-dev/c/EU...
replies(1): >>44386051 #
2. quietbritishjim ◴[26 Jun 25 10:41 UTC] No.44386051[source]▶
That's certainly interesting but to give context for those not following the link: This is for entering into the address/search bar, so it covers all the work of searching history, performing network requests to autocomplete search terms, and displaying those results. It's not like entering a character into a regular text box on a page.
replies(1): >>44386185 #
3. troupo ◴[26 Jun 25 11:08 UTC] No.44386185[source]▶
IMO no amount of context can justify 25000 string allocations per key stroke :)

Also, if you read the issues in the first post, it has nothing to do with "covering all the work". It's just really bad programming