cfreksen

قبل 6 أشهرdiscuss

I haven't really looked at the fastrender project to say how much of a browser it implements itself, but it does depend on at least one servo crate: cssparser (https://github.com/servo/rust-cssparser).

Maybe there is a main servo crate as well out there, and fastrender doesn't depend on that crate, but at least in my mind fastrender depends on some servo browser functionality.

EDIT: fastrender also includes the servo HTML parser: html5ever (https://github.com/servo/html5ever).

cfreksen

قبل 7 أشهرdiscuss

That means that SSIMULACRA2 does not capture quality perfectly.

Note that in that figure the formats are compared at the same SSIMULACRA2 score, not at the same file size. In the "very low quality" category, JPEG uses ~0.4 bpp (bits per pixel), while JPEG-XL and AVIF use ~0.13 bpp and ~0.1 bpp, respectively, so JPEG is roughly given 4 times as much space to work with. In the "med-low quality" category, JPEG-XL and AVIF use around 0.4 bpp, so perhaps you should compare the "very low quality" JPEG with "med-low quality" JPEG-XL and AVIF.

After reading your comment, I assumed you had missed the bpp difference. Please excuse me if I assumed incorrectly.

cfreksen

قبل 10 أشهرdiscuss

Do you mean Microsoft 365 Copilot[0]? : )

I realise that a good portion of the references to the product on that page is just "Microsoft 365", but other parts seem to include "Copilot" in the product name for Microsoft's office suite.

[0]: https://www.office.com/

cfreksen

السنة الماضيةdiscuss

This reminds me of the PIK image format (a precursor to JPEG XL) whose name happens to be a word for penis in some languages[0]. In the present case "SPH" is a kink/fetish term meaning "Small Penis Humiliation"[1]. I don't know how many people would think of that, though.

I am not sure if the lesson is to try harder to avoid offence, or live with the fact that words can have multiple meanings and we can be "professional" enough to ignore some of those meanings in some contexts.

[0]: https://github.com/google/pik/issues/6

[1]: https://www.urbandictionary.com/define.php?term=sph

cfreksen

السنة الماضيةdiscuss

It is a reference to the following XKCD comic: https://xkcd.com/1172/

cfreksen

قبل سنتينdiscuss

I think you are referring to this: https://petapixel.com/2020/08/17/gigapixel-ai-accidentally-a...

Discussed 4 years ago: https://news.ycombinator.com/item?id=24196650

cfreksen

قبل سنتينdiscuss

It seems like that will change in the (near) future according to the following github issue[0]. A quote from one of the developers, rami3l, in that thread[1]:

> My current plan is indeed to remove implicit installations entirely.

[0]: https://github.com/rust-lang/rustup/issues/3635

[1]: https://github.com/rust-lang/rustup/issues/3635#issuecomment...

cfreksen

قبل سنتينdiscuss

Sorry for being off topic, but what is going on with the timestamps of this paper?

The latest version (version 2) has 2018-05-28 as the date above the abstract, but it was added to arxiv on 2014-12-15. Version 1 has the date 2022-05-18, but was added to arxiv on 2010-10-29. I briefly skimmed the .tex source file, but I couldn't find any explanation of the date in there. Did someone mess with the clock on the build server?

cfreksen

قبل سنتينdiscuss

I would say that the instance (or second long interval) in time that we name 2016-12-31T23:59:60Z is 1483228836 seconds after 1970-01-01T00:00:00Z, and that 2017-01-01T00:00:00Z is 1483228837 seconds after 1970-01-01T00:00:00Z [0].

The key here is that I use "seconds" to mean a fixed duration of time, like how long it takes light to travel 299792458 meters in a vacuum[1], and this version of seconds is independent of Earth orbiting the Sun, or the Earth spinning or anything like that[2]. If I understand you correctly, you use "seconds" more akin to how I use "days in a year": Most years have 365 days, but when certain dates starts to drift too far from some astronomical phenomenon we like to be aligned with (e.g. that the Northern Hemisphere has Summer Solstice around the 21st of June) we insert an extra day in some years (about every 4th year).

I haven't read RFC 9562 in detail, but if you use my version of "seconds" then "seconds since the Epoch" is a meaningful and monotonically increasing sequence. I suspect that some of the other commentors in this thread use this version of "seconds" and that some of the confusion/disagreement stems from this difference in definition.

The paragraph in Section 6.1 titled "Altering, Fuzzing, or Smearing" also seems relevant:

    > Implementations MAY alter the actual timestamp. Some examples include ..., 2) handle leap seconds ...
    > This specification makes no requirement or guarantee about how close the clock value needs to be to the actual time.

[0] Please forgive any off-by-one errors I might have made.

[1] I know that the SI definition between meters and seconds is the other way around, but I think my point is clearer this way.

[2] I ignore relativity as I don't think it is relevant here.

cfreksen

قبل سنتينdiscuss

I am a bit fascinated[1] by the "verified" version, as it fetches from the same URL twice. First I found it inefficient, but since they are doing these request for every zsh startup an extraneous request is probably not seen as a performance problem. Then I realised that the data they verify the hash of is not the same copy of the data that they load: An attacker controlling the server at the curl'ed URL could serve a different file on the second request, which in turn reminded me of a blog post describing how to detect `curl | bash` server side[2][3].

I think the lesson of this small aspect of the "zi" tale is that one should strive to have a single source of truth (a single copy of the data served at the URL), and that in security contexts one needs to be very precise with exactly which guarantees have been established for which data at which point in time: it is surprisingly easy to implicitely add an assumption like "GET requests returning 200 OK behave like pure functions".

[1]: Though this might just be me piling on the mockery of their project, for my own amusement and schadenfreude.

[2]: https://www.idontplaydarts.com/2016/04/detecting-curl-pipe-b..., alternatively https://web.archive.org/web/20240406132938/https://www.idont..., discussed here e.g. https://news.ycombinator.com/item?id=11532599 (122 comments)

[3]: I am not sure if zsh behaves like bash in this case, as in: Does zsh only read part its input before it starts executing commands?

cfreksen

قبل 3 سنواتdiscuss

In case someone visits this thread from the future, here is an archived version from around when this was posted here on HN: https://web.archive.org/web/20230329165632/https://www.githu...

cfreksen

قبل 4 سنواتdiscuss

To elaborate, in the Top Chess Engine Championship (which is also used as a benchmark in the AlphaZero vs Stockfish comparison) Stockfish has won all seasons since May 2020[1,2]. A common runner up for those seasons is LCZero[3], which is an engine that is derived from/a reimplementation of AlphaZero. Stockfish is also ahead of LCZero in Fischer random chess (as hosted at TCEC) winning 4 out of the 5 FRC tournaments.

As for how close Stockfish 8 is to a current version of Stockfish, Stockfish 15 has ~400 more ELO than Stockfish 8 as measured in their own self-tests[4].

However, when making these comparisons between AlphaZero and Stockfish it might be tempting to frame it as machine-learning-engine vs classical-engine, which is not true. Stockfish incorporates a neural network when evaluating chess positions[5].

[1]: https://en.wikipedia.org/wiki/Top_Chess_Engine_Championship#...

[2]: https://en.wikipedia.org/wiki/Stockfish_(chess)#Top_Chess_En...

[3]: https://en.wikipedia.org/wiki/Leela_Chess_Zero

[4]: https://github.com/glinscott/fishtest/wiki/Regression-Tests#...

[5]: https://stockfishchess.org/blog/2020/introducing-nnue-evalua...

Submissions

Relicensing versus License Compatibility

comments