shipyard
Node RED
shipyard | Node RED | |
---|---|---|
5 | 200 | |
665 | 18,558 | |
- | 0.8% | |
7.0 | 9.3 | |
9 days ago | 7 days ago | |
Rust | JavaScript | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
shipyard
-
Deploying your Rust WASM Game to Web with Shuttle & Axum
With game matching the binary name used in Cargo.toml, above. The code we use is provided as an example of using the Shipyard Rust ECS. Paste the main.rs square_eater code from the repo into src/bin/main.rs in your project.
-
Sharing Saturday #458
I also initially followed the amazing bracket-lib tutorial, but was not satisfied with specs. Tried legion, but it seems kind of abandonned too. I choose to use shipyard in my project and I am pretty satisfied with it until now. I feel like it's a great compromise between usability and effectiveness, plus there is relatively up-to-date documentation. Maybe can you give it a try ?Shipyard
-
I hope my new-to-programming-enthusiasm gives you all a little nostalgia
Shipyard (Rust)
-
React Renderer for Three.js
It's not that it's incompatible, it's that when the ECS is the primary tool for organization, a DOM tree (or scenegraph) is merely one way of iterating over the entities - not the way.
This provides tons of benefits, so for example you can also decide to iterate over the entites by shader program and gain significant speedups for graphics processing, or maintain components that roughly sort them by their position in world space for physics and culling or lighting, etc.
To add to the sibling comment, there's another wonderful Rust ECS called shipyard[0] and I helped write a scenegraph for it (which I really need to update, one of these days)[1]
[0] https://github.com/leudz/shipyard
-
[Brainstorming] Use cases for variadic generics
Just as a final thing here, are, a, bunch, of, links for shipyard's tuple impls to show how its not an uncommon thing to need to do when writing an ECS :)
Node RED
-
Devin, the First AI Software Engineer
Good question.
I expect that we're moving into a phase of AIs talking to AIs, and initially it'll be wasteful (because it'll be mostly English), but eventually, they'll derive their own language and seamlessly upgrade protocols when they determine they're talking to an AI. No clue how that will come about or what that language will look like, but honestly, it's kind of exciting.
Really interesting to think about how they might handle context, as well. Even though we have much bigger context windows (and they'll only get larger), context management is still a resource-management issue, which we'll probably continue to refine, as well. Imagine different strategies for managing both what is brought into the context of each request, as well as what form it could take (level of detail, additional references or commentary on it, etc). Things could get really unreadable even in English, and still be very interpretable for an LLM.
W.r.t. the graph-oriented interfaces, are you thinking something like Node-RED [1]? I'm seeing more and more people mention having LLMs produce non-text or structured outputs, like JSON, UI, and other things. Easy to imagine an LLM that wires together various open-source platforms, on-demand. Something like Node-RED for pipelines/functions, some UI tools for visualization/interactivity, other platforms for messaging, etc...
[1] https://nodered.org/
- IFTTT is killing its pay-what-you-want Legacy Pro plan
- Node-RED: Low-code programming for event-driven applications
-
Pipe Dreams: The life and times of Yahoo Pipes
I skipped to chapter 9 in the article ("Clogged"), and it looked like Pipes failed because it didn't have a large enough team or a well-defined mission. As a result they couldn't offer a super robust product that would lure in enterprise users. "You could not purchase some number of guaranteed-to-work Pipes calls per month" is the quote from the article.
The reason I think that interesting is because that's the model these days for everything from AI tokens to Monday.com seats. It makes me feel like Pipes was before its time.
That said I've been collecting different "business glue" products that are similar to Pipes. To me, like you say, they aren't as interesting, exciting and intuitive as Pipes was, but maybe it just takes a little more digging. I tried to focus on open source tools but some aren't.
- n8n io: https://n8n.io/integrations/mondaycom/
- Node-RED: https://nodered.org/ (just read about this one in this thread)
- trigger dev: trigger.dev
- automatisch.io: https://automatisch.io/docs/
- Activepieces: https://www.activepieces.com/docs/getting-started/introducti...
- Huginn: https://github.com/huginn/huginn
- budibase: https://budibase.com/
- windmill: https://www.windmill.dev/
- tooljet: https://www.tooljet.com/workflows
- Bracket: https://www.usebracket.com/pricing (just SalesForce <-> PostgreSQL)
- Zapier: zapier.com/
Anyway I hope some of these are fun!
- Open source IPaaS With Drag and Drop integration
- Ask YC: tracking events platform and no-code workflow
-
#OpenSourceDiscovery 84 - Node-RED, alternative to IFTTT or Zapier, a workflow automation tool
Source: https://github.com/node-red/node-red
- Low-code programming for event-driven applications
-
n8n.io - A powerful workflow automation tool
I believe Node-RED (https://nodered.org/) the way to go. It's just an NPM package to install and you can run it how ever you wish (even on Windows). It has a friendly and helpful community with even the main developers tirelessly answering even beginner level questions. In fact the community forum its THE friendliest forum I've ever been a member of by a large margin. Node-RED's development is supported by the JS Foundation and it's completely free and open source. It's widely used in the industrial automation industry and even integrated by some PLC manufacturers such as Siemens.
-
Loops and conditional branching (IF then else) in ComfyUI?
Does anyone know if their are plans to implement something like this (or if there are already custom nodes out there). I'd like to experiment with things like looping and incrementing values (like a for loop) for a Ksampler for example. It's only an example though, so I am not looking for a ksampler specific solution; just a generic way to have a variable (e.g. Seed value), run some nodes that use that value, increment the value, and then loop back to the beginning until some sort of condition is met. Node-Red (an event driven node based programming language) has this functionality so it could defintely work in a node based environment such as ComfyUI (see here).
What are some alternatives?
hecs - A handy ECS
Home Assistant - :house_with_garden: Open source home automation that puts local control and privacy first.
beatmapper - A 3D editor for creating Beat Saber maps
n8n - Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
raylib-rs - Rust bindings for raylib
openHAB - Add-ons for openHAB 1.x
dungeon-bevy - Rust programming -> random generated Dungeon with Bevy engine
Huginn - Create agents that monitor and act on your behalf. Your agents are standing by!
emscripten - Emscripten: An LLVM-to-WebAssembly Compiler
esphome - ESPHome is a system to control your ESP8266/ESP32 by simple yet powerful configuration files and control them remotely through Home Automation systems.
scheduler-test
blockly - The web-based visual programming editor.