3 ms·
> Posted from a memory safe browser - WebKit MiniBrowser compiled with Fil-C. Pretty sure this is safer than even V8 and the heap sandbox. It's easy to be safe
by creshal 29d ago
> Posted from a memory safe browser - WebKit MiniBrowser compiled with Fil-C. Pretty sure this is safer than even V8 and the heap sandbox.
It's easy to be safer, as long as performance can be sacrificed for it.
- vanderZwan 29d agoWe live in a world where my laptop is forced to waste tons of computational power on immensely bloated websites even with ad-block, with now even having to worry about agentic bullshit that I didn't ask for, and plenty of others apparently still think throwing computational cycles at cryptocurrency is good for anything. Complaining about a relatively small performance price for Fil-C in that context honestly feels like that one famous newspaper photo of a smoking pregnant woman drinking a beer with a caption saying she's wbrried about the effects of the loud construction noises next door on her unborn child. Except even that is wrong, because at least she had a point about the construction noises, while this is more of a "refusing to eat your vegetables" kind of situation.
- ChocolateGod 29d agoWe also live in a world where site owners purposely put anime cat girls on their websites that serve no purpose then to waste cpu cycles.
- vanderZwan 29d agoUsing personal websites read by a handful of programmer nerds that work fine if you turn off javascript to justify literally everyone else being forced to navigate bloated, broken company websites isn't particularly convincing as an argument against memory-safe C imo.
- tclancy 29d agoPerhaps you do.
- pizlonator 29d ago> easy to be safer It took over two years and help from contributors to get to the point where WebKit could be made fully memory safe.
- creshal 26d agoSure, but compare that to the effort it would take to have the same safety guarantees without any drop in performance.