ryao

47 ms·

631.
by ryao 2y ago
> Among other things, this would only work if your client is written in a language that supports C structures. Such languages are used at both ends. Otherwise, this would not have been working in production for ~13 years. > Says the o
632.
by ryao 2y ago
Monoprice has low cost cables.
633.
by ryao 2y ago
> It's not just accept. If your socket is non-blocking the same applies to read, write, and everything else. You keep syscalling until it returns EAGAIN. You do not call read/write on a socket that is listening for connections.
634.
by ryao 2y ago
He said elsewhere that he does not even use Rust. He uses typescript. I am confused why he is bothering to push Rust when he does not even use it.
635.
by ryao 2y ago
If it is any consolation, early C did not have dynamic linking either. It was added afterward. From what I understand, UNIX systems had statically linked binaries in /bin until ELF was introduced and gradually switched to dynamically l
636.
by ryao 2y ago
I suggest -Wall -Werror for code hygiene.
637.
by ryao 2y ago
Well, Xenix was extremely popular since it was the cheapest option on x86. That said, I doubt Bill Gates would have hired Dave Cutler had he stuck to Xenix.
638.
by ryao 2y ago
It does not prove that the driver will not crash the kernel. It should be fairly easy to find a driver that passed QA testing under that tool, yet still crashed the kernel. You just need one of the many driver developers for Microsoft Windo
639.
by ryao 2y ago
From your own link: "Driver Verifier is not normally used on machines used in productive work. It can cause ... blue screen fatal system errors."
640.
by ryao 2y ago
Yet drivers that have passed Windows Hardware Qualification Labs certification have had blue screens. Also, Microsoft hands out Windows kernel driver signing keys to anyone who pays them. You don't need to have a driver go through the
641.
by ryao 2y ago
The description is accurate compared to what you get from other more established systems languages.
642.
by ryao 2y ago
> Sorry, it says that in their FAQ[0]. It also says "Should I learn C before I learn C++?" "Don’t bother." and proceeds to advertise a Stroustrup book[1]. They also would say "Don't bother" about using
643.
by ryao 2y ago
Almost nobody using C (or C++ for that matter) has read the standard. The standard exists for compiler developers. If you want to read the standard, you can get copies of the drafts for free. It is an open secret that the final draft is bas
644.
by ryao 2y ago
Some people want to use them, they are useful in some contexts and they often already exist in some form elsewhere, but the majority of people often do not need them. That said, when you learn a foreign language, you do not learn every word
645.
by ryao 2y ago
Astree claims to be able to prove the absence of runtime errors in both C and C++, without requiring the use of subsets: https://www.absint.com/astree/index.htm By the way, C has a formally verified C compiler: https:
646.
by ryao 2y ago
The other guy said "Maybe your program worked due to the bug they fixed.". The RDRAND fix achieved exactly that.
647.
by ryao 2y ago
Only superficially. You cannot specify a past version of Rust where features existed that have since been removed by doing that. You also do not have a situation where two different incompatible languages are being accepted by the same comp
648.
by ryao 2y ago
Use language features not considered “stable rust” that are later discarded and you will learn it is abandonware very quickly. In any case, you asked for proof and now have it. You should be saying thank you instead of trying to argue.
649.
by ryao 2y ago
At a glance, the code is compatible with all C standards ever published. You are too fixated on learning the latest. The latest is largely just a superset of the earlier standards and the new features are often obscure things you are unlike
650.
by ryao 2y ago
Whether you need -dev packages (for headers) depends on your operating system. I run Gentoo. All headers are always on the system. Other distributions ship the headers separately in -dev packages to save space and you need to install them.
651.
by ryao 2y ago
I was not asking for that. I was answering your question. You asked for evidence of rust releases being abandonware. I gave it to you. Someone else trying to ameliorate Rust releases does not change this reality.
652.
by ryao 2y ago
Autocorrect seems to have made a typo worse here. It was supposed to be now, not his.
653.
by ryao 2y ago
Are you unable to use search engines: https://www.learn-c.org/ There are so many free learning resources for these languages that it is ridiculous to say that you need books to learn them. The books are great, but non-essen
654.
by ryao 2y ago
You do not need to know about modern features to write code in C. This is part of computer science.
655.
by ryao 2y ago
C and C++ are two different languages. They are versioned by years. Rust technically does not have versions. The rust tools have versions. Basically all versions of C are binary compatible with each other. I suggest you actually learn and u
656.
by ryao 2y ago
It really is not that complicated. You just use -llibrary when linking and it links.
657.
by ryao 2y ago
Do a web search for rdrand and systemd.
658.
by ryao 2y ago
Rust does not guarantee that all bounds checks can be proven correct at compile time, so it relies on runtime bounds checks. If this does not implement the same bounds checks, then probably not.
659.
by ryao 2y ago
I know a guy who used to love Rust and his cannot stand it. The hype wore off in his case.
660.
by ryao 2y ago
In COBOL’s case, nobody really wanted to write software in it in the first place. People used assembly or FORTRAN at the time. MBAs wanted a language corporate secretaries could use, so they made COBOL. It failed at its main purpose, but si

More ›