The only thing I'm confused about is why more C standards keep coming out. C is what it is. Work with the archaic parts of it as need be. You use C for ultimate cross-platform compatibility (every exotic platform and its mother has an ANSI-C/C99 compiler). If you're able to run on the most bleeding-edge C compiler supporting the most recent WG version of C... then why not just use another language? I say this as someone who loves C. If there are bits that feel old, you just create a DSL to get around these problems that compiles down to C... but you don't change C itself.. Just my perception working with all this for many years now.

Yep

At recent jobs, however, these have been taking place at a much lower level and requiring a deep knowledge of networking in the Linux kernel. I've found the transition difficult and also have found it difficult to find a unified reference for all things Linux networking. The ones I find are either too basic or targeted for SysAdmins.

What I would love to find is something in the style of a Beej's Guide to socket programming (https://beej.us/guide/bgnet/) but covering the following:

1. Overview of Linux networking, including firewalls and routing tables.

2. The lifecycle of a packet through the kernel from coming in "over the wire" through delivery to an application socket (and vice versa).

3. An overview of network interfaces, virtual network interfaces, and the utilities to set them up, tear them down, and configure them. Also covering things like TUN/TAP devices, VLANs, PVLANs, network namespaces, etc (targeted for developers).

4. An overview of all the linux tools to shape traffic (queuing disciplines, etc) and measure network performance.

I have cursory understandings of each of these, and have had such a hard time finding a universal reference (again, the same way Beej's Guide is the de-facto reference for socket programming). Many books that seem to cover the topic are decade(s) old. Thanks for any help.

Comments URL: https://news.ycombinator.com/item?id=36179802

Points: 1

# Comments: 1

  Location: DMV (DC, Maryland, Virginia)
  Remote: Hybrid preferred, but flexible for any arrangement.
  Willing to relocate: Probably not.
  Technologies: C, Rust, Python in Linux environment. Mostly do distributed systems, network protocol design and analysis, and related work. Worked in Aerospace flight software, embedded systems, space mission operations, etc. "Research Engineer" fits my ideal scope-of-work best. Other non-technical/management/leadership activities not mentioned here. I seek to avoid working in product-oriented "Agile" teams.
  Résumé/CV: On request
  Email: vb.temp@gmail.com
  Other: MS and BS in Computer Science. Security clearance (detail on request)

But he's just another guy that has to turn tricks with some new variant of "durr hurr liberal plan for X is elitist and a luxury belief."

It's a little personal with him, because right before the 2020 election he posted something pretentious like "In 2016 I bet and won a lot of money on the outcome of the election, and I bet even more this time" (Implying his non-elitist background gave him the clairvoyance that Trump would win. I asked him who he bet on this time. Then the results came in and Trump was clearly losing in 2020, and then he blocked me.

In the end, even if we agree with him, he's just another culture warrior that whose livelihood depends on feeding the angry masses outrage at whatever Team Blue/Team Red is doing.

I guess if I could rephrase my original question: People who are going to adopt C23 - who are you and what field/industry/line-of-work are you in?

Asking because in my line-of-work, C is ubiquitous and I personally love coding in C, but anything beyond ANSI C (or C99) is "cool" but undermines the point of C as I've used it, which is its use cross-platform for a huge set of common and uncommon architectures and instruction sets. If something only needs to run on common, conventional platforms, C, however much I love it, would no longer necessarily be a strong contender in light of many alternatives. It seems like these standards target an ever shrinking audience (much smaller than the whole universe of software developers working in C).