va1en0k

It'd be probably easy to guess which communities I mean, but I'd rather not name names myself and hope someone supports me with a datapoint to offset my personal paranoia.

Lately I encountered quite a lot of software - fringe and weird of course, but numerous enough - that went for having Nix as the only way to be deployed, typically with a "reproducible" script that doesn't work already after a year or two. As nix files make negative intuitive sense, not even in the smallest-scale bit-fiddling sense, so little intuitive sense that I cried once trying to just make it work - I look around for advice. One of "just take a couple of weeks to learn it, it's not that hard" is seen quickly enough, of course. It's a bit of pure loss from there: everyone who heard something like this knows that it's the moment to either invest fully or ignore and quietly move on and away. Confessing that you just don't think you'd find it in yourself to invest in it is almost a pure loss for one.

However, since we're not in one of those communities, let me say why not. I'm as sure that the good idea of reproducible builds will be implemented soon enough with something intuitive, strongly-typed, easily debuggable/diagnostable and dev-friendly, as I'm sure that diesel cars will be obsolete soon enough not to even think about investing my time and money in them. Regardless of what the current usage says - e.g. in Germany one would make a mistake to follow its wisdom just a few years ago, in case of cars, I mean.

Nix is slowly becoming a major point of contention. In some communities, it’s already scary to even hint that one dislikes it.

looking forward to reading the postmortem

Wow, thank you! We were wondering if it does the job :)

For now, it can be only a separate table. In the future, of course, there're going to be buckets and everything, stay tuned!

If you have some specific ideas about this in mind, my email is [email protected]

Hey,

Yes, we're working on it! :-)

And, of course, you can use multiple different dj.FileFields for that in one model, if you need only a limited number of images.

Ha-ha, I'm on it.

Hi! We're working on several things you can do to avoid having a separate table, make sure to be in touch :-)

Please continue to provide feedback, it's very valuable to us, thank you!

Hi!

Thank you, this was our goal (not to be similar with filepicker.io, but to have a clean, straightforward way to handle files). :-)