71–80 of 83 posts
Node-RED is really tough for Bun to support because it relies on sloppy mode features like implicit global variable assignment (assigning a variable without var/let/const) and Bun currently treats every file as ESM (and transpiles CJS for compatibility)
Does anyone know if they are using any UI toolkit for the nodes/edges blocks or have they built it themselves? I am looking for something something similar but for different purpose, just the ui toolkit without any logic built on top of it
Earlier quoted context omitted.
Is this related to Illa somehow? The UI builder looks very familiar.
Not related with Illa. Entire different software. I believe it would be the next big thing because of the rapid features they add in compare with other tools.
How does it compare to Luna Park? https://luna-park.app/
To use this service, you check to agree to terms which include this: "By posting Content to the Service, you grant us the right and license to use, modify, publicly perform, publicly display, reproduce, and distribute such Content on and through the Service. You retain any and all of your rights to any Content you submit, post or display on or through the Service and you are responsible for protecting those rights. Y…
> it is saying that our IP and content we provide (config, nodes, data, etc.) still belongs to us, but they can also use it however they want. A great many services have similar stipulations. This is similar to how GitHub was OK to use all the public repositories on its service as training fodder for copilot. Though there are ongoing arguments as to how this applies to code someone else uploaded: they didn't necessar…
Microsoft asserts that it had the right to do this under Fair Use, not the Github user agreement.
Earlier quoted context omitted.
Sure. Using Bootstrap 3 is a problem because it hasn't been supported for over three years and is no longer actively maintained [1]. This is a problem for many reasons, security and maintenance among them. The use of var has long been understood to be problematic due to footguns with scoping issues. It's the reason "let" was introduced into the language, and is pretty much exclusively used now. The pythonic approach…
> This is a problem for many reasons, security and maintenance among them How exactly are those problems with Bootstrap 3? Security, in a CSS "framework"? If it works, it works. You don't have to update everything to the latest version to get some sort of "easy to maintain" badge, things don't change quickly enough for that to make sense. Picking one version and sticking with it is a valid choice for "maintenance" as…
I'm deeply confused by your points and similar arguments I've seen in this discussion.
This is an actively maintained project with regular new releases, not some legacy product languishing in maintenance mode. We're discussing it because it was just on the front page of HN.
I find the arguments that the code doesn't need to be maintained, updated or modernized utterly bizarre.
Have you reviewed the source code?
I have.
It doesn't take very long to see that it diverges significantly from current best practices. The code base is difficult to follow, at best.
Would you argue also that the liberal use of global variables and functions throughout the framework is a good idea? And combining that with a home-grown routing and controller framework instead of using express or something similar makes sense?
It may have when this was originally written, but even I (with my NIH leanings) understand the benefits of using battle-hardenend libraries for core functionality, and the dangers of ignoring the module system and polluting the global namespace.
I'm not trying to nitpick flaws, my point is that the project as a whole needs to come up with a plan to update and modernize the code base moving forward.
With projects like node-red, supabase and Directus as competitors, allowing code to rot is going to prevent new adoption.
We're also not talking about some ERP that just needs to be "good enough" to get the job done.
This is a technical platform for technologists. To use to develop new products.
How can an argument supporting code rot possibly make sense here?
Are you going to select this framework for your next project in its current state?
Does anyone know if they are using any UI toolkit for the nodes/edges blocks or have they built it themselves? I am looking for something something similar but for different purpose, just the ui toolkit without any logic built on top of it