fubarx

Ed is getting good at lobbing these darts at hype bubbles.

The thing that this writeup ignores is that the object isn't to show short-term revenue, but to put all competitors out of business, be the last one standing, and create a monopoly. Either that or get bought out so the investors can move on to the next thing. But at $150B valuation, only MSFT or Nvidia can afford to buy them outright.

Google, Meta, and Amazon burned through cash for years, but they eventually outran all competition and then monetized the users who had nowhere else to go.

In earlier drone shows, they moved the drones into position to make the image they were going for, so navigation and collision avoidance was an issue.

With 7500, it feels like they can just set up a pixel grid in the sky, never move the drones (other than adjusting for wind), then just change the colors to get the image they need.

Conclusion: Tim Walz is just too nice a guy to say what needs to be said.

Will the fly be there to fact-check?

I'm getting one of those chargers installed at home next week. The giant mushroom cloud you might see is nothing to worry about.

Dangit, copy-pasta from an unrelated comment. Fixed.

If you use github pages, you can create, deploy, and host static websites for free. Only cost, if you want your own URL, is for a custom DNS name.

You can use their default Jekyll static rendering engine, and create the content using Markdown. And with github actions, all you need to update the content is create markdown, then push the change to the same repo. After a few minutes, the new content shows up.

https://pages.github.com/

Hugo can also be used, but it takes a few extra steps: https://gohugo.io/hosting-and-deployment/hosting-on-github/

You can also find 'themes' to customize the look and feel of the site, specific to the site generation tool.

If you want a lot of extra features, Docusaurus is pretty much as good as it gets, and you can set it up to push out to GH pages: https://docusaurus.io/docs/deployment

OK, you wanted a conversation… :-)

I did read the post, but I assumed it was the starting point of a system or mechanism, not the end-point. Wanting to just run "docker compose up" is fine, but there is more to developing and deploying to production (and continuing post-launch).

That's why I mentioned the CLI. It lets you go from a simple local app (Django on sqlite) to a Docker one (postgres, celery, redis, etc.), to all the way out to the cloud (ECS/EKS/serverless lambda/RDS), without having to remember what commands do what or managing lots of separate docker-compose files.

I can see we are VERY far apart on how docker should be used in moving toward a production-ready system.

For one thing, recommending putting secrets inside docker-compose is an instantly disqualifying piece of advice. There's a whole 'secrets' section of docker compose that is there to prevent people from inadvertently including those in cleartext and baking them into images: https://docs.docker.com/compose/how-tos/use-secrets/.

Github itself has a secret scanning mechanism to prevent leakage: https://docs.github.com/en/code-security/secret-scanning/introduction/about-secret-scanning. For gitlab, there's also Blackbox or HashiCorp vault. Putting AWS key/secret inside a repo can be VERY expensive and open one to legal liability if the account is misused. Repeated infractions could lead to AWS banning one's account.

I really recommend you take down that part of your post, instead of proliferating bad practices.

As for the rest, to each their own.

Good stuff.

A few things I'd change:

• A CLI to simplify local vs docker vs cloud operations. Reduces chance of operator error. Have had good luck with python click library.
• Moving config settings into separate JSON and .env files to avoid loading too many config and secrets in the docker-compose file.
• For AWS, I'd go with CDK. That way, cloud deployment is all in python (or typescript).
• For cloud, you can also package Django into a single lambda, with dependencies inside a lambda layer. Not sure I'd use it in heavy production, but for small apps, really handy.
• Inside Django settings, you can switch DB and services whether running local (sqlite, Redis), docker (postgres, RabbitMQ), or cloud (RDS, SQS).

This could be big. The fact that it's sub-dollar, open-source, AND could be put on FlexPCBs opens up a whole lot of applications.

Only concern is the same as for RFID. They end up so cheap they're tossed into landfills or end up in waterways without a second thought. At least there, people are working on biodegradable solutions: https://bioplasticsnews.com/2020/01/12/stora-enso-sustainable-rfid-tag/

If the Flex-RV people address sustainability, they could have a real winner.

Thanks, fixed.