- Mar 2021
-
www.jackfranklin.co.uk www.jackfranklin.co.uk
-
Svelte is different in that by default most of your code is only going to run once; a console.log('foo') line in a component will only run when that component is first rendered.
Tags
- turning things around / doing it differently
- difference
- opinionated
- Svelte vs. React
- reasonable defaults
- opinion
- important point
- trying to doing things the same way you did in a different library/framework (learning new way of thinking about something / overcoming habits/patterns/paradigms you are accustomed to)
- unfortunate defaults
Annotators
URL
-
- Feb 2021
-
www.infoworld.com www.infoworld.com
-
This article explains why you shouldn't use getters and setters (and when you can use them) and suggests a design methodology that will help you break out of the getter/setter mentality.
-
- Oct 2020
-
github.com github.com
-
Svelte doesn't re-render, so you need to respond to component mount/dismount and prop changes separately as they are distinct concepts and never tied together, unlike in React.
Tags
- distinction
- different way of thinking about something
- trying to doing things the same way you did in a different library/framework (learning new way of thinking about something / overcoming habits/patterns/paradigms you are accustomed to)
- lifecycle callbacks
- UI library: reacting to prop changes
Annotators
URL
-
-
medium.com medium.com
-
Sometimes, you may be tempted to write that wrapper. Because all your (React or Vue or insert your reactive framework here) instincts tell you so.Resist the temptation. There is a better way. A svelter way. Introducing: the use-directive (a.k.a. “actions”).
-
However, especially when starting out, it’s very easy to fall into the “this is how I did things in my previous framework” trap.
Tags
- getting a fresh perspective
- Svelte: action (use:)
- overcoming preconceived opinions
- paradigm shift
- different way of thinking about something
- Svelte
- trying to doing things the same way you did in a different library/framework (learning new way of thinking about something / overcoming habits/patterns/paradigms you are accustomed to)
Annotators
URL
-
- Jul 2020
-
egghead.io egghead.io
-
multi-paradigm
Programming paradigms are a way to classify programming languages based on their features - these include imperative, declarative,
https://upload.wikimedia.org/wikipedia/commons/f/f7/Programming_paradigms.svg
https://en.wikipedia.org/wiki/Comparison_of_multi-paradigm_programming_languages
-
- Mar 2019
-
plato.stanford.edu plato.stanford.edu
-
such as scope, simplicity, fruitfulness, accuracy
Theories can be measured according to multiple metrics. The current default appears to be predictive accuracy, but this lists others, such as scope. If theory A predicts better but narrower and theory B predicts worse (in A's domain) but much more broadly, which is a better theory?
Others might be related to simplicity and whatnot. For example, if a theory is numerical but not explanatory (such as scaling laws or the results of statistical fitting) this theory might be useful but not satisfying.
-
Like in evolution, the process does not change toward some fixed goal according to some fixed rules, methods or standards, but rather it changes away from the pressures exerted by anomalies on the reigning theory (Kuhn 1962, 170–173). The process of scientific change is eliminative and permissive rather than instructive.
This is similar to evolution: not guided, but not random. Does this view contradict the idea of progression?
It also suggests a complex dynamic system that possess path dependence and environmental interaction.
-
- Feb 2019