I'll be honest, I've had times where there's the "simple" solution, and "the solution I remember off the top of my head", and 10/10 the one that's happening is the one that I remember because I just did it last week.
I have no desire to google the arguments for self signing a cert with openssl, and I cannot remember which webserver wants the cabundle and the public cert in the same file. If I had done it even kinda recently I'd still remember what to poke in the certbot config.
Do you think that, in this example, using certbot is fucking shit up, or breaking something?
The thing about overkill is that it does work. If you're accustomed to using a solution in a professional setting, it's probably both overkill and also vastly more familiar than the bare minimum required for a class project that would be entirely unacceptable in a professional setting.
In OPs anecdote, they did get their certificates, so I don't quite see your "intentionally fucking things up" claim as what's happening.
This is confusing to me, because the point of the request seems to be "get a certificate", not "get a self signed certificate generated by running the openssl command". If you know how to get the result, it doesn't really matter if you remembered offhand the shitty way or the overkill way.
Is it really more helpful to say "I remember how to do this, but let me lookup a different way that doesn't use the tools I'm familiar with"?
That's not the case, you just need to be able to make an outbound connection.
The minutiae of how certbot works or if that specific person actually did it right or wrong is kind of aside the point of my "intended to be funny but seemingly was not" comment about how sometimes the easiest solution to implement is the one you remember, even if it's overkill for the immediate problem.
For a brief moment in the beta for all this, it basically just summarized the top two or three reputable results, and attached a link to where it got the data.
They should have just left it at that, and not started mixing in random blogs and social media sites.
The ability to summarize the Wikipedia article and a random university professors page where they list every fact known to man about pine trees or something was actually helpful.
If I want the AIs best guess about how to fuck up a pizza, I just go to the site where I can ask it. Bad advice when searching is just shit.
A tldr for "what is turpentine" is actually helpful.
Your's is a "featured snippet", which is where it highlights a relevant portion from a top result.
The AI results have the AI synthesize a new sentence or set of paragraphs answering the question using data from multiple sources.
They're different results because you didn't seem to get the AI search results. After making it available to everyone they've been hit with a bunch of weird results and have started scrambling to manually remove the particularly strange ones as they crop up.
It's also "infectious" software. The way systemd positions itself on the system, it can make it more difficult for software to be written in an agnostic way. This isn't all software, and is often more of a complaint by lower level software, like desktop environments. https://catfox.life/2024/01/05/systemd-through-the-eyes-of-a-musl-distribution-maintainer/
This isn't a terrible summary of some of the aspects of it.
Another aspect is that when it was first developed, the lead on the project was exceptionally hostile to anyone who didn't immediately agree that systemd definitely should take over most of the system, often criticizing people who pointed out bugs or questionable design decisions as being afraid of change or relics of the past.
It's more of a social reason, but if people feel like the developer of a tool they're forced to use doesn't even respect their concerns, they're going to start rejecting the tool.
It's that it also decided to take over log management, event management, networking, DNS resolution, etc, etc.
If it were just an init system that would be perfectly portable. People were able to write software that way with sysv for years.
It's that in order to do certain low level tasks on a systemd system, you need to integrate with systemd, not just "be started by it". Now if a distro wants that piece of software, it needs to use systemd, and other pieces of software that want to be on that distro need to implement integration with systemd.
A dependency isn't infectious, but a dependency you can't easily swap out is, particularly if it's positioned near the base of a dependency tree.
Almost all of my software can run on x86 or arm without any issues beyond changing compiler targets.
It's closer to how it's tricky to port software between Mac and Linux, or Linux and BSD. Targeting one platform entails significant, potentially prohibitive, effort to support another, despite them all being ostensibly compatible unix like systems.
No, not everyone thinks it's a bad thing. It is, however, infectious, which is a reason some people don't like it.
Knowing why people dislike something isn't the same as thinking it's the worst thing ever, and liking something doesn't mean you can't acknowledge it's defects.
I think it's a net benefit, but that it would be better if they had limited the scope of the project a bit, rather than trying to put everything in the unit system.
Do or do not, there is no try ( sh.itjust.works )
I am the outwitter! ( lemmy.world )
Couldn’t find anything with less pixels, please save to disk and remove resolution yourself ❤️
Last one, i've been farming Ai for memes but last one with lore ( lemmy.ca )
systemdeez nuts ( sh.itjust.works ) Englisch
My cousin said the gas savings for a prius and a motorcycle were the same. ( lemmy.ml ) Englisch
Mathematically they're equivalent, but the feelings could not be further apart.