TWAIN was not limited by PhotoShop, native (and naive) MS application "Scan & Fax" supported it too, and many other raster editors and document organizing applications too.
Also, TWAIN is not Windows-specific! It is (was?) supported on Windows, Linux and macOS. It was not invented by MS or Adobe, but by working group where MS and Adobe doesn't present!
It is supported by vueScan (of course), but Classic Mac doesn't.
Film photography revival goes full swing, I hope there will be new good film scanners with MF format support. Nikon CoolScan 9000 costs unreasonable money, if you factor in lamp which can burn-out and overall age of the machine. And drivers are pain in the ass on modern systems, though, again, vueScan supports it. But ICE (dust removal) works better in Nikon software.
Windows officialy removed support for WebDAV. It still works, but nothing is guaranteed. It has stupid limitation on file size of 10MB, it can be lifted to 2GB (max signed 32 bit number) in Registry, but it is still not very much in modern world (I wanted to share my medial library via WebDAV and failed due to this limitation). It lose credentials on regular basis, errors are too vague («Wrong credentials» means both mistyped password AND expired server certificate), etc.
It is why I (right-handed) was tфught by my first boss on first job in 2000s to use left hand for the mouse: secondary hand for secondary task (I'm not designer, artist or pro-gamer, so keyboard is primary tool).
Now I have a big problem with this: there is no good left-handed mouses on the market anymore, and symmetric mouses has right-handed buttons (and no thumb buttons like forward-backward or left-handed side). Buttons can be swapped in OS, but it messed up remote access like VNC or RDP to systems without swapped buttons... So, buttons must be swapped physically. No luck.
Most of the useful keyboard shortcuts are chordable from the left hand. Left mouse is inconvenient for that. I'm lefty and stuck using left mouse periodically due to injuries and I don't love it but it's tolerable. For the mouse situation I just stick to symmetric 3-button mice and never swap buttons so I can change hands or have a coworker use the mouse uninterrupted.
I also mouse left-handed, but it never occurred to me to swap the buttons from the right-handed configuration. It's always been a practical thing. The only mice I'm likely to have within reach at any point are probably right-handed, so I just had to learn that way. Left click with middle finger, right click with index.
I would kill for a true ambi five-button mouse to replace my old Microsoft Intellimouse, but I've run into the same problem, they just don't seem to exist anymore. All five button mice on the market either have both buttons 4 and 5 on the left side for righties, or have a grotesquely unbalanced design in some other way.
> I would kill for a true ambi five-button mouse to replace my old Microsoft Intellimouse, but I've run into the same problem, they just don't seem to exist anymore.
I was going to say Steelseries Sensei but it looks like those have been discontinued.
Looks like Steelserise Sensei Ten is ambi, symmetrical, with two additional buttons on each side. But not on a cheap side. If you can find one. It is still present on site, but I cannot find places which sell it.
It has one problem: buttons not swapped physically! Yes, leftmost button is primary one (first), and rightmost is secondary (third).
I have this one and use it, with software swapping, but each time I login to remote computer via RDP I need to un-swap in settings again and then back :-(
It is striking, that Logitech forgot how to make proper left-handed mouse. Their older models (discontinued for long time) were perfectly Ok!
Also, it very small for my hand. But better than nothing.
Fwiw this is how cars work when you change to a country that drives on the other side of the road. It seems like mirroring the car would make sense. But really everything is shifted to the opposite side as a translation without reflection. It's easier to manufacture, but as many of you will know and is apparent to all rental agencies, adapting doesn't take long for the average driver, even on manual transmission.
My trouble is I really do want an ambi mouse, not a lefty mouse, since I like to switch back and forth (and always game right-handed.) Maybe I should just get one of each..
> - My ISP gives me a /64, what am I supposed to do with that anyways?
For me, it is main problem. /64 is too small: SLAAC needs /64 per collision domain, and I have more than one (wired network, my WiFi, guest WiFi, control plane for UniFI APs), and it is painful to distribute /64 among them. I'm using HE tunnel which provides /48 to client and it is easy to configure, as intended.
There is recommendation (SHOULD, not MUST in RFC lingo) for ISPs to provide at least /56 to clients, but most domestic ISPs ignore this recommendation.
> - What happens if my ISP decides to change my prefix ?
And it is another problem: tooling. There is no standard way to reconfigure router with dynamic prefix(es). Yes, it is possible to write scripts for it, but it will be fragile. No Linux distribution or FreeBSD is ready to have dynamically allocated prefixes. It is not a real problem with IPv4 because real life practice to dynamically allocate one address and then configuration changes are trivial, and if you are delegated /24, it is typically static delegation.
Somewhat tangent: x86-based laptops of this brand (it is new to me, I never meet Tuxedo Computers before) looks attractive, but there is no information about their screens main property: are they glossy or matt?
My wife is very sensitive to glossy screens and we have big problems to find new laptop for her, as most good ones are glossy now.
If she's ok with macOS, the new "nano-textured display" options on the MacBook Pros are very nice. I'm typing form one right now. It has the sharp color response of the glossy displays, but absolutely no noticeable glare.
KiCAD becomes better and better, but one limitation embedded into its DNA is very annoying: one project - one schematic - one PCB.
It is very kludgy and cumbersome to split project into several PCB (for example, stack of PCBs connected by backplane or headers, like Arduino & Shield for it) and/or to have variations of the PCBs for one schematics, like TH and SMD variants of the PCB for exactly same schematics.
Even in my very modest almost-electrical (as opposed to electronic) projects I need one or another from time to time.
As far as I understand it is limitation which is not easy to fix, because all architecture of KiCAD is based on this 1-1-1 principle.
My workaround for multiple PCB's for one schematic is to have the schematic as a top level sheet which can then be imported into sub-level projects. so each PCB becomes it's own project but use the common schematic sheet
reply