Lot of criticism going on lately stating that Bun is becoming a bloated runtime and that Bun image would better be a Library or Extension.
In a nutshell: Yes the Image feature is a runtime lock-in, Yes you might not use it but it is shipped anyway just like lot of other features (Sqlite etc.), Tho those features are very handy.
My POV on the feature being a lock-in might be totally far from what I've seen been discussing online.
Imagine you start your project with a library A-Image later on a new lbirary has a better coverage of your needs we will name it B-Image, You decide to move to the new Library, You will Spend X time.
Hmm, So you are telling me that If I use Bun Image and I move to Node, I will need to migrate to a new Image Library and spend X time? Yes that's the cost always.
You don't wake up on a good morning and say let's use Node instead of X runtime, there must be a valid reason. Stop vibing/straying and write specifications. A good old saying states 'Weeks of coding can save you hours of planning'
Bun is defined as an all-in-one toolkit it doesn't claim to offer "POSIX" (portable) runtime.
Excuse my English,
Peace.