there are several good articles explaining this, especially on Timescable blog, but in short, without time partitioning and just index, at some given point the performance for reads and writes degrades exponencially.
jasonshen's blog is awesome! And regarging the case, that is basically what my father did. Left a corporate job to run his own small business 25 years ago and he has been much happier ever since.
With many news articles on the North Korean missile that flew over Japan yesterday, one obvious question is not even mentioned: why didn't Japan shoot it down? But an article from 2017, at the timing of the previous occurrence might explain it. Maybe it simply cant'.
This is indeed a hard problem, when you have a country like China, with a long term strategic plan and control over its companies and a country like US in which companies are more focused on keep Wall Street and media happy.
That is my opinion. LOGO had several changes along the years, such as bringing Ethernet many years ago when it was usually an expensive expansion in other brands. So I see it as a compact and affordable piece that if does not continue to innovate and bring more value it will loose market to others like PLCnext and industrial grade Arduino/Raspberry Pi based ones.
For the next years, to remain relevant, Logo needs:
- Higher input frequency
- MQTT with SparkplugB support
- Compute module, even if as optional, to allow container installation and Edge processing, possibly also ML with GPU add ons
They do that on a higher level, after the PLC. But for PLC, you need something robust and is not easy for them to it just for themselves without scale.
There is no legacy OS as when you start it it simply starts running the program. You just need to program it on a computer, but the software suite is always updated. It is ugly indeed, but not broken.
I understand that for those that have never looked on Operational Technology this looks pretty unimpressive and obsolete. And for a great part it is. For more modern devices and you search for Opto22 and PLCnext. They have not only the controller capability but also can run Linux and deploy containers.
It is just a matter of where it is acceptable or not. If one hour of downtime will cost 100 of LOGOs, production managers won't take a risk with an Arduino not rugged.
It is for different applications usually. These kind of controllers exist for a very long time and they are built to last several years (like 10, 20, even 30) and they can handle rough environments such as a wide range of temperature and dust. Arduino is now popular and great for prototyping but many won't accept simply the board on a industrial and mission critical environment.
I'm totally in favor for more positivity. It is very easy to criticize something when you don't know what is happening on the other side. HN is a place for Hackers to discuss facts and not to imply what they think others think. If two comparisons differ, there might be several reasons as lack of trials on both sides or lack of a common ground for comparison but a lot here are doing their best to make lives of developers easier.