833 karma · joined May 12, 2015
> 70 binaries just for initialising and logging
It’s just not true. Those 70 binaries provide much more functionality than an init system, they can cover a significant portion of system management, including a local DNS resolver, network configuration or system time management. You can dislike the fact everything is so tightly integrated (which feels ironic given that the post goes on to praise a user space from one team), but let’s at least be correct about this.
That sounds like an overall good idea to me. The client fork might be questionable, but it's clearly targeting a non-technical audience (or, not necessarily technical), so having a low barrier of entry makes sense to me. Kudos to them, hope they can keep it maintained.
I also don't think that "but what about space requirements" is an argument with enough weight to dismiss the long list of advantages given by the GP. We have so much unused space on roofs. We could get rid of a few parking lots if you're concerned for ground.
[1] https://www.iaea.org/newscenter/pressreleases/worlds-uranium...
I’m admittedly not from the US so I had different scientists talking about the pandemic, but around here 70% vaccination was never considered enough.
It’s more likely the other way around: Cluster API needs a so-called infrastructure provider that creates cloud resources to get a Kubernetes cluster running. The logic to join/create a Kubernetes cluster within the VMs created by that is managed by a separate provider, the bootstrap provider.
So, I guess it would be possible to externalise the creation of cloud resources to Crossplane and write a small shim infrastructure provider that just translates your cluster specification into Crossplane resources.
Crossplane has a different use case than Cluster API (create any cloud resources vs create a Kubernetes cluster), so Crossplane using Cluster API doesn’t make a lot of sense. Crossplane basically is „what if Terraform was a Kubernetes Operator“, so that somewhat sounds like what you’re interested in with the later parts of your post.
You get more effective by understanding their needs and why they are asking you for something.
A genuine question that I wonder about: How does a single server protect you against someone in your DC pulling a plug by mistake or your cloud provider being unreliable? If it’s a database it seems like a huge potential for going out of business.
I guess if you are running single-server databases you better have a good backup strategy anyway, but is that a risk people and businesses just accept?
I've been doing a bit of technical interviewing and I usually try to help people along so they reach the "end" of the interview, especially if they're not doing too well. So many candidates sound defeated when they're struggling with a task and it's a form of respect for me. They've put themselves out there, after all.
Treating candidates - which you know you are going to reject at some point of the interview - with dignity is the right thing to do and can go a long way when it comes to your company's reputation.
I think that the documentation is making several technical claims (from the quotes I've provided) that are factually false. You're agreeing that it CAN be done with Terraform. Best practice isn't what is being discussed in the documentation, it claims that reusing isn't possible.
Granted, I'm not your target audience, but I would recommend to a) rephrase those claims so they're closer to the truth and b) start documenting the architecture of your targets and the quality of your Terraform code (does it pass tfsec tests for example).
If someone asked me to review this product for their startup, I would primarily see Terraform modules with unknown quality or architecture.
Maybe you have great ideas for this target concept, but the claims in your documentation[1] that this is new and the inference that Terraform isn't capable of this don't hold up:
> it describes a particular architecture that can produce many possible variations for a wide variety of stacks, depending on configuration.
You can do exactly that, with Terraform modules, today, no digger needed.
[0] https://www.terraform.io/docs/language/modules/develop/index...
[1]https://learn.digger.dev/overview/how-it-works.html#understa...
I find this statement from the documentation[0] unfair, given that the "target" concept this introduces seems to be mainly based on Terraform modules to _reuse code and expose an interface_. Terraform has its problems, but this doesn't seem to be right.
At best, this seems to be a curated set of Terraform modules and a managed CD pipeline execution SaaS. I get that it is supposed to simplify things, but it is lacking documentation for what it will do to an AWS account (you'll still pay for it, after all) and even provides documentation on how to drop "raw" Terraform into it. Why not go with Terraform directly then instead of sending your AWS credentials to a SaaS?
[0] https://learn.digger.dev/overview/how-it-works.html#technica...
And if the way Mozilla gathers data is much more considerate, what results can I expect from it? Better parallel requests and data fetching, hardware acceleration, etc are all features that are missing for me as a Linux user. They don't need my dataset for that, it's probably all in their bug tracker.
If the mechanism works, fine, but why should I use Firefox over Chromium then? Opt-out data collection is in violation to my core beliefs and what I believed to be Mozilla's principles.
Collecting data without asking the user about it is - to me - in violation to the very definition of privacy and calling some way to anonymise data (who guarantees that the cryptographic approach to this is not obsolete in a few years?) "differential privacy" is at the very least dishonest.
If they start opt-out tracking using the same approach as Google I do not see any reason to use it nor install it for my friends and family. That's some data for you, Mozilla.
I may be wrong, but isn't that basically AppLocker? Why introduce a custom version of your operating system if you could easy merge such a feature into already existing administrative tools (assuming that it isn't, I'm not that familiar with AppLocker)?
Turning on "developer mode" isn't exactly jailbreaking, so yes, they have access to the underlying Linux and can even run a Linux desktop environment of their choice on top of ChromeOS. They can't install Steam because that only supports x86 but you can't blame ChromeOS for that.
I'm pretty sure you won't be able to do that with Windows S, so, no, it's not exactly like ChromeOS.
edit: See http://www.dudleymediagroup.com/Detail/id/how-to-game-with-s...
Kodi is not an offshoot/fork, it's XBMC's new name.
Felonies exist and people still commit them. Should they? God no. But people with a lower moral code exist and they can be flipped to do "good work" if there's enough money for them (and I think you should get more money in general for your important work anyway). I find the notion of your profession only consisting of good people highly offending to the rest of the world.
Of course it's illegal/wrong to sell an exploit to third parties, but that doesn't stop people from doing illegal things as long as they get money for it. You just don't know about the issues that are sold because that's obviously not going public.
Don't forget that your hardware vendor is also responsible for firmware. Not saying that Lenovo is special in any way here, but delivering terrible software on the factory OS image might have implications for software quality in general.