Use the system webview, you cowards!

Developers bundle all of Chromium, because they're afraid the OS webview will have a different browser engine. Testing is too hard…

This is such a terrible excuse — usually the same app runs in browsers too, so it already has to deal with even wider variety of browser engines.

Epic sponsoring Godot was a 4D chess move against Unity.

https://godotengine.org/article/godot-engine-was-awarded-epic-megagrant/

I’ve got an ARM Mac. I’ve got ARM VPSes from Hetzner, and I’m compiling native code for the server.

It’s definitely easier to develop, build, and test on the same architecture, than to deal with cross-compilation and emulation.

So I think Linus is right.

Rust tries to move language functionality to libraries where possible. Instead of adding high-level magic to the language, Rust prefers to add a low-level feature that can be used to build higher-level features. For example, instead of built-in nullable types, it has enums with data, which were used to make Option. This way hopefully you can do more things with fewer language features. Functionality of higher-level features can be explained by lower-level ones (knowing how things are implemented is important for systems programming), and you can reimplement them if you need (e.g. Rust in the Linux kernel uses its own smart pointers instead of those from the standard library).

Rust tries to keep the standard library small, and move unnecessary code into crates-io crates. The problem with stdlib is that there is only a single version shared by all programs, so it has to stay backwards-compatible forever. Long term stdlib accumulates outdated functionality and deprecated APIs, which can't be fixed. Crates.io crates support versioning, so they can evolve and iterate without breaking anyone.

Another reason is that Rust supports low-level programming, including embedded. This means that the language itself can't depend on any fat runtime, and doesn't even perform heap allocations.

The annoying popups are an act of malicious compliance from data harvesting companies. The tracking industry wants people to associate the right to privacy with stupid annoyance, so that people will stop demanding privacy.

The legislation does not say anything about cookies. It's about rights and responsibilities in data collection (no matter how it's done technically). The "consent" part of it exists as a compromise, because there has been heavy lobbying against the legislation.

This is not a technical problem — we've had many technologies for it, and the industry has sabotaged all of them. There was the P3P spec in 2002! It has been implemented in IE that had 90%+ market share back then. And Google has been actively exploiting a loophole in IE's implementation to bypass it and have unlimited tracking. Google has paid fines for actively subverting Safari's early anti-tracking measures. Then browsers tried DNT spec as the simplest possible opt-out, and even that has been totally rejected by the data harvesting industry. There are easy technical solutions, but there are also literally trillions of dollars at stake, and ad companies will viciously sabotage all of it.

Generally yes.

GIF's ancient LZW compression is remarkably ill-suited for modern CPUs, and more expensive than modern algorithms. Combined with significantly larger file sizes, it costs much more to decode, on top of increased costs of transfer and caching.

GIF might have an edge if the animation is very small (<16px, few frames).

It also gets messy if you need to play hundreds of animations. GIF will be terribly inefficient, but also browsers aren't designed to have hundreds of video elements, so both will eat memory in their own way, and it will vary which is worse.

This is how security works in the C programming language.

Filomena is brilliant

I don't know about C++, but in Rust the push is inline, and still doesn't always optimize checks away due to an annoying edge case: integer overflow. Reserving (old_len + new_len) could give you a smaller buffer than new_len. The optimizer sees it and is pedantic about it.

This has always been the case. When Windows XP came out people hated it needed 64MB (not GB) of RAM, because that was more than the entire disk installation of Windows 95, which was also bloated compared to older Macs and Amigas.

Severe performance issue on day one is most likely a bug, some incompatibility, or debug code accidentally left in.

I don’t know why people interpret it as if the game will never be playable and behave as if it was some master plan to make 4090 look slow.

Happy to see Rust’s standard library near the top in performance. It’s nice to have a good implementation out of the box.

eGMP cars (Hyundai/Kia) need 20 minutes of charging per 2-3 hours of driving. It really works — I've driven across Europe twice now, and often my coffee breaks take more time than the car needs to recharge.

The battery tech has advanced significantly in the last 10 years. Leaf used to be 24kWh, now it's 40kWh for the same price. If the trend continues (and likely will thanks to economies of scale ramping up), by the time you need to replace the battery in today's EVs, the replacements will be cheaper and better.

Only signed overflow. size_t is unsigned.

It's a great game. Very good story. The game is mostly serious noir detective story, except that roaring Zootopia setting.

It's nice they're moving away from libgit2.

This dependency made rustsec library unusable in any project that used any other version of libgit2, and libgit2 kept making incompatible releases causing fragmentation, churn, and conflicts.

Renault 5 looks promising.

I just hope they can make charging faster than it is in their current e-tech cars.

A better link: https://www.gog.com/en/game/baldurs_gate_iii

It’s also (obviously) a problem limited to North America.

Everywhere else Teslas and Superchargers use a CCS2 connector.

In Europe, non-Tesla charging networks together are bigger than the Supercharger network, and Ionity and Fastned have 300kW chargers that are significantly faster for Hyundai/Kia/Genesis than Superchargers.

There’s aarch64 version of Linux.