News for hackers. Stuff that matters.
Re:An Introduction to Cloud Native Buildpacks by igorzij on Wednesday July 12, 2023 @09:47AM (#36694444)
amazing stuff! rooting for you guys
Re:An Introduction to Cloud Native Buildpacks by jimmychoozyx on Wednesday July 12, 2023 @09:53AM (#36694537)
Problems I see in this article:

** This is an Article to market EgroMake. **

It's not some unbiased informational article. It's not even well written in my opinion. Waste of time. I read it trying to understand "Why should I use this?" Left disappointed.

No offense Author... but... hand this to someone who has never heard of BuildPack and have them edit. It reads like you did not write an outline. Plan the article before writing it: an intro, the purpose: who are you trying to persuade and what are you trying to persuade them about.

___________

This article is a "How To"

but it's written as if the Author and the Reader recently collaborated on some project and they both have the same mental context & understanding of the product.

Please consider changing it to a "Why to".

I need a "Why" before I even consider "How"

I don't want to learn HOW to use your product without knowing WHY.

I wish the article was straight to the point, very concisely.

Tell me in 5 bullet points-- 1 sentence each-- why your solution is better than Docker.

Then, expand those 5 points into 5 sections.

I found them scattered in the article, among a bunch of info which is irrelevant to me because I don't even know what this product is and how it's more useful to me than Docker.

...

- Building images without writing Dockerfiles is the first and most obvious advantage of using buildpacks.

- The first reason to consider using CNBs is that they save you time from updating Dockerfiles whenever you update your application.

- [Ok this is pretty cool] The second reason to use buildpacks is to have standardized images across different applications. When using buildpacks, every Node.js service written by your team will end up with the same dependency layers. Therefore, if there's a vulnerability in any of them, you can patch your buildpack instead of asking every team to update their Dockerfile manually.

- Something something rebase your build file

- Cacheing stuff

TLDR:

...Yeah, I am not going to change my workflow for this.... I'm dockerizing some apps to throw 'em into kubernetes. There's enough work between now and that goal that introducing something like this is a wrench in my spokes.