I wish these tools like Cursor, Windsurf etc. provide free option for working with open source projects, after all they trained their models via open source code.
I worked there for a few years during the Novell/Attachmate management. They had a strong bias towards the kernel teams and engineers. They had an european work culture and some very good leads. Their Engineers were very good. The internal mailing lists were ripe with technical discussions. Got some amazing friends and inspirational engineers with whom I would love to work again.
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.
> However, There were infighting between the GNOME and KDE desktop teams
I like to imagine an alternate world where KDE won, became the de facto standard Linux desktop environment, and was refined to perfection (along with a huge set of desktop apps with a consistent user interface design).
> and heavy thumbs down for the Management, is how I remember my time there.
This is exactly what is reflected to the public with their flappy and sloppy unpredictability of product lines (openSUSE that is).
LEAP is beta/rc for Enterprise -> LEAP is now based ON Enterprise -> LEAP will be canned for NEW thing just Tumbleweed for community in the future -> Nothing about new thing but new LEAP are still published -> Community still wants something like LEAP, creates Slow-roll Tumbleweed in fear of SUSE still canning LEAP...maybe? -> Now, no news about EOL of LEAP, no "new thing", but Slow-Roll for Tumbleweed...what a Clown-show...
SUSE/openSUSE you are terrible in messaging, like chickens on meth with a new brain-fart every two month.
Nothing against the Dev's but the C-suite and Marketing should probably be replaced, those ping-pong announcements is the opposite from what someone wants from a Distro.
Really openSUSE why should anyone use LEAP for a professional project if there is a really big chance that in 3-4 years a complete re-installation/migration is needed? Or is it not? I don't know, also pretty sure you don't know too. So fck it i use Debian/Ubuntu/FreeBSD or Slackware hell even Oracle-Linux, literary anything else is more predictable longterm.
You guys have no technical problems but a trust and communication one.
Congrats on the launch. I have a golang backend, postgres db and a react app. I have added auth using email, password salting and saving in pg. It was about 1 day of work to implement all of this.
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 ?
First, incorporating Stack into your project is really easy if you use Next.js — literally just a single command:
npx @stackframe/init-stack@latest
If you use our managed hosting, we'll deal with deployment, backup, ... for you.
.
Anyways, here are a few things that you'd have to build for yourself but come for free with Stack Auth:
- Session management, because you probably don't want to store passwords in cookies, and JWTs should not be long-living
- Impersonation to debug users or do customer support early on
- A user dashboard for basic analytics & editing, saves you from having to build this yourself in Retool
- Email shenanigans — for example, some mail clients click verification links automatically to check them for spam and then even interact with the page
- User profiles and account settings pages
- OAuth access token management, if you ever want to access APIs on the user's behalf
- App-based 2FA with HOTP/TOTP — we don't actually have this yet, but should be released this week still
- Redirects, so users land back on the same page after they successfully logged in
- Teams, so you can segment your B2B clients
- Access permissions for your users
- and more stuff, every time I make this list it's slightly different
> Email shenanigans — for example, some mail clients click verification links automatically to check them for spam and then even interact with the page
What is the technical workaround for this issue? Do you check user agent?
Check for cookies. If they exist, we can continue like normal. If not, require user interaction (none of the spam filters we tested click buttons, but from what I could gather, one of them — Outlook — moves the mouse).
That is a good idea: Require interactivity. Even something very simple like: "Click this button to continue." Any human will click it immediately. A spam checker: Stumped.
Most mature web frameworks (ie, not Janky JavaScript stacks) handle this either out of the box or by pulling in a popular community library. The benefits are no separate service to run and operate and the user model being directly tied to the database.
Nice. Do you guys also provide all the UIs for permission management/roles/orgs such that I can just css it and bolt it on? That was always a major pain point for me. You still had to make all the user facing ui and integrate it.
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).
I recently bought a home and had to spend a lot of time with a professional interior designer to explain the interior ideas that I had in my head. However, I was not fully satisfied with the video model, that the designer prepared, as there were problems in conveying my vision.
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.
