Solid.js feels like what I always wanted React to be

Post by benatkin » Tue, Mar 01, 2022, 8:14 AM UTC

rk06 wrote: post #120

intrnl wrote: post #96

Earlier quoted context omitted.

i'm finding a hard time articulating what you said, if React is against side effects then useEffect wouldn't have existed and we wouldn't have data fetching. React is unique in that everything in the component is within the render path, while the rest of the frameworks (that you've mentioned) doesn't. you might be mistaking "side effects during render is bad" for "side effects is bad", the two statements are not the…

I mean side effects from a functional point of view. Let me explain in more details React’s philosophy is View = F(data) I.e. view is a pure function of data. By “pure”, we mean F() does not do console.log, ajax calls, date time and other stuff which is not consistent every where. This assumption is ingrained in React. You see it when you are told that react can overrender and your code should handle overrendering. A…

Post by alskdjflaskjdhf » Tue, Mar 01, 2022, 8:25 AM UTC

ryansolid wrote: post #89

alephnan wrote: post #84

This is the same code in Svelte.js # Counter.svelte let count= 0 setInterval(() => { count += 1 }, 1000) The count is: {count}

What does a reusable (ie import from another file) `useAutoCounter` look like in Svelte?

  
    import { writable } from "svelte/store";
  
    function autoCounter(interval, initialValue = 0) {
      let { subscribe, update } = writable(initialValue);
      setInterval(() => update((n) => n + 1), interval);
      return { subscribe }
    }
  
    let counter = autoCounter(1000);
  
  
  The count is: {$counter}

Post by rk06 » Tue, Mar 01, 2022, 8:37 AM UTC

benatkin wrote: post #122

rk06 wrote: post #120

Earlier quoted context omitted.

I mean side effects from a functional point of view. Let me explain in more details React’s philosophy is View = F(data) I.e. view is a pure function of data. By “pure”, we mean F() does not do console.log, ajax calls, date time and other stuff which is not consistent every where. This assumption is ingrained in React. You see it when you are told that react can overrender and your code should handle overrendering. A…

> View = F(data) That's just how templates are meant to work. Underscore.js templates don't allow making an AJAX call before calling render() either. https://underscorejs.org/#template

Post by alephnan » Tue, Mar 01, 2022, 8:43 AM UTC

  export default function ParentComponent() {
    const [value, setValue] = createSignal("");
      return (
         
            
             setValue(e.currentTarget.value)} /> 
        
    );
  }
  
  const ChildComponent1 = ({ props }) => {props};
  const ChildComponent2 = (props) => {
    const value = props.value || "default";
    return {value};
  };
  const ChildComponent3 = (props) => {
    return {props.value || "default"};
  };
  const ChildComponent4 = (props) => {
    const value = () => props.value || "default";
    return {value()};
  };
  const ChildComponent5 = (props) => {
    const value = createMemo(() => props.value || "default");
    return {value()};
  };
  const ChildComponent6 = (props) => {
    props = mergeProps({ value: "default" }, props);
    return {props.value};
  };
  const ChildComponent7 = (props) => {
    const { value: valueProp } = props;
    const value = createMemo(() => valueProp || "default");
    return {value()};
  };
  const ChildComponent8 = (props) => {
    const valueProp = props.value;
    const value = createMemo(() => valueProp || "default");
    return {value()};
  };

Post by onion2k » Tue, Mar 01, 2022, 8:45 AM UTC

bryanrasmussen wrote: post #45

joeyjojo wrote: post #24

Earlier quoted context omitted.

This is just iteration on the awesome groundwork that React laid, and shows that things can still be much better. React has some very peculiar patterns that don't really jive well with javascript as a language, or its ecosystem. If the setInterval example is fundamentally against what React is, then IMO that really hammers the point the author is making. I have a few React projects under my belt, and often times stil…

In my personal opinion when there is a lot of complicated state in a component and there is no real benefit to splitting it up into smaller components then hooks are inferior to the older lifecycle methods (in creating understandable, maintainable code), however in my experience whenever I come to place nowadays this would be considered heresy and everything needs to be in hooks even if you have 10+ and growing numbe…