I'll throw in my own niche usecase for thermoelectric - deep sky imaging.
I do astrophotography as a hobby (taking pictures of galaxies/nebulae/etc). This involves doing long, multi-minute, exposures repeatedly all night long. The heat generated from such long exposures produces what are called "hot pixels" - noise generated by heat disrupting the electronics.
To combat this, dedicated deep sky imaging cameras run a thermoelectric cooler to bring the sensor to sub-zero temperatures. These sensors tend to be about 23.5×15.7mm in size.
Niche, sure. But I saw an opportunity to bring up an aspect of my own life where I sincerely do not think even the smallest compressors would be practical. Plus, the lack of moving parts in thermoelectric is very attractive.
The unique thing about astrophotography is that the subject that we are imaging is (relatively speaking) static. Any slight deviation, even the smallest detail, that is not structurally accurate is PAINFULLY obvious.
As an aside, we do use traditional neural networks for certain processing steps. Deconvolution and noise reduction are very common. However, these are only helping in correcting errors caused by viewing conditions. They are not the "imaginative" AI that you are dreading.
I had a feeling something like this was true, thank you for confirming it!
I would actually be more worried about a knowledgeable human engaging in clever Photoshop alterations, or pasting different images together. Is this an issue in astrophotography? Are there ways to easily detect this?
How is it odd and entitled for an end user to not like it when things suddenly break?
That is, I believe, the entire point of the parent, is it not? That this whole migration was not quarantined to the Python developer community. That it spilled over to users in totally unrelated spaces.
> Russia in rubble in two weeks from sanctions and Russia out of missiles in two weeks.
I'm not sure I ever heard such promises. In fact, I distinctly remember the opposite being the general zeitgeist of the time - that Russia would rollover Ukraine with little resistance.
Of all the things to backup, how does a technician NOT include Documents/Pictures?
"Oh, I know, better save these DLLs. Also, a copy of the registry juuuuust in case they changed some obscure IE8 settings and want that on their new system."
I'm not so sure about this one. Software development is quite usually "build functionality to serve a given use case" whereas this line of inquiry is more along the lines of "find a use case for the given functionality".
Perhaps if you intend for the conversation to head into a chat about charting and data science?
Some time ago I got into the habit of naming my home network after Pokemon that I happen to thought fit well. My Windows desktop is Charizard and it's Ubuntu dual boot is DarkCharizard. My fileserver/Docker box is Metagross. My wireless SSID is Raichu, my laptop is Pikachu, and my phone is Pichu. And so on.
ASN.1 is specified as a compilable language. Open source compilers, such as snacc, have existed for 30 years. ASN.1 also defines multiple encodings, DER is used in crypto as you can compare encoded blocks bit by bit. Other encoding rules, such as BER, are tagged. Protobuffers is the same thing re-invented by people who probably never saw ASN.1.
This is the precise insight that jumped out at me.
I often get raised eyebrows when I state that, by my definition, Python and Javascript are among the mostly brutally difficult programming languages out there.
Python is a wonderful candidate for one-off tooling and experimentation, particularly because the cost of wild explosions in these cases, and the odds of requiring long term maintenance, are rather low. However, if your plan is to hire fresh college grads, hand them a Python 2.7 interpreter, and ask them to a build a mission critical, 200k+ line, product - that just seems professionally negligent.
I do astrophotography as a hobby (taking pictures of galaxies/nebulae/etc). This involves doing long, multi-minute, exposures repeatedly all night long. The heat generated from such long exposures produces what are called "hot pixels" - noise generated by heat disrupting the electronics.
To combat this, dedicated deep sky imaging cameras run a thermoelectric cooler to bring the sensor to sub-zero temperatures. These sensors tend to be about 23.5×15.7mm in size.
Niche, sure. But I saw an opportunity to bring up an aspect of my own life where I sincerely do not think even the smallest compressors would be practical. Plus, the lack of moving parts in thermoelectric is very attractive.