Expecations have changed.
It is 2004, your company needs a simple CRUD app so your employees can work with some structured data in a DB somewhere, let's say so sales can check inventory levels in an existing database.
A single developer can start up a Winforms project and throw something together in a matter of days to weeks. It can only be used by people on desktops running Windows while they are at the office, but that is fine because that is the world of 2004.
2022, your sales team needs to access inventory levels in a database. Assuming you haven't already been sold some multi-million dollar solution to do this (and you likely have, multiple times, and at least some of the implementations have failed), you now have the following requirements:
1. Some of your employees use Apple laptops, some use Windows.
2. People want to be able to access the data on their phones as well, which adds another 2 OSes to the mix.
3. Restricting the app to being onsite in the office doesn't cut it.
So, you can write 4 (!!) native apps. The ugly WinForms one is still simple, but you can either adopt a proprietary "simple app building" solution for the other 3 OSes (or just use it for all 4 OSes), and have serious issues finding devs who know the niche tech you've picked, or you can make a website.
Now, native apps on smart phones are a constant maintenance headache. Major OS releases break things on mobile all the time, and entire APIs get deprecated. (Another reason why writing against Windows is good, that Winforms app from 2004 probably runs just fine with 0 changes in 2022) It is easier to maintain 1 website than 2 mobile apps and 2 desktop apps.
So, website it is.
What framework are you going to use? Whatever one is stable, easy to hire for, and has the best tooling. OK so I wouldn't call React "stable", hopefully it has undergone its last major redesign for awhile (LOL), but there is tons of tooling for it. Of course the docs suck compared to what Microsoft had in 2004, because it turns out part of that $500 per seat license for Visual Studio went towards amazing documentation and example code. And because Web you'll get breaking changes now and then, but it still is easier than maintaining 4 native apps.
People underestimate how simple Windows everywhere made life for developers. Amazing documentation, stupid good tooling, and an obscenely stable platform to develop against. A major OS version came out what, once every 3 or 4 years? And unless you were writing drivers, that major OS version wasn't going to break anything.
Just a minor nitpick, but the NT device driver API has in fact stayed largely the same since Windows 2000 and in comparison to the various technologies that came and went in userland.
If I pay someone $100 to come clean my house and they take my money and don't clean my house, its no different than if they came into my house and stole $100. It's legally different, but there's harm being done and I consider it theft. It's not complicated.
In regards to slacking, there's no expectation that someone is working 100% of the time and no reasonable person would expect that someone is working 100% of the time. But a reasonable person would expect that they work some of the time, perhaps a reasonable amount based on the work of their peers.
> Most managers would expect you to share in terms of how it affects you, not some vague air of "they don't do anything":
I've been a manager and worked with lots of managers. I strongly disagree and this is not what I've seen. They want to have more information about efficiency and happiness on the team that they're managing. And they certainly want to know if someone is not working... at all... for over a year...
You can tell them and if they say "don't care", so be it. But a reasonable manager would want to know. I don't know if you've ever been in a managerial role, but I suggest you have a talk with superiors about this hypothetical and get their opinion on it.
It is not OP's house though. He is just another employee, so it's none of his business to worry about this. Your argument sounds just like an excuse to morally justify snitching on co-workers.