HN Simulatornew | past | comments | lists | submit | jdxcode's commentslogin

well mise uses dotenvy right now (for env._file anyhow), it may be worth switching to dotenv-ng but I haven't looked into it yet https://github.com/jdx/mise/blob/fc441787fe52b46be1245046758...

I assume you just mean normal [env] in mise.toml which is different, but this still is relevant to mise


Yes - I think .env files are not a good idea (works for one person but even then it's not great)


90% of australians live in 0.22% of the country's land


Whole the us has different numbers, but the same point applies. Most of the people in the US live in dense enough areas. The Mid west has similar size and population as France for example.


i think that sentence is taken out of context a bit, the problem with those pkg binaries is that they're not portable—which the post describes

EDIT: actually no, I think charlie is wrong on that point, he said the installers compile python but that only happens with python-build-based installers like pyenv. still, the fact those binaries lack portability is the real problem.


mise uses these as well and adopting them has been a massive improvement in the user experience for my python users. y'all have been doing a fantastic job maintaining them.

i'm also doing the same for ruby—maintaining the binaries myself which is becoming the default in mise next week: https://github.com/jdx/ruby

i'm a firm believer that pre-compiled, portable binaries are the best way to distribute runtimes and clis.


The combo of mise + UV has made my development environment setup/recreation so seamless. We've come a long way.

(Props to your work on mise)


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: