Start simple add the rest later when you needed it. How will you know you need it later? At 3AM. If it makes you feel better add a comment what will be needed when it breaks.
I see over and over wildly overdone code. When all I really wanted was some simple if conditions and a couple of loops. But that doesnt scale to XYZ per ns. Does it need to?
Yeah that probably should just be an option. Basically the default is to least mangle the zip file. Where the most extreme is turned on by flags. One of those could be 'remove empty folders'.
Heh, not sure why but it makes me wonder if you could 'Ship of Theseus' something like that into a modern day desktop. By going thru the different eras of DIY compute.
Yeah I was thinking that. Also at some point you will be switching motherboards every other cpu update just due to the socket changes between generations.
That can happen many times during a buyout. Some company buys a thing. The problem then is ownership of the thing. Who in the new company is going to own the 'make sure it stays good' problem. Sometimes with a buy out the people who were doing that may even stay at the company. But it is a matter of motivation. MS has a real serious problem. You can see the gaps where they have glued together at least 10 companies together and called it microsoft. They have a huge reputational risk issue. Where something breaking in the xbox div can have a negative impact on the tools division. Also the other way around. They lack focus on many items. They have needed a 'service pack 2' stop the presses moment and fix this mount everest of tech debt.
Sometimes also the project is just 'done'. I many years ago made a windows screensaver (never released to anyone else). Just so I could have a '2001' screen saver. Basically in the background of the movie was all these screens flashing just weird status stuff. It was a cool aesthetic I kinda liked. Spent many weeks getting it to flash 'just right' and have the right animations for the right feel. Then LCD screens basically killed any need to have a screen saver. As basically instant on/off meant there was no reason to have the monitor running all the time. So the project was done.
IoT was an absolutely terrible fit for the home space. My parents have light switches in their house installed in the 1940s. They still work just as good. Getting something from the IoT of home automation to last like that is very difficult. Yet it seems to be the first model everyone reaches for when talking about it. If they had to replace the switches it would not cost too much to do either.
IoT really comes into its own space though when you pair it up with something that is a real pain to get to. Think somewhere you have to have a crainlift and a 4 hour drive just to touch the 20 year old computer something is hooked up to. Or basically anywhere that takes hours to get to. The space my company typically targeted was high rise air con companies. Or companies where the customer would service out any sort of PLC work to a 3rd party. At that point the savings of having to roll a guy out there vs looking on a computer has the thing pay for itself in 1-2 trips. Also the ability to show up on site with the correct parts. That alone was a huge savings.
IoT's big issues is you have to beat many things that are already dead simple to do.
reply