Rippling: Instancing got easier! [REQUESTED UPDATE #1 (v3 TOTAL)]

[jasperagent_dev (StillSyriarting)]

(Also to @SubtotalAnt8185)

There is a reason for the manual Properties section, however I am working on it as of when I’m writing this, and I have taken that into account and I’ve figured out a way to remove it. As for RbxUtility.Create- I did say

@jasperagent_dev

As far as I know, there aren’t any competetors, but this isn’t a project to go against them, more to just give people a resource.

So please, if you do find it helpful, do you use whatever one you prefer :).

[BIGHEAD_RIPOFF (BIGHEAD_RIPOFFWX)]

How come this is faster than Instance.new?

[jasperagent_dev (StillSyriarting)]

The ability to add children and properties immediately instead of having to rely on multiple lines at once. This may be slower for some people who’ve adapted to constant

local a = Instance.new("Part")
-- begins to repeat a lot
a.Color = Color3.fromRGB(255, 255, 255)
a.Name = "super cool part"
a.Anchored = true
a.CanCollide = false
a.Position = Vector3.new(0, 8, 0)
a.Parent = workspace
-- then you have to do this again with children
local b = Instance.new("BillboardGui")
...

But for me and some others it’s faster for it to just be there. This (in my opinion) is also helpful with DockWidgetPlugins when developing the UI.

[AridTheDev (Arid)]

I like this module since it’s reliable. But, 1 thing that I don’t like about the post is the documentation. Could you please make a proper documentation instead of showing examples?

But, my feedback on this module is just, 8.5/10

It’s not something that I could say

OH MY GOD, WOOOOWWW

… to.

So yeah, other than that it’s a decent module. Keep up the good work!

[jasperagent_dev (StillSyriarting)]

Hi there!

Thanks for the feedback, it really helps me out :). For the documentation, I am currently working on that, but I do understand it.

[ffrostfall]

@commitblue

I do not agree with fusion being great. Its a ripoff of roact, except with way less features.

This is fundamentally wrong, and I don’t think you fully get why Fusion exists.

1. Fusion is meant for game UI- Roact isn’t. Roact is the Roblox version of React- which is meant for websites.
2. Roact requires lots of third-party packages to do well in a game environment. Look at: roact-hooks, roact-rodux, roact-flipper, otter, and roact-spring. This is a dealbreaker for many who just don’t want that many dependencies- in fact, a project I’m in is using Fusion over Roact primarily because of this.
3. Roact is verbose, and the API is not native Roblox. Fusion is not anywhere nearly as verbose, and it is built for Roblox.
4. Fusion and Roact have wildly different APIs and structure. However, they are both declarative UI frameworks. This does not mean Fusion is a ripoff of Roact.

[commitblue]

im not gonna lie, this thread went too off topic to the point its now just fusion meat munchers trying to debunk my point

first of all,

@ffrostfall

Fusion is meant for game UI- Roact isn’t. Roact is the Roblox version of React- which is meant for websites .

Roact is literally for game UI, most projects using roact are making game UIs with it, just because its based on react, which is for websites does not mean its for websites directly too, what makes this more ironic, is that the React tutorial example is literally a game

@ffrostfall

Roact requires lots of third-party packages to do well in a game environment. Look at: roact-hooks, roact-rodux, roact-flipper, otter, and roact-spring

I like it like that. Because its more convienient to split roact dependancies instead of merging it to one making it extremely huge and take memory, so you can only download the needed dependancies
Why not make it into one api then? modules like otter and roact-spring is literally for animation
Each module has its own benefits and thats what makes it more convienient.

@ffrostfall

Roact is verbose, and the API is not native Roblox. Fusion is not anywhere nearly as verbose, and it is built for Roblox.

Roact is for roblox?

@ffrostfall

Fusion and Roact have wildly different APIs and structure. However, they are both declarative UI frameworks. This does not mean Fusion is a ripoff of Roact.

Sure. Then its just rbxultility.Create with some roact features and maybe its not a ripoff but something worse?

If your gonna try to debunk my points, go to dms

---

Anyway i kind of like the syntax of this module, One issue

@jasperagent_dev

Position = Vector3.new(0, 8, 0),
	Color = Color3.fromRGB(60, 255, 184),
	CanCollide = false,
	Anchored = true,
	Parent = workspace

I dont see that the module is optimized. Does it set the parent after it set all the previous values

[Objectionist]

Not another Fusion Meat Muncher™, but I would like to say that with Fusion v0.2’s release here in the coming weeks or so, this module will become pretty much obsolete. v0.2 adds many useful features when doing just general work with Fusion, UI or otherwise. If you’d like to give the new Fusion a peek, here’s the (currently unfinished) docs: Fusion v0.2 Documentation

I’m not here to actively tell people to not use Rippling, but I am coming to say that unless you do some really special things to make this one stand out, it’ll be obscured by a tool that goes beyond this in a lot of ways.

[jasperagent_dev (StillSyriarting)]

For children, it does set parents after all properties so it’s a child of that property, but with normal elements it’s in order of the properties set.

[Dierythros]

You may want to do it the ideal way which would be New(“Part”, Parent, {Properties}) to keep it optimal.