tambre

> when October 14, 2025 is around the corner, when official support for Windows 10 is supposed to end.

That's the Enterprise LTSC EOL for 1507. Seems unlikely you're running that unless you're a big enterprise?

Regular GAC 21H2 will last you only until June 13, 2023.

Unity builds, but also unified and jumbo builds.

autoconf is nix-only in practice, macro-based, verbose and has a significant legacy burden. I have suffered plenty of pain from trying to build the few projects that still use it. In such cases it's often been faster to write own build scripts for some other newer buildsystem.

CMake and Meson I've used across tens of different projects, there's solid online documentation, significant usage, a good underlying language and I already have my toolchain files ready. Using autoconf instead of something more common and modern is likely to turn off people contributing or using your project as they'll be unfamiliar with it and are going to have more trouble solving issues on their own.

autconf in 2021 instead of something more humane like CMake, Meson, Bazel, build2. Why?

I also ended up with Fender's, but it wasn't terribly responsive so eventually purchased a strobe tuner [0]. Has some disadvantages over something like a smartphone, but better for my simple usage.

[0]: https://www.thomann.de/intl/ee/peterson_stroboclip_hd.htm

> where is Nvidia with Wayland support?

They released drivers at the end of October that support GBM. Since XWayland 21.1.3 hardware acceleration for X should work too. I haven't tried myself though, since Nouveau is enough for my basic desktop usage.

Fixed in C++23 by adoption of P1949R7 [0], which didn't originally set out to fix that, but seems to have after a Netherlands national body ballot comment.

[0] http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p194...

> So generally, to use your example, a non-ECC processor is a regular processor "who's" ECC logic has failed and is inoperable.

But no high performance mainstream desktop Intel CPU supports ECC [0]. Meanwhile AMD doesn't have any that lack it.

What gives? Surely Intel's ECC logic doesn't have such a huge defect ratio that Intel can't have even a single regular mainstream part with ECC.

At work I need fairly low performance CPU with decent integrated graphics. Intel's iGPUs are great were it not for the lack of any parts with ECC. Nevermind that finding a non-server Intel motherboard with ECC support would restrict the choice such that there'd likely be none with also other desired features.

[0] https://ark.intel.com/content/www/us/en/ark/search/featurefi...

Having a license for the architecture isn't worth much if you aren't playing by the rules anyway. The IP and expertise for the best implementations? That's useful.

That tweet, and the whole thread, only speak of the Display Controller and Linux render/framebuffer management. Graphics drivers are another separate topic, which as the parent noted, aren't usable yet.

Amazon enabled IPv6 for various CDN endpoints serving images and static assets this year. At least they've made progress.

A few years ago when forcing Reddit to IPv6 through /etc/hosts many pages resulted in 500 errors, but they gradually fixed them.

Aptly [0] is also really nice for maintaining mirrors and one's own Apt repositories though it is unmaintained.

[0]: https://github.com/aptly-dev/aptly

LLVM got upstream support for the swifttailcc calling convention last week [0].

[0] https://github.com/llvm/llvm-project/commit/82a0e808bb2cddc1...

Chromium is working on it [0]. The infrastructure team posted a schedule [1].

Depot tools should work and about 1.5 years you could build most of Chromium on Windows with Python 3.

[0] https://bugs.chromium.org/p/chromium/issues/list?q=Proj%3DPy... [1] https://bugs.chromium.org/p/chromium/issues/detail?id=942720...

People rarely seem to add release notes for their changes and I don't think anyone goes back at the end of the release cycle and picks out the highlights.

For C++ features you also might be better off looking at cppreference.com [0].

[0]: https://en.cppreference.com/w/cpp/compiler_support

Does the control format have an official spec? I too have had to resort to parsing those files with regexes.

They do have something – Clear Linux [0]. Definitely not too mcuh investment, but they do differentiate by compiling packages for much newer instruction sets compared to other distros.

[0]: https://clearlinux.org/

> Apple bought up TSMC’s entire 5nm manufacturing capacity

... until the end of 2020.

Project Denver lives on in NVIDIA's Carmel cores shipping in Tegra 194 (Xavier) chips today. Though they seem to be giving up on it, as they'll be using Cortex "Hercules" A78 cores in the successor named Orin.

Intel has EMIB [0], which they've used in i7-8809G [1]. And they seem to be going all-in on chiplets heavily... for 7nm [2]. At their current pace it'll be a few years before that.

[0] https://www.intel.com/content/www/us/en/foundry/emib.html [1] https://en.wikichip.org/wiki/intel/core_i7/i7-8809g [2] https://www.anandtech.com/show/16021/intel-moving-to-chiplet...

Chrome has supported draft versions for the past few years already. The current spec is considered to be basically final and there are no more expected backwards compatibility breaks. Seems useful to get some widespread real-world experience in case there is actually something unexpected at a large scale.

Youtube is Google's own global CDN, Twitch is Fastly.

Fastly is also seeing problems. [0]

However, they report that they've identified the issue and are fixing it.

[0]: https://status.fastly.com/

It seems Google is running their nightly pipelines with additional profile generation, but sounds like that's restricted to their internal Chrome (not Chromium) pipelines.

Microsoft would have to do their own setup. Hopefully they do.

Source? That would be great news, but I can't find anything.

> NVIDIA licenses ARM IP now, if they bought ARM they would actually own the designs

NVIDIA Carmel is NVIDIA's own Arm v8.2-A design [0]. They only licence the architecture. The core is quite interesting, as it's doing dynamic recompilation for an underlying VLIW architecture.

However, NVIDIA Orin[1] (followup for Tegra Xavier) will use a Cortex-A78 core[2] (formerly Hercules) licenced from ARM.

[0] https://en.wikipedia.org/wiki/Project_Denver

[1] https://nvidianews.nvidia.com/news/nvidia-introduces-drive-a....

[2] https://en.wikichip.org/wiki/arm_holdings/microarchitectures...

> MS and Google don't make chips

MS designed and produced custom silicon for HoloLens 2 (the Holographic Processing Unit 2.0) [0][1]. The Microsoft SQ1 in Surface Pro X is probably also produced by them, though the design is in collaboration with Qualcomm.

[0] https://www.hotchips.org/hc31/HC31_2.14_Terry_Microsoft_Aug2...

[1] https://youtu.be/IjxpMZUqu6c?t=3814

Notably they return invalid results for queries without EDNS information from only Cloudflare.

This release dropped support for macOS due to Apple being unpleasant with Nvidia.

Zink has next to no optimization effort so far and is thus very slow from what I've read. Maybe in a few years, since they currently seem to be focusing on compatibility.