5 ms·

Going Full Time on Open Source

203 points by thunderbong 6mo ago

drcongo 6mo ago
I hope this works out - I love mise and sponsor on GitHub already.
slopinthebag 6mo ago
Oooh, bad idea. Bun guy is saying OSS will be written exclusively by AI in 2027, with human authors banned.
- Brian_K_White 6mo ago
  Are people dinging you because they think you're taking Bun seriously, or because they think you're not?
  - slopinthebag 6mo ago
    Probably the former
  - pseudalopex 6mo ago
    I thought it was snarky and added nothing to the discussion.
    - slopinthebag 6mo ago
      Oh, kind of like this comment? https://news.ycombinator.com/item?id=48031424 https://news.ycombinator.com/item?id=48031424
- okkdev 6mo ago
  That's such a dumb take. Nobody can ban me from writing OSS.
wek 6mo ago
Congratulations! I think that a lot of the value will be in the judgement of the maintainer about the marginal next feature (and saying no to all those other features) ... if software is a stream then the value is in what gets into the stream. That is an AI resistant value and if you can provide it for your project.
dan_sbl 6mo ago
Good luck, and I hope it works out! Make sure you are ready to ride the roller coaster of highs and lows, as there are going to be many. Remember that your time and experience are the most valuable things you have - make sure you're in control of both.
spankalee 6mo ago
We just started exploring Mise as a (much) simpler alternative to Nix + Bazel for a polyglot monorepo. One of my concerns was about how well maintained Mise would be given that it's mostly a single maintainer, so I think this is good news in that respect. Good luck to Jeff!
- xyzzy_plugh 6mo ago
  As a proponent of both Nix and Bazel, unless you need them for a specific reason you should totally use Mise. I recommend Mise to everyone. If everyone on your team gets Mise and you're starting to feel pain at the periphery then it can definitely make sense to adopt a more elaborate toolchain orchestrator.
  - invalidSyntax 6mo ago
    All these positive reviews really makes me wonder. Maby I should use Mise. The creator looks like he's really in it. Starting it now might be a good option.
- JamesSwift 6mo ago
  Devenv is "mise but nix" and is very good. It is currently undergoing a big migration though, so still a few rough edges. I highly recommend checking it out if you find yourself wanting nix at all.
- sangeeth96 6mo ago
  Likewise looking to adopt mise at work, have a PR nearly there and especially with all the LLM/skills CLIs, mise looks well positioned. I've been using it for a long time personally and is a delight to work with. Curious given polyglot monorepo and bazel, does mise have something that solves the build graph/caching stuff that IIUC comes with Bazel or is that something that's not needed for the monorepo you help maintain?
  - spankalee 6mo ago
    Yeah, Mise has caching: https://mise.jdx.dev/cache-behavior.html https://mise.jdx.dev/cache-behavior.html I'm a massive fan of Wireit and its caching behavior, so I'm looking for something to live up to that. I have more testing to do. I think Mise defaults to mtime-keyed cache but has an option for content hashing, which it what Wireit uses and makes it quick to undo a change and get a cache hit.
hashkb 6mo ago
I had the pleasure of working with Jeff in ... I want to say 2012 - he taught me so much, is a fabulous developer and teammate, and we had some great times together. Edit: mise rocks.
- jdxcode 6mo ago
  Feeling is mutual!
brzz 6mo ago
Pleased for him. I've been an enthusiastic mise user for quite some time, and am keeping an eye on how aube shakes out.
avree 6mo ago
Man, that's a weird looking "f" in the font. Why does it have a tail? Feels like someone is trying to inject a company logo/function symbol into the otherwise normal-looking characters.
- kajman 6mo ago
  > So I left Figma to work on these full time. The Mise website makes way more sense to me now. I suppose some artistic license is justified when you're at the cutting-edge of the CLI aesthetic and what not.
kajman 6mo ago
I don't know what to call this - a "freelancer launch"? It is the best executed one I've seen, though. Maybe even a black-mark on OSS if it does not go well.
- antonvs 6mo ago
  > Maybe even a black-mark on OSS if it does not go well. No, because realistically, this is the opposite of what corporations want. If a project is only being maintained by one or two people, that’s a risk, pure and simple. So you look somewhere else for something that matches your needs, with a more sustainable story. Nothing against the author, but what he’s describing is a business model - just one that’s likely to bring in a negligible amount of money. This is less about open source and more about what kinds of projects society is willing to pay people to work on.
  - kajman 6mo ago
    Corporations seem to rely on key software that just a few people maintain all the time already, but you're right and the bus factor does not look great. Mise is also currently MITMing my shell, along with presumably many other dev machines, so the threat of compromise is pretty scary.
