I believe there’s a finite, fixed amount of complexity in problems; that there is, categorically, no way to solve problems without that amount of complexity that is inherently part of the problem domain.
So, what you have here does not remove complexity from problems, it moves the complexity from one place to another.
So, when you have a simple task, and a straightforward framework, what you see is “it’s easy!”. …because when you use the complex framework you get a bunch of “solutions” to problems that don’t exist on your problem.
That’s why it appears overly complex.
…but for a complex problem, when all you have is a simple framework (like <For…>) you have to implement the complexity yourself, which makes you view the framework as feeble and under whelming.
So, you are just moving the complexity from one place to another; the question is, is the complexity of react really something most people need, or can a framework like solid solve the 90% of simple problems most developers have?
It’s hard to tell.
Most new frameworks excel at solving simple problems because it makes for cute demos.
Is solid any different?
That’s my question. How does it work at scale, for large complex projects? Is there a whole design system implemented in it? Who’s using it and for what?
The claim that it’s “not complex” doesn’t help.
All that means is there are probably a crap load of things it doesn’t include I’ll have to do myself.
There is no magic bullet that removes complexity from tasks.
React is a complex beast, and a nice clean framework to replace it would be welcome.
…but you have to approach this kind of discussion honestly.
So, what you have here does not remove complexity from problems, it moves the complexity from one place to another.
So, when you have a simple task, and a straightforward framework, what you see is “it’s easy!”. …because when you use the complex framework you get a bunch of “solutions” to problems that don’t exist on your problem.
That’s why it appears overly complex.
…but for a complex problem, when all you have is a simple framework (like <For…>) you have to implement the complexity yourself, which makes you view the framework as feeble and under whelming.
So, you are just moving the complexity from one place to another; the question is, is the complexity of react really something most people need, or can a framework like solid solve the 90% of simple problems most developers have?
It’s hard to tell.
Most new frameworks excel at solving simple problems because it makes for cute demos.
Is solid any different?
That’s my question. How does it work at scale, for large complex projects? Is there a whole design system implemented in it? Who’s using it and for what?
The claim that it’s “not complex” doesn’t help.
All that means is there are probably a crap load of things it doesn’t include I’ll have to do myself.
There is no magic bullet that removes complexity from tasks.
React is a complex beast, and a nice clean framework to replace it would be welcome.
…but you have to approach this kind of discussion honestly.
Hello world examples are a dime a dozen.