brodock

A lof of people care. Not all choose opensource because of religion/beliefs. It's the most sane choice when you want to ensure business continuity as the company who owns it can do whatever they want with the product/service including sunsetting it. When it's open you at least have a choice.

People don't want to risk get sued for nothing

If you don't host yourself, you don't own anything.

The hidden costs of migrating away from a monolith... The promise is you will be able to better allocate resources as they are divided into small pieces. The reality is over engineering everywhere just to the what you have been doing before, but with added latency

I'm happy they are finding ways of monetising that don't rely on adtech

people are asking for consul support for many months... it seems they refactored the dependency on zookeeper to make it easier to use something else

As this is another shim based manager, you can expect that at some point in time, someone in your team will have a broken setup due to shims generation failing for some reason or because something else messed with the way the tool relies on the PATH.

This has been my experience with rbenv, asdf and all other solutions that relies on shims.

Depending on what you are trying to do (for example running short lived CLI), you will incur into a slightly performance cost because of the bash/zsh/fish shell you need to spawn before running your code. In ruby's case rbenv/asdf adds around 20-50ms (could be more etc depending on your shell and your shells initialization code etc).

Once systems are in place, all it takes is a change in will of who controls it.

In italy...

Isn't trying to break security of the "entire internet" some kind of crime (despite whatever the excuse is)?

People got swatted for less.

Yes

Many cities artificially block that citing things like "will modify the current architecture/aspects of the city" etc. Basically the argument is that cities shouldn't evolve from what they were in early last century, ignoring the major influx of new residents.

For GitLab if you don't have at least developer access to the repository (as in you are sending a MR from a fork) that will run in the context of your user, so you don't have access to any secrets configured upstream, etc.

If you have access to a repository you can customize the script to do whatever you want, but there will always be a trace tracking it back to you.

There is a discussion about ultimate security (access only when asked) Vs the convenience of self-service.

You can still avoid that by having people use a fork model, or triggering CD from an external project with tight access.

Putting a burocratic process between ICs will only limit their throughput as in Jenkins paradigm.

The better advice is don't hire people you can't trust

Isn't the whole NFT a piramide scheme where "Auction" platforms incentivize artist A and B to buy each other arts (while taking a cut) in the hope it will boost "fame" and have someone unadvised of the deal think it's worth anything?

Isn't that "5 seconds" a cloudflare thing?

I would "bet" they will not perform well in the long run. Their most valuable asset is trust and that was lost

Good coffee is not abundant. Not the crap you will find in local supermarket, that will almost always taste the same. It's like cheap wine.

There is a location/clima reason. Cocoa grows (well) only in a certain part of the world around the equator line as it requires tropical weather with regular rains and small dry seasons.

It may be possible to use artificial techniques to grow it elsewhere, but I'm assuming it's not economically viable or you get a product with worst quality in the end

So, who owns the "Docker Engine" ? Mirantis or Docker Inc?

Funny they didn't had to build 10 million Microservices and host it through a million kubernetes pod instances to handle "internet traffic".

Telegram can also sell "premium reaction packs" (steam hats), and/or go Discord mode and have people "boost" private groups etc with "premium features"... I would actually pay for better video calls (no one is giving us 1080p or greater)

The only perfect code is the one you write, all others are crap

I think we got there also by desperation of lacking good cross-platform GUI toolkits.

The current state is, you either use something that looks like Windows 95 in all platforms, or web app.

What the web made possible is to anyone to create a decent custom UI with little effort. I still remember how messed up was to create a custom component for Java Swing, which I believe is still one of the easiest to do. How would you do that for QT? GTK? WxWidgets? etc

The API currently exists: https://gitlab.com/users/<youruser>/calendar.json. But I think this should be exposed in the public API, so I've created an issue for it: https://gitlab.com/gitlab-org/gitlab/-/issues/322153

I guess someone can create a "free and open" version of that, generate the STL and use a similar provider as above.

3D printing yourself and using a cheapo CNC can also do the trick... I wonder how hard it is to programmatically generate the STL yourself.

we are finally getting some improvements in bluetooth audio support in both pipewire and pulseaudio after the multi year effort of https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge...

I am really happy this didn't succeed. Google is the type of company with the wrong incentives to screw up the whole gaming industry turning them into marketing data mining, microtransactions ad machines.

Self hosted GitHub Enterprise does not allow for public access. So you can't expose your opensource projects to the world using your own instance.

migrating GitLab from "cloud" to self-hosted is as easy as importing the project. You can even import in batch and things will "just work".

https://docs.gitlab.com/ee/user/project/import/gitlab_com.ht...

hosting CI yourself is equally simple. The worker can be installed with few commands, and with a few extra you can configure autoscalling:

https://docs.gitlab.com/runner/install/

considering how similar many CI providers are in terms of how you write your tests, I would say that this is either very achievable or not that worth it.

you already can do a lot by writing a bunch of scripts that will be executed on a CI, and just fiddle with differences in like metadata/artifact/how you declare your containers.

and while you are there, you can generate the code CI definitions for more than one CI provider (think of it like "multi-cloud" but for CI approach.