I don't agree with the assumptions baked into the tool (eg env vars over config, new vs edit, no deletion), yet I like it being opinionated. Keep coding :)
i like the 'no deletion' attitude. so much can go wrong when writing custom code to delete stuff. as deletion here is trivial to do yourself using whatever preferred method and policy (like moving stuff to trash) you have to delete stuff, i do appreciate the decision to stay away from that.
for the env vars, i hope there are defaults that make even setting the env vars optional and not needed unless i want to change the defaults.
Unfortunately, the DNS provider (dns1) does not expose DNS over IPv6. Therefore your site is exposed over IPv6 by Netlify, but it will not be reachable by a (probably non-existant) IPv6-only client.
The thing is that `dig AAAA dns1.p04.nsone.net` does not resolve anything. A pure-ipv6 network would not be able to resolve my domain, as there is no way to contact dns1.p04.nsone.net via IPv6.
It really didn't. I can tell you with first hand knowledge the majority of the internet by any measure, but especially high scale systems where I've worked and know much of the small community, use neither Docker nor Kubernetes. That's not any indictment on either technology it's just simple fact. Fad tech appears a much bigger tiger in echo chambers like this website but the majority of the companies aren't even using languages that are popular to this crowd let alone tooling. Whether or not these tools have staying power or contribute meaningfully to the industry the jury is still out on, and will have to wait about 5 years to tell. In the past you "were an idiot" if you weren't using C++ or CORBA or RPC or Java or SOAP or message queues or Ruby on Rails or AWS or or Hadoop or OpenStack or blockchain or machine learning or.. all of these are fads and all that mattered then and now for consumers of the tech is solving business problems cost effectively.
Software developers are an incredibly easy demographic to influence with marketing. There is an industry of startups that have been minting money on this for a long time. But it's important to know that a lot of software development tools we use are just fashion statements.
It's not about current market share but about adoption rates. Which container technology/toolset/ecosystem is more likely to be adopted by the average software shop today?
It's the wrong question unless you are in the business of profiting off of container tech directly. What are you doing for the stakeholders delegating your pay checks and the person authorized to fire you? If they are happy, then it doesn't matter what the company uses. Most transactions and the world's wealth are stored and processed on operating systems and frameworks most people have never heard of which will outlast either of these by decades but that doesn't mean you should or shouldn't use them necessarily..
I'm well aware that there's tons of time proven software that serves us well and will continue to do so for some decades. Yes, most of this is not written in the PL/framework combo du jour, true. You seem to think I want everyone to switch to Docker/Kubernetes. I don't.
Fair enough, and the parent topic about /switching/ between broadly similar technology like operating systems is where departments usually go awry. My axe to grind is about initial selection when starting from scratch (do you really need fad tech? Statistically, likely not), or playing nicely in an existing environment and being very careful with new tech (can the company internalize and support fad tech? Statistically, likely not)
OP asked what stops people from switching to BSD. I agreed that for me, too, the missing Docker toolchain/runtime is a dealbreaker for me, as I have to work with these technologies on a daily basis. As Docker and friends see rapid adoption, others will think twice whether they switch to a BSD and have to run a Linux VM, too. I'm not sure what you're after here. You seem to think that Docker and Kubernetes are "fad technology" and are inferior to some alternative? Which orchestrator would you recommend? Which container tech?
Again it's not a judgement against the technology. What I'm getting at is the talking that fad technologies won the industry is false and too early to call like that; in the particular company you are working in docker and kube you may have to use. In industrial terms, they are far from required and are not used in the majority of deployments. Proprietary schedulers or other deployment machinery are running most workloads. Distant second by cluster size is Mesos, which has passed its fad phase.
I am currently using Nomad which works on multiple platforms and that is a requirement for my particular setting. I don't currently use containers in production environments and only see negatives to introducing them into this particular setting. This is not general advice to use nomad, just a counterpoint to any particular fad tech being an industrial requirement.
Very much so, and nearly one decade separated between the three in their respective fad cycles. Being a fad isn't a judgement against the technology, some will fail and some will prevail.
>Those are the guys that don't let you use special chars in passwords "in order to prevent unintentional wrong password entries".
is that really an issue? using all the special characters (assuming uniform distribution) gives you ~33% more entropy[1] for the same amount of characters, at the expense of increased input time (especially on touch keyboards) and being much harder to remember. why not just make your passwords 33% longer instead?
