283 Matching Annotations
  1. Last 7 days
    1. In a browser, deep-diff defines a global variable DeepDiff. If there is a conflict in the global namespace you can restore the conflicting definition and assign deep-diff to another variable like this: var deep = DeepDiff.noConflict();.
  2. Oct 2020
    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. hyperscript is much simpler to refactor and DRY up your code than with JSX, because, being vanilla javascript, its easier to work with variable assignment, loops and conditionals.
    1. BitTorrent is a peer-to-peer (P2P) communications protocol for file sharing. It may also refer to: BitTorrent (company), a company which develops and maintains the BitTorrent protocol BitTorrent (software), the original BitTorrent client
    1. encapsulation refers to one of two related but distinct notions, and sometimes to the combination thereof:[3][4] A language mechanism for restricting direct access to some of the object's components.[5][6] A language construct that facilitates the bundling of data with the methods (or other functions) operating on that data.[1][7]
  3. Sep 2020
    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. It's fashionable to dislike CSS. There are lots of reasons why that's the case, but it boils down to this: CSS is unpredictable. If you've never had the experience of tweaking a style rule and accidentally breaking some layout that you thought was completely unrelated — usually when you're trying to ship — then you're either new at this or you're a much better programmer than the rest of us.
    1. In mapbox.js you'll see this line: const key = {};We can use anything as a key — we could do setContext('mapbox', ...) for example. The downside of using a string is that different component libraries might accidentally use the same one; using an object literal means the keys are guaranteed not to conflict in any circumstance (since an object only has referential equality to itself, i.e. {} !== {} whereas "x" === "x"), even when you have multiple different contexts operating across many component layers.
    1. The previous example contained a default slot, which renders the direct children of a component. Sometimes you will need more control over placement, such as with this <ContactCard>. In those cases, we can use named slots.

      This is a nicer solution than react children props, which is only clean if you pass in a single child.

      The React children prop is an unregulated wild west where people are free to use the prop almost any way they want (including passing in a function).

      I kind of like how Svelte provides a standard, consistent API, which doesn't have the limitations of React childern.

  4. Aug 2020
    1. Ruby is the programming language used in Translation Proxy. For Sarah, Object Oriented Design “done the Ruby way” is so enjoyable and is the part of her work that she likes most.
  5. Jul 2020
    1. Because the Web IDE is based on the Monaco Editor, you can find a more complete list of supported languages in the Monaco languages repository. Under the hood, Monaco uses the Monarch library for syntax highlighting.
  6. Jun 2020
  7. May 2020
    1. Also known as "serverless", "client-side", or "static" web apps, unhosted web apps do not send your user data to their server. Either you connect your own server at runtime, or your data stays within the browser.

      serverless has another meaning (that does actually use a server) so I prefer the term "unhosted" since it has no such ambiguity.

      See also:

    1. A serverless app is an app that doesn't require a server for it to work. Most apps nowadays require a server, such as Facebook, quora, twitter etc. As a rule of thumb any app that doesn't connect to the internet is a serverless app (there are some others that are serverless but that is harder to tell). Flappy bird is an example you’ll be familiar with that is serverless.

      See also this comment:

      While this answer is true in the literal sense of the term, the question is most likely referring the new serverless trend in cloud infrastructure, with services like AWS Lambda and Iron.io.

    2. Serverless architectures allow you to build and run applications and services without having to manage infrastructure. Your application still runs on servers, but all the server management is done by Provider. You no longer have to provision, scale, and maintain servers to run your applications, databases, and storage systems.Serverless architecture accelerates development as a set of small, distinct, and independent actions. By abstracting away infrastructure, by doing this the developers can just concrete on building micro services/functions which performs some action and integrate with others to build a bigger service.
    1. This has too many, very different meanings.

      Especially these 2 which are themselves similar, but seem unlike the first 3:

      • an establishment engaged in doing business for another
      • an administrative division (as of a government) Both are basically an organization.
    1. Don’t go to code academy, go to design academy. Be advocates of the user & consumer. It’s not about learning how to code, it’s about translating real-world needs to technological specifications in just ways that give end users agency and equity in design, development and delivery. Be a champion of user-centric design. Learn how to steward data and offer your help.

      The importance of learning to design, and interpreting/translating real-world needs.

    1. function (or in the case of type classes, we call these methods)
    2. If you can tell that two types are equal or not equal, that type belongs in the Eq type class.

      two types or rather two things of the same type?

    1. If you update your pages and push to github, people revisiting the pages who have already got cached copies will not get the new pages without actually cleaning their browser cache. How can a script running in a page determine that it is stale and force an update?
    1. The issue of the different layers is similar. If you chose software that doesn’t deal with those layers in a sophisticated way, you will not reap the benefits in the long term. Your archive will note work as a whole. I think that this is one of the reasons why many retreat to project-centered solutions, curating one set of notes for each book, for example. The problems that come with big and organic (= dynamic and living) systems is avoided. But so is the opportunity to create something that is greater than you.

      Interesting point where the author compares the barrier that is created between the editing and the writing mode in a wiki (which makes it more cumbersome to continue lines of thought) to the barriers that appear when you're not using the right software or conventions to structure your knowledge items, as well as to structure your knowledge items' structure.

    1. Make it clear that signing up is optional. Consent must be “freely given”; you may not coerce users into joining your mailing list or make it appear as if joining the list is mandatory. For this reason, you must make it clear that signing up is optional. This is especially relevant in cases where you offer free white-papers (or e-books) for download. While the user’s email address is required for the delivery of the service, signing up for your newsletter is not. In such a case, you must not make it appear as if signing-up to the newsletter list mandatory and must make it clear that it is optional.

      Question (answer below)

      Are they saying that it's not allowed to make signing up for a mailing list a precondition/requirement for anything? This was surprising to me.

      So if you have a newsletter sign-up page that sends a digital bonus gift (like an e-book) to new subscribers, are required to completely change/repurpose your "newsletter sign-up page" into a "download e-book page" (that has an optional checkbox to also sign up for the newsletter, if you want)? That seems dumb to me, since it requires completely reversing the purpose of the page — which was, in my mind, primarily about signing up for the newsletter, with a bonus (an essentially optional one) thrown in for those who do so. Are you required to either repurpose it like that or remove the free bonus offer that would be sent to new subscribers?

      The irony of this is that it requires websites that have a newsletter sign-up page like that to change it into a "newsletter sign-up page" where the newsletter sign-up part is optional. Which make you look kind of stupid, making a page that claims to be one thing but doesn't necessarily do what it says it's for.

      Does this mean, in effect, that you may not lawfully provide any sort of incentive or reward for signing up for something (like a mailing list)? As long as it's very clear that some action is required before delivery of some thing, I don't see why this sort of thing should not be permitted? Would this fall under contract law? And as such, wouldn't such a contract be allowed and valid? Are mailing lists a special class of [service] that has special requirements like this? Or is it part of a broader category to which this requirement applies more generally?

      Why is requiring the user to provide an email address before they can download a digital reward allowed but not requiring signing up to a mailing list? Why isn't it required that even the email address be optional to provide? (To answer my own question, probably because it's allowed to allow a user to request a specific thing to be sent via email, and an email address is required in order to fulfill that request. But...) It seems that the website could just provide a direct link to download it via HTTP/FTP/etc. as an option for users that chose not to provide an email address. (But should they be required to provide that option anytime they / just because they provide the option to have the same thing delivered via email?)


      Looks like my question was answered below:

      Explicit Form (where the purpose of the sign-up mechanism is unequivocal). So for example, in a scenario where your site has a pop-up window that invites users to sign up to your newsletter using a clear phrase such as: “Subscribe to our newsletter for access to discount vouchers and product updates!“, the affirmative action that the user performs by typing in their email address would be considered valid consent.

      So the case I described, where it is made very clear that the incentive that is offered is conditional on subscribing, is listed as an exception to the general rule. That's good; it should be allowed.

    1. If any Firefox engineers are reading this, please don't try to subvert the above workaround, it requires multiple steps and administrator rights to set up, and we must all agree that it is of little sense for Firefox to try defending against unwanted programs or malware that has root access on the device.
    1. Firefox is the most compliant with the proposed standard, and is, therefore, your best place to start when developing browser extensions
  8. Apr 2020
    1. Mild to moderate normovolemic anemia does not appear to adversely affect wound oxygen tension and collagen synthesis. However, profound anemia with 15% less hematocrit can interfere with wound healing
    2. Wounds with delayed healing are characterized by decreased wound-breaking strength in comparison to wounds that heal at a normal rate; however, they eventually achieve the same integrity and strength as wounds that heal normally.
    3. HBOT was found to improve graft survival, complete healing of grafts, and lessen infection in patients with a graft
    1. As with neck injuries, hemodynamically stable patients with transmediastinal gunshot wounds should undergo CT scanning to determine the path of the bullet
    2. Patients with diffuse cerebral edema resulting in excessive ICP may require a decompressive craniectomy, although a recent AAST multicenter trial questioned the benefits.
    3. Patients with open or depressed skull fractures, with or without sinus involvement, may require operative intervention.
    4. Attention, therefore, is focused on maintaining cerebral perfusion rather than merely lowering ICP.
    5. Resuscitation efforts aim for a euvolemic state and a SBP of >100 mmHg.
    6. The goal of resuscitation and management in patients with head injuries is to avoid hypotension (SBP of <100 mmHg) and hypoxia (partial pressure of arterial oxygen of <60 or arterial oxygen saturation of <90%).
    1. Among the people who died from COVID-19 reported by the NHC, 11.8% of patients without underlying CVD had substantial heart damage, with elevated levels of cTnI or cardiac arrest during hospitalization.
    2. some of the patients first went to see a doctor because of cardiovascular symptoms. The patients presented with heart palpitations and chest tightness rather than with respiratory symptoms, such as fever and cough, but were later diagnosed with COVID-19.
  9. Mar 2020
    1. I've been meaning to remind readers that I do read the comments. Some time ago, one disappointed commenter mused that others' reflections seemed to go (as I recall) "into a void," because I remained silent to each. Perhaps I was ignoring readers' remarks? I assure you that is not the case. I read them all — although on this site, for some reason, "all" means somewhat sparse — and I find them nearly all remarkable in their perceptiveness. I especially welcome, and enjoy, intelligent disagreement. I choose not to respond, however, only because of my editorial philosophy, which holds that the comment section is, rightfully, for commenters — and commenters alone. I've already had my say, and it seems to me rather rude to take another whack in reply. Whenever I'm so substantively shaky or incoherent as to make my case unpersuasively the first time around, I figure I should live with the consequences. And whenever I find criticism flawed, I figure readers — perceptive as they are — will see the flaw as well, therefore there's no need for me to rub it in. So, I beg you not to take my silence personally.
    2. Whenever I'm so substantively shaky or incoherent as to make my case unpersuasively the first time around, I figure I should live with the consequences. And whenever I find criticism flawed, I figure readers — perceptive as they are — will see the flaw as well, therefore there's no need for me to rub it in.
    1. Because it's easier for Indiana Jones to recover the Sankara Stones than for someone with an idea for an App to find a decent App developer.  And because we wanted to finally have a place to send friends and clients who constantly ask for our help in finding developers. Yeah, we know there are more than 140,000 iPhone applications out there already, so not everyone is struggling to find a developer. But believe us, the demand outweights the supply. Hence, this site.
    1. 4. Build With Not For This simple but compelling phrase sums up our approach to building technology. The concept comes from a long history of movement work, and in the civic tech space has been popularized by Laurenellen McCann, who has written extensively on the topic. To us, the ethos of “build with note for” is a reminder that the moment we are in the mindset of building something “for” our partners rather than with them, we have failed. Going back to the theme that technology is not neutral and that our values are embedded in our work, whether it’s conscious or not, building “for” inherently conjures up a feeling of saviorism, of believing we have the answers, or believing we are here to do something for someone else. Building with means constantly checking our assumptions, being open to ideas we haven’t thought of, and, most of all, results in much better work.
  10. Feb 2020
    1. Performance Benchmarking What it is: Testing a system under certain reproducible conditions Why do it: To establish a baseline which can be tested against regularly to ensure a system’s performance remains constant, or validate improvements as a result of change Answers the question: “How is my app performing, and how does that compare with the past?”
    1. Nix is a purely functional package manager. This means that it treats packages like values in purely functional programming languages such as Haskell — they are built by functions that don’t have side-effects, and they never change after they have been built.
    1. k6 does not run in Node.js because it would perform poorly while running larger tests.Javascript is not generally well suited for high performance. It's a Go program - to achieve maximum performance - embedding a JavaScript runtime for running tests written in JavaScript.
  11. Jan 2020
  12. Dec 2019
  13. burnsoftware.wordpress.com burnsoftware.wordpress.com
    1. Files are sorted by moving them all into a folder with today’s date, and you can organize these folders by day, week, or month.
    1. Superseded by (replacement project): https://github.com/QTodoTxt/QTodoTxt2/

      Before I realized there was a replacement project:

      Blah. Looks good but unmaintained. Too many competing forks.

      Other interesting fork: https://github.com/kmicc/QTodoTxt/tree/dev

      This branch is 17 commits ahead, 201 commits behind QTodoTxt:dev. https://github.com/QTodoTxt/QTodoTxt/compare/master...kmicc:dev https://github.com/kmicc/QTodoTxt/network

    1. Please don't name binstubs common executable names. It just creates a whole bunch of shadowing issues. Granted, I also have an npm issue at hand, but I do think naming your binstubs webpack and webpack-dev-server is asking for trouble. Why not webpacker and webpacker-dev-server?
    2. The global executables are removed in latest release.
    1. Note that adding the X-Requested-With header makes the request "unsafe" (as defined by CORS), and will trigger a preflight request, which may not be desirable.
    2. It shouldn't be useful to distinguish between requests made by Ajax and other kinds of request. Pretty much any usecase where you'd want to do that is better served by using the Accept header to ask for data in a specific format.
  14. Nov 2019