It's a no-name mini PC with four HDD bays. It doesn't seem to exist anymore.
It's a weird Chinese board with a silly gen1x1 pcie link to a 4 port sata controller on a daughter board. I bet it was designed for the 2 port version of the controller and two bays. And some lhow they sold a 4 bays version. So I only have half the bandwidth required to drive the 4xHDDs. Sucks for linux raid.
Interestingly this tiny mobo also has two full speed sata ports on it, that are completely inaccessible, I am not even sure a low profile and thin sata cable can even fit in there. Maybe one day I will try to solder in place from the mobo to the daughter board.
No, it's a generic android keyboard and works with all apps. But you need a keyboard like it (arrow keys, ctrl, etc.) for termux to not be a total PITA to use.
(Android has full physical keyboard support, so with it you can use Ctrl+A/Ctrl+X/Ctrl+V in all input fields. Usually a lot faster than fumbling with the touch equivalents that keep randomly bugging out…)
To add to this you can define custom keyboards quite easily for just about any unicode character you can imagine and more. It is an extremely underrated keyboard. It doesn't come with autocorrect built in though, but i barely notice. The privacy it offers is a nice touch, and its functionality unmatched.
It depends on what you want. If you want to install an old copy of Visual Studio from 20 years ago then you should be able to write a program and compile it and have that work on XP. But that comes with limitations. You're not going to be able to use even C++11 and will be stuck with C++03, or maybe even C++98. If that's acceptable to you then it can work. But if you want to compile something that somebody else wrote or want to use some library that somebody else wrote, it probably won't work in that environment.
Or you could install and old copy of Cygwin or MinGW.
Do you want to run a modern Visual Studio and target XP? Maybe you can make that work if you install an old platform SDK and set WINVER and _WIN32_VERSION and work around all the warnings and compatibility problems that you'll run into. It is fighting an uphill battle and it will continue to get worse with each new version of VS that you want use.
For rust there is Rust9x https://seri.tools/blog/announcing-rust9x/. But I think this is the effort of handful of people. It is behind the upstream rust and it could go away at any time. If you want to write a toy program in Rust then it is fine, but if you want something that's going to be supported long-term you're rolling the dice.
Python 3.4.4 is the last version of Python that will run on Windows XP. That's 10 years old and many things on PyPI now require newer versions of Python so you'd be stuck with old, unsupported versions of those modules, possibly containing security issues.
As far as I'm aware so long as you limit yourself to APIs that were available in XP you don't actually need an older SDK to develop for it with modern MSVC. The early windows platform layer stuff in the handmade hero series demonstrates doing so without anything like Cygwin or MinGW.
Most new APIs introduced since Vista are COM based, and after Windows 8, WinRT based (basically COM with IIinspectable, application identity, and .NET metadata instead of type libraries).
Plain old Win32 C API is basically frozen on Windows XP view of the world, although there are a couple of new .....ExNum() suffixes for stuff like HDPI or various IO improvements, the userspace drivers initially COM (UMDF), but reverted back to plain C struct with function pointers on version 2.0.
The only officially (at least partially) supported way from Microsoft is to add into Visual Studio the toolchain named "C++ Windows XP Support for VS 2017 (v141) tools". It is still there in the "individual components" of Visual Studio Installer for the latest VS but it is marked as [Deprecated]. It is a safe bet that MS will never fix any existing bugs in it or update it so at this point your best bet might be with the open source tools.
All other currently supported toolchains rely on runtimes that are explicitly not compatible with Win XP.
There were issues and outages for weeks after the layoffs though. Many people also believe its overrun with far more bots than when it had more robust content moderation tools and teams.
Also things break. Vulnerabilities come along that need to be carefully patched and deployed. Tools and packages get depreciated. Updates can be done to save compute, and money. Things don't just hum along with zero intervention by no one for years and years.
I would like to point out the long term prospects part may not be true for high earners. Some models make a senior software engineers annual salary in a matter of months. Many of these people can retire and live off investments at age 35.
Perfectly fair point! Although when I've seen OF stats published the median model makes like $1,000 a year or something. So I think if you took even the top 5,000 models out of the computation, most of them are not earning enough to pay for a nice lifestyle in the moment, let alone funding retirement by the time their beauty declines.
What I think is more likely to happen though with an immigrant OF model (who isn't in that elite earning tier) is that she meets a partner in the US, which affords her an exit strategy if she doesn't want to (or can't) keep doing OF forever.
This is cool. So "175mAh battery, 4 weeks standby time" what is the battery time during normal use? Not just sitting on a shelf. Use all day at work, sleep tracking during the night, etc.
reply