I'm not questioning what you do once you get to that hypothetical Rustic++. I'm questioning whether it's possible to get there using automated tooling in the first place.
I think you have a point. Rustic++ won't be vibe-coded in a weekend.
Readit NewsGeorgeTirebiter commented on Hardening the C++ Standard Library at scale queue.acm.org/detail.cfm?... · Posted by u/ndesaulniers
GeorgeTirebiter commented on Hardening the C++ Standard Library at scale queue.acm.org/detail.cfm?... · Posted by u/ndesaulniers
There kind of is. There's __cplusplus, which I'll grant you is quite janky.
#IF __cplusplus==202302LI'm wondering if the C++ -> Rust converters out there are part of the Solution: After converting C++ to Rust, then convert Rust to C++ and you now have clean code which can continue to use all the familiar tooling.
GeorgeTirebiter commented on Terminal Latency on Windows (2024) chadaustin.me/2024/02/win... · Posted by u/bariumbitmap
Any chance of getting native support for Serial (DB9/RS232) communication in Windows Terminal? Would love to use it but I'm still using PuTTY and HyperTerminal.
Is there something lacking in PuTTY ?
GeorgeTirebiter commented on x86 architecture 1 byte opcodes sandpile.org/x86/opc_1.ht... · Posted by u/eklitzke
In this case the person was not asking anything. The person was stating they didn't understand. The equivalent in my analogy is a French speaker commenting that they don't understand English without further translation into French.
Geez. I was the first one to comment. It was "This may be great, but... would you please give us more explanations / context." It's not "laziness" but trying to understand how this table is useful / teaches us something. And, to the OP, that a 'typical' HN reader didn't get it.
I know 8008, 8080, z80, 80186, 80286, 80386, 80486, and some fancy opcodes for SSEx. The table still, IMHO, needs further explanation. Some have provided pointers to more info; thank you.
GeorgeTirebiter commented on x86 architecture 1 byte opcodes sandpile.org/x86/opc_1.ht... · Posted by u/eklitzke
I don't understand, without further description of the symbols.
GeorgeTirebiter commented on Let's Help NetBSD Cross the Finish Line Before 2025 Ends mail-index.netbsd.org/net... · Posted by u/jaypatelani
I just donated. It's important to keep projects like NetBSD vital, as a monoculture benefits nobody but the monoculturists. I think of it as a way to help ensure Survival of the Species - by diversity.
I dont think there is nearly enough attention on how much of our great science in the US has come to a complete halt.
China will pick up the slack.......
Our ANNs have abandoned any similarity with brain neural networks basically right after they appeared. As we've learned more about neuro-biology, the gap has simply grown larger.
I've been impressed with CfCs --- and the stuff Liquid https://www.liquid.ai/research/liquid-neural-networks-resear... is trying to do: model neurons as differential equations, and use CfC methods to alleviate runtime ODE solving, using approximations (or tight integral bounds), so there’s often a tradeoff between approximation error and speed. https://chatgpt.com/share/68f2ada8-06ac-8002-9191-269b0cbba4...
The Big question is: WHERE is the Complexity? If Complexity is Fixed in a System, it must be Somewhere. (you can see this at play any time you look at a large software system.) Do you have simple 'blocks' and many of them? OR, do you have more complicated blocks (requiring more computons), but fewer of them? I think this is an exciting research area right now.
Time to re-designed our artificial neural networks
how? Also, is this any different than 'merely' providing more bits of I/O to neurons via this different 'channel'?
GeorgeTirebiter commented on Upcoming Rust language features for kernel development lwn.net/Articles/1039073/... · Posted by u/pykello
Rust is more complex than C, yes, but as someone who has used both professionally, it is not even close to being as complex as C++. In fact it is closer in complexity to C than to C++.
Perhaps you can help guide a C expert but C++ avoider (and super-avoider of Rust, so far): If C is 1 in complexity, where does C++ and Rust fall. By 'complexity' here I mean: the ability to keep the Entire Language in your head at the same time. C, although it does have complex corners, is -- mostly -- not overly complicated. (As you can probably tell, I prefer assembly, because it is the least complicated. You can build your own abstractions up, which is the proper way to use assembly). Thank you for any insight; I'm not wedded to my views when shown a Better Way.