mihaitodor 6mo ago
10th most downloaded Homebrew formula and the maintainer makes ~$600 / month. Not very encouraging for people who are thinking to follow the same path…
- zaphirplane 6mo ago
  How is that counted ? Is it unique installs or counting updates as well It is very very frequently updated
  - mihaitodor 6mo ago
    It doesn’t really matter… My point is that we’re still in a world where such projects are highly unlikely to become sustainable, no matter how popular they get.
    - deleted 6mo ago
      [deleted]
- nulltrace 6mo ago
  [dead]
- otterley 6mo ago
  Mise is number 64, not number 10. Please verify your facts before posting in the future. https://formulae.brew.sh/analytics/install/30d/ https://formulae.brew.sh/analytics/install/30d/ (That said, your observation is well taken.)
  - jdxcode 6mo ago
    this is the leaderboard that matters for CLIs: https://formulae.brew.sh/analytics/install-on-request/30d/ https://formulae.brew.sh/analytics/install-on-request/30d/ it's 12th now. It was 10th when I wrote this post. GP is just mentioning what I wrote in the blog body.
    - 6mo ago
Lazare 6mo ago
Not exactly on topic, but I have to endorse mise; it's a really, really great tool that solves a number of different problems. Example: I was recently working on a large project that needed a specific version of Python, and there's a lot of ways to solve that, but mise was an easy and robust one. But also, the project needed a bunch of different tools to build it, deploy it, do local dev, perform certain maintenance tasks like rotating secrets, work through certain operational runbooks, etc., and mise was an easy and robust way to solve that too. Once you know everyone on the team will have the same tools available, if a runbook would be simpler if you could assume everyone has jq installed, well, just add it your the project's mise config, and now they do. And then when I switched to working on a Java service, and then later a Node service, well, obviously mise was an easy and robust solution there too. By contrast, I made an effort a year or two back to adopt nix, which (despite starting from a very different place) solves a lot of similar problems, but found it a bit daunting (large, complex, poorly documented, and felt hard to partially adopt), and while I love the concept of nix, as a practical matter I ended up abandoning the effort. But mise was really easy to understand, adopt, and progressively add to an existing project without unduly impacting other team members. (Example: Mise will read existing verion manager configs from tools like sdkman, which makes adopting it over time easier.) It's got to the point now where I'm using mise in place of Homebrew or other system level package managers for basically all CLI tools. Which feels weird when I think about it, but mise genuinely just feels like the better solution. If mise has a flaw, I haven't stubbed my toe on it yet.
- jdxcode 6mo ago
  I'm glad you're seeing it this way and finding value in it, this was very intentional. I wasn't happy with the status quo with all of the other tools in this space (nix, bazel, buck2, etc) that all force you to adopt everything from day 1. I think of mise as an overlay on existing systems, not a system in itself.
  - c-hendricks 6mo ago
    Very quickly mise went from "what's that?" to "I need it everywhere" because of the "overlay on existing systems" approach. It's all over our org at work, and all over the local dev community here. It has also simplified all of our CI and made the random python projects a breeze to run. Great work! Ironically I pushed for it because it also has tasks that can be written in Bash (we have a mix of Bash scripts and Makefiles for task running across projects while I will die on the hill that shell scripts should be written in a shell script: not Makefile, not a string in a json file, not a string in a yaml file) but we never did get around to that.
ggoo 6mo ago
This is great news! I use mise everyday - it's basically muscle memory to type "mise" before a command in many of my projects now thanks to mise tasks
jdmoreira 6mo ago
I really really like mise! I've been using it for everything lately. all my repos / projects now start with a mise.toml
nicbou 6mo ago
Thank you for mise! I started adding it to my projects, because it removes a lot of the mental overhead of moving between them. I just cd to a project and everything just works. The documentation is a little difficult, but LLMs seem pretty capable of understanding it and generating new tasks. Good luck with your new endeavour! I have made a similar move in 2020 and it made me a much happier person.
techalchemist 6mo ago
Best of luck and hope it works out for you.

