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

[jasperagent_dev (StillSyriarting)]

Ah! So a created instance can have multiple children, however having more children inside of those children are not possible currently.

[jasperagent_dev (StillSyriarting)]

My point with it was that it’s mainly based upon UI, however this is focused on all types of instances instead of just UI. This means Fusion or Roact are going to contain more UI-Based functions or features. My resource is trying to respond to all of this.

[commitblue]

I can help u with that if you want. its rlly ez

[GlowyUmbreon (Umbreon)]

I looked at your complains on your repl free tier website and your arguments seem to consist of

1. Roact has more stars on github
2. Fusion is in alpha
3. You have to make your own components

Honestly those first 2 literally do not matter at all unless you need a high amount of support.
And the 3rd one? The whole point in using a library like fusion is to create your own components and have them easily interface well with your scripts, if you really want to have components made by other people you can just use a module made by another person which uses fusion.

The only thing that you mentioned that I agree with is that I wish fusion would use a state management system separate from fusion itself but its not a major concern for me.

[commitblue]

continue in dms its getting so offtopic

anyway, what you said is too bogus. First of all, I like how you said “free tier repl website” to make me feel worse. If anything, I would rather a worse server than read this at all.

Second,
I know you said “consist of” but your saying its like the only reasons i put it in my website, mind debunking the other reasons or are you scared to get wrecked?

@GlowyUmbreon

The whole point in using a library like fusion is to create your own components and have them easily interface well with your scripts, if you really want to have components made by other people you can just use a module made by another person which uses fusion.

Then its really awful. The point of 3rd party modules, is to use the functions in it so you dont have to write it yourself. In this special case, you have to? The only thing fusion has wrote so far is state, element, animations, and thats so far i know at a 20 minute look into fusion.

Roact? you have all these, but you dont have to make these yourself. sure, some things like animations are in other modules like roact-spring, but its better than having to make these functions yourself.

Thats it.

[jasperagent_dev (StillSyriarting)]

In the module’s current form it’s gotten the functions for it, however the functions fail to work. I’m still investigation it now, but I’ll let you know if I’m ever in need of help

[EatSleepCodeRepeat (cybescr)]

This is awful.

@jasperagent_dev

shortens the outcome of code when creating new objects which helps you clean up your code and overall improves the speed of development time, with the same quality outcome.

This module does not shorten the “outcome of code”, “clean up your code” or increase productivity. Does it also cook my code too? In fact, I cannot come up with one use case for this.

@jasperagent_dev

Why use rippling?

This may be the first question you ask, and also a good one.

Definitely.

I don’t get the hype of UI libraries incorporated to game engines that already make this task easier for you by providing visual assistance. It’s bad practice and highly redundant.

[savio14562 (savio14563)]

Is this like the old RbxUtility.Create, except you have to directly put “Properties” which is a little annoying. Or is it intended to be more like Roact?

-- RbxUtility.Create

create "Model" {
    Name = "Test"
    create "Part" {
       Position = Vector3.zero,
       Anchored = true,
    }
    Parent = workspace,
}

[SubtotalAnt8185]

It really does seem like that library. Why should we choose this over the RbxUtility.Create module?

[jasperagent_dev (StillSyriarting)]

Hiya! Thanks for the feedback(?)

I get that everyone has their own views of certain things, and thats fine :). I get that you might not like this resource:

@EatSleepCodeRepeat

This is awful.

But for me it helps, and I just took into concideration some people might think it helps too;

@jasperagent_dev

If you use different instancing tools, and find no use for this- just don’t continue,

@jasperagent_dev

in my opinion it makes it easier, but it may be different for different people working on different projects

Whether it helps you or not, it does not cook your code- so please, don’t eat it.

[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.