HackerTrans
TopNewTrendsCommentsPastAskShowJobs

toddnni

no profile record

comments

toddnni
·9 miesięcy temu·discuss
Have been looking for minio alternative for long already. Found versitygw lately and would like to share the joy. It feels very promising. Fits to many small or lab use cases.

It does not actually solve the trickiness of managing large storage but relies on the backend (that is usually fs like zfs in small setups).

However, seems to be quite new project plus the risk, that the owning company takes it to bad direction, is there too.

https://github.com/versity/versitygw/
toddnni
·2 lata temu·discuss
GDevelop. My son has used that happily. Meant for no-code development, so no real programming experience there, but good to get something out quick.

Nowadays supports 3D also, but that is recent feature and will definitely evolve for some time.
toddnni
·4 lata temu·discuss
Using none currently, the following seems to be enough: containers for apps and KVM+vagrant on a laptop for experimenting.

However, for VM orchestration. OpenStack has been my choice for long time, but about to check KubeVirt and (old and underappreciated?) Apache CloudStack.
toddnni
·5 lat temu·discuss
Maybe a dump question, but was it so, that it is not only Let's Encrypt that uses Certificate Transparency Log, but all the other providers too?

If so, then the decision is more like, whether to use a public or private certificate for an internal service.
toddnni
·5 lat temu·discuss
Is it so that the fragmentation (the long list of distributions), or variety of configuration options, is a bad quality? This seems to be used as a counter argument to Kubernetes.

Probably, it could be end result of unconsistent design or bad technical choises. However, most likely it just means that there are multiple organizations and interest groups pushing changes and ideas to the project. This should be seen as a good thing. The downside is that there is no single source of best practices and this is confusing to newcomers. You just need to pick one distribution and trust the choises, or develop the competence and understanding.

And we could imagine that the userbase or the number of developers in single distribution (take OpenShift or Rancher) could be bigger that in Nomad itself.

Having said that, I still would like to see more stable Kubernetes landscape, and that has to happen eventually. The light distributions k3s and k0s are pushing things to nice direction.

OpenStack had similar, or maybe even worse, fragmentation and complexity issue when the hype was high. There were probably technically better alternatives (Eucalyptus?), but people (and companies) gathered around OpenStack and it won the round. However, comparing OpenStack to Kubernetes feels bad, as Kubernetes is technically far superior.