203 points by thunderbong 6mo ago

drcongo 6mo ago

I hope this works out - I love mise and sponsor on GitHub already.

slopinthebag 6mo ago

Oooh, bad idea. Bun guy is saying OSS will be written exclusively by AI in 2027, with human authors banned.

Brian_K_White 6mo ago
Are people dinging you because they think you're taking Bun seriously, or because they think you're not?
- slopinthebag 6mo ago
  Probably the former
- pseudalopex 6mo ago
  I thought it was snarky and added nothing to the discussion.
  - slopinthebag 6mo ago
    Oh, kind of like this comment? https://news.ycombinator.com/item?id=48031424 https://news.ycombinator.com/item?id=48031424
okkdev 6mo ago
That's such a dumb take. Nobody can ban me from writing OSS.

wek 6mo ago

Congratulations! I think that a lot of the value will be in the judgement of the maintainer about the marginal next feature (and saying no to all those other features) ... if software is a stream then the value is in what gets into the stream. That is an AI resistant value and if you can provide it for your project.

dan_sbl 6mo ago

Good luck, and I hope it works out! Make sure you are ready to ride the roller coaster of highs and lows, as there are going to be many. Remember that your time and experience are the most valuable things you have - make sure you're in control of both.

spankalee 6mo ago

We just started exploring Mise as a (much) simpler alternative to Nix + Bazel for a polyglot monorepo. One of my concerns was about how well maintained Mise would be given that it's mostly a single maintainer, so I think this is good news in that respect. Good luck to Jeff!

xyzzy_plugh 6mo ago
As a proponent of both Nix and Bazel, unless you need them for a specific reason you should totally use Mise. I recommend Mise to everyone. If everyone on your team gets Mise and you're starting to feel pain at the periphery then it can definitely make sense to adopt a more elaborate toolchain orchestrator.
- invalidSyntax 6mo ago
  All these positive reviews really makes me wonder. Maby I should use Mise. The creator looks like he's really in it. Starting it now might be a good option.
JamesSwift 6mo ago
Devenv is "mise but nix" and is very good. It is currently undergoing a big migration though, so still a few rough edges. I highly recommend checking it out if you find yourself wanting nix at all.
sangeeth96 6mo ago
Likewise looking to adopt mise at work, have a PR nearly there and especially with all the LLM/skills CLIs, mise looks well positioned. I've been using it for a long time personally and is a delight to work with. Curious given polyglot monorepo and bazel, does mise have something that solves the build graph/caching stuff that IIUC comes with Bazel or is that something that's not needed for the monorepo you help maintain?
- spankalee 6mo ago
  Yeah, Mise has caching: https://mise.jdx.dev/cache-behavior.html https://mise.jdx.dev/cache-behavior.html I'm a massive fan of Wireit and its caching behavior, so I'm looking for something to live up to that. I have more testing to do. I think Mise defaults to mtime-keyed cache but has an option for content hashing, which it what Wireit uses and makes it quick to undo a change and get a cache hit.

hashkb 6mo ago

I had the pleasure of working with Jeff in ... I want to say 2012 - he taught me so much, is a fabulous developer and teammate, and we had some great times together. Edit: mise rocks.

jdxcode 6mo ago
Feeling is mutual!

brzz 6mo ago

Pleased for him. I've been an enthusiastic mise user for quite some time, and am keeping an eye on how aube shakes out.

avree 6mo ago

Man, that's a weird looking "f" in the font. Why does it have a tail? Feels like someone is trying to inject a company logo/function symbol into the otherwise normal-looking characters.

kajman 6mo ago
> So I left Figma to work on these full time. The Mise website makes way more sense to me now. I suppose some artistic license is justified when you're at the cutting-edge of the CLI aesthetic and what not.

kajman 6mo ago

I don't know what to call this - a "freelancer launch"? It is the best executed one I've seen, though. Maybe even a black-mark on OSS if it does not go well.

antonvs 6mo ago
> Maybe even a black-mark on OSS if it does not go well. No, because realistically, this is the opposite of what corporations want. If a project is only being maintained by one or two people, that’s a risk, pure and simple. So you look somewhere else for something that matches your needs, with a more sustainable story. Nothing against the author, but what he’s describing is a business model - just one that’s likely to bring in a negligible amount of money. This is less about open source and more about what kinds of projects society is willing to pay people to work on.
- kajman 6mo ago
  Corporations seem to rely on key software that just a few people maintain all the time already, but you're right and the bus factor does not look great. Mise is also currently MITMing my shell, along with presumably many other dev machines, so the threat of compromise is pretty scary.

