News for hackers. Stuff that matters.
Re:Google patches second Chrome zero-day in two weeks by bsdubernerd on Tuesday November 03, 2020 @11:52AM (#24981349)
As if this was available 25 years ago. IMHO the real issue is embedded pngs in _fonts_, but YMMV.

Feel free to start rewriting libpng and freetype in rust. See you in 25 years?

Re:Google patches second Chrome zero-day in two weeks by jimrandomh on Tuesday November 03, 2020 @03:48PM (#24983808)
Looks like this work is already well under way, maybe even already done: https://docs.rs/png/0.16.7/png/ and https://docs.rs/ttf-parser/0.8.2/ttf_parser/ .
Re:Google patches second Chrome zero-day in two weeks by pjmlp on Tuesday November 03, 2020 @03:13PM (#24983484)
System programming languages with bounds checking enabled go back to 1961.

We are stuck with C due to the synergy effects of having a free beer OS with source code available.

Re:Google patches second Chrome zero-day in two weeks by jeffbee on Tuesday November 03, 2020 @12:02PM (#24981458)
It's incorrect to believe that C was the right choice even in 1996. At that time it was already obviously the wrong choice.
Re:Google patches second Chrome zero-day in two weeks by extropy on Tuesday November 03, 2020 @12:32PM (#24981796)
It was the only choice that met the performance constraints at the time.

And the common sense at the time did not put too much focus on memory safety.

Re:Google patches second Chrome zero-day in two weeks by pjmlp on Tuesday November 03, 2020 @03:14PM (#24983491)
I was meeting the performance constraints of doing software in MS-DOS with Turbo Pascal.
Re:Google patches second Chrome zero-day in two weeks by stonogo on Tuesday November 03, 2020 @03:40PM (#24983723)
I wasn't; back then there were a LOT of things, especially in graphics and linear algebra, that required dropping to embedded ASM to accomplish in a performant way. I think Turbo- and Object Pascal were great languages, but let's not pretend they were anywhere near the speed of C.
Re:Google patches second Chrome zero-day in two weeks by pjmlp on Tuesday November 03, 2020 @04:21PM (#24984143)
C machine code quality was just as slow as anything else on 16 bit computers, lets not pretend otherwise.

Modula-2 and Pascal compilers had the necessary switches to make the languages just as unsafe as C, and anything related to ultimate performance out of 8086 and 68000 required Assembly anyway.

Re:Google patches second Chrome zero-day in two weeks by jeffbee on Tuesday November 03, 2020 @03:42PM (#24983746)
The point of my remark here is we aren't talking about rendering text along a path or whatever. We're talking about opening a file and parsing a binary format, which is in most use cases not at all performance-sensitive.
Re:Google patches second Chrome zero-day in two weeks by jeffbee on Tuesday November 03, 2020 @03:40PM (#24983728)
FreeType was initially written in Pascal.
Re:Google patches second Chrome zero-day in two weeks by echlebek on Tuesday November 03, 2020 @03:02PM (#24983388)
What would you have written freetype in?
Re:Google patches second Chrome zero-day in two weeks by pjmlp on Tuesday November 03, 2020 @03:14PM (#24983487)
Modula-2, Object Pascal.
Re:Google patches second Chrome zero-day in two weeks by Dylan16807 on Tuesday November 03, 2020 @03:43PM (#24983755)
> IMHO the real issue is embedded pngs in _fonts_, but YMMV.

Png is a pretty simple format that everyone already implements. Would you rather use something ad-hoc?