PudgePacket

That's correct.

Webgl is honestly a pretty good mid ground between them.

Yes, multiple scenes are common practise. Using it to stitch game worlds is not common though. Most terrain systems would have their own, more optimal/efficient ways of doing that.

https://docs.unity3d.com/ScriptReference/SceneManagement.Loa...

https://gamedevacademy.org/a-guide-to-handling-huge-worlds-i...

With service workers disabled on firefox the site just breaks, no graceful degradation/progressive enhancement. When clicking links in the header the url will change, but the page content doesn't.

So.. I can't get to the about page because when I scroll down to see the links in the footer, it loads more content :)

Netlify results seem disappointing, I say that as a happy user of their service.

Netlify is an outlier in this comparison. For them, static site hosting is their core product, bread and butter if you will. To have such mediocre performance, as well as a relatively bad time to first byte is quite surprising.

What do you mean by "no JS overhead"?

Distractions are orthogonal to space.

It's generally not productive to play "who has it worse".

"rust community" is not a single organism.

I also think we should understand someone was probably quite excited to see something they liked taken seriously by a company they respect. Maybe in their excitement and rush they user hyperbole.

Most of the options are hosted or static, which are generally "secure enough" for the intended audience.

As soon as you're self hosting now you're doing server admin etc and that would be outside the scope of the article.

For further reading see "Studying Studies" https://peterattiamd.com/ns001/.

Oh boy I definitely understand you, in fact I built a Rust CLI tool to solve exactly that ;) https://github.com/tbillington/kondo

Rust is statically linked by default, not sure how D works. Rust still includes some debug features that can give you a stack trace. Size will also depend on the compile options, if LTO was enabled, how much generics were used, how much string printing was used (print is a macro in Rust that generates code at the callsite), etc. Most, if not all, of these can be resolved.

See https://github.com/johnthagen/min-sized-rust for aiming for small binary size.

This article shows a 93% size reduction, 2.7m -> 200kb, with some relatively simple modifications https://www.collabora.com/news-and-blog/blog/2020/04/28/redu....

Here is someone using Rust for a 3kb demoscene program https://www.codeslow.com/2019/12/tiny-windows-executable-in-....

Off-topic but it seems the quotes around the title don't render on the front page, but they do render on this page? It flips the entire tone of this article.

Initially on reading the title I just eye-rolled, but clicking through and seeing it was a response to that, and was actually the quote in quote marks made much more sense!!

6. Authors who haven't heard of XDG_CONFIG_DIR.

True!

You can turn them off in browser settings, I have in firefox :)

The lever and github links are broken.

Yes, that's the whole point though.

Can you rephrase or restate your point? It's really hard to understand..

> Note the use of pointers, this forces other systems to take care of the actual storing of objects, leaving the physics engine to worry about physics, not memory allocation.

Based on the access patterns in the code (iterating through every physics object every step), keeping the physics objects behind a pointer is actively cache hostile! If at all possible try to have these objects in contiguous memory.

18 hours of the day not eating, 6 eating. It's usually called time restricted eating/feeding or an eating window with the idea being you'd do it every day. This is in contrast to extended/prolonged fasting, which is typically 24hr+.

In general IF (intermittent fasting) is a catch-all phrase, and not a particularly helpful one.

From what I've read there's a cap on how much VitC you can absorb orally, IV VitC can give you much much more (think order of magnitude or more).

Curious how this would apply to the Redis protocol. It's a text protocol that is friendly/intended for character by character parsing. The example code at the bottom of the page is an example of iterating the characters of a byte stream.

https://redis.io/topics/protocol

I don't know if it would be in the spirit of Go.

(I'm not for/against the philosophy of the decision making, just pointing it out).

That's what I meant though. Neither parts needs to use crates.io.

> but who writes vanilla css in 2020?

Even if your point is good, that's just not a productive way to start out.

You can add crates from other registries or git urls.

https://doc.rust-lang.org/cargo/reference/specifying-depende...

Damn.. super interesting!

Seems like it's just being used as a distribution method here.