It compiles and sends bytecode to the server, no? I'm quite sure the server at least does not run a plain interpreter, and I know for sure you build a graph there. That's why you can also use it with other languages (Saw a clojure example I think I wanted to give a try)
Edit: that person (or bot) has almost exclusively posted on this website about the current US president. I think it's a waste engaging and I already regret my comment here
The house in Zurich I live in was initially built something like in the 12th century, but the floor I reside on was added in the 17th century. This is the case for most houses in the old town. So this is going on for a while.
Physical units help modeling and review, it's much easier to sanity check values from just reading, and comparing constants. I've heard that for rendering/raytracing, a lot of people move to model light intensities by actual physical values which makes it much easier to author and compare - such as for example "oh I want a light here that is as bright as this old lightbulb I like so much, but there's sunlight also shining through the window". That's much easier than estimating it in arbitrary units, in particular as here human perception is non-linear. I assume this would be similar for other simulations.
Meh, I have the impression the blog author really hates Zig's new Writer (fair, I disagree, but fair), but his criticism in this example is in my eyes slightly questionable -- it is a bug in the implementation and not a conceptual issue. He then uses quite some loaded phrasing like "I must be too dumb to understand this" and "I can't be really too dumb can I?" which I think ruin the discussion (as do the titles. He failed to convince me, for instance, that the new Writer was inherently unsafe by design). It feels like a "Look I told you!!! You run into bugs like this!!!" which is not helpful for a feature/refactor that was already advertised as complex and not fully implemented or verified.
Disclaimer: I'm a zig fanboy and do all my hobby stuff in it
I strongly disagree. There are things far, far worse than JavaScript. I would even go so far as calling it "quite decent". I like to use it for prototyping and scripting quite a bit, it can be rather efficient and the "standard library" is very decent in my eyes. It has some footguns, and certainly used to have a couple more (that are discouraged now, but still people complain and call it bad because technically, you can still use the bad parts that any linter refuses). I even really like the idea of protoype-oriented programming and find it a bit sad we lost this in favor of classes, but I guess this actually makes the language a bit easier. Disclaimer: I am not a webdev, and if I do webdev, I use TypeScript. Personally, I consider e.g. Python far worse.
reply