- Oct 2020
-
humanwhocodes.com humanwhocodes.com
-
Once again, this isn’t good or bad, it’s just the most efficient way to create something that is similar to something else
-
This isn’t to say that multiplying code is good or bad – it’s a characteristic of all code regardless of quality.
-
Anyone who’s ever worked with me knows that I place a very high value on what ends up checked-in to a source code repository.
-
The reason for this is very simple: once code gets checked-in, it takes on a life of its own.
-
Checking in is akin to sharing your code with others, and once out in the world, it’s hard to predict what that code will do.
Tags
- better/superior solution/way to do something
- avoid extra/needless work
- time wasters
- ubiquity
- valued highly
- inherent
- once published/shared/online can't control what happens to it (copied/used)
- applicable
- quality
- quality of what is pushed/published to repository
- can't effectively predict/forecast
- not necessarily good or bad
- duplication
- inherent to all
- characteristic/property/attribute/feature
- outside of our control
- most efficient way
- inevitable
- duplication of work/effort
- code quality
Annotators
URL
-
-
-
I'm okay with an overall design that allows people to plugin the parts they need in order to be able to generically support a compile-to-javascript language, but to bake in support for one singular solution because its popular is simply bad engineering.
-
Of all the compile-to-languages, the one that strikes me as having the least merit is JSX. It's basically a ton of added complexity for the sake of what boils down to syntax. There are no real gains in terms of language semantics in JSX.
-
Furthermore, JSX encourages bad non-dry code. Having seen a lot of JSX over the past few months, its encourages copypasta coding.
-
I know where you're coming from, and to a degree, I think you're right.
-
If the react cargo cult didn't have the JSX cowpath paved for them and acclimated to describing their app interface with vanilla javascript, they'd cargo cult around that. It's really about the path of least resistance and familiarity.
-
hyperscript is much simpler to refactor and DRY up your code than with JSX, because, being vanilla javascript, its easier to work with variable assignment, loops and conditionals.
-
The only "issue" it has is that its unfamiliar. People have been working with HTML for years and are comfortable with it. That's basically the only reason that people find it more readable. If you make an effort to spend sometime with hyperscript, it becomes as familiar and readable as jsx.
-
However, as a developer that uses JSX, I find it too useful/concise to give up in the name of syntax purity, especially when I know that what it translates to is still very isolated and computationally pure.
What does "isolated" mean in this case? Is it a different sense than how isolated is usually used in programming context?
What does "computationally pure" mean? Sounds like a bit of a vague weasel word, but this is an honest question of curiosity and wanting to understand/learn.
-
This is the problem with baking in support for frameworks with special cases in the codebase. You can never support all the frameworks. :-(
-
I've recently started playing with segmentio/deku, an alternative to React, and I'm also using Babel to transpile my js and jsx code.
Tags
- alternative to mainstream way
- paving cow paths
- cargo cult
- minimal benefits
- making it easy for later refactoring
- do pros outweigh/cover cons?
- encourages the wrong thing
- too useful to give up
- alternative to:
- Deku
- making it easy to do the wrong thing
- difficult/hard
- have a good reason
- readability
- advantages/merits/pros
- making it easy to do the right thing
- purity
- duplication
- hard to make it work in _all_ cases
- isolation (programming)
- special cases
- transpiling
- investing time to really understand something
- hypothetical/alternate history
- javascript
- plugins
- copy and paste
- to understand others
- it's just _
- UI library
- adding special cases only for certain popular things but not others
- is it worth the effort?
- familiarity
- React
- can't support everything / all cases
- UI library: syntax
- subjective
- reuse existing language constructs
- making it too easy to do the wrong thing
- due to historical reasons
- familiar syntax
- doing something without knowing why/how it works
- extensibility
- not enough advantages/merits/pros to make it worthwhile
- it's just plain JavaScript
- JSX
- template language: bad: by not reusing existing language constructs; forced to reinvent equivalents which are inferior and unfamiliar
- not a real/actual problem
- comparison with:
- favoring/catering to the needs of … over …
- template language vs. reusing existing language constructs
- bad engineering
- not merited
- comfortable because familiar
- readability: depends on familiarity
- copy and paste programming
- path of least resistance
- unfamiliar
- hyperscript
- JavaScript
- can't do everything
Annotators
URL
-
-
github.com github.com
-
The reason why we don't just create a real DOM tree is that creating DOM nodes and reading the node properties is an expensive operation which is what we are trying to avoid.
-
-
www.npmjs.com www.npmjs.comhyperx1
-
This module is similar to JSX, but provided as a standards-compliant ES6 tagged template string function.
-
-
www.merriam-webster.com www.merriam-webster.com
-
github.com github.com
-
if you think this project can help you or anyone else, you may star it on GitHub
-
For the sake of best compatibility we convert the className attribute to class for svelte.
Svelte refuses to standardize on any way to pass a CSS class. I thought className was actually the most common name for this prop though even in Svelte...
-
For event listeners we support the standard jsx naming convention onEventname (this is converted to on:eventname in svelte) as well.
-
We aim to support all svelte features. In some cases this is not possible. For those cases we provided feasible workarounds.
-
jsx currently does not allow to use : in attribute/property names. As a workaround every : can be replaced be _ (for example bind_value is converted to bind:value for svelte).
Tags
- asking someone to upvote something for you
- provided
- Svelte: events
- explicit goals
- React
- Svelte: how to affect child component styles
- React: events
- standard
- impossible
- Svelte
- differences
- feature parity
- JSX
- limitations leading to workarounds
- design goals
- conversion (transform)
- workarounds
- naming convention
- equivalent/analogous/alternative ways to do something between 2 libraries/languages/etc.
- lack of standard
Annotators
URL
-
-
github.com github.com
-
-
The goal is to bring element creation down to this logic:
-
In React 0.12 time frame we did a bunch of small changes to how key, ref and defaultProps works. Particularly, they get resolved early on in the React.createElement(...) call. This made sense when everything was classes, but since then, we've introduced function components. Hooks have also make function components more prevalent. It might be time to reevaluate some of those designs to simplify things (at least for function components).
-
However, in function components there really isn't much need for this pattern since you can just use JS default arguments
-
-
softwareengineering.stackexchange.com softwareengineering.stackexchange.com
-
Right, and if most uses of an FTP service use new FtpService() the one that sets an alternate port will stand out (service.SetPort(12345))
-
-
leiss.ca leiss.ca
-
Good risk management is inherently simple; adding too many complexities increases the likelihood of overlooking the obvious.
-
-
-
I recommend folks use https://github.com/shama/bel instead of this package; we've been working hard on it for the past two years to make sure it has all the features you could want to write inline HTML. Hope it's good; closing for now!
-
-
github.com github.com
-
github.com github.com
-
By default all content inside template strings is escaped. This is great for strings, but not ideal if you want to insert HTML that's been returned from another function (for example: a markdown renderer). Use nanohtml/raw for to interpolate HTML directly.
-
-
github.com github.com
-
Hyperscript syntax for React.js markup
-
-
facebook.github.io facebook.github.io
-
However, this would lead to further divergence. Tooling that is built around the assumptions imposed by template literals wouldn't work. It would undermine the meaning of template literals. It would be necessary to define how JSX behaves within the rest of the ECMAScript grammar within the template literal anyway.
-
-
github.com github.com
-
Deku is a library for rendering interfaces using pure functions and virtual DOM.
-
It also aims to support only modern browsers to keep things simple.
-
-
www.agileconnection.com www.agileconnection.com
-
One of the inherent dangers of any form of iterative development is confusing iteration with oscillation.
-
-
www.python.org www.python.org
-
However, know when to be inconsistent -- sometimes style guide recommendations just aren't applicable.
-
When applying the guideline would make the code less readable, even for someone who is used to reading code that follows this PEP.
-
although this is also an opportunity to clean up someone else's mess
-
To be consistent with surrounding code that also breaks it (maybe for historic reasons)
-
-
developer.mozilla.org developer.mozilla.org
-
An onevent event handler property serves as a placeholder of sorts, to which a single event handler can be assigned. In order to allow multiple handlers to be installed for the same event on a given object, you can call its addEventListener() method, which manages a list of handlers for the given event on the object.
-
-
medium.com medium.com
-
Then at some moment I just stumbled upon limitations and inexpressiveness of templates and started to use JSX everywhere — and because JSX was not a typical thing for Vue I switched to React over time. I don’t want to make a step back.
-
But the vast majority of things that our apps are doing are just conditional and list rendering.
-
In my opinion it is okay to say your tool is revolutionary compared to existing ones. And it is hard to be fully unbiased about your own creation, I get it.
-
-
github.com github.com
-
Tables are not yet supported. If you love impossible to read regular expressions, submit a PR!
-
-
-
I suppose it all comes down to tooling. It should be easy to author a pattern. A set of implicit (possibly explicit) patterns to author patterns may be useful.
Tags
Annotators
URL
-
-
github.com github.com
-
Thank you to those who have failed many times, yet never gave up
Tags
Annotators
URL
-
-
docs.google.com docs.google.com
-
But it’s really hard to see, because our human brains struggle to think about this Clock function as something for generating discrete snapshots of a clock, instead of representing a persistent thing that changes over time.
-
-
-
A reasonably clean alternative would be to map a function over the array and use destructuring in the each loop: {#each [1, 2, 3, 4].map(n => ({ n, sqr_n: n * n })) as { n, sqr_n }} {sqr_n} {sqr_n / 2}<br> {/each}
-
-
github.com github.com
-
I discovered that a solution can be hacked using an {#if}, but a proper one would be nice:
-
-
tech.ebayinc.com tech.ebayinc.com
-
Every new variation to the view requires updating both the view model and the template. This holds true even for simple variations.
-
Offsetting the rules of a logic-less template requires a lot of helper methods.
-
Writing a logic-less template requires a bloated view model with comprehensive getters for the raw data. As a result, a messy and difficult-to-maintain view model usually accompanies logic-less templates.
-
that does not mean that I am advocating the other extreme–i.e., a templating language that allows a lot of logic. I find such templating languages, especially those that allow the host programming languages to be used inside the template, to be hard to read, hard to maintain, and simply a bad choice.
Tags
- solving one problem introduces another
- logic in templates: allowing host programming language to be used in template
- co-location: not co-located
- arbitrary limitations leading to less-than-ideal workarounds
- boilerplate
- hard to maintain
- logic in templates: logic-less
- duplication of work/effort
- duplication: need to update in multiple places
Annotators
URL
-
-
-
It's certainly something I've wanted to reach for prior
-
An alternative (maybe not good) would be to restrict {@const} to certain blocks like {#each} and {#if}. In both cases, it significantly reduces the "multiple ways to do the same thing" problem and avoids ergonomic and performance overhead of our current situation.
-
it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.
Tags
- idiomatic pattern (in library/framework)
- programming: multiple ways to do the same thing
- software development: code organization: where does this code belong?
- consistency
- idiomatic code style (programming languages)
- strong conventions resulting in code from different code bases/developers looking very similar
- uniformity
- "wanted to reach for"
- convention
Annotators
URL
-
-
-
I had this problem and figured out how to make something like this work with the compiler quirks.
-
Here's a proxy store I wrote to derive the value of a store nested within other stores, it plays nice with typescript and can go infinitely deep
-
-
svelte.dev svelte.dev
-
This is the Svelte version of this example: https://codesandbox.io/s/reactivity-react-responds-to-changing-props-forked-d2j44?file=/src/Label.js
-
-
nginx.org nginx.org
-
Hannah Stepanek annotated the hell out of this reference. I would do well to read what she had to say.
Tags
Annotators
URL
-
-
svelte.dev svelte.dev
-
Generally, you should read the value of a store by subscribing to it and using the value as it changes over time. Occasionally, you may need to retrieve the value of a store to which you're not subscribed. get allows you to do so.
-
-
github.com github.com
-
They even named the main file
react.js
so when converting/migrating components from React you could (at least some of the time, perhaps) simply leave some of the imports as-is:import {createHooks, useRef} from './react';
-
-
github.com github.com
-
This reactive statement is just used to have the store automatically subscribed and unsubscribed.
-
I'm not sure I understand the problem, everything you are describing is already possible.
-
Svelte right now has a lot of opportunities to have component state become out of sync with props.
-
I'm suggesting this is a problem generally. Users will not think of being out of sync with props
-
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
- can we do even better?
- easy to forget
- 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)
- issues: discuss more before closing
- different way of thinking about something
- issues: not taking the time to really understand the issue before closing
- abuse of feature
- missing feature leading to less-than-ideal workarounds
- easy to get wrong
- investing time to really understand something
- distinction
- too quick to dismiss
- a problem worth solving properly
- general problem
- UI library: reacting to prop changes
- lifecycle callbacks
Annotators
URL
-
-
dylanvann.com dylanvann.com
-
the code is a bit verbose/convoluted
-
To fix our Svelte version you might think we could use beforeUpdate or afterUpdate, but these lifecycle functions are related to the DOM being updated, not to prop updates. We only want to rerun our fetching when the album prop is changed.
-
When using React hooks there is no concept of onMount because the idea of only running some code on mount leads to writing non-resilient components, components that do one thing when they mount, and then don’t take prop changes into account.
-
Beautiful, except that switching albums does not update the PhotoGrid. This is not the automatic reactivity we were promised by Svelte.
Tags
- convoluted
- abuse of feature
- missing feature leading to less-than-ideal workarounds
- easy to get wrong
- Svelte for someone coming from React
- false assumptions
- failed to deliver on expectations
- ugly/kludgey
- surprising
- the natural assumption
- confusing for newcomers
- easy mistake to make
- Svelte
- not delivering on promise
- lifecycle callbacks
- hard to understand
- easy to forget
- easy to confuse (mix up)
- component design: resilient components
- UI library: reacting to prop changes
Annotators
URL
-
-
dylanvann.com dylanvann.com
-
Using another reactive statement with $effect we have Svelte automatically handle subscribing and unsubscribing to the store
-
I’d still be interested in Svelte making things easier so I’ve opened a feature request for Reactive statement cleanup functions.
Tags
- cross-linking to issue
- can we do even better?
- abuse of feature
- missing feature leading to less-than-ideal workarounds
- community (for a project or product)
- awkward workarounds
- take the extra time/effort to open an issue (in the appropriate project)
- cross-linking so readers can get the full context / see the outcome/resolution
- Svelte: store: custom
- don't just complain; help improve/fix things
Annotators
URL
-
-
github.com github.com
-
It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
-
-
recoiljs.org recoiljs.org
-
For reasons of compatibility and simplicity, it's best to use React's built-in state management capabilities rather than external global state.
-
-
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
- 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)
- different way of thinking about something
- Svelte: action (use:)
- paradigm shift
- overcoming preconceived opinions
- getting a fresh perspective
- Svelte
Annotators
URL
-
-
rjlipton.wordpress.com rjlipton.wordpress.com
-
A “solution” to GR is more like a model in logic: it may satisfy a theory’s axioms but have other properties that are contingent (unless the theory is categorical, meaning that all of its models are isomorphic).
-
-
bookbook.pubpub.org bookbook.pubpub.org
-
Safiya Noble, Algorithms of Oppression (New York: New York University Press, 2018). See also Mozilla’s 2019 Internet Health Report at https://internethealthreport.org/2019/lets-ask-more-of-ai/.
-
-
blog.joinmastodon.org blog.joinmastodon.org
-
So that’s already a huge advantage over other platforms due the basic design. And in my opinion it’s got advantages over the other extreme, too, a pure peer-to-peer design, where everyone would have to fend for themselves, without the pooled resources.
Definitely something the IndieWeb may have to solve for.
-
-
www.economist.com www.economist.com
-
“INFORMATION RULES”—published in 1999 but still one of the best books on digital economics—Carl Shapiro and Hal Varian, two economists, popularised the term “network effects”,
I want to get a copy of this book.
-
-
-
In the Ars memorandi noua secretissima, published in 1500 or 1501,20 Jodocus Weczdorff de Triptis (Weimar) inserted an alphabetical list of words, similar to that of Celtis, but he simply suggested that it could be used as a memory house without any scope for our private associations. Moreover, the alphabetic table of Celtis was included in the famous Margarita philosophica nova of Gregor Reisch, which was probably the most popular handbook of the artes scholars in the fi rst two decades of the 16th century.
Books on memory that used Celtes' trick
-
“The Art of Memory in Late Medieval East Central Europe (Bohemia, Hungary, Poland): An Anthology,” co-written by Lucie Doležalová, Rafał Wójcik and myself.
-
-
-
In 1945 Jacques S. Hadamard surveyed mathematicians to determine their mental processes at work by posing a series of questions to them and later published his results in An Essay on the Psychology of Invention in the Mathematical Field.
I suspect this might be an interesting read.
-
-
myscript.com myscript.com
-
MyScript MathPad
This looks like something I could integrate into my workflow.
-
-
bookbook.pubpub.org bookbook.pubpub.org
-
In April of 2019, at a digital learning conference, Manuel Espinoza spoke with educators, technologists, and annotation enthusiasts about R2L.d-undefined, .lh-undefined { background-color: rgba(0, 0, 0, 0.2) !important; }.d-undefined, .lh-undefined { background-color: rgba(0, 0, 0, 0.5) !important; }1Nate Angell and “the role that Hypothesis plays in human rights work.”
Manuel Espinoza, “Keynote,” AnnotatED Summit, April 2, 2018, https://youtu.be/5LNmSjDHipM.
-
-
danallosso.substack.com danallosso.substack.com
-
Horwitz argued a fairly radical point, which I think never received wide enough recognition due to the subject matter and his extremely difficult (dense and dry) style. He said, “I seek to show that one of the crucial choices made during the antebellum period was to promote economic growth primarily through the legal, not the tax, system, a choice which had major consequences for the distribution of wealth and power in American society”
I'll have to add this book to my to read stack.
Tags
Annotators
URL
-
-
longviewoneducation.org longviewoneducation.org
-
Universal Design for Learning: Theory and Practice by Meyer, Rose, and Gordon (a book recognized as the core statement about UDL, which you can read for free) walks us through how educators actively change their practice to become more inclusive and helps us weigh choices in terms of how we create unnecessary barriers:
-
-
github.com github.com
-
Solid supports templating in 3 forms JSX, Tagged Template Literals, and Solid's HyperScript variant.
-
So while Solid's JSX and might resemble React it by no means works like React and there should be no illusions that a JSX library will just work with Solid. Afterall, there are no JSX libraries, as they all work without JSX, only HyperScript or React ones.
Tags
- React
- JSX
- programming: multiple ways to do the same thing
- template language
- flexibility
- SolidJS
- unopinionated
- decoupled
- misleadingly similar (don't expect everything to be the same just because some things are)
- hyperscript
- misleading
- javascript: tagged template literals
- differences
Annotators
URL
-
-
-
Unfortunately people lack the the time to invest to really understand those things
-
If there was a place I thought reactivity would be weak, I embraced it and I worked on it until I was happy with the results.
-
It was clear no one was interested in what I was working towards.
-
but everything they were doing started to make sense
-
I kept on wanting them to work like Fine-Grained reactivity, since it was much more intuitive.
-
Vue was always felt contrived for me.
-
I couldn't land on how I wanted to box primitives. Should I use a getter/setter, or function form like Knockout, or explicit get/set like MobX? These were all ugly.
-
Over time Adam, Surplus' creator, had less and less time to spend on the project and I decided to take my own shot.
-
I started Solid years ago before I thought anyone would be interested in using it. I only started promoting it because it had already achieved the goals I had set out for it.
Tags
- constant evolution/improvement of software/practices/solutions
- better/superior solution/way to do something
- being explicit
- API design
- going a different direction
- needs to feel right
- not enough time
- common/shared goal
- ugly/kludgey
- abandoned due to lack of free time
- having a clear vision in mind / goal you're working towards even if no one else seems to understand/be interested
- build your own
- build the product you want to use yourself
- work on it until happy with the results/how it works/looks/feels
- can we do even better?
- finally got it right
- contrived
- build your own ideas
- feels natural
- beauty
- ergonomics (software API)
- only as good/strong/etc. as weakest link
- finding time for open-source projects
- investing time to really understand something
- forking
- finally / at last
- API
- sharing/publishing what started as a personal project; so others can use it/benefit too
- reactivity
- primitives
- intuitive
Annotators
URL
-
-
github.com github.com
-
Might have to cut my own version of the extension if its maintainers won't add support.
Tags
Annotators
URL
-
-
-
Templates are prone to unnoticed runtime errors, are hard to test, and are not easy to restructure or decompose.
-
In contrast, Javascript-made templates can be organised into components with nicely decomposed and DRY code that is more reusable and testable.
-
-
-
The $: can also be used to trigger effects.
-
We can run effects when some data changes using watchEffect - it takes a function that runs whenever a reactive value used inside changes.
-
MobX - for me personally MobX is a far better way to manage state than React Hooks. It doesn't care about the UI layer so it can be used outside the React ecosystem, and it's simple to mutate data.
-
-
twitter.com twitter.com
-
Matt Bishop on Twitter. (n.d.). Twitter. Retrieved October 9, 2020, from https://twitter.com/MatthewLBishop/status/1313949882454077441
-
-
www.thingiverse.com www.thingiverse.com
-
-
final-form.org final-form.org
-
Note that if you are calling reset() and not specify new initial values, you must call it with no arguments. Be careful to avoid things like promise.catch(reset) or onChange={form.reset} in React, as they will get arguments passed to them and reinitialize your form.
-
-
github.com github.com
-
It's really useful if your PR relates to an outstanding issue, so please reference it in your PR, or create an explanatory one for discussion. In many cases, features are absent for a reason.
-
-
html.com html.com
-
If a part of the content deserves its own heading, and that heading would be listed in a theoretical or actual table of contents, it should be placed in a <section>. The key exception is where the content may be syndicated; in this case, use <article> element instead.
-
-
neilkakkar.com neilkakkar.com
-
Confidence to express ignorance is a super power. One good way I hone this skill is by saying “Nothing to add” when I have nothing to add, instead of repeating what other people said.
-
-
github.com github.com
-
React hook for creating a value exactly once. useMemo doesn't give this guarantee unfortunately - https://reactjs.org/docs/hooks-faq.html#how-to-create-expensive-objects-lazily
-
-
github.com github.com
-
Because I haven't worked with React Native, and so I'm not a specialist in it, and developing a React Native version of this package would better be done by someone being an expert in React Native.
-
-
atomicdesign.bradfrost.com atomicdesign.bradfrost.com
-
-
impedagogy.com impedagogy.com
-
How To Write This Poem
begin here …with TIME
where words
are layered with text
where the pen
etches into screen …
then go here …
(https://www.vialogues.com/vialogues/play/61205)
… only to leap from one place
to another,
where my mind goes
I hardly every know,
only that it ventures forward …
… heard by hearts,
and scattered stars,
where I see the sky fall,
you find the debris …
our thoughts.
(https://nowcomment.com/documents/234044)
Might we be permitted them?
The dragonfly
rarely yields her ground
to the critics among
us.
-
Kevin's Response
How To Write This Poem
begin here …with TIME
where words
are layered with text
where the pen
etches into screen …
then go here … https://www.vialogues.com/vialogues/play/61205
... only to leap from one place to another, where my mind goes I hardly every know, only that it ventures forward ...
… heard by hearts, and scattered stars, where I see the sky fall, you find the debris …. https://nowcomment.com/documents/234044
Your thoughts?
-
-
github.com github.com
-
This library exports a single React Hook, useMethods, which has all the power of useReducer but none of the ceremony that comes with actions and dispatchers.
-
-
moodle.unbc.ca moodle.unbc.ca
-
r self-r
This paragraph discuses the use of the word "bullshit" as it is used in every day life. Decide whether this is arguement, structure or both.
-
A Kind Word for Bullshit: The Problem of Academic Writin
Add MLA citation
-
-
www.amazon.com www.amazon.com
-
The Pianist: The Extraordinary True Story of One Man's Survival in Warsaw, 1939-1945 Paperback – Illustrated, September 2, 2000
-
-
rjlipton.wordpress.com rjlipton.wordpress.com
-
www.quantamagazine.org www.quantamagazine.org
-
leanprover-community.github.io leanprover-community.github.ioSchedule1
-
www.nature.com www.nature.com
-
The Indian government is pushing a bold proposal that would make scholarly literature accessible for free to everyone in the country
"... accessible for free ..."
open access sampai hari ini memang hanya diartikan sebagai membuat artikel ilmiah dapat diunduh dengan membayar APC atau dikenal sebagai modus Gold OA.
Artikel oleh Peter Suber ini menjelaskan bahwa OA tidak hanya bisa dilakukan melalui jurnal Gold OA.
-
-
-
But maybe this PR should still be merged until he finds time for that?
-
Sorry this sat for so long!
Tags
- pull request stalled
- iterative process
- open-source software: progress seems slow
- waiting for maintainers to review / merge pull request / give feedback
- don't let big plans/goals get in the way of integrating/releasing smaller changes/improvements
- not a blocker (issue dependency)
- big change/rewrite vs. continuous improvements / smaller refactorings
Annotators
URL
-
-
fs.blog fs.blog
-
be quick to start books, quicker to stop them, and read the best ones again right after you finish
farnam street blog tips on reading
-
-
stackoverflow.blog stackoverflow.blog
-
He says that he sees the combination of long form pieces and Q&A as a new level of support. “We used to have level one, which was sending a ticket to the help desk, and it was something we could easily resolve for you. Level two was a more complex problem that maybe required an engineer or specialist from a certain team to figure out. I look at this new system as a level zero.” Before sending us a ticket, folks can search Teams. If they find a question that solves the problem, great. If they need more details, they can follow links to in-depth articles or collections that bring together Q&A and article with the same tags.“
-
-
leanprover.github.io leanprover.github.ioLean1
-
I'm so tempted to toy around with this.
-
-
github.com github.com
-
I created a pull request to have the if (node.parentNode) conditional added to detach. It was not applied due to the desire to find the root cause of the <meta> tag manifestation of this issue.
-
However, IMO, having the conditional in the detach function is necessary, because there are other manifestations of this error. For example, if the DOM element in a component is removed from software outside of svelte, detach will have the same error.
-
IMO, the conditional needs to be added to detach to fix all manifestations of this error.
-
- Sep 2020
-
github.com github.com
-
remaining: 0, callbacks: [] r: 0, // remaining outros c: [], // callbacks p: outros // parent group
Ugh. Why did he change this?
Similar question here: https://hyp.is/kayb_AN1EeuCb5OkL5-Yqg/github.com/sveltejs/svelte/pull/3209
Answer here: https://github.com/sveltejs/svelte/pull/3209
-
-
github.com github.com
-
Why the obfuscation of remaining to r and callbacks to c? This is fine for function-local variables but in this instance makes the code significantly harder to reason about? There is no notion of what c and r mean.
-
-
github.com github.com
-
I pushed the build files & tested it in my environment so this should work as is.
-
I pushed a hotfix, based on v3.6.3 proposed by #2086 (comment) In package.json, under devDependencies, use: "svelte": "btakita/svelte#svelte-gh-2086-hotfix"
-
-
stackoverflow.com stackoverflow.com
-
do I really have to do something like that in order to have my local modules working? it's quite impracticable to explain it to a team! there's nothing a little bit more straightforward?
-
-
sapper.svelte.dev sapper.svelte.dev
-
page components can have an optional preload function that will load some data that the page depends on. This is similar to getInitialProps in Next.js or asyncData in Nuxt.js.
-
-
www.youtube.com www.youtube.com
-
-
www.youtube.com www.youtube.com
-
-
lukeplant.me.uk lukeplant.me.uk
-
nedbatchelder.com nedbatchelder.com
-
www.theatlantic.com www.theatlantic.com
-
This dynamic is playing out during the pandemic among the many people who refuse to wear masks or practice social distancing.
people who are refusing not to wear a mask are not helping reduce transmission of coronavirus
-
-
final-form.org final-form.org
-
Keep in mind that the values in meta are dependent on you having subscribed to them with the subscription prop.
-
-
-
I guess we could always add a bunch of adapter code to watch the flag and trigger a callback when it becomes true or false...
-
-
svelte.dev svelte.dev
-
www.javascriptjanuary.com www.javascriptjanuary.com
-
The problem I have with this approach to state and prop variables is that the difference between them is very blurry. In React you can clearly see that a prop is an input to component (because of clear function notation), and that state is something internal. In Svelte they are both just variables, with the exception that props use export keyword.
This is something I've seen before: people noticing that Svelte is missing some kind of naming convention.
React has use___ convention, for example. Without that, it makes it hard to see the difference between and know just from the name that a function is an (mentioned in the other article I read) action and not a event handler or even component, for example.
-
-
svelte.dev svelte.dev
-
Because Svelte is a compiler, we're not bound to the peculiarities of JavaScript: we can design a component authoring experience, rather than having to fit it around the semantics of the language.
-
-
rollupjs.org rollupjs.orgRollup1
-
/node_modules/
This might be better than explicitly listing all external modules...?
Tags
Annotators
URL
-
-
discuss.rubyonrails.org discuss.rubyonrails.org
-
Insisting on a specific implementation, rather than proposing a clear problem, suggesting a possible solution, and “not being married” to your initial preferred solution.
-
-
shipshape.io shipshape.io
-
medium.com medium.com
-
Modules using code that doesn’t exist in browsers such as process.env.NODE_ENV and forcing you to convert or polyfill it.
-
The benefit of this approach is that rather than having these defaults and fighting against them, it’s fully up to you to decide how to handle everything.
-
Instead, rather than trying to implement what it thinks is the best way to bundle different type of assets, it leaves that entirely up to the developer to decide.
-
Personally for me, this is incredibly hard to read. Regex everywhere, nested objects with different rules and configurations that are very intuitive, multiple loaders that resolve backwards, built in loaders having obscure issues that require using third party loaders in between, separation of plugins and loaders, and so on.
-
In my opinion, because Webpack was one of the first bundlers, is heavily packed with features, and has to support swathes of legacy code and legacy module systems, it can make configuring Webpack cumbersome and challenging to use. Over the years, I’ve written package managers, compilers, and bundlers, and I still find configuring Webpack to be messy and unintuitive.
-
Unfortunately, many third party libraries, even though they are written in ESM, are published to npm as CJS modules, so we still need to concatenate them.
Tags
- better/superior solution/way to do something
- holdover
- control (programming)
- not user-friendly
- feeling in control
- under my control
- having more control/certainty when you do something manually
- CommonJS modules
- unfortunate decisions leading to less-than-ideal workarounds
- configurable
- legacy designs being a hindrance for building upon
- javascript: server environment vs. browser environment
- obscure issues
- slow to upgrade/switch to latest version/current best practice/way of doing things
- fighting against your tools
- it's up to you to decide
- webpack
- hard to use
- unopinionated
- workarounds
- strange problems
- unfortunate
- hard to read (readability)
- unintuitive
- misunderstanding
Annotators
URL
-
-
stackoverflow.com stackoverflow.com
-
Wow, no answers to this question. That's too bad. Did you ever find the solution?
-
-
jimmyutterstrom.com jimmyutterstrom.com
-
Did you know that you can create a Svelte component and with almost no extra steps distribute- and use it like any classic old Javascript library through a global constructor (let myComponent = new MyComponent())?
-
-
github.com github.com
-
So I guess what @Rich-Harris is trying to say is that (sorry, I'm just logging it here for my own benefit)
-
we've learned why you might want to use external but not globals: libraries. We've started to factor some of our client-side JS as libraries to share between projects. These libraries import $ from 'jquery'. However they don't want to presume how that import might be "fulfilled". In most projects it's fulfilled from a global i.e. a script loaded from a CDN. However in one project it's fulfilled from a local copy of jQuery for reasons I won't get into. So when these libraries bundle themselves for distribution, as ES6 modules, they mark 'jquery' as an external and not as a global. This leaves the import statements in the bundle. (Warning: Don't bundle as an IIFE or UMD, or Rollup will guess at fulfilling the import from a global, as @Rich-Harris mentions above.)
-
-
engineering.mixmax.com engineering.mixmax.com
-
There are two ways of handling this with Rollup, as described by the troubleshooting link from the warning. Unfortunately, both Rollup and React recommend the wrong one.
-
-
github.com github.com
-
Luckily, there is absolutely no good reason not to use strict mode for everything — so the solution to this problem is to lobby the authors of those modules to update them.
-
-
medium.com medium.com
-
small modules allow library authors to become lazy. Why include that six-line helper function when you can do a one-line `require`?
-
These are all things that make your life as a library author easier.
-
This happens because npm makes it ridiculously easy for people to release their half-baked experiments into the wild. The only barrier to entry is the difficulty of finding an unused package name. I’m all in favour of enabling creators, but npm lowers the barriers right to the floor, with predictable results.
-
I think I know why: it’s because the small modules philosophy favours library authors (like Sindre) at the ultimate expense of library users.
-
-
github.com github.com
-
I hope I won’t forget, but I’ll come back to you once we’ve got an idea on how to improve this Svelte API
-
-
github.com github.com
-
DX: start sapper project; configure eslint; eslint say that svelt should be dep; update package.json; build fails with crypt error; try to figure what the hell; google it; come here (if you have luck); revert package.json; add ignore error to eslint; Maybe we should offer better solution for this.
-
When the message say function was called outside component initialization first will look at my code and last at my configuration.
Tags
- useless/unhelpful/generic error messages that don't reveal why/how error was caused
- can we do even better?
- errors are helpful for development (better than silently failing)
- what a reasonable person would do
- frustrating
- web search for something brings me here
- dev experience
- error messages: should reveal/point to why/how error was caused and how to fix/prevent it
- errors
- expectations
- reasonable expectation
- good point
Annotators
URL
-
-
github.com github.com
-
GitHub issues aren't the right place for support questions like this. Please ask on StackOverflow or in our Discord chat room.
It was actually cross-posted here: https://stackoverflow.com/questions/62101637/urql-svelte-function-called-outside-component-initialization-if-not-in-onmou
-
-
stackoverflow.com stackoverflow.com
-
The recommended solution for onMount is the same as for useEffect — place an async function inside the handler
-
(Note that you're responsible for handling any race conditions that arise as a result of the component being destroyed before the promise resolves, though assigning state inside a destroyed component is harmless.)
-
-
-
Most simple example: <script> import ChildComponent from './Child.svelte'; </script> <style> .class-to-add { background-color: tomato; } </style> <ChildComponent class="class-to-add" /> ...compiles to CSS without the class-to-add declaration, as svelte currently does not recognize the class name as being used. I'd expect class-to-add is bundled with all nested style declarations class-to-add is passed to ChildComponent as class-to-add svelte-HASH This looks like a bug / missing feature to me.
-
Also Svelte is so great because developer do not need to worry about class names conflict, except of passing (global) classes to component (sic!).
-
-
I wrote hundreds of Rect components and what I learned is that Componets should be able to be styled by developer who is using it.
Tags
- +0.9
- surprising behavior
- Svelte: how to affect child component styles
- consistency
- key point
- features
- missing feature
- missed opportunity
- framework taking care of responsibility so users can leverage it and not have to worry about that responsibility themselves
- who should have control over this? (programming)
- how to affect child component components without their cooperation
Annotators
URL
-
-
-
I think instead, there would need to be some special way to make the distinction of what is a slot attribute and what is a slot prop to be consumed with let:. Maybe a new directive like <slot attr:class="abc"/>?
-
I can't add special props and keywords to every single component I have and will ever create for this to work.
-
There are work arounds, but nothing clean. I just feel like this should be functionality that should be part of the slot feature.
Tags
- clean solution
- too hard/difficult/much work to expect end-developers to write from scratch (need library to do it for them)
- how to affect child components
- first-class support
- distinction
- workarounds
- maintenance burden to explicitly define/enumerate/hard-code possible options (explicit interface)
- how to affect child component components without their cooperation
- library/framework could make this easier
Annotators
URL
-
-
github.com github.com
-
Explicitly exposing any attributes that might get overridden by a parent seems impractical to me.
-
feel like there needs to be an easy way to style sub-components without their cooperation
-
There's no way to change style incapsulation method without patching the compiler, and this means maintaing a fork, which is not desirable.
-
The problem with working around the current limitations of Svelte style (:global, svelte:head, external styles or various wild card selectors) is that the API is uglier, bigger, harder to explain AND it loses one of the best features of Svelte IMO - contextual style encapsulation. I can understand that CSS classes are a bit uncontrollable, but this type of blocking will just push developers to work around it and create worse solutions.
Tags
- interesting wording
- impractical
- control (programming)
- Svelte: how to affect child component styles
- arbitrary limitations leading to less-than-ideal workarounds
- scalability
- forking to add a desired missing feature/change
- avoid forking if possible
- missing out on the benefits of something
- +0.9
- key point
- trying to prevent one bad thing leading to people doing/choosing an even worse option
- Svelte: CSS encapsulation
- important point
- maintenance burden to explicitly define/enumerate/hard-code possible options (explicit interface)
- how to affect child component components without their cooperation
- quotable
Annotators
URL
-
-
github.com github.com
-
There is a good amount of properties that should mostly be applied from a parent's point of view. We're talking stuff like grid-area in grid layouts, margin and flex in flex layouts. Even properties like position and and the top/right/left/bottom following it in some cases.
-
Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.
-
Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.
-
If you want this control then wrap them in a DOM node that the parent controls. If you want to pass in values then use props and if you want to pass in values from higher up the tree, the new style RFC may be able to help.
-
new style RFC
-
This allows passing classes to child components with svelte-{hash} through the class prop and prevents removing such classes from css.
Tags
- being explicit
- official opinion/stance/position
- Svelte: how to affect child component styles
- official preferred convention / way to do something
- ugly/kludgey
- make it a link if can be made a link to something useful/relevant
- forking to add a desired missing feature/change
- component/library author can't consider/know ahead of time all of the ways users may want to use it
- run-time dynamicness/generics vs. having to explicitly list/hard-code all options ahead of time
- explicit interfaces
- maintenance burden
- trying to prevent one bad thing leading to people doing/choosing an even worse option
- burden
- workarounds
- missed opportunity
- maintenance burden to explicitly define/enumerate/hard-code possible options (explicit interface)
- who should have control over this? (programming)
- missed opportunity: link to what you are referring to
- Svelte: components are their own boss (encapsulation)
- forced to fork/copy and paste library code because it didn't provide enough customizability/extensibility / didn't foresee some specific prop/behavior that needed to be overridable/configurable (explicit interface)
Annotators
URL
-
-
svelte.dev svelte.dev
-
github.com github.com
-
Would style .classInChild from your parent. The only drawback is that you might need an extra wrapping element.
-
-
github.com github.com
-
This has already forced me to forgo Svelte Material because I would like to add some actions to their components but I cannot and it does not make sense for them to cater to my specific use-case by baking random stuff into the library used by everyone.
-