My theory (from anecdotal use) is that the OOXML complexity also explains why M365 office implementation is lacking in so many features and is just not very good at all when compared to the Google office suite.
I do have strong memories of OOXML and the scandals that were with it when it became a standard through MS allegedly buying/stacking/influencing votes:
It's just obvious. To make a 1sq km area of sunlight, you need a mirror at least 1sq km in size - in practice, probably far more. This idea is so absurdly implausible it concerns me anyone over the age of 12 believed it.
I like your nuanced observation here. It reminds me of a quote I come back to often when I am seeing toxic behaviour in some organisations.
> Dysfunctional behaviour is ubiquitous and systemic, not because people are wicked but because the requirement to serve the hierarchy competes with the requirements to serve customers. People's ingenuity is engaged in survival, not improvement.
Yes, there were more of these goal audit firms (for legal reasons they are organised as groups of companies not a single large corporation named say KPMG), at first they merged and then a few of them did scandalous things (but they're run by rich old white men so they can't go to jail, the firm going bankrupt is the closest you get, everybody responsible retired wealthy and has no regrets) we're at the point where there are three left, they can count on no real consequences no matter what they do because fewer is just worse and nobody wants to admit that zero might be the correct number.
Wow. I made several fairly important errors here: 1. I wrote "goal" when I clearly should have written "global" - that's a typo but it's a pretty serious once.
2. There are currently four of these global firms not three.
3. I also omitted to even mention that of these four, three have their headquarters in London, England. This is clearly not a good idea, as a British person I'd like to think we could have one of the world's significant auditors based here, but it's obvious things aren't working properly when almost all of them are.
Yes, pretty well all of the big firms have one big product they're selling: cover for questionable behaviour.
They usually don't just break the law or cheat out of simple desire to. They're for hire and openly compete with their willingness to "transform", "cut red tape", "do things differently™" which are euphemisms for questionable behaviour, usually at the public's expense but their customer's gain.
I also enjoyed ultra processed people. I found the book waffled a bit and some bits were a bit shoe horned in. There is also a tendency towards exaggeration for dramatic effect.
The strongest arguments I found were that we have evolved with our food over millions of years and eating is such a core role of any biological organism. Introducing all these edible synthetic products would understandably have unintentional consequences.
The other good one is an economic argument: all the food companies want you to consume more, so there is an incentive to make you over eat these products.
I also use NixOS, but if the target was not NixOS, I don't think you should be requesting the set up as needing fixing by the author. It just doesn't sound right - or maybe it is just me. NixOS isn't the defacto standard, and breaks the Linux FHS to achieve all the good stuff it does do.
Either try to package it or use a docker image or maybe raise an issue noting the blocker and request it as a feature for some changes to give an easier path for to having it build more easily for NixOS
Apart from that, as expected, the docker image that is produced following the instructions is working fine with NixOS as host. All it needed for the build was the openssl packaged on the host.
Cody is great, it had become my go-to (and I pay for Github Co-pilot).
With that said, they have recently changed the architecture, with the local install required, and I have not managed (yet) to get it working with NixOS. Once I have some more time, I will try again - it looks like there will be some hoops to go through. https://nixos.org/manual/nixpkgs/stable/#ssec-pkgs-appimageT...
Kudos to the Source Graph team, Source Graph's original product was nicely thought out and ahead of it's time. Nice to see how the original product gave a nice basis for building out Cody.
Hello, Sourcegrapher here! We are making some simplifications to eliminate the need for the separate local app install. Should be out in the next month or so. Until then, apologies for the added friction here, we're working hard to smooth it out.
Drake's book looks great. I appreciate his efforts to create a mental model and learning approach to NixOS.
I found a set of tutorials on YouTube by Will, to be incredibly helpful at the beginning of my NixOS journey. Even though these tutorials are a couple of years old, they should have aged well.
Drake's book, should help confirm some assumptions I've made about how NixOS works. Given NixOS's declarative nature, I find it easy to copy configurations to do what I want - a handy approach when pressed for time, but it does leave some gaps in understanding that need to be filled.
I do have strong memories of OOXML and the scandals that were with it when it became a standard through MS allegedly buying/stacking/influencing votes:
https://chatgpt.com/share/68bf5e11-4e10-8003-ac9d-d4d10f7951...