mihaitodor 6mo ago

10th most downloaded Homebrew formula and the maintainer makes ~$600 / month. Not very encouraging for people who are thinking to follow the same path…

zaphirplane 6mo ago
How is that counted ? Is it unique installs or counting updates as well It is very very frequently updated
- mihaitodor 6mo ago
  It doesn’t really matter… My point is that we’re still in a world where such projects are highly unlikely to become sustainable, no matter how popular they get.
  - deleted 6mo ago
    [deleted]
nulltrace 6mo ago
[dead]
otterley 6mo ago
Mise is number 64, not number 10. Please verify your facts before posting in the future. https://formulae.brew.sh/analytics/install/30d/ https://formulae.brew.sh/analytics/install/30d/ (That said, your observation is well taken.)
- jdxcode 6mo ago
  this is the leaderboard that matters for CLIs: https://formulae.brew.sh/analytics/install-on-request/30d/ https://formulae.brew.sh/analytics/install-on-request/30d/ it's 12th now. It was 10th when I wrote this post. GP is just mentioning what I wrote in the blog body.
  - 6mo ago

Lazare 6mo ago

Not exactly on topic, but I have to endorse mise; it's a really, really great tool that solves a number of different problems. Example: I was recently working on a large project that needed a specific version of Python, and there's a lot of ways to solve that, but mise was an easy and robust one. But also, the project needed a bunch of different tools to build it, deploy it, do local dev, perform certain maintenance tasks like rotating secrets, work through certain operational runbooks, etc., and mise was an easy and robust way to solve that too. Once you know everyone on the team will have the same tools available, if a runbook would be simpler if you could assume everyone has jq installed, well, just add it your the project's mise config, and now they do. And then when I switched to working on a Java service, and then later a Node service, well, obviously mise was an easy and robust solution there too. By contrast, I made an effort a year or two back to adopt nix, which (despite starting from a very different place) solves a lot of similar problems, but found it a bit daunting (large, complex, poorly documented, and felt hard to partially adopt), and while I love the concept of nix, as a practical matter I ended up abandoning the effort. But mise was really easy to understand, adopt, and progressively add to an existing project without unduly impacting other team members. (Example: Mise will read existing verion manager configs from tools like sdkman, which makes adopting it over time easier.) It's got to the point now where I'm using mise in place of Homebrew or other system level package managers for basically all CLI tools. Which feels weird when I think about it, but mise genuinely just feels like the better solution. If mise has a flaw, I haven't stubbed my toe on it yet.

jdxcode 6mo ago
I'm glad you're seeing it this way and finding value in it, this was very intentional. I wasn't happy with the status quo with all of the other tools in this space (nix, bazel, buck2, etc) that all force you to adopt everything from day 1. I think of mise as an overlay on existing systems, not a system in itself.
- c-hendricks 6mo ago
  Very quickly mise went from "what's that?" to "I need it everywhere" because of the "overlay on existing systems" approach. It's all over our org at work, and all over the local dev community here. It has also simplified all of our CI and made the random python projects a breeze to run. Great work! Ironically I pushed for it because it also has tasks that can be written in Bash (we have a mix of Bash scripts and Makefiles for task running across projects while I will die on the hill that shell scripts should be written in a shell script: not Makefile, not a string in a json file, not a string in a yaml file) but we never did get around to that.

ggoo 6mo ago

This is great news! I use mise everyday - it's basically muscle memory to type "mise" before a command in many of my projects now thanks to mise tasks

jdmoreira 6mo ago

I really really like mise! I've been using it for everything lately. all my repos / projects now start with a mise.toml

nicbou 6mo ago

Thank you for mise! I started adding it to my projects, because it removes a lot of the mental overhead of moving between them. I just cd to a project and everything just works. The documentation is a little difficult, but LLMs seem pretty capable of understanding it and generating new tasks. Good luck with your new endeavour! I have made a similar move in 2020 and it made me a much happier person.

techalchemist 6mo ago

Best of luck and hope it works out for you.