psankar
Joined 16 years ago
Joined 16 years ago
However, There were infighting between the GNOME and KDE desktop teams. The VPs were mostly overpaid and practically useless. The constant churn of acquisition, looking for a new buyer, etc. did not help their long term cause.
With the older system software (kernels, compilers, etc) and infra layer getting commoditized I wonder how long they may remain relevant. When they brought in a new CEO and acquired Rancher I hoped that they may recover with K8S etc, but the CEO has quit and the acquisition has not done much it seems. Until they remove some dinosaurs from the old management at VP levels, I honestly do not see any recovery for them. Thumbs up for the Engineering (and leads) and heavy thumbs down for the Management, is how I remember my time there.
I do not have OAuth or SAML however. Is that the differentiating factor, if I have to use your solution ? Is a basic auth setup such a complex thing to handroll ourselves ? I do not intend to be snide but genuinely curios about it. Incorporating your project, its lifecycle management, etc. seems more work than implementing a 3-4 APIs (/signup /signin /verify-email /forgot-password /reset-password) and a periodic job (trigger emails and stuff). Is it so complex that we should bring in a new dependency with its own deployment, backup, monitoring etc. lifecycle management ?
But I really wish gofmt gets inspired by prettier and automatically breaks long (80+ columns) lines into smaller lines (For example, move parameters of a long function each into their row).
LOL
I so wish that I had your website a few months back. It is quite nice. This understands what I want clearly, and helps me play with various options almost instantly. If one has worked with some of the outdated interior modelling tools, they will understand what slowness pain, I am referring to.
We had to use another FOSS project called Gatekeeper as an authentication software along with keycloak, which got obsoleted and replaced with a different project (lukedo proxy or some such).
The community support was also relatively not that active like other FOSS project that we used (for other areas of the stack). Overall, the experience was not so great that we decided to ditch both keycloak and gatekeeper. This was about a couple of years back. Not sure what the current status is.
Some other alternatives that we wanted to try were from the Ory project (Kratos etc.) But we just went with some proprietary AUTH solution in our startup.