- Jan 2021
-
discourse.ubuntu.com discourse.ubuntu.com
-
but that doesn’t mean that confining applications is not a benefit also to FOSS applications, security is an issue that needs to be addressed with many layers of measures no mater what licensing approach you use to license the software
-
The benefits for developers do reflect on benefits for users, with more software delivered faster and more securely.
-
« Half solved » because, hey, still it’s proprietary so who knows ? You have to trust the software editor then, it’s just moving the trust cursor.
-
This example of the chromium really shows that unless snaps or other similar format was used, applications would have to be sometime very heavily patched to work on older versions of systems to the point that it generates so much work that it would not be worth do to it otherwise, or at least not worth when the snap option exists and doesn’t require that much more work.
-
But now Chromium is no more available as deb, so what to expect ?
-
Adding layer of settings and complexity for the end user might also bring bad practices to keep a comfortable use of app’s by installing snap without confinement…
Tags
- unfortunate
- moving/shifting the problem (to a different area/place)
- better for some but worse for others
- pull the rug out from under someone
- trust/reliance/dependence on third party
- software licensing
- bad user experience
- surprising
- advantages/merits/pros
- security
- Snap
- trust
- not necessarily the case
- not
- benefit to both developer and to user
- confinement (security)
- the benefits of both
- unintended consequence
- not delivering on promise
- reducing the amount of work/effort required (efficiency / maintenance burden)
- user expectations
- bypassing security constraints because they get in the way
- benefiting one party benefits another
- user experience
- delivering software/changes faster
Annotators
URL
-
-
outline.com outline.com
-
https://outline.com/tan7Ej
Why Do People love Kungfustory?
It’s well-established among the original novel/translating community that Kungfustory.com is the best.
Kungfustory.com is just a place where Kungfustory can be hosted. It’s very user-friendly for readers, with a superb app that functions very well and reliably on phones. It’s easy to compile a list of reads, to know when those reads have been recently updated, and to follow along your favorite story.
Select any genre you like: romance, stories with reborn heroes, magical realism, eastern fantasy the world of wuxia, horror stories, romantic love novels, fanfiction, sci-fi.
New chapters added daily, Never be bored with new addictive plots and new worlds.
-
-
hypothes.is hypothes.is
-
Why Do People love Kungfustory?
It’s well-established among the original novel/translating community that Kungfustory.com is the best.
Kungfustory.com is just a place where Kungfustory can be hosted. It’s very user-friendly for readers, with a superb app that functions very well and reliably on phones. It’s easy to compile a list of reads, to know when those reads have been recently updated, and to follow along your favorite story.
Select any genre you like: romance, stories with reborn heroes, magical realism, eastern fantasy the world of wuxia, horror stories, romantic love novels, fanfiction, sci-fi.
New chapters added daily, Never be bored with new addictive plots and new worlds.
-
- Dec 2020
-
material-ui.com material-ui.com
-
Heading hierarchy. Don't skip heading levels. In order to solve this problem, you need to separate the semantics from the style.
-
-
journals.plos.org journals.plos.org
-
Moher D, Bouter L, Kleinert S, Glasziou P, Sham MH, Barbour V, et al. (2020) The Hong Kong Principles for assessing researchers: Fostering research integrity. PLoS Biol 18(7): e3000737. https://doi.org/10.1371/journal.pbio.3000737
-
-
tools.ietf.org tools.ietf.org
-
When the RFC 822 format ([28], [4]) is being used, the mail data include the header fields such as those named Date, Subject, To, Cc, and From.
This just answered my question regarding the quote from "Postfix: The Definitive Guide":
ENVELOPE ADDRESSES AND MESSAGE HEADERS A common source of confusion for email users is the fact that the To: address in email message headers has nothing to do with where a message is actually delivered. The envelope address controls message delivery. In practice, when you compose a message and provide your MUA with a To: address, your MUA uses that same address as the envelope destination address, but this is not required nor is it always the case. From the MTA’s point of view, message headers are part of the content of an email message. The delivery of a message is determined by the addresses specified during the SMTP conversation. These addresses are the envelope addresses , and they are the only thing that determine where messages go. See Section 2.2.8 later in the chapter for an explanation of the SMTP protocol.
Mailing lists and spam are common examples of when the envelope destination address differs from the To: address of the message headers.
Also an answer to this question.
-
-
outline.com outline.com
-
Its called the Dunning-Kruger effect
The Dunning-Kruger effect is undoubtedly important, but since stupidity has always existed, this doesn't explain why the problem has become worse in recent years.
I think David Riesman hinted at it in his 1959 The Lonely Crowed. Specifically, the transition from a production-oriented economy to a consumption-oriented one has increased the distance between personal experience and expertise that has consequences.
Once there were many workers whose jobs involved listening to and excepting expert guidance. An auto mechanic knew the wrong kind of oil would ruin an engine; a railroad worker knew some steels work better as rails in difference circumstances; a seamstress knew there were important differences between different thread materials. They received expert advice, and saw what happened when it was ignored.
The vast majority of expertise can be denied without any consequence at all to the individual. Even when there are consequences -- such as with the brain-surgeon example from the article -- the denying individual isn't likely to learn any lesson. Honestly, how often can a patient actually see the consequence of that doctor's advice, when alternative narratives are pervasive?
This is a large part of a more general trend towards individualized epistemology, based on each individual's tribal affiliations and social identification.
Education could overcome it, but that requires winning the coordination game that has always crippled education.
-
-
chem.libretexts.org chem.libretexts.org
-
Nodes A wave function node occurs at points where the wave function is zero and changes signs. The electron has zero probability of being located at a node.
Nodes
Tags
Annotators
URL
-
-
github.com github.com
-
Jbuilder gives you a simple DSL for declaring JSON structures that beats manipulating giant hash structures. This is particularly helpful when the generation process is fraught with conditionals and loops.
-
-
github.com github.com
-
I tried leaking session and page data and indeed it's easy. Too easy. So I definitely agree that session data should not be readable from anywhere but the request itself.
-
-
twitter.com twitter.com
-
ReconfigBehSci @SciBeh (2020) For those who might think this issue isn't settled yet, the piece include below has further graphs indicating just how much "protecting the economy" is associated with "keeping the virus under control" Twitter. Retrieved from: https://twitter.com/i/web/status/1306216113722871808
-
-
psycnet.apa.org psycnet.apa.org
-
Jarecki, J. B., & Wilke, A. (2018). Into the black box: Tracing information about risks related to 10 evolutionary problems. Evolutionary Behavioral Sciences, 12(3), 230–244. Retrieved from: https://psycnet.apa.org/doiLanding?doi=10.1037%2Febs0000123
-
-
wiki.gnome.org wiki.gnome.org
-
Why Vala? Many developers want to write GNOME applications and libraries in high-level programming languages but can't or don't want to use C# or Java for various reasons, so they are stuck with C without syntax support for the GObject type system. The Vala compiler allows developers to write complex object-oriented code rapidly while maintaining a standard C API and ABI and keeping the memory requirements low.
Tags
Annotators
URL
-
-
-
It is quite large, the letters along its spine are big and bright, and readers are required to own it in print, because Mr. Caro, who still uses a typewriter, has refused to distribute the written version in any other way.
I've always wondered why there wasn't a digital edition available after all this time.
-
-
www.aier.org www.aier.org
-
such as Elon Musk and the scientists who drafted the Great Barrington Declaration — are giants in their fields. They risk everything, weathering exhausting personal attacks from all sides, in order to battle the crowd.
Social pressure to conform is strong. What must we make of those that do not. What's there problem. They must be insane, batshit crazy, driven, courageous and or strong. Nothing to like about them. If it wasn't for the fact that they have skin in the game I wouldn't give them much thought.
-
Princeton professor Robert P. George, a specialist in moral and political philosophy and the theory of conscience, uses the example of slavery to demonstrate that every serious moral dilemma reveals two categories of people: the majority, who go along with the popular zeitgeist no matter how atrocious it is; and the minority, who risk their very existence to fight it.
Does the majority always goes along with the popular zeitgeist?
-
-
hypothes.is hypothes.is
-
No athlete has embodied the soul of a city and the spirit of its people as Richard did in the 1940s and '50s in Montreal. The Rocket's triumphs were the people's triumphs. In a match the previous Sunday, Richard had twice viciously slashed his nemesis, Hal Laycoe of the Boston Bruins, and then assaulted a linesman. Richard was then suspended for the remaining regular season. Richard had led the Canadiens to three Stanley Cups and had scored 50 goals in 50 games, but he had never won a scoring title and was on the brink of his first. The Richard Riot is generally considered the first explosion of French-Canadian nationalism, the beginning of a social and political dynamic that shapes Canada to this day.
-
Cleophas Pesant is the son of Thadee Pesant also known as the blacksmith, was already in light-coloured summer garments, and sported an American coat with broad padded shoulders. Beside him Egide Simard, and others who had come a long road by sleigh, fastened their long fur coats as they left the church, drawing them in at the waist with scarlet sashes. The young folk of the village, very smart in coats with otter collars, gave deferential greeting to old Nazaire Larouche; a tall man with gray hair and huge bony shoulders who had in no wise altered for the mass his everyday garb: short jacket of brown cloth lined with sheepskin, patched trousers, and thick woollen socks under moose-hide moccasins. Cleophas Pesant waited for Louisa Tremblay who was alone, and they went off together along the wooden sidewalk in the direction of the house. Samuel Chapdelaine and Maria had gone but a little way when a young man halted them. Samuel Chapdelaine and Maria were to dine with their relative Azalma Larouche. There was nothing to look at; in the settlements new houses and barns might go up from year to year, or be deserted and tumble into ruin; but the life of the woods is so unhurried that one must needs have more than the patience of a human being to await and mark its advance. Telesphore busied himself with the dog-harness and made believe not to hear.
-
Brebeuf commenced his letter when he described the conversion , baptism, and happy death of some Hurons. At a council of the Huron chiefs, Brébeuf produces letters from Champlain and Duplessis-Bochart, who exhort the tribesmen to follow the teaching of the missionaries. The Hurons are in constant dread of hostile incursions from the Iroquois. In August, Mercier and Pijart arrive from Quebec. Brébeuf recounts the many perils of the journey hither, and the annoyances and dangers to which apostles of the faith are continually exposed among the savages. But he offers much encouragement. Brébeuf closes his account with an expression of much hope for the future success of their labors. Mingled, however, with fear lest these savage neophytes may grow restive when placed under greater restrictions on their moral and social conduct, than have thus far seemed advisable to the cautious missionaries.
-
-
niklasblog.com niklasblog.com
-
I heard a female voice softly reading these lyrics
The song is Dial D For Devotion.
Tags
Annotators
URL
-
-
www.npmjs.com www.npmjs.com
-
You can afford to make a proper PR to upstream.
-
No more waiting around for pull requests to be merged and published. No more forking repos just to fix that one tiny thing preventing your app from working.
This could be both good and bad.
potential downside: If people only fix things locally, then they may be less inclined/likely to actually/also submit a merge request, and therefore it may be less likely that this actually (ever) gets fixed upstream. Which is kind of ironic, considering the stated goal "No more waiting around for pull requests to be merged and published." But if this obviates the need to create a pull request (does it), then this could backfire / work against that goal.
Requiring someone to fork a repo and push up a fix commit -- although a little extra work compared to just fixing locally -- is actually a good thing overall, for the community/ecosystem.
Ah, good, I see they touched on some of these points in the sections:
- Benefits of patching over forking
- When to fork instead
Tags
- taking the time to do it right/properly
- pull request
- irony
- pull request stalled
- doing it right/properly
- proper
- maintaining a fork while waiting for upstream to merge
- making it easy to do the wrong thing
- forking to add a desired missing feature/change
- limited time: not right now (maybe later)
- forking (patching vs. forking)
- when to _
Annotators
URL
-
-
github.com github.com
-
Also agree that <svelte:slot> is perhaps a little confusing since it replaces the slot attribute rather than the slot element, so <svelte:fragment> would make more sense
-
-
github.com github.com
-
Just to reiterate the discussion on the RFC, there was a suggestion that we change <svelte:slot slot="foo"> to <svelte:fragment slot="foo">, since it's the counterpart to a <slot> rather than an equivalent to it
-
-
github.com github.com
-
-
Treating the web as a compile target has a lot of implications, many negative. For example “view source” is a beloved feature of the web that’s an important part of its history and especially useful for learning, but Svelte’s compiled output is much harder to follow than its source. Source maps, which Svelte uses to map its web language outputs back to its source language, have limitations.
-
With some frameworks, you may find your needs at odds with the enterprise-level goals of a megacorp owner, and you may both benefit and sometimes suffer from their web-scale engineering. Svelte’s future does not depend on the continued delivery of business value to one company, and its direction is shaped in public by volunteers.
-
Svelte components are a thin layer over the DOM and naturally expose the web platform. Coding in Svelte feels like I’m moving with the grain of the web.
-
but really, the whole is what feels so good.
-
These are valid comments. I think it is worth noting that svelte didn’t choose a non-javascript method for fun or because we think we should redesign the language. The additional constructs, for the most part, are there to allow svelte to more clearly work out exactly what is going on in the code in order to optimise. In short svelte needs a certain amount of information to do what it does and pure javascript is often difficult to analyse in this way. But I appreciate your concerns and comments and we try to take all feedback on board where we can. So thank you!
Tags
- learning from others
- business interests/needs overriding interests/needs of users
- excellent writing
- web platform
- learning by reading the source
- answer the "why?"
- balance of power
- going with the grain
- thin abstraction/layer
- feels good
- at odds with
- open-source projects: allowing community (who are not on core team) to influence/affect/steer the direction of the project
- more interested in their own interests
- receiving feedback
- organic
- conflict of interest
- Svelte
- the whole (as opposed to the individual parts)
- read the source code
- future of project depending on continued delivery of business value to one company
- recommended software
Annotators
URL
-
-
github.com github.com
-
locked and limited conversation to collaborators
Why do they punish the rest of us (can't even add a thumb up reaction) just because someone was "talking too much" or something on this issue?
-
-
hacks.mozilla.org hacks.mozilla.org
-
Better contribution workflow: We will be using GitHub’s contribution tools and features, essentially moving MDN from a Wiki model to a pull request (PR) model. This is so much better for contribution, allowing for intelligent linting, mass edits, and inclusion of MDN docs in whatever workflows you want to add it to (you can edit MDN source files directly in your favorite code editor).
-
-
github.com github.com
-
I think the main difference between the two are the way API are served. Some smelte components need you to input big chunk of json as props, while i prefer keep props as primitive types and in the other hand give you different components tags to compose.
-
I don't think this is what really matters at the end, since whatever is the implementation the goal should be to provide a library that people actually like to use.
-
I personally think that starting from google's components makes easier to keeping update to material specs updates.
Tags
- build upon the work of others
- something people like to use
- not following the standard/specification
- +0.9
- MDC
- implementation detail
- svelte-material-ui
- ergonomics (software API)
- keeping in sync with changes to the standard/specification
- API design
- simple API
- doesn't matter
- building blocks / primitives
- see content below
- technical details
- nice API
- primitives
- better than the alternatives
- easy to use
- usability
- comparison
- better/superior solution/way to do something
- comparing one's project/product with competition/alternatives
- pleasant/enjoyable to use
- being the thing that people are looking for
Annotators
URL
-
-
github.com github.com
-
These are sequential because build:ssr imports the public/index.html that build:dom produces.
-
-
www.unicef.org www.unicef.org
-
Appeal highlights
Gives obvious area for facts (logos) which also can create ethos from them knowing so much information
-
UNICEF’s Humanitarian Action for Children appeal helps support the agency’s work as it provides conflict- and disaster-affected children with access to water, sanitation, nutrition, education, health and protection services. Read more about this year’s appeal here.
Gives overall mission as UNICEF, to show wide range of efforts
-
Key planned results for 2020
Shows what they want to achieve
-
Funding requirements for 2020
Show how much money is needed to achieve results
-
-
www.harborfreight.com www.harborfreight.com
-
For safety reasons, certain pumps and sprayers cannot be returned to the store if opened.
More likely: they don't want to deal with these returns because of risk to store and because they want to keep the money they made from the sale.
-
- Nov 2020
-
epeus.blogspot.com epeus.blogspot.com
-
This seems like a useful reference within my research for determining things online that are "beyond the pale". Also includes some additional prior art and references itself.
-
-
www.theatlantic.com www.theatlantic.com
-
Selection by association, rather than indexing, may yet be mechanized. One cannot hope thus to equal the speed and flexibility with which the mind follows an associative trail, but it should be possible to beat the mind decisively in regard to the permanence and clarity of the items resurrected from storage.
It should be easy to surpass the mind's performance in terms of storage capacity as well as lossiness. It might be more difficult to surpass it in terms of the speed and flexibility with which it "follows an associative trail"
-
-
acorwin.com acorwin.com
-
The answer should be: you write a language that compiles to Go’s IR.
-
One important other option is using another programming language as your IR! If you can compile (or perhaps more accurately transpile) your language into C, then you can leverage gcc (or clang, etc) into compiling that all the way down into machine code.
-
-
stackoverflow.com stackoverflow.com
-
delete myObject.regex; // or, delete myObject['regex']; // or, var prop = "regex"; delete myObject[prop];
-
-
stackoverflow.com stackoverflow.com
-
emphasizing that 'this' and 'global object' are two different things not only in Node.js but in JavaScript in general
-
-
www.reddit.com www.reddit.com
-
I wouldn't use Flutter for web, mobile is good though.
-
It's super promising for web apps, just maybe not for web pages. I went from React to Svelte to Flutter for my current app project, and every step felt like a major upgrade.Flutter provides the best developer experience bar none, and I think it also has the potential to provide the best user experience. But probably only for PWAs, which users are likely to install anyway. Or other self-contained experiences, like Facebook games. It does have some Flash vibes, but is far more suitable for proper app development than Flash ever was while still feeling more like a normal website to the average user. It won't be the right choice for everything, but I believe it will be for a lot of things.
-
I also find that a lot of the complexity of Flutter can be avoided, and I mostly use it to define the UI as a more app-centric alternative to HTML/CSS.
I mostly use it to define the UI as a more app-centric alternative to HTML/CSS.
-
Svelte by itself is great, but doing a complete PWA (with service workers, etc) that runs and scales on multiple devices with high quality app-like UI controls quickly gets complex. Flutter just provides much better tooling for that out of the box IMO. You are not molding a website into an app, you are just building an app. If I was building a relatively simple web app that is only meant to run on the web, then I might still prefer Svelte in some cases.
Tags
- Flutter
- Svelte
- using the right tool for the job
- UI library
- comparison
- annotation meta: may need new tag
- framework taking care of responsibility so users can leverage it and not have to worry about that responsibility themselves
- good point
- determining if something is an appropriate application / best tool for the job
Annotators
URL
-
-
ux.stackexchange.com ux.stackexchange.com
-
However, in the all caps example the order of importance goes Title->Actions->Description (or even the actions before the title), while in the others this order is not as evident at first glance.
-
-
uxdesign.cc uxdesign.cc
-
When writing copy for buttons, make sure that you keep consistency.
-
Note: Yes, it is sentence case, and yes, there should be a full stop if it was true sentence case — but for the love of all things good and designy, please don’t add a full stop.
-
“Why?” you ask. This is for two reasons.
-
-
github.com github.com
-
enables passive event listeners by default for some events (see list below). It basically will set { passive: true } automatically every time you declare a new event listener.
-
-
-
github.com github.com
-
There are actually 3 other libraries that implements material in svelte, i hope this to become the community favorite because using MDC underneath it implements correctly Material guidelines.
-
from my point of view, it is (by far) the best way, to build a layer on top https://github.com/material-components/material-components-web . This is also the path that the Angular Material team has taken, although they have already made a huge effort to create the components themselves.
-
After i've stabilized the library i can start to discuss about adding new components and features!
-
This one gets the SEO, so I hope you're successful @raythurnevoid.
I assume this gets search traffic because people hope/assume that since there's a React "material-ui" that there might already be a "svelte-material-ui" port/adaptation available. So they search for exactly that (like I did). That and being the first to create that something (with that name).
Tags
- being the thing that people are looking for and hoping/assuming already exists
- stability (API not changing)
- MDC
- getting/attaining wide reach/audience/popularity due to being first to market
- better than the alternatives
- competition in open-source software
- pointing out gaps/downsides/cons in competition/alternatives
- order is important / do things in the right order
- web search for something brings me here
- having a name containing a search term that people are looking for
- port (adaptation/translation)
- building upon other software projects
- good point
- excellent name
- comparing one's project/product with competition/alternatives
- don't reinvent the wheel
- getting/attaining wide reach/audience/popularity due to being or having a name containing a search term that people are looking for
- recommended option/alternative
Annotators
URL
-
-
github.com github.com
-
There is no rerender, when you call listen, then all scroll events will warn on chrome. See this entry from svelte: breaking the web
Even the author of this library forgot this about Svelte?? :) (Or maybe he didn't and this response misunderstood/falsely assumed that he had.)
-
-
hackernoon.com hackernoon.com
-
Many linguists believe that the natural language a person speaks affects how they think. Does the same concept apply to computer languages?
-
-
www.grammarly.com www.grammarly.com
-
In the case of email, it can be argued that the widespread use of the unhyphenated spelling has made this compound noun an exception to the rule. It might also be said that closed (unhyphenated) spelling is simply the direction English is evolving, but good luck arguing that “tshirt” is a good way to write “t-shirt.”
-
-
timdeschryver.dev timdeschryver.dev
-
Svelte makes the pit of success larger because it hides all of this from us at compile time.
-
At the start this is hard to get right, and bad practices will sneak into the codebase.
-
-
github.com github.com
-
Because of those similarities, it's possible to automate some of the changes.
-
-
www.kickstarter.com www.kickstarter.com
-
I'm still calling this v1.00 as this is what will be included in the first print run.
There seems to be an artificial pressure and a false assumption that the version that gets printed and included in the box be the "magic number" 1.00.
But I think there is absolutely nothing bad or to be ashamed of to have the version number printed in the rule book be 1.47 or even 2.0. (Or, of course, you could just not print it at all.) It's just being transparent/honest about how many versions/revisions you've made. 
-
-
-
So handling the interop upfront will avoid users writing invalid ES6 and make sure that they write ES6 that loads CommonJS in the right way.
-
-
laniewski.me laniewski.me
-
It is important to notice that if you are planning on making your application a PWA, you don’t have to rewrite all the logic.
-
-
openlibrary.org openlibrary.org
-
The ultimate goal of the Open Library is to make all the published works of humankind available to everyone in the world. While large in scope and ambition, this goal is within our grasp.
-
-
github.com github.com
-
This library is part of a general project at the Internet Archive (archive.org) to support the decentralized web.
-
-
help.archive.org help.archive.org
-
We convene the Decentralized Web Summit, dedicated to creating the Web we want and the Web we deserve. A Web that is private, safe and locked open for good.
-
-
www.npmjs.com www.npmjs.com
-
This module should not be used in other npm modules since it modifies the default require behavior! It is designed to be used for development of final projects i.e. web-sites, applications etc.
-
-
greenelab.github.io greenelab.github.io
-
IL-1β is anti-inflammatory
maybe some error here, IL-1beta is considered inflammatory, as far as I know https://en.wikipedia.org/wiki/Interleukin_1_beta
-
-
stackoverflow.com stackoverflow.com
-
Never use x && y || z when y can return a non-zero exit status.
-
-
unix.stackexchange.com unix.stackexchange.com
-
I think what the author intended to do was check if the second argument was a non-empty string (which is not the same thing as checking whether there are more than 1 argument, as the second argument could be passed but be the empty string).
-
-
stackoverflow.com stackoverflow.com
-
Man, for some reason, I really like this answer. I recognize it's a bit more complicated, but it seems so useful. And given that I'm no bash expert, it leads me to believe that my logic is faulty, and there's something wrong with this methodology, otherwise, I feel others would have given it more praise. So, what's the problem with this function? Is there anything I should be looking out for here?
I think the main thing wrong with it is the eval (which I think can be changed to
$("$@")
and it's pretty verbose.Also, there are more concise ways to do it that would probably appeal more to most bash experts...
like set -x
and it does unnecessary things: why save output to a variable? Just let output go to where it would normally go...
So yeah, I can see why this solution isn't very popular. And I'm rather surprised by all the praise comments it's gotten.
-
-
mywiki.wooledge.org mywiki.wooledge.org
-
However, this construct is not completely equivalent to if ... fi in the general case.
The caveat/mistake here is if you treat it / think that it is equivalent to if a then b else c. That is not the case if b has any chance of failing.
-
Some people try to use && and || as a shortcut syntax for if ... then ... else ... fi, perhaps because they think they are being clever.
-
-
-
The imports in the published package should now be fixed in 3.29.5.
-
-
github.com github.com
-
It is open to the community to help set its direction.
-
-
en.wikipedia.org en.wikipedia.org
-
The meaning of the word "modularity" can vary somewhat based on context. The following are contextual examples of modularity across several fields of science, technology, industry, and culture:
-
-
github.com github.com
-
This seems to be #31189 . It should be fixed when you update to v17.03.0-ce
-
-
github.com github.com
-
It took us a long time for everyone to get on the same page about the requirements spanning frameworks, tooling and native implementations. Only after pushing in various concrete directions did we get a full understanding of the requirements which this proposal aims to meet.
-
-
stackoverflow.com stackoverflow.com
-
that's the only really accurate answer to the question: all the others propositions run an "almost same" container, but they forget the volumes, env, UIDs,
-
-
-
Why the urgency? You can always fall back to a full clone.
Tags
Annotators
URL
-
-
github.com github.com
-
In Rust, we use the "No New Rationale" rule, which says that the decision to merge (or not merge) an RFC is based only on rationale that was presented and debated in public. This avoids accidents where the community feels blindsided by a decision.
-
I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)
-
also, should RFCs include working code (basics for the IETF work)?
Tags
- welcoming feedback
- soliciting feedback
- the value of working code
- feeling blindsided
- allowing sufficient time for discussion/feedback/debate before a final decision is made
- open-source projects: allowing community (who are not on core team) to influence/affect/steer the direction of the project
- have discussion/feedback/debate in public (transparency)
- attracting contributors
- change proposal workflow: RFCs
- build concensus
Annotators
URL
-
-
stackoverflow.com stackoverflow.com
-
All browers handle 302 incorrectly. Chrome 30, IE10. It became the de facto incorrect implementation; that cannot be changed because so many web-sites issue mistakenly issue 302. In fact ASP.net MVC incorrectly issues 302, depending on the fact that browsers handle it incorrectly.
-
-
inst-fs-iad-prod.inscloudgate.net inst-fs-iad-prod.inscloudgate.net
-
You’ve let this room and this house replace you and yourwife in your children’s affections.
Children's dependence on and love for their parents has been replaced by technology
-
Their approach sensitized a switch somewhere and the nursery light flicked on when they came within ten feet of it. Similarly, behind them, in the halls, lights went on and off as they left them behind, with a soft automaticity.
The background is the future, where people have higher technology, but are more distant from their children.Because a nursery can provide everything a child needs
-
“Don’t let them do it!”wailed Peter at the ceiling, as if he was talking to the house, the nursery. “Don’t let Father kill everything.”He turned to his father. “Oh, I hate you!”“Insults won’t get you anywhere.”
It is against the rules that technology affects people so much that children become more attached to it than their parents
-
-
stackoverflow.com stackoverflow.com
-
Things that cause the error to go away If I change any one of the following factors (which should not make any difference), then everything works fine:
-
-
github.com github.com
-
I guess I was just waiting for some interest from a maintainer, since there's not much point in wasting my time on developing this if the maintainers aren't even interested in this feature.
-
-
webpack.js.org webpack.js.orgConcepts2
-
Some of these values are suited for development and some for production. For development you typically want fast Source Maps at the cost of bundle size, but for production you want separate Source Maps that are accurate and support minimizing.
-
We expect a certain pattern when validate devtool name, pay attention and dont mix up the sequence of devtool string. The pattern is: [inline-|hidden-|eval-][nosources-][cheap-[module-]]source-map.
-
-
github.com github.com
-
I've only done components that need to/can be Svelte-ified. For some things, like RTL and layout grid, you can just use the MDC packages.
-
This is Sass based, and therefore doesn't require Svelte components
Just because we could make Svelte wrapper components for each Material typography [thing], doesn't mean we should.
Compare:
material-ui [react] did make wrapper components for typography.
- But why did they? Is there a technical reason why they couldn't just do what svelte-material-ui did (as in, something technical that Svelte empowers/allows?), or did they just not consider it?
svelte-material-ui did not.
- And they were probably wise to not do so. Just reuse the existing work from the Material team so that there's less work for you to keep in sync and less chance of divergence.
-
-
stackoverflow.com stackoverflow.com
-
can you not also use a .babelrc?
-
-
github.com github.com
-
There are a few intentional behavioral differences between Dart Sass and Ruby Sass. These are generally places where Ruby Sass has an undesired behavior, and it's substantially easier to implement the correct behavior than it would be to implement compatible behavior. These should all have tracking bugs against Ruby Sass to update the reference behavior.
Tags
- don't let previous decisions/work constrain you
- intentional/well-considered decisions
- reversible decisions
- learn from your mistakes
- reverting a previous decision/change/commit
- get back on course
- intentional
- reference implementation
- intentionally doing it differently / _not_ emulating/copying the way someone else did it
Annotators
URL
-
-
css-tricks.com css-tricks.com
-
Internal Sass features have also moved into the module system, so we have complete control over the global namespace.
-
will only apply up the chain
Should this "up the chain" be "down the chain"?
In terms of a tree, I think of the caller/consumer/thing that imports this file as "up" and the things that I call/import as "down".
That is more consistent with a tree, but not a stack trace (or any stack), I suppose, which has most recently called thing at the top ("up"), and the consumer of that at the bottom ("down").
-
-
-
We already are reserving a prop called slot so that we can do <Foo slot='bar'/> someday
-
-
www.npmjs.com www.npmjs.com
-
Note that when using sass (Dart Sass), synchronous compilation is twice as fast as asynchronous compilation by default, due to the overhead of asynchronous callbacks.
If you consider using asynchronous to be an optimization, then this could be surprising.
-
You will be disrupted by this first issue. It is natural to expect relative references to be resolved against the .sass/.scss file in which they are specified (like in regular .css files).
-
-
github.com github.com
-
When you do import '../scss/application.scss', you're telling webpack to include application.scss in the build. This does not mean it's going to be compiled into your javascript, only that webpack now compiles and knows how to load this file.
Not necessarily the case that importing something into a JS file means the thing being imported is also JS.
-
-
Local file Local file
-
You’ll learn how to cause stack overflows, illegal memory access, andother common flaws that plague C programs so that you know what you’re upagainst
When you learn from "Learn C the Hard Way"
-
-
github.com github.com
-
If the goal of this is purely to avoid showing a runtime warning (and isn't needed for other functionality) I think we should try to consider other ways of dealing with the root issue. See also #4652, which has been opened for just this concern.
-
-
github.com github.com
-
they're in the svelte compiler: https://github.com/sveltejs/svelte/blob/master/src/compiler/compile/nodes/Element.ts#L668 (search for the warning text)
-
-
github.com github.com
-
Obviously we shouldn't rush into anything. But changes like these are best made earlier on in a project's lifecycle, so I'm eager to hear what people think so that we can start making some progress.
-
-
www.benkuhn.net www.benkuhn.net
-
When you’re implementing a bad plan yourself, instead of having a mentor bail you out by fixing it, a few really useful things happen:You learn many more details about why it was a bad idea. If someone else tells you your plan is bad, they’ll probably list the top two or three reasons. By actually following through, you’ll also get to learn reasons 4–1,217.You spend about 100x more time thinking about how you’ll avoid ever making that type of mistake again, i.e., digesting what you’ve learned and integrating it into your overall decision-making.By watching my mistakes and successes play out well or badly over the course of months, I was able to build much more detailed, precise models about what does and doesn’t matter for long-term codebase health. Eventually, that let me make architectural decisions with much more conviction.
There's a benefit to embarking on a challenge without a more experienced authority to bail you out.
- You learn many more details about why it's a bad idea.
- The lessons you learn in terms of how to avoid the mistakes you made stick with you longer
(I would add that the experience is more visceral, it activates more modalities in your brain, and you remember it much more clearly.)
These types of experiences result in what the author calls more "detailed, precise models". For me they result in a sort of intuition.
-
-
github.com github.com
-
This is linux. Ouput first, formatting second. systemctl --no-pager -l should be the default.
-
- Oct 2020
-
github.com github.com
-
The make install task installs the following files:
-
-
security.stackexchange.com security.stackexchange.com
-
Why is it your solution? Can you talk us through it?
-
-
www.scispike.com www.scispike.com
-
I came up with this solution by piecing together man pages and random google result. I was surprised at how many incomplete and inaccurate answers were out there. What may have been more surprising was the complete lack of a full intact solution.
-
-
meta.stackoverflow.com meta.stackoverflow.com
-
Retagging the HTML/CSS questions to use html-heading seems the right thing to do. For the other uses, I don't have enough grounding in the geographic area to know whether the direction and bearing are replacements for heading. But the tag information for heading should be created and should firmly point at the other tags — at least until it is expunged.
-
-
github.com github.com
-
We could broadcast a warning if we find the variable to be set in the environment, but that is more likely than not to annoy people who intentionally set it.
New tag?: warnings that may annoy people who intentionally do something. (Need a way to selectively silence certain warnings?)
-
It took a lot of searching around to find that variable.
-
-
-
In summary TLS uses PKI to secure information over the internet. However, it is important to note that TLS supports other encryption standards which are not part of PKI.
-
-
stackoverflow.com stackoverflow.com
-
If you have a better/simpler/"more official" solution, I'd still love to see it!
The "official" solution is to use submitErrors (see Erik's answer).
-
-
github.com github.com
-
I'd be happy to take on this issue, if no one else has up to this point!
-
-
www.latindex.org www.latindex.orgLatindex1
-
http://purl.org/spar/fabio/BibliographicDatabase,http://purl.org/spar/fabio/Journal,http://purl.org/spar/pso/open-access,http://www.geonames.org/7730009/latin-america-and-the-caribbean.html bnfrmcn/recurso/ejercicio/articulo_revista_indexado
-
-
Local file Local file
-
The great ones have a thought pro-cess, philosophy and habit all rolled into one that overshadows the rest: I am responsible.
-
-
www.basefactor.com www.basefactor.com
-
You may want to execute validations in a given specific order (this can be tricky especially when you have got asynchronous validations).
-
Of course you can start implementing your own thing, but you will waste a lot of precious time reinventing the wheel. Why not take advantage of a validation library that takes care of all this complexity for you?
-
You can try to build a solution to tackle these issues on your own, but it will cost you time and money... why not use a battle-tested solution to handle all this complexity?
-
-
www.youtube.com www.youtube.com
-
Unfortunately, it is an expression mired with a negative context because of how Rumsfeld used it to lie.
-
-
svelte.dev svelte.dev
-
-
-
I really dont need a solution to this problem! I can find many workararounds
Actually, the answer that was given was a good answer, as it pointed to the problem: It was a reminder that you need to:
assign to a locally declared variable.
So I'm not sure the answer was intended to "just" be a solution/workaround, but to help correct or fill in the misunderstanding / forgotten piece of the puzzle to help OP realize why it wasn't working, and realize how reactivity is designed to work (based on assignments).
It was a very simplified answer, but it was meant to point in the right direction.
Indeed, it pointed to this main point that was explained in more detail by @rixo later:
Personally, this also totally aligns with my expectations because in your function
fruit
can come from anywhere and be anything:
-
-
www.cambridge.org www.cambridge.org
-
Description: The authors discuss the usage of blogs in political science classrooms at a university level. There are five skills (critical thinking, political awareness, background research, essay writing, and reflection) which are improved through the use of blogging and the article dedicates a segment to each skill. The last section of the article discusses two types of blogging students can attempt: response to news clippings or experiential blogging. The first kind is available to all students and requires learners to find and respond to news articles. The second is more reflective of a current opportunity students might have such as studying abroad or an internship.
Rating: 7/10
Reason for the rating: The article gives detailed explanations for the impact blogging has on student achievement. It gives examples of each type of blogging to help the reader fully understand the writers ideas. Yet, the article focuses only on political science students while blogs-- and four out of the five skills mentioned above-- can be applies to the majority of university classes.
-
-
australiancybersecuritymagazine.com.au australiancybersecuritymagazine.com.au
-
medium.com medium.com
-
First of all, we solved our problem! As demonstrated here our app is happily running again.
-
-
-
Yeah I see what you're saying. In my case, I had a group of classes that relied on each other but they were all part of one conceptual "module" so I made a new file that imports and exposes all of them. In that new file I put the imports in the right order and made sure no code accesses the classes except through the new interface.
-
-
github.com github.com
-
Doing so also means adding empty import statements to guarantee correct order of evaluation of modules (in ES modules, evaluation order is determined statically by the order of import declarations, whereas in CommonJS – and environments that simulate CommonJS by shipping a module loader, i.e. Browserify and Webpack – evaluation order is determined at runtime by the order in which require statements are encountered).
Here: dynamic loading (libraries/functions) meaning: at run time
-
Specifically, since Root, Rule and AtRule all extend Container, it's essential that Container is evaluated (and therefore, in the context of a Rollup bundle, included) first. In order to do this, input.js (which is the 'gateway' to all the PostCSS stuff) must import root.js, root.js must import rule.js before it imports container.js, and rule.js must import at-rule.js before it imports container.js. Having those imports ensures that container.js doesn't then try to place Root, Rule or AtRule ahead of itself in the bundle.
-
Replaced nested `require` statements with `import` declarations for the sake of a leaner bundle. This entails adding empty imports to three files to guarantee correct ordering – see https://github.com/styled-components/styled-components/pull/100
-
-
medium.com medium.com
-
Modules from the following layer can require anything from all the previous layers, but not vice versa.
-
-
-
You might think something like “don’t request the same resource thousands of times a day, especially when it explicitly tells you it should be considered fresh for 90 days” would be obvious, but unfortunately it seems not.
-
Any software that makes HTTP requests to other sites should make it straightforward to enable the use of a cache.
-
-
johnstoniatexts.x10host.com johnstoniatexts.x10host.com
-
“Ajax, one of the gods dwelling on Olympus, in a prophet’s shape, tells us both to fight on by the ships. For that man was no prophet Calchas, [70] who reads our omens. It was easy for me, as he went away, to see that from the back 80 by the markings on his feet and legs. Besides, it’s easy to recognize the gods.
Recognition of the gods can be connected to an earlier comment that I made about what form they appear in. Here it seems the "voice" of Poseidon comes from within rather than taking on a physical form. Poseidon chooses to speak through Calchas who can see signs of the gods through birds. Birds are referenced in the paragraph before which is an interesting correlation (between Poseidon and Calchas) as well as a shout out to Calchas and all his bird wisdom.
-
-
m5qwxpr6o8.csb.app m5qwxpr6o8.csb.app
-
Note that the <WarningEngine/> component must be at the bottom of the form to guarantee that all the fields have registered.
-
-
hypothes.is hypothes.is
-
"Most Native Americans did not neatly distinguish between the natural and the supernatural. Spiritual power permeated their world and was both tangible and accessible"
This shows how much more open Natives were to the super Naturaul unlike the Europeans who were more than likely christians.
-
my first question: is what do they mean exactly by "kinship"?
My second question is: what does the reading mean by Chiefdoms?
-
"Food surpluses enabled significant population growth, and the Pacific Northwest became one of the most densely populated regions of North America"
This is significant because it shows how succesful the natives were before the Europeans showed up and spread native European diseases to Natives.
-
-
newrepublic.com newrepublic.com
-
As The Social Dilemma shows, entertainers are in no rush to hold us, or themselves, accountable.
-
It seems like a waste of money to hire an actor to play the “algorithm guy” when there are actual algorithm creators being interviewed in the film.
It does seem like they're trying to normalize themselves and divert from the facts of what they have personally done. Imagine if Adolf Hitler, Joseph Goebbels, Heinrich Himmler, and Hermann Göring were able to do the same? And the state of the art of their propaganda was nothing in comparison.
-
-
github.com github.com
-
// Use `noConflict` to restore the pre-fp variant. var fp = _.noConflict();
-
-
ponyfoo.com ponyfoo.comPony Foo1
-
Sometimes we can’t implement a solution that’s fully spec-compliant, and in those cases using a polyfill might be the wrong answer. A polyfill would translate into telling the rest of the codebase that it’s okay to use the feature, that it’ll work just like in modern browsers, but it might not in edge cases.
-
-
humanwhocodes.com humanwhocodes.com
-
github.com github.com
-
Polyfills are naughty as they patch native APIs, while ponyfills are pure and don't affect the environment.
-
How are ponyfills better than polyfills? A polyfill is code that adds missing functionality by monkey patching an API. Unfortunately, it usually globally patches built-ins, which affects all code running in the environment. This is especially problematic when a polyfill is not fully spec compliant (which in some cases is impossible), as it could cause very hard to debug bugs and inconsistencies. Or when the spec for a new feature changes and your code depends on behavior that a module somewhere else in the dependency tree polyfills differently. In general, you should not modify API's you don't own.
-
-
medium.com medium.com
-
It’s a risky blanket statement that causes bloat by including all the mistakes you made while building the original product.
-
-
-
mixing the turing complete of javascript with the markup of HTML eliminates the readability of JSX so that it is actually harder to parse than a solution like hyperscript
-
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.
-
One of the primary tasks of engineers is to minimize complexity. JSX changes such a fundamental part (syntax and semantics of the language) that the complexity bubbles up to everything it touches. Pretty much every pipeline tool I've had to work with has become far more complex than necessary because of JSX. It affects AST parsers, it affects linters, it affects code coverage, it affects build systems. That tons and tons of additional code that I now need to wade through and mentally parse and ignore whenever I need to debug or want to contribute to a library that adds JSX support.
-
Without elegant ways of expressing loops/iterators (like angular does with directives), the primary way to keep JSX readable thus becomes copying and pasting.
I'm not quite sure I understand this (so until I do, I'm not sure I agree)...
Why does he think copying and pasting is the only way to make it readable? Like he pointed out, you can extract JSX snippets and use loops within JSX. But maybe he means (his previous point), that people often don't do that. Hmm. 
-
Furthermore, JSX encourages bad non-dry code. Having seen a lot of JSX over the past few months, its encourages copypasta coding.
-
Supporting JSX out of the box is the engineering equivalent of Mozilla supporting DRM out of the box in FireFox.
-
@subfuzion That error looks unrelated to the existing discussion.
I assume they locked it in reaction to someone posting something unrelated / off-topic.
-
Doesn't require the use of transpiler or modifications to all JS tooling ever invented.
Tags
- syntax
- leverage the fact that tooling already exists
- making it too easy to do the wrong thing
- plugins
- have a good reason
- not enough advantages/merits/pros to make it worthwhile
- duplication
- transpiling
- extensibility
- mentally filter/ignore
- analogy
- special cases
- primary task/job/responsibility
- infectious problem
- ruined it for the rest of us
- good analogy
- making it easy to do the right thing
- comparison with:
- missing out on the benefits of something
- not
- benefiting from shared tooling that can be reused
- can't keep entire system in your mind at once (software development) (scope too large)
- encourages the wrong thing
- Turing complete
- elegant
- JavaScript
- equivalent
- can't support everything / all cases
- copy and paste
- mental bandwidth
- can't do everything
- hybrid/mixture
- DRM
- off topic
- implementation complexity
- avoid complexity
- do pros outweigh/cover cons?
- fundamental
- locked discussion threads
- is it worth the effort?
- adding special cases only for certain popular things but not others
- react-hyperscript
- not merited
- the cost of changing something
- engineering (general)
- for-reaching consequences
- copy and paste programming
- supporting something/feature
- making it easy to do the wrong thing
- bad combination/mixture/hybrid/frankenstein
- complexity
- advantages/merits/pros
- semantics (of programming language)
- too complicated
- hard to make it work in _all_ cases
- bad engineering
- not necessarily the case
- out of the box
- I have a differing opinion
- JSX
- not:
- hyperscript
- expressiveness
- unintended consequence
- minimal benefits
- good point
- engineers
- favoring/catering to the needs of … over …
- high-cost changes
Annotators
URL
-
-
github.com github.com
-
Other frameworks, which use a template syntax built atop HTML — Svelte, Vue, Ractive, Glimmer etc — have historically been fragmented, meaning those tools need to be reinvented many times.
-
-
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))
-
-
github.com github.com
-
This proposal simplifies how React.createElement works and ultimately lets us remove the need for forwardRef.
-
-
-
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!
-
-
www.onwebsecurity.com www.onwebsecurity.com
-
Yet it can be deceivingly difficult to properly encode (user) input
They were talking about output encoding but then switched to input encoding? Did they really mean to say input encoding here?
-
Encoding is dependent on the type of output - which means that for example a string, which will be used in a JavaScript variable, should be treated (encoded) differently than a string which will be used in plain HTML.
-
-
2ality.com 2ality.com
-
trusktr herman willems • 2 years ago Haha. Maybe React should focus on a template-string syntax and follow standards (and provide options for pre-compiling in Webpack, etc).
Well anywho, there's other projects now like hyperHTML, lit-html, etc, plus some really fast ones: https://www.stefankrause.ne...
React seems a little old now (and the new Hooks API is also resource heavy).
• Share ›  Michael Calkins trusktr • 4 years ago • edited That's a micro optimization. There isn't a big enough difference to matter unless you are building a game or something extraordinarily odd.
• Share › −  trusktr Michael Calkins • 2 years ago True, it matters if you're re-rendering the template at 60fps (f.e. for animations, or for games). If you're just changing views one time (f.e. a URL route change), then 100ms won't hurt at all.
-
-
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.
-
Why not just use that instead of inventing a syntax that's not part of ECMAScript?
Tags
- leverage the fact that tooling already exists
- prefer plain code over new template language
- benefiting from shared tooling that can be reused
- ECMAScript standard
- JSX
- assumptions
- divergence
- javascript: tagged template literals
- exceptions to the rule
- why invent a new syntax?
- reinventing the wheel / not invented here
- good point
- undermine
- non-standard
Annotators
URL
-
-
www.npmjs.com www.npmjs.comhyperx1
-
http://facebook.github.io/jsx/#why-not-template-literals (respectfully disagree)
-
-
gist.github.com gist.github.com
-
This is valid javascript! Or harmony or es6 or whatever, but importantly, it's not happening outside the js environment. This also allows us to use our standard tooling: the traceur compiler knows how to turn jsx`<div>Hello</div>`; into the equivalent browser compatible es3, and hence we can use anything the traceur compile accepts!
-
-
www.agileconnection.com www.agileconnection.com
-
This balancing act needs to take into account project complexity (size, distribution, etc.), uncertainty (risk, innovation need, etc.), and the cost of change at the project level and for each major component.
-
Compounding the problem of iteration disguised as oscillation is the cost of change.
-
-
www.python.org www.python.org
-
A style guide is about consistency. Consistency with this style guide is important. Consistency within a project is more important. Consistency within one module or function is the most important.
-
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.
-
-
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
-
But the vast majority of things that our apps are doing are just conditional and list rendering.
-
It would be cool though to have a framework that does not add any specific limitations
-
Svelte chooses a reverse approach.
-
This is a very dangerous practice as each optimization means making assumptions. If you are compressing an image you make an assumption that some payload can be cut out without seriously affecting the quality, if you are adding a cache to your backend you assume that the API will return same results. A correct assumption allows you to spare resources. A false assumption introduces a bug in your app. That’s why optimizations should be done consciously.
-
Moreover, React team even removed the “highlight updates” feature from dev tools because people used to obsessively haunt wasted renders with no reasoning behind it
-
In the vast majority of cases there’s nothing wrong about wasted renders. They take so little resources that it is simply undetectable for a human eye. In fact, comparing each component’s props to its previous props shallowly (I’m not even talking about deeply) can be more resource extensive then simply re-rendering the entire subtree.
Tags
- contrast
- rationality
- assumptions
- time wasters
- good/preferred/recommended behavior
- intentionally doing it differently / _not_ emulating/copying the way someone else did it
- it is enough to be basic (don't need all the bells and whistles)
- the optimization costs more than not having the optimization
- limitations
- false assumptions
- bugs: less attack surface/possibility for bugs
- not good enough reason/rationale/explanation
- premature optimization
- risk
- not adding feature because of the risk it may be abused / shoot self in foot
- risky/dangerous assumptions
- fast (software performance)
- describe the ideal hypothetical solution
- different approaches
Annotators
URL
-
-
github.com github.com
-
"The Map is not the territory" —Alfred Korzybski
-
-
en.wikipedia.org en.wikipedia.org
-
-
Alfred Korzybski remarked that "the map is not the territory" and that "the word is not the thing", encapsulating his view that an abstraction derived from something, or a reaction to it, is not the thing itself.
-
The map–territory relation describes the relationship between an object and a representation of that object, as in the relation between a geographical territory and a map of it.
-
"The menu is not the meal."
-
A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness.
-