The whole thing is a cobbled together bodge over SharePoint as a backend. I wouldn't ever trust my company data with that dogwater product.
Back when I had to work with it I found a bug that could cause folders to become un-synced without you realising, meaning changes would not be tracked and cause merge-conflicts when it was fixed.
Managed to use our Gold partner tickets to raise the issue with the product team, they flat out refused to fix the issue even knowing it was a bug. This was back in 2020 or so, I wonder if they ever fixed that bug. It's pretty simple to reproduce:
1. - Sync a nested subfolder from Sharepoint
2. - Sync the parent folder
3. - Note that the folder synced in 1. is not longer being tracked (no checkmark)
4. - Normal users will now go to folder 1. by default and have no idea none of their changes are no longer being tracked now that it's being synced within folder 2.
The university I attend uses SharePoint, classroom and moodle for various courses.
SharePoint is by far the worst piece of software I've ever used. Like, there's no mental model to be done, not intuitive, not working, files disappear from time to time, and I could go on for hours
I'd say its ui is not that great and it is not intuitive when searching courses, but at least it... Works? I mean, using SharePoint might require me to reload the page more than once because I literally don't see the files sometimes
Somehow finding the Frontpage HTML editors down at the bottom makes it feel slightly better. At least it bring a fond memory while navigating our corporate Sharepoint horrorfest.
Don't forget the worst SQL Server database I have ever seen. Single threaded hacks all throughout because it so shitty it can't deal with parallel queries.
It's an interesting point but I fear Go's FFI is going to kneecap its ability to be widely adopted unless that story improves significantly. It's a lovely language if your interop with other languages is minimal.
You can reveal it later when you come up with a new mechanism and out all the fake images. Basically the first layer is first defence, second layer is cleanup when releasing a new mechanism. That way your generated images will always be identifiable eventually.
This is what stopped me from picking up Podman more, all our devs use Docker and have been writing compose files for years now. When the response at the time was "you're using Podman wrong, Quadlets are the hot stuff now" it just felt like too big a risk and commitment to jump to at the time. Have things settled more? Getting away from Docker is a bigger priority nowadays for us.
While modern LLMs are a far cry from biological synapses, I do find it fascinating that if you take the highly reciprocal data of a biological connectome and unroll it into a DAG, you suddenly see motifs popping up that look similar to what we find in AI. I found this both looking at temporal unrolling of RNNs or mapping layer activation weights of a Transformer. Totally agree though, the current LLM architecture itself is driven by the need to shove all of this nicely into parallelized compute hardware.
> if you take the highly reciprocal data of a biological connectome and unroll it into a DAG, you suddenly see motifs popping up that look similar to what we find in AI
That sounds interesting. Where have you heard about that? Or is this your own research?
Yeah actually I haven't been dissapointed with the quality of the new videos so far, I will hold my breath though as venture capitals priorities aren't always aligned long-term.
reply