413 karma · joined August 11, 2023
Similar with header files. Issues arise if there is a "misuse" to derive actually not a compatible but competing solution.
And "a few moments later" happens the same as with those "cost effective" clouds.
[1] https://www.heise.de/en/news/IDC-Many-companies-want-partly-...
[2] https://www.idc.com/resource-center/blog/storm-clouds-ahead-... (original)
[1] "debhelper: support for split debugging symbols"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=215670
[2] https://salsa.debian.org/debian/debhelper/-/commit/79411de84...
Never thought the difference mastering writing can be so significant. Just like to add what I understand regarding this. It's rather about not making any mistake writing by hand ca. 1-2 DIN A4 pages while someone reads a text (slow enough). I can't remember exactly but making only one (or two) mistake(s) and it is not anymore excellent (just good). Making 4-7 mistakes and it is not good (just sufficient). Making few more and it is bad which means failed. It's a long text with a very short path to fail.
Ukrainian is less difficult to write. There are claims that standardization/reform of Russian made it more artificial (far from natural people language) with overtaking too many words from Latin languages. When I read / listen to Belorussian I think they have even more luck with matching pronunciation/writing than Ukrainian. Which suggests this language is even closer to the common roots old language. (I'm not a linguist.)
$ wc -l ...
265908 sqlite-amalgamation-3510100/sqlite3.c
Is there any as large as possible single source (or normal with amalgamation version) more or less meaningful project that could be compiled directly with rustc -o executable src.rs? Just to compare build time / memory consumption.I'd say the amount of L3 is not increased but adapted/scaled to the increased core count, since per each core there is still the same amount of cache available as before.
We get faster cores, so we need to get from 5600 to e.g. 6000 DDR5. Since core count is increased by 50%, we'd need 9000... DDR5^W, well yes, we'd need actually as planed before AM6 and DDR6!
Considering PC desktops. DDR4 is 3200 MT/s max JEDEC. DDR5 is available on AMD since 3 years and is 5600. DDR6 specification is almost finished. It looks like DDR5 will double performance just right before new DDR6 DIMMs appear. Thus I'd expect DDR6 to double the bandwidth just as late when the new memory standard arrives.
Observing server mainboards reveals many PCIe 5.0 connectors for cables to attach PCIe-SSDs looking similar to SATA ones.
Recently some UI ignored my action by clicking an entry in a list from drop down button. It turned out, this drop down button was additionally a normal button if you press it in the center. Awful.
> UI creation compared to MFC
Here I'd prefer Borland with (Pascal) Delphi / C++ Builder.
> relative resizable layout that's required today.
While it should be beneficial, the reality is awful. E.g. why is the URL input field on [1] so narrow? But if you shrinks the browser window width the text field becomes wide eventually! That's completely against expectations.
I can't imagine what I'd be doing without MATE (GNOME 2 fork ported to GTK+ 3).
Recently I've stumbled upon:
> I suspect that distro maintainers may feel we've lost too many team members so are going with an older known quantity. [1]
This sounds disturbing.
[1] https://github.com/mate-desktop/caja/issues/1863#issuecommen...
Similar to polluted air/environment such deaths will hardly be backtracked to the true roots.
The most recent were deaths in conjunction with COVID. Was it due to COVID directly, indirectly or it was so bad that COVID could not really make it worse...
I'm missing nanobind here.
> Method lookup. Python sees a.dot and searches for the dot attribute. It checks a.__dict__,
> Each attribute access (self.x) involves:
Dictionary lookup in self.__dict__
Since C++ classes are fixed, I'd expect attributes to be declared once in python (slots).One thing yet important for cross-language projects: callbacks (events). Would be nice if the sample could be extended.
Just looked at standard desktop: still no 64GB 5600MT/s modules. CUDIMMs are missing 32GB.
> And don't forget about Nanya
BTW, what is the status of Elpida now?
> China's AI Analog Chip Claimed to Be 3000X Faster Than Nvidia's A100 GPU (04.11.2023)
https://news.ycombinator.com/item?id=38144619
> Q.ANT’s photonic chips – which compute using light instead of electricity – promise to deliver a 30-fold increase in energy efficiency and a 50-fold boost in computing speed, offering transformative potential for AI-driven data centers and HPC environments. (24.02.2025)
https://qant.com/press-releases/q-ant-and-ims-chips-launch-p...
Since DDR5 has 2 independent subchannels, 2 additional chips are needed.
I've been thinking mathematicians have fun doing math, making discoveries, crafting proofs.
Does Tour de France & Co. make no sense since small, lightweight and powerful e-bicycles appeared?
Using computer as a helper like bicycles is one thing, using LLMs seems more like e-bicycle and is something another.
11 years after specification released.
DDR4 makes it possible since 5 and half years to build 128GB AMD PC using 4x 32GB DDR4-3200 1.2V JEDEC modules. Only since half a year it is at last possible to build AMD PC with 128GB DDR5-5600 RAM. Because Ryzen DDR5 controller cannot operate with 2 sticks sharing the same channel at JEDEC speed/voltage.
DDR4 just cannot be EOL already because of unbuffered ECC! Even today it is not possible to have 128GB with 2 DDR5 sticks on AMD. Only 96GB.
And actually I'd expect 256GB (DDR5-8800 1.1V JEDEC) to be possible with DDR5. We're now only from 4000 to 5600 5(!) years since the specification was published. What if AMD achieves this only few months before DDR5 EOL?..
> DDR6 will be out in 2026 with consumer availability in 2027
... or not at all?..
> you’re still writing at 1.5GB/sec.
Except of few seconds at the start, the whole process lasts as if you had PCIe 2.0 (15+ years ago). Having so fast SSDs there is no chance to make a quick backup/restore. And during restore you're second time in a row too slow.
It's crazy that instead of using slow PLC at the time of slow PCIe 1.0, back then fast SLC was in use. Now with PCIe 5.0 when you really need fast SLC, you get slow TLC or very slow QLC or even worse PLC coming.
It took AdaCore so long to port the plugin system of the GNAT Studio (GPS) to Python 3 (which seems to be a fraction of the whole code base), that even conservative Debian had to remove the whole GNAT-GPS package.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082332