5,754 Matching Annotations
  1. Feb 2021
    1. These two mistakes, especially the second one, plant worries in your customers mind before they’ve even had time to think of them.
    2. Stop warning people – no contract, no obligations, cancel anytime – companies can’t resist saying this on every pricing page but by using negative words they’re just putting ideas into people’s heads.
    1. Let's face it, these days, if you want to socialize, you don't go out to the mall or the library, and it's a 50/50 shot if you even have anything resembling a town square. You go on the internet.

      And this is the problematic part of the internet as a town square: we have no defined governance or pale beyond which to cast people who go far beyond societal norms.

    1. The Timeless Way of Building is the first in a series of books which describe an entirely new attitude to architec- ture and planning. The books are intended to provide a complete working alternative to our present ideas about ar- chitecture, building, and planning—~an alternative which will, we hope, gradually replace current ideas and practices,

      [[the timeless way of building]]

    1. Historical LowSteam on 2020-05-100% off$0.00

      If you zoom in on the timeline, it looks like they accidentally set price to $0.00 (probably meant to set discount to 0 instead?) and then corrected it.

      17:16: 0% off of $0.00 17:23: 0% off of $19.99

      Having this mistake/outlier shown as the historical low is misleading and confusing and incorrect, and should be corrected.

    1. Yes, you do face difficult choices (moral) but you don't care about it. All you care are the reputation bars. So... Let's kill this guy, who cares if he is innocent, but this faction needs it or I'm dead. Sounds great on paper but to be honest... you just sit there and do whatever for these reputation bars. If you won't, then you lose
    2. The press will tell you that "the concept" is great but the execution is bad. What should I tell you? The experience is shallow. The game is mediocre. But listen carefully, when a game is mediocre and can't even make you feel something then it's the worst kind of gaming. I will give it a 4 out of 10. You know, if this was a test in a school then this game should be marked D (someone answered a few questions, but overall missed the point). I understand that many people care about the "concept" of this game, but why if the experience is just... not here. I'm talking about the experience becaus We. The Revolution tried to be an actual experience. And it fails so badly.
    3. the gameplay is meaningless and the devs just missed the point.
    1. Now if you think about it, PJAX sounds a lot like Turbolinks. They both use JS to fetch server-rendered HTML and put it into the DOM. They both do caching and manage the forward and back buttons. It's almost as if the Rails team took a technique developed elsewhere and just rebranded it.
    2. Our app is mostly about displaying pages of static information. We crunch a lot of data to generate a single error report page.
    3. Honeybadger isn't a single page app, and it probably won't ever be. SPAs just don't make sense for our technical requirements.
    1. It’s always about the money… Fish got’a swim, birds got’a fly, and development has to have money. If you think otherwise you’re a fool!
    1. Flexbox's strength is in its content-driven model. It doesn't need to know the content up-front. You can distribute items based on their content, allow boxes to wrap which is really handy for responsive design, you can even control the distribution of negative space separately to positive space.
    1. Although one thing you want to avoid is using frames in such a manner that the content of the site is in the frame and a menu is outside of the frame. Although this may seem convienient, all of your pages become unbookmarkable.
    1. There is one situation where iframes are (almost) required: when the contents of the iframe is in a different domain, and you have to perform authentication or check cookies that are bound to that domain. It actually prevents security problems instead of creating them. For example, if you're writing a kind of plugin that can be used on any website, but the plugin has to authenticate on another domain, you could create a seamless iframe that runs and authenticates on the external domain.
    2. Iframes can have similar issues as frames and inconsiderate use of XMLHttpRequest: They break the one-document-per-URL paradigm, which is essential for the proper functioning of the web (think bookmarks, deep-links, search engines, ...).
    3. The most striking such issue is probably that of deep linking: It's true that iframes suffer from this to a lesser extent than frames, but if you allow your users to navigate between different pages in the iframe, it will be a problem.
    4. never care and try to understand design standards
    1. I normally try to figure out if that's a good solution for the problem before resorting to iframes. Sometimes, however, an iframe just does the job better. It maintains its own browser history, helps you segregate CSS styles if that's an issue with the content you're loading in.
    1. cultural capital

      Introduced by Pierre Bourdieu in the 1970s, the concept has been utilized across a wide spectrum of contemporary sociological research. Cultural capital refers to ‘knowledge’ or ‘skills’ in the broadest sense. Thus, on the production side, cultural capital consists of knowledge about comportment (e.g., what are considered to be the right kinds of professional dress and attitude) and knowledge associated with educational achievement (e.g., rhetorical ability). On the consumption side, cultural capital consists of capacities for discernment or ‘taste’, e.g., the ability to appreciate fine art or fine wine—here, in other words, cultural capital refers to ‘social status acquired through the ability to make cultural distinctions,’ to the ability to recognize and discriminate between the often-subtle categories and signifiers of a highly articulated cultural code. I'm quoting here from (and also heavily paraphrasing) Scott Lash, ‘Pierre Bourdieu: Cultural Economy and Social Change’, in this reader.

    1. So what's the worst part? Well, if you're like most entrepreneurs, marketers, and salespeople... it's finding your potential clients' email addresses to reach them out. (Yawn... I almost fall asleep just writing about it.) You see, it's boring and time-consuming, you wish you could skip this part and go straight to the sales process.
    2. What's the best part about running a business? You know, it's closing the deals and counting the money.
  2. Jan 2021
    1. Ubuntu also supports ‘snap’ packages which are more suited for third-party applications and tools which evolve at their own speed, independently of Ubuntu. If you want to install a high-profile app like Skype or a toolchain like the latest version of Golang, you probably want the snap because it will give you fresher versions and more control of the specific major versions you want to track.
    1. The Gmail Android app that comes pre-installed with most new Android phones contains a feature to access non-Google accounts using POP and IMAP. Unfortunately, emails accessed through this setup lack the embedded style (<style>) support as well as the support for background images.
    1. Avec la construction de complexes tels que le Mirage (ouvert en 1989) et le Mandalay Bay (1999), l’architecture des casinos de Las Vegas s’est complètement écartée des formes des années 1950 et 1960, devenant encore plus spectaculaire.

      The Mirage au nord du Las Vegas Strip et le Mandalay Bay au sud.

    1. George was seen as sharing the hardships of the common people and his popularity soared.
    1. overflow-wrap: break-word; makes sure the long string will wrap and not bust out of the container. You might as well use word-wrap as well because as the spec says, they are literally just alternate names for each other. Some browsers support one and not the other.
    1. definite good news, as it will hopefully have a ripple effect on crappy chipset makers, getting them to design and test their hardware with Linux properly, for fear of losing all potential business from Lenovo.
    2. I suppose it means 2 things, first, you get official support and warranty, and second, the distros will be Secure Boot approved in the UEFI, instead of distro makers having to figuratively ask Microsoft for pretty please permission.
    1. No, this is not a duplicate of that linked question. I don't need to know "why it's a snap". I want to know how to use it without snap.
    1. this paper identifies / lists 5 reasons to follow the money in health care. These reasons are applicable to social services or other areas of philanthropy as well.

    1. At least one Zoom leaker has already been unmasked: a member of the New York State Assembly who apparently filmed his “self-view” while recording a dispute within the Democratic assembly conference over the renomination of the speaker. That may sound careless, but a feature developed by Zoom will allow future leakers to be exposed even without that sort of misstep.
    1. A big app will have lots of components compared to regular html elements and these need to be wrapped before being fed to a slot, every single time on the call site
    2. This syntax easily provides all the features of components, like let: bind: and on:. <svelte:fragment /> is just a component with a special name.
    3. Ahh ok, it's a regular let. It's too bad it has to be so intrusive on the call sites.
  3. trumpwhitehouse.archives.gov trumpwhitehouse.archives.gov
    1. There was not yet, formally speaking, an American people. There were, instead, living in the thirteen British colonies in North America some two-and-a-half million subjects of a distant king. Those subjects became a people by declaring themselves such and then by winning the independence they had asserted as their right.

      • There were many American peoples. None of them were White.
      • "those subjects became a people by declaring themselves such and then by winning the independence they had asserted as their right" - OK no. Quite a lot of people did not have the autonomy to "declare themselves" part of a people, and indeed were not recognized as such. There were also loyalists. And this idea of "a people" is...really complicated.
      • While it's true that the first citizens of the United States were former British subjects, it is worth noting that a lot of other people lived in the current United States at the time who were tribal citizens, French colonists, Spanish colonists, and enslaved people who weren't considered citizens of anywhere.
    1. Why the ^=? This means "starts with", because we can also have variation placements like top-start.
    1. Why is CORS important? Currently, client-side scripts (e.g., JavaScript) are prevented from accessing much of the Web of Linked Data due to "same origin" restrictions implemented in all major Web browsers. While enabling such access is important for all data, it is especially important for Linked Open Data and related services; without this, our data simply is not open to all clients. If you have public data which doesn't use require cookie or session based authentication to see, then please consider opening it up for universal JavaScript/browser access. For CORS access to anything other than simple, non auth protected resources
    1. The same-origin policy fights one of the most common cyber attacks out there: cross-site request forgery. In this maneuver, a malicious website attempts to take advantage of the browser’s cookie storage system.
    1. “JSONP is JSON with extra code” would be too easy for the real world. No, you gotta have little discrepancies. What’s the fun in programming if everything just works? Turns out JSON is not a subset of JavaScript. If all you do is take a JSON object and wrap it in a function call, one day you will be bitten by strange syntax errors, like I was today.
    1. Why? I wrote MagpieRSS out of a frustration with the limitations of existing solutions. In particular many of the existing PHP solutions seemed to: use a parser based on regular expressions, making for an inherently fragile solution only support early versions of RSS discard all the interesting information besides item title, description, and link. not build proper separation between parsing the RSS and displaying it.
    1. While you may have some objections due to your specific setup, please consider you’re not the usual use case. Most people install Ubuntu on a single drive, not separate /home, and not multiple disks. Most are quite happy with automatic updates - in line with how their phone is likely setup - both for debs (with unattended-upgrades) and snaps (via automatic refresh in snapd). Experts such as yourself are capable of managing your own system and are interested in twiddling knobs and adjusting settings everywhere. There are millions of Ubuntu users who are not like that. We should cater for the widest possible use case by default, and have the option to fiddle switches for experts, which is what we have.
    2. Frankly, if the Ubuntu Desktop team “switch” from making a deb of Chromium to making a snap, I doubt they’d switch back. It’s a tremendous amount of work for developer(s) to maintain numerous debs across all supported releases. Maintaining a single snap is just practically and financially more sensible.
    3. Progress is made of compromises, this implies that we have to consider not only disadvantages, but also the advantages. Advantages do very clearly outweigh disadvantages. This doesn’t mean it perfect, or that work shouldn’t continue to minimize and reduce the disadvantages, but just considering disadvantages is not the correct way.
    4. 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
    5. The benefits for developers do reflect on benefits for users, with more software delivered faster and more securely.
    6. « 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.
    7. 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.
    8. But now Chromium is no more available as deb, so what to expect ?
    9. 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…
    1. 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.

      https://www.kungfustory.com/

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

      https://www.kungfustory.com/

  4. Dec 2020
    1. 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.

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

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

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

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

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

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

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

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

    1. You can afford to make a proper PR to upstream.
    2. 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
    1. 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.
    2. 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.
    3. 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.
    4. but really, the whole is what feels so good.
    5. 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!
    1. 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?

    1. 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).
    1. 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.
    2. 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.
    3. I personally think that starting from google's components makes easier to keeping update to material specs updates.
    1. Appeal highlights

      Gives obvious area for facts (logos) which also can create ethos from them knowing so much information

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

    3. Key planned results for 2020

      Shows what they want to achieve

    4. Funding requirements for 2020

      Show how much money is needed to achieve results

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

  5. Nov 2020
    1. 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.

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

    1. I wouldn't use Flutter for web, mobile is good though.
    2. 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.
    3. 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.

    4. 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.
    1. When writing copy for buttons, make sure that you keep consistency.
    2. 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.
    3. “Why?” you ask. This is for two reasons.
    1. 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.
    2. 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.
    3. After i've stabilized the library i can start to discuss about adding new components and features!
    4. 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).

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

    1. Many linguists believe that the natural language a person speaks affects how they think. Does the same concept apply to computer languages?
    1. 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.”
    1. 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. 

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

    1. 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.
    1. 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.
    2. 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)
    3. also, should RFCs include working code (basics for the IETF work)?
    1. 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.
  6. inst-fs-iad-prod.inscloudgate.net inst-fs-iad-prod.inscloudgate.net
    1. 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

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

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

    1. 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.
    2. 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.
    1. 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.
    2. 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.
    1. Internal Sass features have also moved into the module system, so we have complete control over the global namespace.
    2. 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").

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

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

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

    Tags

    Annotators

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

  7. Oct 2020
    1. 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.
    1. 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?)

    2. It took a lot of searching around to find that variable.
    1. 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.