5,542 Matching Annotations
  1. Oct 2020
    1. 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.
    2. 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
    1. 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.
    2. Any software that makes HTTP requests to other sites should make it straightforward to enable the use of a cache.
    1.                                         “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.

    1. Note that the <WarningEngine/> component must be at the bottom of the form to guarantee that all the fields have registered.
    1. "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.

    2. my first question: is what do they mean exactly by "kinship"?

      My second question is: what does the reading mean by Chiefdoms?

    3. "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.

    1. As The Social Dilemma shows, entertainers are in no rush to hold us, or themselves, accountable.
    2. 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.

    1. 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.
    1. Polyfills are naughty as they patch native APIs, while ponyfills are pure and don't affect the environment.
    2. 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.
    1. 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
    2. 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.
    3. 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.
    4. 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.
    5. 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. 

    6. Furthermore, JSX encourages bad non-dry code. Having seen a lot of JSX over the past few months, its encourages copypasta coding.
    7. Supporting JSX out of the box is the engineering equivalent of Mozilla supporting DRM out of the box in FireFox.
    8. @subfuzion That error looks unrelated to the existing discussion.

      I assume they locked it in reaction to someone posting something unrelated / off-topic.

    9. Doesn't require the use of transpiler or modifications to all JS tooling ever invented.

    Tags

    Annotators

    URL

    1. 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.
    1. 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?

    2. 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.
    1. 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.

    1. 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!
    1. 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.
    2. Compounding the problem of iteration disguised as oscillation is the cost of change.
    1. 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.
    2. However, know when to be inconsistent -- sometimes style guide recommendations just aren't applicable.
    3. When applying the guideline would make the code less readable, even for someone who is used to reading code that follows this PEP.
    1. 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.
    1. But the vast majority of things that our apps are doing are just conditional and list rendering.
    2. It would be cool though to have a framework that does not add any specific limitations
    3. Svelte chooses a reverse approach.
    4. 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.
    5. 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
    6. 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.
    1. 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.
    2. 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.
    3. "The menu is not the meal."
    4. A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness.
  2. mdxjs.com mdxjs.com
    1. MDX seeks to make writing with Markdown and JSX simpler while being more expressive. Writing is fun again when you combine components, that can even be dynamic or load data, with the simplicity of Markdown for long-form content.
    2. Why?
    1. Description: This text describes adult learning theories best used in a workforce training. It describes the environmental factors which lead to success in an adult student (such as a positive atmosphere) as well as techniques like heterogeneous learning groups. It attempts to persuade the reader to address the personal needs of each student while still moving the class towards the trainings goal. As a whole, this article covers the basics of what trainers need to know when teaching adults in a workface setting.

      Rating: 6/10

      Reason for rating: This article is very quick and direct. It discusses each technique, skill, or factor with examples and reasoning for the suggestions. Each suggestion is well-thought out and logical. Yet, the article cites few other texts which discredits it a little. The article was found through JSTOR which only sources peer-reviewed texts.

    1. 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.
    2. 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.
    1. 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.
    1. I'm suggesting there should be a way to write lifecycle related code that also responds to changing props, like how useEffect works. I think how React handles this could be a good source of inspiration.
    2. I'm not sure I understand the problem, everything you are describing is already possible.
    3. 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.
    4. While react hooks were one of the catalysts for v3 we don't agree with with the APIs or the model and won't be emulating it.
    1. Meanwhile, politicians from the two major political parties have been hammering these companies, albeit for completely different reasons. Some have been complaining about how these platforms have potentially allowed for foreign interference in our elections.3 3. A Conversation with Mark Warner: Russia, Facebook and the Trump Campaign, Radio IQ|WVTF Music (Apr. 6, 2018), https://www.wvtf.org/post/conversation-mark-warner-russia-facebook-and-trump-campaign#stream/0 (statement of Sen. Mark Warner (D-Va.): “I first called out Facebook and some of the social media platforms in December of 2016. For the first six months, the companies just kind of blew off these allegations, but these proved to be true; that Russia used their social media platforms with fake accounts to spread false information, they paid for political advertising on their platforms. Facebook says those tactics are no longer allowed—that they've kicked this firm off their site, but I think they've got a lot of explaining to do.”). Others have complained about how they’ve been used to spread disinformation and propaganda.4 4. Nicholas Confessore & Matthew Rosenberg, Facebook Fallout Ruptures Democrats’ Longtime Alliance with Silicon Valley, N.Y. Times (Nov. 17, 2018), https://www.nytimes.com/2018/11/17/technology/facebook-democrats-congress.html (referencing statement by Sen. Jon Tester (D-Mont.): “Mr. Tester, the departing chief of the Senate Democrats’ campaign arm, looked at social media companies like Facebook and saw propaganda platforms that could cost his party the 2018 elections, according to two congressional aides. If Russian agents mounted a disinformation campaign like the one that had just helped elect Mr. Trump, he told Mr. Schumer, ‘we will lose every seat.’”). Some have charged that the platforms are just too powerful.5 5. Julia Carrie Wong, #Breaking Up Big Tech: Elizabeth Warren Says Facebook Just Proved Her Point, The Guardian (Mar. 11, 2019), https://www.theguardian.com/us-news/2019/mar/11/elizabeth-warren-facebook-ads-break-up-big-tech (statement of Sen. Elizabeth Warren (D-Mass.)) (“Curious why I think FB has too much power? Let's start with their ability to shut down a debate over whether FB has too much power. Thanks for restoring my posts. But I want a social media marketplace that isn't dominated by a single censor. #BreakUpBigTech.”). Others have called attention to inappropriate account and content takedowns,6 6. Jessica Guynn, Ted Cruz Threatens to Regulate Facebook, Google and Twitter Over Charges of Anti-Conservative Bias, USA Today (Apr. 10, 2019), https://www.usatoday.com/story/news/2019/04/10/ted-cruz-threatens-regulate-facebook-twitter-over-alleged-bias/3423095002/ (statement of Sen. Ted Cruz (R-Tex.)) (“What makes the threat of political censorship so problematic is the lack of transparency, the invisibility, the ability for a handful of giant tech companies to decide if a particular speaker is disfavored.”). while some have argued that the attempts to moderate discriminate against certain political viewpoints.

      Most of these problems can all fall under the subheading of the problems that result when social media platforms algorithmically push or accelerate content on their platforms. An individual with an extreme view can publish a piece of vile or disruptive content and because it's inflammatory the silos promote it which provides even more eyeballs and the acceleration becomes a positive feedback loop. As a result the social silo benefits from engagement for advertising purposes, but the community and the commons are irreparably harmed.

      If this one piece were removed, then the commons would be much healthier, fringe ideas and abuse that are abhorrent to most would be removed, and the broader democratic views of the "masses" (good or bad) would prevail. Without the algorithmic push of fringe ideas, that sort of content would be marginalized in the same way we want our inane content like this morning's coffee or today's lunch marginalized.

      To analogize it, we've provided social media machine guns to the most vile and fringe members of our society and the social platforms are helping them drag the rest of us down.

      If all ideas and content were provided the same linear, non-promotion we would all be much better off, and we wouldn't have the need for as much human curation.

    1. I just wrote a long, considered, friendly, and I hope helpful comment here but -- sorry, I have to see the irony in this once again -- your system wouldn't let me say anything longer tahn 1,500 characters. If you want more intelligent conversations, you might want to expand past soundbite.

      In 2008, even before Twitter had become a thing at 180 characters, here's a great reason that people should be posting their commentary on their own blogs.

      This example from 2008 is particularly rich as you'll find examples on this page of Derek Powazek and Jeff Jarvis posting comments with links to much richer content and commentary on their own websites.

      We're a decade+ on and we still haven't managed to improve on this problem. In fact, we may have actually made it worse.

      I'd love to see On the Media revisit this idea. (Of course their site doesn't have comments at all anymore either.)

    1. Capitalists and market-thinkers inevitably seek to enclose the commons, privatizing benefits and externalizing costs onto society.
    1. Mr. Duncombe published the results online using CommentPress, open-source software by the Institute for the Future of the Book. Online discussion and commenting is made possible by Social Book, a social-reading platform created by the institute.
    1. Conservatives have fought for schools to promote patriotism, highlight the influence of Christianity and celebrate the founding fathers. In a September speech, President Trump warned against a “radical left” that wants to “erase American history, crush religious liberty, indoctrinate our students with left-wing ideology.”

      I can't help but think here about a recent "On The Media" episode A Civilization As Great As Ours which highlighted changes in how history is taught in India. This issue obviously isn't just relegated to populist India.

    1. I can't help but wonder what Jonah Goldberg's review of this book will be given his prior effort earlier this year?

      I'm also reminded here of Mark Granovetter's ideas that getting a job is more closely tied to who you know. One's job is often very closely tied to their identity, and even more so when the link that got them their job was through a friend or acquaintance.

    1.  recording it all in a Twitter thread that went viral and garnered the hashtag  #PlaneBae.

      I find it interesting that The Atlantic files this story with a URL that includes "/entertainment/" in it's path. Culture, certainly, but how are three seemingly random people's lives meant to be classified by such a journalistic source as "entertainment?"

    1. It's the part of your garden that you might actively show people when they come round to visit, that you're most proud of.

      It's a bit like cleaning up just for company, or in our current pandemic, just cleaning up the section of the house that's seen in the camera as in this New Yorker Cartoon:

    1. Put another way, many tools for thought are public goods. They often cost a lot to develop initially, but it’s easy for others to duplicate and improve on them, free riding on the initial investment. While such duplication and improvement is good for our society as a whole, it’s bad for the companies that make that initial investment. And so such tools for thought suffer the fate of many public goods: our society collectively underinvests in them, relative to the benefits they provide
    1. Solid supports templating in 3 forms JSX, Tagged Template Literals, and Solid's HyperScript variant.
    2. Why struggle with custom Syntax DSLs when you can use one so widely supported?
    3. It was only pragmatic to use a tool that basically gives you that all for free.
    4. 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.
    1. People constantly suggest that I should have just worked with a different library instead of writing another one.
    2. 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.
    3. focuses way too much on the getter/tracking part of the equation which is really the part you want reduce the mental bandwidth on
    4. 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.
    1. 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.
  3. Sep 2020
    1. let:hovering={active}

      It seems like it should be the other way around:

      let:active={hovering}
      

      to make it look like a regular let assignment.

      It's only when you consider what/how let:hovering on its own means/works that it makes a bit more sense that it is the way it is. When it's on its own, it's a little clearer that it's saying to "make use of" an available slot prop having the given name. (Very much like bind, where the LHS is also the name of the prop we're getting the data from.) Obviously we have to identify which prop we're wanting to use/pull data from, so that seems like the most essential/main/only thing the name could be referring to. (Of course, as a shortcut (in this shorthand version), and for consistency, it also names the local variable with the same name, but it wouldn't have to.)

      Another even simpler way to remember / look at it:

      1. Everything on the left hand of an prop/attribute [arg] corresponds to something in the component/element that you're passing the [arg] to. Usually it's a prop that you're passing in, but in this case (and in the case of bind:) it's more like a prop that you're pulling out of that component, and attaching to. Either way, the name on the LHS always corresponds to an export let inside that named component.
      2. Everything on the right side corresponds to a name/variable in the local scope. Usually it passes the value of that variable, but in the case of a let: or bind: it actually "passes the variable by reference" (not the value) and associates that local variable with the LHS (the "remote" side).

      Another example is bind: You're actually binding the RHS to the value of the exported prop named on the LHS, but when you read it (until you get used to it?) it can look like it's saying bind a variable named LHS to the prop on the RHS.

    1. Why do we use bundlers again?Historically, bundlers have been used in order to support CommonJS files in the browser, by concatenating them all into a single file. Bundlers detected usages of require() and module.exports and wrap them all with a lightweight CommonJS runtime. Other benefits were allowing you to serve your app as a single file, rather than having the user download several scripts which can be more time consuming.
    1. You can see that Rollup mapped browser globals called "React" and "ReactDOM" to variables called "React" and "ReactDOM". The latter are what you imported by writing import React and import ReactDOM. (The variable names don't have to be the same as the browser globals, but it's common.)
    1. But library users are more numerous, and so their needs are more important.
    2. remember that the needs of the many outweigh the needs of the few
    3. small modules allow library authors to become lazy. Why include that six-line helper function when you can do a one-line `require`?
    4. These are all things that make your life as a library author easier.
    5. possibly making it harder for them to appreciate how severe the discoverability issues are for the rest of us.
    6. The natural assumption is that this is because a) it is the best package manager, and b) the JavaScript community is the most energetic and productive.
    7. I think I know why: it’s because the small modules philosophy favours library authors (like Sindre) at the ultimate expense of library users.
    1. 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.
    2. The main rationale for this PR is that, in my hones opinion, Svelte needs a way to support style overrides in an intuitive and close to plain HTML/CSS way. What I regard as intuitive is: Looking at how customizing of styles is being done when applying a typical CSS component framework, and making that possible with Svelte.
    3. 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.
    4. Web developers are well aware of the mess you can get into with global CSS, and the action of writing <Child class="foo"/> and <div class={_class}>` (or similar) in the child component is an explicit indication that, while taking advantage of all the greatness of style encapsulation by default, in this case you have decided that you want a very specific and controlled "leak", of one class, from one component instance to one component instance.
    1. 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.
    2. The point of the feature is to not rely on the third-party author of the child component to add a prop for every action under the sun. Rather, they could just mark a recipient for actions on the component (assuming there is a viable target element), and then consumers of the library could extend the component using whatever actions they desire.
    3. I think Svelte's approach where it replaces component instances with the component markup is vastly superior to Angular and the other frameworks. It gives the developer more control over what the DOM structure looks like at runtime—which means better performance and fewer CSS headaches, and also allows the developer to create very powerful recursive components.
    1. Does it look like a decorator plugin in Ractive, right
    2. Lets not extend the framework with yet another syntax
    3. Your LazyLoad image is now inextensible. What if you want to add a class? Perhaps the author of LazyLoad thought of that and sets className onto the <img>. But will the author consider everything? Perhaps if we get {...state} attributes.
    4. one problem with 'behavior' is that's the terminology we use to describe all of a component's encapsulated logic — methods, transitions, etc.
    1. While there is some precedence in other frameworks for using as, the word doesn't fit well. Since you are adding functionality to elements I like the word add better (and it only has 1 more character).
    1. The more I think about this, the more I think that maybe React already has the right solution to this particular issue, and we're tying ourselves in knots trying to avoid unnecessary re-rendering. Basically, this JSX... <Foo {...a} b={1} {...c} d={2}/> ...translates to this JS: React.createElement(Foo, _extends({}, a, { b: 1 }, c, { d: 2 })); If we did the same thing (i.e. bail out of the optimisation allowed by knowing the attribute names ahead of time), our lives would get a lot simpler, and the performance characteristics would be pretty similar in all but somewhat contrived scenarios, I think. (It'll still be faster than React, anyway!)
    2. I'll work on a preliminary PR (which I expect will need some love from maintainers, sorry!)
    1. The value of dotAll is a Boolean and true if the "s" flag was used; otherwise, false. The "s" flag indicates that the dot special character (".") should additionally match the following line terminator ("newline") characters in a string, which it would not match otherwise: U+000A LINE FEED (LF) ("\n") U+000D CARRIAGE RETURN (CR) ("\r") U+2028 LINE SEPARATOR U+2029 PARAGRAPH SEPARATOR This effectively means the dot will match any character on the Unicode Basic Multilingual Plane (BMP). To allow it to match astral characters, the "u" (unicode) flag should be used. Using both flags in conjunction allows the dot to match any Unicode character, without exceptions.
    1. Your knowledge of her character dates from a day or two since. My knowledge of her character dates from the beginning of her life. State your suspicion of her as strongly as you please–it is impossible that you can offend me by doing so. I am sure, beforehand, that (with all your experience) the circumstances have fatally misled you in this case. Mind! I am in possession of no private information. I am as absolutely shut out of my daughter’s confidence as you are. My one reason for speaking positively, is the reason you have heard already. I know my child.”

      Is it not possible that Rachel read the will, that proposed the diamond be sent away and chopped up into little pieces? Is it not possible that being possessed by the diamond, she decided to protect it? Why have the other characters not noticed this? Am I missing something?

    2. The Colonel had been a notorious opium-eater for years past

      It should be mentioned that Wilkie Collins was a "notorious opium-eater" himself. The Colonel may be an allusion to himself, and the negative way in which he is depicted could be interpreted as Collins' self-loathing.

      The curse of the Diamond itself may be an allegory for the corrupting influence of opium addiction. The "wretched crystal" that he "picked up" in India can be construed as a metaphor for a bad drug habit.

    3. “The Last Rose of Summer”

      I looked up a recording of “The Last Rose of Summer”, and the rose in the lyrics/story of the song seem to fit Rosanna (who obviously has “rose” in her name)...the story is about the last rose of summer that has survived all the other roses that have died and faded. Ultimately though, the narrator decides to kill it because it seems so sad that the rose is the last one, saying in the last stanza that they would choose a quick death than to be like the friendless, lonely rose. Could this be parallel to Rosanna being the rose and somehow the narrator being Betteredge/Lady Verinder breaking her off into being with people she doesn’t fit in with as some twisted Christian act in the name of helping the poor?

    1. when choosing community building activities that ask students to disclose information about themselves, and especially about how they are feeling, it is important to recognise the risk of unintended harm.

      Most faculty in a teaching setting chooses to do certain activities that can make a student very uncomfortable. In high school my teachers would do "icebreakers" and I would hate them because that meant I would have to talk in front of people and sometimes the topic would be a little too personal.

    1. But you think sometimes about what the real world is. Just what your brain mixes together from what your senses tell you. We create the world in a lot of ways. I suppose it shouldn’t be surprising that, when we’re not being careful, we can change it.
    1. They might even hate each other; the creature who already lived loathed his own deformity, and might he not conceive a greater abhorrence for it when it came before his eyes in the female form? She also might turn with disgust from him to the superior beauty of man; she might quit him, and he be again alone, exasperated by the fresh provocation of being deserted by one of his own species.

      A lot of misogyny is radiating from these lines. Victor is implying that his female creation might be so ugly that even his male creation will be offended by her existence one he sees her. But on the other hand, what if his creation isn't her type and just abandon's him? It's interesting to see how much thought Victor puts in when it comes to making a female creation...I thought he was trying to create a new species?

    1. Nic Fildes in London and Javier Espinoza in Brussels April 8 2020 Jump to comments section Print this page Be the first to know about every new Coronavirus story Get instant email alerts When the World Health Organization launched a 2007 initiative to eliminate malaria on Zanzibar, it turned to an unusual source to track the spread of the disease between the island and mainland Africa: mobile phones sold by Tanzania’s telecoms groups including Vodafone, the UK mobile operator.Working together with researchers at Southampton university, Vodafone began compiling sets of location data from mobile phones in the areas where cases of the disease had been recorded. Mapping how populations move between locations has proved invaluable in tracking and responding to epidemics. The Zanzibar project has been replicated by academics across the continent to monitor other deadly diseases, including Ebola in west Africa.“Diseases don’t respect national borders,” says Andy Tatem, an epidemiologist at Southampton who has worked with Vodafone in Africa. “Understanding how diseases and pathogens flow through populations using mobile phone data is vital.”
      the best way to track the spread of the pandemic is to use heatmaps built on data of multiple phones which, if overlaid with medical data, can predict how the virus will spread and determine whether government measures are working.
      
    1. Why make another UI component kit when we already got Smelte and SMUI? What's so special about Svelta?
    1. Because of that, it's easy to end up in a situation where the styles for a given piece of markup are defined far away (in terms of number of lines) from the markup itself, which reduces the advantage of having styles and markup co-located in the first place.
    1. Please focus on explaining the motivation so that if this RFC is not accepted, the motivation could be used to develop alternative solutions. In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind.
    2. A huge part of the value on an RFC is defining the problem clearly, collecting use cases, showing how others have solved a problem, etc.
    3. An RFC can provide tremendous value without the design described in it being accepted.
    1. One key advantage of 'HTML-plus' languages is that you don't actually need tooling in order to be productive — most editors give you out-of-the-box support for things like syntax highlighting (though imperfect, as JavaScript expressions are treated as strings) and auto-closing tags. Tools like Emmet work with no additional setup. HTMLx should retain that benefit.
    1. I’ve seen some version of this conversation happen more times than I can remember. And someone will always say ‘it’s because you’re too used to thinking in the old way, you just need to start thinking in hooks’.

      But after seeing a lot of really bad hooks code, I’m starting to think it’s not that simple — that there’s something deeper going on.

    2. Now of course we know how React handles this conflict: it takes the new nodes in your virtual DOM tree — the waters in your flowing river — and maps them onto existing nodes in the DOM. In other words React is a functional abstraction over a decidedly non-functional substrate.

      To me this is a warning sign, because in my experience, the bigger the gap between an abstraction and the thing it abstracts, the more likely you are to suffer what programmers like to call ‘impedance mismatches’, and I think we do experience that in React.

  4. eclass.srv.ualberta.ca eclass.srv.ualberta.ca
    1. he will crush[j] your head,(BL)    and you will strike his heel.”

      God curses the serpent after deceiving Eve in the garden, and creates "enmity between [the serpent] and the woman." In the "Harry Potter" series by JK Rowling, the serpent is a symbol of evil, and near the end of the books, is the only piece of evil left to destroy before good can truly be restored.

    1. While I am not homosexual, I have always felt that discrimination against homosexuality is completely ludicrous because I think people should love who they love. This belief that I have has giving me an idea for my research topic for my bibliography project where I look over the state of homosexuality in 2020. I decided to annotate this article because it gave a lot of good information about the state of homosexuality in 2020 and it has some links to other articles about homosexuality.

    1. loss of Silesia

      Conquered from Maria Theresa during the War of Austrian Succession in violation of the Pragmatic Sanction of 1713, to which Frederick was a signatory.

      In many ways, this is seen as an example of Realpolitik, in which a nation's strategic strength is the determining factor in how it conducts policy (rather than promises or a sense of honour). This is a concept that will become increasingly important in Prussian policy into the 19th century, under Bismarck.

    1. Thus, Confucius meditated upon water; and the Confucian Xunzi later attempted to systematize the relationship between water’s various forms and people’s moral qualities. This assumption of a correspondence between the principles which inform both water and human conduct was not limited to the Confucians; it was generally assumed in all early philosophical texts. Nor was the imagery the provenance of any particular school. For example, water which moves forward without force, giving life to everything, is described in Xunzi as ‘wuwei’ (without action) or (doing nothing) a term that is particularly associated with Daoism.

      CONTEXT: Shuen-fu Lin addresses "the sage", the person with the highest spiritual attainment who was first emulated and thought of in the Wei-Jin movement, following the Han Dynasty. The sage allows the innate tendencies and has all five of the human emotions addressed in the passage, but "...does not act, complies, and does not implement. He eliminates what leads things astray and gets rid of what confuses them." The sage is addressed as exhibiting qualities of both the Daoist way of life and the Confucianist way. The sage is like the image of water that is an unattainable, sage-like, presence and moral conduct, desired by both Daoist and Confucianist beliefs. "Gentlemen" look at water in awe, gazing upon the perfection of its inaction and lack of effort in attaining its intellect, beauty, and respect. The water has of "ziran", or perhaps, is "ziran" that humans are able to express communion with nature and nonpurposive action. This word is also described as spontaneously existing and being "so oneself" -nothing acting behind them. Water does not decide or dwell for too long, it just exists in movement and in detachment which I think human beings desire greatly.

      Cai, Zongqi. Chinese Aesthetics: The Ordering of Literature, the Arts, and the Universe in the Six Dynasties. Honolulu: University of Hawaii Press, 2004.

      RELATE: In 'The Experience of Nature' by Rachel and Stephen Kaplan, human action and thought is addressed as influenced by our setting/environment whether the setting require immediate responsive action or the response take place in a slower, observational method varies. The authors write, "People are particularly aware of information that is visual, that concerns what they see. That does not mean that people interpret the information in visual terms exclusively; rather, visual stimuli are effective in conjuring associated information. The sight of water provides information about potential opportunities which may or may not be visual in themselves" (Kaplan, 4). Reverie from observation that allows self reflection, thought free from distraction, and intuitive action is typically included in our broader categorization of landscape qualities when we discuss as landscape architects. Human reaction to landscape is so much bigger than the texture, color, or even kinesthetic feeling within the place and can be thought of as artwork in addition- prompting development of thought even subconsciously within the the one experiencing.

      Kaplan, Rachel, and Stephen Kaplan. The Experience of Nature: A Psychological Perspective. Cambridge: Cambridge University Press, 1989.

    1. LSP creates the opportunity to reduce the m-times-n complexity problem of providing a high level of support for any programming language in any editor, IDE, or client endpoint to a simpler m-plus-n problem.
    1. Customers care more about the value our application adds to their lives than the programming language or framework the application is built with. Visible Technical Debt such as bugs and missing features and poor performance takes precedence over Hidden Technical Debt such as poor test code coverage, modularity or removing dead code
    2. In the real world — the time to pay off technical debt is scarce — in most of the time fueled by the fear of the unknown. The management loves to milk the cow but not to change the litter. The developers on another hand avoid modernizing legacy code — to avoid trouble in case anything breaks.
  5. Aug 2020
    1. It can come as a refreshment to follow the hype and ride the bandwagon from time to time, but you should always do your research first.
    2. The hype is something common in our industry. Remember NoSQL? Or when everyone went crazy over microservices? Or the AI / Machine learning burst? The list goes on and on. People get excited about new and breakthrough technologies and ideas.
    3. The idea of having to learn something new is good, and I agree with that, but how often should you do that? Looking at the world of JavaScript, a new idea, blog post, library, framework, and whatnot pops up very often. Things become trending, and people quickly try to adopt that. I’m not saying you should not adopt new things and consider different approaches to a solution, not at all! I am trying to propose the idea of doing that less often.