HN user

dmarinus

84 karma
Posts5
Comments80
View on HN

I don't agree that you don't have to know CSS/HTML when you use a frontend framework.

I guess some frontend frameworks can abstract it away but most don't and you almost certainly will run into the limitations of those frameworks and then you still need to understand HTML/CSS

I tried this for a virtualized full screen gnome desktop environment but the latency was unbearable. I also couldn't get passthrough of command/caps lock etc to the virtual machine stable. Finally connecting an USB device (like a yubikey) didn't work seamless.

something more problematic of this smart bike is that it also requires an app to unlock.

from what I read they used many (low quality) custom parts for this bike which aren't available anymore.

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.

Lately I was thinking "what's the best way to integrate/use a task runner like mise in a github actions workflow".

Looking at the workflow files in the mise repository it seems like they gave up and just put in a few run: mise steps (having to rewrite / unable to use dependencies etc).

I think it would be better if you could generate the workflow files but I haven't found such a project yet.

Rclone is a magic tool, I've used it for many different use cases.

When I last checked it doesn't use the AWS SDK (or the Go version is limited). Anyway, it isn't able to use all settings in .aws/config.

But it is kind of understandable that it doesn't support all backend features because it's a multifunctional tool.

Also the documentation is full of warnings of unmaintained features (like caching) and experimental features. Which is a fair warning but they don't specifically tell you the limitations.

I'm often in the same position, for me it's often quicker to hack something together with what I know than using a new technology.

It's just a matter of experience with the toolchain.

You only have to be cautious when your input is mangled in some way (with escape characters etc) and your toolchain cannot cope with such things.

There are many different versions of cut, awk, sed and even jq. I don't consider this very portable.