notebook VS bevy

https://github.com/ilse-langnar/notebook

Project Description: It's a tool for thought, browser, note-taking application with inspiration from: Roam Research, Obsidian, SigmaOS, Chrome etc. I'm trying to have a all-in-one browser where I don't have to leave to do anything. Everything should be done inside the browser.

Testing help: Anyone who has a non-linux, non-windows machine would be of great help because I need to fix the small bugs still.

Contact info: On on the githu issues (:

I'm working on something similar.

It's a Collaborative "Second Brain" or Zettelkasten, it's local by default but you can sync your brain with other people. Still in aplha. The local version is free and the collaborative one will cost per sync. So if you only want to use the local version then its ok.

https://github.com/ilse-langnar/notebook/

What's you life work?

What is it that you're working on, be it an area, company, game, language, subject, cause etc. That you expect to work until the end of your life?

Starting with me it's a little bit hard. I have so many interests that picking a single one out of all of them is hard. But I plan on working on companies, causes, philosophies, books, areas etc.

Some of the areas I'm interested in are: Intelligence, IQ, Collective Intelligence, Knowledge Management, Writing, Sleep, Comics, AI, Game Design, Meta Cognition, Zettelkasten, Linguistics, Design, Coordination etc.

My current project is: https://github.com/ilse-langnar/notebook.

If you want to quickly check out, I'm working on a tool that works using a "generic" filesystem/files/folders to build a note-taking app, so even if you stop using the app, your stuff is still there in a normal format that can be extended with something like vim, Emacs, Sublime, VSCode, ??? etc.

https://github.com/ilse-langnar/notebook

I've experienced similar frustrations with notetaking apps.

I'm now working on a tool similar to "Obsidian, Logseq and Dendron".

It came as a frustration of previous tools(I've used ALL of them). They're either not flexible enough, not light enough, not powerful enough, not portable enough etc.

So I made: https://github.com/ilse-langnar/notebook/

It combines both studying/references. So it's a flashcard(I don't user Supermemo algo tho) + Notetaking. It's also built on a standard so you can develop commandline/mobile/toaster app that is compatible.

Bevy. A very young engine where you need to write the game entirely in Rust—that was appealing. But fatal flaws overshadowed everything: no editor, the engine brutally enforces the ECS approach, and the game's architecture must literally bend to fit this paradigm. So, you won't migrate to another engine at all—you just throw away all the code and start from scratch.

Missing one of the best choices as long as "maturity" isn't on the top of your list: Bevy - https://bevyengine.org/

Game engine written in Rust, leveraging ECS in almost every place and way, with a really capable WASM export option. Wrestling ECS for the first time might take you some time, but in my experience helps you keep game code as clean and decoupled as game code could be.

I don't see WASM/WebGPU changing anything when it comes to gaming, as an industry, personally. 3d visualizations and interactive websites? Yeah definitely a nice improvement over WebGL 2, if years late.

WebGPU is pretty far behind what AAA games are using even as of 6 years ago. There's extra overhead and security in the WebGPU spec that AAA games do not want. Browsers do not lend themselves to downloading 300gb of assets.

Additionally, indie devs aren't using Steam for the technical capabilities. It's purely about marketshare. Video games are a highly saturated market. The users are all on Steam, getting their recommendations from Steam, and buying games in Steam sales. Hence all the indie developers publish to Steam. I don't see a web browser being appealing as a platform, because there's no way for developers to advertise to users.

That's also only indie games. AAA games use their own launchers, because they don't _need_ the discoverability from being on Steam. So they don't, and avoid the fees. If anything users _want_ the Steam monopoly, because they like the platform, and hate the walled garden launchers from AAA companies.

(I work on high end rendering features for the Bevy game engine https://bevyengine.org, and have extensive experience with WebGPU)

I was working through an example in the repo for the Bevy game engine recently and came across this code

That's possible. I did spend quite a bit of time tinkering with compiler flags, and followed the recommendations.

Some notes I found just now seems to agree with my results, though: https://github.com/bevyengine/bevy/issues/3978#issuecomment-...

I cannot recommend immediate mode GUI programming based on the limitations I've experienced working with egui.

egui does not support putting two widgets in the center of the screen: https://github.com/emilk/egui/issues/3211

It's really easy to get started with immediate mode, it's really easy to bust out some UI, but the second you start trying to involve dynamically resized context and responsive layouts -- abandon all hope. The fact it has to calculate everything in a single pass makes these things hard/impossible.

... that said, I'm still using it for https://ant.care/ (https://github.com/MeoMix/symbiants) because it's the best thing I've found. I'm crossing my fingers that Bevy's UI story (or Kayak https://github.com/StarArawn/kayak_ui) become significantly more fleshed out sooner rather than later. Bevy 0.13 should have lots more in this area though (https://github.com/bevyengine/bevy/discussions/9538)

I've also been enjoying building My First Game™ in Bevy using ECS. The community around Bevy really shines, but Flecs (https://github.com/SanderMertens/flecs) is arguably a more mature, open-source ECS implementation. You don't get to write in Rust, though, which makes it less cool in my book :)

I'm not very proud of the code I've written because I've found writing a game to be much more confusing than building websites + backends, but, as the author notes, it certainly feels more elegant than OOP or globals given the context.

I'm building for WASM and Bevy's parallelism isn't supported in that context (yet? https://github.com/bevyengine/bevy/issues/4078), so the performance wins are just so-so. Sharing a thread with UI rendering suuucks.

If anyone wants to browse some code or ask questions, feel free! https://github.com/MeoMix/symbiants

These days, some game engines have done pretty well at making compute shaders easy to use (such as Bevy [1] -- disclaimer, I contribute to that engine). But telling the scientific/financial/etc. community that they need to run their code inside a game engine to get a decent experience is a hard sell. It's not a great situation compared to how easy it is on NVIDIA's stack.

[1]: https://github.com/bevyengine/bevy/blob/main/examples/shader...

This is the API you need: https://github.com/bevyengine/bevy/pull/9774