If anyone else is as puzzled as me I think i've cracked it: rich hickey and rob pike are language owners. That's a real specific job, and it's one that requires unbridled arrogance. Pretty sure that's what we're seeing here. Why else does their anger seem so poorly thought out.. so surprised? So it's one of those tragic flaw things. So let me piss them off by saying: thanks! thanks but your immense focus has forced you to ignore until now this huge thing bearing down on us.. but we who use your stuff and respect your work would benefit more if you happened to find time for a more thoughtful take on this massive thing happening right in our backyard, now that you've deigned to notice it at all. What would be cool would be if you were like "yes this is all terribly powerful I will apply my massive intellect towards helping it not cause our extinction, sorry about yelling at clouds, that was distracting"
They released software with a requirement to use it (license, attribution) and it's been immensely helpful to people, yet these tools come and use it without even following the simple requirements. Yes they care about this thing more than others, but I don't think that it's poorly thought out.
Let's say you have a newborn so you can't easily answer the door for Halloween. So you put out a bowl of candy with a sign that says "take 2 per person, please". Every year the kids come by and take 2. They are happy, you are happy, you gave them candy and they accepted it under the conditions you desire to share it under. Then one year let's say someone makes a robot that scurries from door to door picking up the entire bowl and dumping it into a container then leaving. You will be pissed. If it just took 2 you probably won't even care, but the fact it takes the whole thing is a violation of the conditions you agreed to put the candy out under. The reasonable thing to do would be for it to either take 2 or none, but it doesn't care. I don't think this is a puzzle to understand why that violation of the agreement of use would make someone mad.
I need this, and I need it for seats, but I need it on-prem or it will never get approved. You should sell an iOS subscription based version that allows changing the api/auth url so we can self host. Plenty of companies would be willing to do the infra/config schlep in exchange for holding onto their data, and I mean if you charge 100 bucks per month per seat for the app, can I really complain?
yep totes. good style is sometimes proximate to good ideas because both indicate the author has spent lots of 'thinking tokens' on the thing, which is a costly and therefore sometimes-more-reliable signal. but i believe it falls apart under intensive selection -- the things we read are popular, and so on average are selection-survivors, which means they'll approach the optimal ratio of thinking token spend on style/vs substance for survival, which may not be the same as the best ratio for precise or insightful communication.
but the best communication survives too because it touches universal truths by connecting them with specific real phenomena. the worst (most harmful) communication survives because it frantically goodharts our quality evaluation process, even when it contradicts truth or reality. e.g. Orwell on the good side, L Ron Hubbard on the bad side. Unfortunately these categories are often not well sorted until after the principals are all dead (probably because everyone has to die before you can tell whether the values are universal or just generationally interesting), and there's a style-bar that has to be cleared before you even get to join the canon for consideration; interestingly this this would tend to increase the illusion that style is associated with substance, especially in older writing.
where do you keep the ECS service/task specs and how do you mutate them across your stacks?
How long does it take to stand up/decomm a new instance of your software stack?
How do you handle application lifecycle concerns like database backup/restore, migrations/upgrades?
How have you supported developer stories like "I want to test a commit against our infrastructure without interfering with other development"?
I recognize these can all be solved for ECS but I'm curious about the details and how it's going.
I have found Kubernetes most useful when maintaining lots of isolated tenants within limited (cheap) infrastructure, esp when velocity of software and deployments is high and has many stakeholders (customer needs their demo!)
Not sure if this is a rhetorical question but I'll bite :-)
> where do you keep the ECS service/task specs and how do you mutate them across your stacks?
It can be defined in CloudFormation, then use CloudFormation Git sync, some custom pipeline (ie. github actions) or CodePipeline to deploy it from github
You can also use CodeDeploy to deploy from Git or even a AWS supplied github action for deploying a ECS task.
> How long does it take to stand up/decomm a new instance of your software stack?
It really depends on many factors, ECS isn't very fast (I think it's on purpose to prevent thundering herd problems).
> How do you handle application lifecycle concerns like database backup/restore, migrations/upgrades?
From what I learned from AWS is that ECS is a compute service and you shouldn't persist data in ECS.
Run your database in RDS and use the supplied backup/restore functionality
> How have you supported developer stories like "I want to test a commit against our infrastructure without interfering with other development"?
If it's all defined in CloudFormation you can duplicate the whole infrastructure and test your commit there.
Yeah, that doesn't really answer the question at all...
Do you just have a pile of cloudformation on your desktop? point and click? tf?
And then none of the actual questions like
> How do you handle application lifecycle concerns like database backup/restore, migrations/upgrades?
There is no difference between cloudformation, clicking, terraform, boto, awscli, pulumi, or whatever else. The platform at the other end of those tools is still ECS.
Backing up databases isn't the job of the container-running platform (ECS), especially not in AWS-world where databases are managed with RDS.
The rest of the questions were "how do I run containers on ecs?" in various forms. The answers to all of them is "by asking ecs to run containers in various forms."
In so many wayswe don't own the technology we buy anymore, and playing with someone else's toys doesn't invite the same enthusiasm, especially long term where ecosystems are involved.
In the thread: bunch of tech workers acting like 19th century small farmers. The story here is that chemistry is a blunt tool and in 50 years we won't need it for agriculture. Biocontrols will have totally taken over. In the meantime anything we can do to remove incumbent chemical technologies and create economic room for their replacements is.. important. Why? cause we're gonna need those biocontrols anyway to keep farming at current yields under an evolving pest/weed regime.
We got through the 20th century without sustainable farming. I'm OK with that, it led to things like me existing. Now it's time to focus a little more effort on doing the job properly.
Biocontrols have potential, but they have certainly not taken over. We will always use a combination of herbicides, genetic engineering, RNAi, and biocontrols. The key will be finding a balance between these technologies.
