3 ms·

Articles like this remind me of that Innovation Tokens article. Your time and attention is precious as a developer. I'm absolutely sure it's possible to implem

Articles like this remind me of that Innovation Tokens article. Your time and attention is precious as a developer. I'm absolutely sure it's possible to implement uniqueness constraints, transactions, indices, and history yourself, but is that really the most valuable use of your time? There's probably not a need for you to have a unique solution, so you're quite literally just re-inventing something someone already had for not a lot of benefit. Wouldn't your time be better spent actually solving the problems that whatever you're building is supposed to solve?

bob1029 24d ago
Development of video games is the final boss of this one. If you want to kill someone's dream of publishing a game, encourage them to build their own engine from scratch. I cannot think of a more malicious piece of advice given how effective it is, statistically speaking. The exceptions to this are so incredibly rare. Virtually all of the in-house engine work at indie scale has been replaced by Godot in recent years. It used to be something like 10-11% of studios were in-house fully custom. Now it's probably closer to 1-2% fully custom and 8-10% on Godot. Having a reasonably stable OSS option has removed the last major argument that I am familiar with for simply using what already exists.
- my-huge-pony 24d ago
  >last major argument that I am familiar with for simply using what already exists I was interested in gamedev as a kid. I always went with a custom engine. You're right, I never released/finished a large game. But now I think I was just into game engine dev. Every time I finished my game engine and started working on game content I ingredient got bored and went to another project. So I guess this is the reason, engine development is fun :).
jauntywundrkind 24d ago
You don't write your own libc to talk to the filesystem, do you? Same vibe here imo. Use zerofs, juicefs. Use picomq, automq, s3stream. Use slatedb. Use lancedb, fusion, tonbo, iceberg, vertex. Use duckdb, data fusion, polars. These systems all natively speak to object storage. Use Qwikwit, rising wave / hummock, greptine mito, use warp stream, neon. Use celld. Over half of the projects here are very specifically about object storage. Many deal with uniqueness, transactions, indicies. Which is extra impressive because its across machines. Managing data on a box creates a huge array of challenges and difficulties, backup and scaling and HA, etc etc. A huge reason to face object storage head on is that often you are headed towards that fray one way or another, and object storage makes an excellent easy to scale and manage disaggregation layer that keeps your problems from complecting together, is a clear, well known separation point. With an incredible ecosystem around it.

bob1029 24d ago

Development of video games is the final boss of this one. If you want to kill someone's dream of publishing a game, encourage them to build their own engine from scratch. I cannot think of a more malicious piece of advice given how effective it is, statistically speaking. The exceptions to this are so incredibly rare. Virtually all of the in-house engine work at indie scale has been replaced by Godot in recent years. It used to be something like 10-11% of studios were in-house fully custom. Now it's probably closer to 1-2% fully custom and 8-10% on Godot. Having a reasonably stable OSS option has removed the last major argument that I am familiar with for simply using what already exists.

my-huge-pony 24d ago
>last major argument that I am familiar with for simply using what already exists I was interested in gamedev as a kid. I always went with a custom engine. You're right, I never released/finished a large game. But now I think I was just into game engine dev. Every time I finished my game engine and started working on game content I ingredient got bored and went to another project. So I guess this is the reason, engine development is fun :).

jauntywundrkind 24d ago

You don't write your own libc to talk to the filesystem, do you? Same vibe here imo. Use zerofs, juicefs. Use picomq, automq, s3stream. Use slatedb. Use lancedb, fusion, tonbo, iceberg, vertex. Use duckdb, data fusion, polars. These systems all natively speak to object storage. Use Qwikwit, rising wave / hummock, greptine mito, use warp stream, neon. Use celld. Over half of the projects here are very specifically about object storage. Many deal with uniqueness, transactions, indicies. Which is extra impressive because its across machines. Managing data on a box creates a huge array of challenges and difficulties, backup and scaling and HA, etc etc. A huge reason to face object storage head on is that often you are headed towards that fray one way or another, and object storage makes an excellent easy to scale and manage disaggregation layer that keeps your problems from complecting together, is a clear, well known separation point. With an incredible ecosystem around it.