Imagine you are in a marriage and your spouse say: "I can sleep with other people, doesn’t want to do that. It feels off-mission".

I don't understand context, but my honest reaction will be: "WTF, you just said? What type of relationship you think we have if we discuss such things?"

I definitely understand why people worry. This is just crazy to weight trust in money. If this is on the table and discussed internally, then what we are talking about?

'T' in Mozilla Firefox means 'Trust'.

Yeah, I've once said in a relationship "Look, sure, she maybe pretty, but I want to be with you, so no, I am not going to reach out to her, don't worry". Apparently, it was a poor way to word this idea.

"Fucking her brains out would feel off mission"

Yes, people tend to try to dig out additional information from the particular wording (talk about a hidden channel) based on how they would phrase the same message themselves. That's why communication is hard.

We use Gitlab for CI/CD and tbh it is amazing. Simple, predictable, debuggable.

This whole thread is various people saying "[This] is trash, [that] is awesome", with the next person claiming the opposite. I suspect most people with strong negative opinions here know enough to have felt the pain, and not enough to be able to properly reason about the system.

I've worked with Github Actions, Gitlab-CI and CircleCI in the last 10 years, and they've all been such an improvement over Jenkins, or god forbid, CVS with manual deployments, that I'm generally just counting my blessings.

For me the pain only came when not adhering to KISS. All the mentioned VCS are pretty much feature complete and only really differ on meta-topics (cost, license, lock-in) or niche topics (Actions marketplace, matrix builds, SSH on Runners). I've not yet run into an issue that would have actually blocked me, because there's always sh to fall back to in case of a bug or missing feature.

Pffff... No AI? Who need it? Even my shower gel is AI already.

Does it conform Occam's razor rule to have something that can be easily done very similar way without changing language?

Having some limited experience with lazy imports, yes, but this eliminates a lot of gross boilerplate. It also has the effect of "blessing" the practice of lazy imports which can have a cultural impact; it also prevents a situation wherein multiple subtly incompatible approaches to lazy imports become individually popular.

Not sure that's Occam's razor any more.

Regardless lazy loading needs widespread use to be most effective so having a unified syntax and no extra dependencies makes a lot of sense.

So basically you just rewrote boilerplate code with complexity of "hello world" and deploy scripts. Without any dependencies, data migrations, real user data and downtime SLA. And after that you had time to write quite long article.

What honest reaction you expect from readers?

I have no idea how you reached this conclusion from the article that I read.

Just simple arithmetics.

I blocked Disqus locally on my computer via /etc/hosts many years ago. Reason is very simply. Because comments as genre is almost useless.

> comments as genre is almost useless.

Writing a comment that categorizes comments as a literary genre and then immediately argues that comments are useless is some meta level deconstruction. Kudos.

You are putting comments on HN right now. i guess not entirelly useless then?

> putting comments on HN [...] not entirelly useless then?

Comment systems are useful/effective when someone is paying the full cost of moderation.

OP wrote "almost useless" which, by definition, is also "not entirely useless".

You are technically correct, best kind of correct.

If it weren't for the "almost," the commenter would be in serious trouble.

Labuba driven development

This one is amazing, I almost pissed myself laughing reading it. So true about YAML. Another caveat is using --- as section separator in the file. It will starts new file inside your existing file.

Still love it.

To be honest, right now I'm thinking about isolating of build process for frontend on my local environment. It is seems not hard to send my local environment variables like OPENAI_API_KEY or .ssh/* to some remote machine.

I know it is not very different comparing to python or projects in any other language. But I don't feel that I cannot trust node/js community at this point.

Switching to Deno might help. It's sandboxed by default and offers granular escape hatches. So if a script needs access to a specific environment variable or read or write specific files, it's simple to configure that only those accesses are allowed.

Running vite inside a docker container would probably get you what you want

I don't think you even need a container for that type of containment.

You could do it with namespaces.

I think node/whatever-js-run-time/package-manger could allow for namespaced containment for packages with simple modern linux things.

The realms proposal was a step towards that at one time.

Wow! It is crazy how much money people will to pay for such problems.

I restrict myself from distractions by disabling hosts via custom rules in my nextdns account. It is enough and free.