They weren't exotic, they just weren't part of your writing style
The reason "--" autocorrects to an em dash in practically any word processing software (not talking about browsers) is that that's the accepted way to type it on a typewriter. And you don't need to go into any system settings to enable it. It came in around when things like Smart Quotes came in.
Complexity of the fab processes is isn't what the parent was talking about. They're talking about the major changes in the relationship between fabless semiconductor companies and commercial foundries.
The complexity of actual fabrication was always, and still is, entirely within the foundry. But in the early days of that model, designs could be more easily handed off at the logical level, leaving the physical design to back end companies, which makes designs much more portable between foundries. (The publisher analogy.) What's changed is that the complexity of physical design has exploded, and you can't make the handoff at nearly as high a level, and there is much more work that depends directly on the specific process you are targeting. Much more work at the physical level falls to the fabless semi companies. So it is much more work to retarget a design to a different foundry or process.
The site looks nice, but I think you'd benefit from having some beta testers who are not familiar with HW design already. I mention a few issues below, which I hope you take as constructive suggestions of how to improve the site, and not just as criticism.
It feels a bit like you are expecting completely inexperienced users, but the site doesn't quite anticipate their needs. Loading on mobile was not legible (which is fine, it's an early version.) Switching to the desktop version, the instruction for the initial design to "set" a bit is unclear. What is the function you want the user to implement? It's underspecified.
Further, there needs to be an explanation of what a testbench is, before you present a "Run" button, as well as an explanation as to what stimui the TB will present, and even the entire idea of Verilog simulation. It would be good to have an opportunity to see the testbench code and what the site expects the correct output to be; I didn't see an option for that. New users may not understand waveforms at all without an explanation.
The AI component is fine, but it feels a bit like all of the educational aspect has been delegated to the user to ask questions of the AI. A user who is inexperienced would not even know to use the word "testbench" is to frame their questions. I would suggest some careful thought as to who exactly your target audience is, and specifying early on what prior knowledge you expect them to have.
You are buried in the details. The guy is a hero who opposed a fascist takeover of the US government. He's not going to have any difficulty finding employment.
I had a CS professor as an undergrad who would teach a couple of advanced seminars in his own research area. His approach to those simplifications was to announce, "I'm going to lie to you now, but just go with it and I promise that later we're going to learn the real truth." I liked that as a compromise, to make some practical progress, but not to mistake the simplification for full understanding. (And he wasn't rigid about it -- if somebody would ask a deeper question he'd happily answer it to some level and then get on with his plan.)
To allow the sender to set the TTL, right? Without adding another field to the packet header.
If you count up from zero, then you'd also have to include in every packet how high it can go, so that a router has enough info to decide if the packet is still live. Otherwise every connection in the network would have to share the same fixed TTL, or obey the TTL set in whatever random routers it goes through. If you count down, you're always checking against zero.
The best one I saw today (can't remember the source): Suppose you gave your broker money to invest for you, and she bought herself a really nice house instead. That's basically it.
No, it's just false. She pleaded guilty to 7 charges already. We don't know what she'll be sentenced to for those crimes. That's a completely separate issue. She's already pleaded guilty. The source is the Justice Department.
"CAROLINE ELLISON, 28, is charged with and has pled guilty to two counts of conspiracy to commit wire fraud, each of which carry a maximum sentence of 20 years in prison; two counts of wire fraud, each of which carry a maximum sentence of 20 years in prison; one count of conspiracy to commit commodities fraud, which carries a maximum sentence of five years in prison; one count of conspiracy to commit securities fraud, which carries a maximum sentence of five years in prison; and one count of conspiracy to commit money laundering, which carries a maximum sentence of 20 years in prison.
...
"The statutory maximum sentences are prescribed by Congress and are provided here for informational purposes only, as any sentencing of the defendants will be determined by a judge. "
Those are separate issues -- whether crimes were committed, and whether depositors will be made whole eventually. If some of the bets they illegally made end up paying off, enough to reimburse the people who trusted them, that doesn't mean it was legal or ok to take that money to make their own bets with in the first place.
And while John Ray did say they were bad at record keeping, he also said that “This is just old fashioned embezzlement, taking money from others and using it for your own purposes,” he said. “This is not sophisticated at all.”
Programmability is always the biggest issue, and that's not really a chicken-and-egg problem because decades of research have gone into writing compilers and languages for massively parallel machines -- it's just hard, some would say intractable (and local memories tend to make programmability issues worse.) There are niche or embarrasingly-parallel problems that will run great. But it's hard to sell hardware that will solve only some of your problems well. And GPUs have taken over for many of those very regular problems as well.