While I mostly agree, I have some small quibbles which I think will present a more complete picture.
I've had a good developer experience with 74LS00-family SSI chips (like the quad-NAND-gate 74LS00 and the hex-inverter 74LS04), so your mileage may vary.
Just to clarify, the Padauk and Nyquest chips I linked above are one-time programmable (PROM), not mask ROM, except the PFS122 (3.53¢), which is reprogrammable Flash. (It's advisable to debug your code with a Flash chip or an ICE before you start consuming PROM chips, unless you really like to desolder.) Padauk doesn't seem to make mask-ROM chips at all, and I haven't seen any from Nyquest.
I'm not sure what you mean by "highly specialized". They're tiny, slow 8-bit microcontrollers, so you will certainly be disappointed if you go in hoping for STM32-like capabilities. But they're programmable, and their peripherals don't include things like LiDAR pulse timing circuits or AES encryption hardware or anything like that. It's just very general-purpose stuff like watchdog timers and PWM generators.
> Europe's size may not lead you to comprehending the US' size.
Why not?
Europe seems to be about 10 million km2 in land size, and the USA 9 million km2. Are you trying to say that because Europe has bigger land size, it's hard for Europeans to imagine individual states' sizes?
Here's some quick facts comparing population and area
- There are 17 European countries >100km2 but 37 US states are
- 13 states (only one of those is <100km2) has a population density <= Norway.
- The most population dense state is Jersey, at 488 people/km2. 5 European countries are more dense than that.
- 10 US states have >100 people/km2 but 25 European countries do (I'm rounding Albania up)
- California, the most populous state, is smaller than Sweeden, but larger than Germany in area. It has half the population of Germany. 90% of CA's population lives in 5% of the area (near SF and LA)
- Driving North-South through California takes a bit over 13hrs but if you add 30 minutes you'll only hit one of those areas.
- Driving East-West across Texas takes 12 hrs and you'll only go through 2 major cities. You are likely to see more tornadoes than cities and definitely more cows than people (I know from experience)
Most of the US population is in the East and West coasts. With far more in the east. Most of the US is just empty, but also the land is not nearly as nice as in Europe.
I don't think it is hard for Europeans to imagine individual state sizes, but likely won't imagine how empty it is. Hell, even Americans aren't good at that
By everyone thinking you can get 100% coverage across the Great Basin Desert? Yes. Yes I do think that the population density of Europe leads them to think everything is closer and easier than it is.
That one desert, of many, is about 190,000 miles in size. That's half the size of the whole of France.
Are you really saying covering that, with 100% coverage, with no dead spots at all, is a reasonable task to undertake?
If you want to challenge the myth of coverage in Europe forget about size comparisons and look to some of the hard walking trails in remote areas; Via Dinarica Kosovo is known for it's beauty and harsh terrain, not for it's cell reception.
Elsewhere in the Balkans, Romania, et al you'll find blind spots.
The signal in the Kimberley's is shithouse, mate. Last time I was there, I went three days with zero signal, because I was in some more remote communities. That's not really an argument against what I was suggesting, is it?
> That's not really an argument against what I was suggesting, is it?
No, that's pretty much just a tangential straw interpretation of your own design as the signal quality in Kimberley, or lack thereof, has got three tenths of f'all to do with the issue being population distribution rather than size.
Both Europe and the US have low population regions with poor signal.
Upthread I suspect the anecdata about good quality signal in Europe came from somebody who had more exposure to the well trod higher population density parts of Europe and hadn't encounter less covered corners.
> I'm running LTE-only with zero problems for 2 years now without a single coverage gap. Even in the rural parts.
The anecdote, was suggesting that our vast and empty lands are trivial to cover. But as you know, that has nothing to do with reality. I'm so sorry I tried to convey it with a tinch of kindness to them. Next time I'll tell them to pull their fucking head in.
> Are you really saying covering that, with 100% coverage, with no dead spots at all, is a reasonable task to undertake?
Well, do people live in this desert? If not, then I wouldn't say that's reasonable.
But then I don't feel like your replies here are reasonable either and pretty disingenuous overall, so maybe lets just leave it at that, and you can continue believe your country is much bigger than it is.
> Well, do people live in this desert? If not, then I wouldn't say that's reasonable.
It stretches from Reno Nevada to Salt Lake City Utah. It also includes Las Vegas, Ogden Utah, and Provo Utah. But there are plenty of small cities in between. If you drove on the I-80 from Reno to SLC you'd pass through Fernley (23k people), Lovelock (2k), Imlay (200), Winnemucca (8.5k), Carlin (2.4k), Elko (21k), Wells (1.3k), Oasis (34), West Wendover (4.5k), and a few dozen more cities comparable to Imlay or Oasis as well as just as many ghost towns. That drive would take over 7hrs and is over 800km long.
This is not an uncommon setting in the US either. I'm sure there's a few unique paths like this in Europe, but honestly, are there that many? I once drove the majority of the US (I started in The South, so think 24 -> 70 -> 29 -> 80 -> 29 -> 90) and despite driving across almost all of America the biggest city I drove through was St Louis, which doesn't even have 300k people. I think if you counted all the people that were <5km distance from me over the subsequent several days and several thousand kilometers I doubt the number would add up to my stop in St Louis and would only have happened because I went through Sioux Falls (~200k at the time).
I think the comparison here would probably be the Greek archipelago. Or indeed Greece, or even more broadly the Balkans, given how the settlements are mostly in valleys and there's a lot of mountains, but I wrote the next paragraph before thinking of that:
You can go into the absolute wilderness of the states/the waters of the Mediterranean with suitable gear, and there's some dotted isolated communities within the uninhabited territory/EEZ of the greater region.
I don't know if either has good cell coverage. I presume not, given I managed to lose cell coverage even just crossing the English Channel by ferry a few years back.
But no, I don't live in America. I live in the much, much, much less dense country of Australia. Where tourists frequently die, because they believe that they'll have cell signal everywhere.
When I see this, I suspect the vendor is operating under conditions that approach absolute chaos: dumping whatever junk someone imagines might be necessary into the stack with zero resistance, for years on end. Zero effort spent on any factoring that might threaten redundancy.
I'm not saying the tools aren't bloated, but I believe that a lot of the size (sorry, can't quantify right now) are the datasets for each and every FPGA model that the tool supports. This includes, among other things, timing information for every wire in the chip. You really only need the files for the device that you are targeting and you do have the option to install only that, or you can install larger groups (e.g. same family, same generation), all the way up to installing every device that ever existed that the tool supports. That's how you get to hundreds of GB.
Are you sure about that, or is it just a guess? If that is the case, how will the open source toolchains avoid the same problem when they eventually become the industry standard? (I can imagine something like a software repository for serving device-specific information on demand.) Are they planning anything right now?
Xilinx toolchain installations used to include a file which was just the concatenation of the license files of every single open source library they were using somewhere inside any of their own software. Now if you installed two or more components of their toolchain (for example, Vivado, Vitis, and PetaLinux) into the shared installation directory, this same file was installed several times as well. Together, they made up something like 1.5 GiB alone.
Welcome to modern development lol. Try to refactor it and get an answer of "no money for testing".
On top of that, the "agile" mindset all too often also means there is no coherent vision where the project should go, which can and does lead to bad fundamental architecture decisions that need extensive and expensive workarounds later on.
And yes, there have been people describing exactly that in ASML [1], although the situation seems to have improved [2].
We evaluated it BT5.x and the performance was not overly satisfying.