The fact that nobody wants it is telling. It's an uninhabited, landlocked strip of desert with no water. Would be hard to start a new settlement there.
Guess I'll just write my next project in Bash then, after all, if it's a good idea they will come right? Execution can wait until you've got a few hundred mil.
How can you say that before trying? Have you ever tried VR? You can see the pixels, it's not at all immersive. I find it hard to believe that Apple have somehow invented revolutionary display technology before Meta/Oculus who have had about decade to do R&D. Not to mention that "inside-out" tracking is nowhere as good as shown as show at the WWDC keynote.
It's creepy how deceptive phone cameras are. I've noticed in pictures that I've taken that certain elements have been postprocessed to look better than they actually are.
As it happens I had an exit interview today. I have no idea what the author is talking about but I don't think HR retribution because of feedback is a thing in London, at least not as far as I know. I don't care if there's nothing for me to "gain". You know, not everything in life has to be for your benefit. Sometimes what people say is what they really mean and they're not trying to subvert you or trap you.
I will be honest until the day I die. I hate the avoidant, sugar coating culture we've developed. Brutal honesty is a path to big change.
Facebook, Meta, whatever it's called, I won't touch it with a ten foot pole. I'm a major VR enthusiast and a developer but I dumped my Rift as Facebook's tentacles took hold of Oculus.
I can't say I want them to fail because VR is exciting, but I do hope other companies can catch up and do R&D of their own.
This might get me some shit but running away like that isn't a good trait to have. Not for Microsoft, but also not for themselves. This will probably be in the back of their mind for a chunk of their career since they have no closure.
I would expect somebody working on a greenfield project at one of the biggest software companies in the world to tackle issues head on with grace.
The difference here is that the developer of RefTerm is an experienced, professional developer passionate about his craft and building good software. Microsoft is a faceless entity composed of people who mostly don't care about what they do during the day and are just getting by so they can get paid. There's no shame in that. But there is shame in patronising someone when they demonstrate something to be false and locking the thread on GitHub such that no further discussion is possible...
Microsoft is sluggish and delivers products that do the job and nothing more. Sadly, that's the modus operandi of most software companies. That's why nimble little startups are still managing to steal pieces of various markets.
I use Windows Terminal quite often and have definitely noticed its terrible performance. So this is definitely something visible in the real world and not just nitpicking.
There's so many cases where a hacky Exec or five becomes necessary. For example, I am not aware of any Puppet module that does disk partitioning + formatting. Our solution was to write a class with a few Execs to do that. But there's so many edge cases where this can go wrong if it's not truly idempotent. An accidental disk wipe across our fleet would be a disaster, so what did we do? We basically wrapped the class in a big if guard that checks if the disk is already partitioned. That's not idempotent at all of course or declarative - it's just a script.
I can think of another horrifying example. We extract archives on to the machine to a specific target directory, and all files in that directory should have a specific owner and group. So we have a File resource that states the target directory exists which is ordered before the Archive resource. But we need to recursively chown after extraction too because tarballs preserve the original owner and group on extraction. We can't add a File resource with the same path that states the owner and group after extraction because duplicate resources aren't allowed. The only solution in this case is a hacky Exec. And that isn't declarative either because you'd have to check the owner/group of all files recursively to know whether it's in the right state or not. We just have this Exec run if the Archive resource refreshes. What if something else adds a file to this directory with the wrong owner/group? It wouldn't be corrected. Again, not declarative.
And god help you if a machine in the fleet runs out of disk space and resources only partially apply. The state will be completely fucked up and you'll have to manually nuke directories to correct it. Because Puppet only pretends to be declarative.