53 Matching Annotations
  1. Last 7 days
    1. Presumably this is so that you can import React libraries, even if they depend on ReactDOM, and they will work with Svelte instead.

      Reminds me of Wine. IIRC they have some system calls that they just make to be no-ops on Linux.

  2. Oct 2020
  3. Sep 2020
    1. This code would work on any system with an x86 processor due to backward compatibility

      Kittler a le souci de penser la compatibilité (et surtout la rétro-compatibilité) de son écriture, de sa production.

      la pensée s'inscrit dans un médium, un médium qui évolue et qui, peut-être plus que jamais, soulève des enjeux d'archivage très importants (comme les œuvres artistiques qui reposent désormais sur des supports numériques à présent non supportés)

    1. But what if we want to use it in a legacy app built with for example Bootstrap 3 and lots of jQuery where there's no sign of Node.js? No problem! We'll just use the IIFE build and instantiate the component class through its global constructor:
    2. Did you know that you can create a Svelte component and with almost no extra steps distribute- and use it like any classic old Javascript library through a global constructor (let myComponent = new MyComponent())?
    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. This package exposes an hyperscript compatible function: h(tag, properties, ...children) which returns a svelte component.
    1. For interoperability with RxJS Observables, the .subscribe method is also allowed to return an object with an .unsubscribe method, rather than return the unsubscription function directly.
  4. Aug 2020
    1. So let’s say Apple pulls a Guido and breaks compatibility. What do you think will happen? Well, maybe 80–90% of the developers will rewrite their software, if they’re lucky. Which is the same thing as saying, they’re going to lose 10–20% of their user base to some competing language, e.g. Flutter.Do that a few times, and you’ve lost half your user base. And like in sports, momentum in the programming world is everything. Anyone who shows up on the charts as “lost half their users in the past 5 years” is being flagged as a Big Fat Loser. You don’t want to be trending down in the Platforms world. But that’s exactly where deprecation — the “removing APIs” kind, not the “warning but permitting” kind — will get you, over time: Trending down. Because every time you shake loose some of your developers, you’ve (a) lost them for good, because they are angry at you for breaking your contract, and (b) given them to your competitors.

      Twitter is a good example of this, and they've just created a shiny new API in an apparent attempt to bring developers back...

      Wonder if it's going to be backwards compatible? (Probably not...)

    2. It’s a sure sign, when there are four or five different coexisting subsystems for doing literally the same thing, that underlying it all is a commitment to backwards compatibility. Which in the Platforms world, is synonymous with commitment to your customers, and to your marketplace.

      This same sort of thing applies to WordPress for its backwards compatibility.

      I wonder if there were some larger breaking changes in Drupal 7 and 8 that removed their backwards compatibility and thereby lost them some older websites?

    3. Successful long-lived open systems owe their success to building decades-long micro-communities around extensions/plugins, also known as a marketplace.

      This could be said of most early web standards like HTML as well...

    4. In the Emacs world (and in many other domains, some of which we’ll explore below), when they make an API obsolete, they are basically saying: “You really shouldn’t use this approach, because even though it works, it suffers from various deficiencies which we enumerate here. But in the end it’s your call.”
    5. Backwards compatibility keeps systems alive and relevant for decades.
    1. WPML knows how to communicate with the Translation Proxy, and the Translation Proxy knows how to communicate with translation services. If a Translation Service company happened to change their API, we needed to only update the Translation Proxy.
  5. Jul 2020
  6. Jun 2020
    1. If you’re working in spreadsheet software (for example, Microsoft Excel, Google Sheets, or Apple Numbers), you can copy from a spreadsheet, and GitLab will paste it as a Markdown table. For example, suppose you have the following spreadsheet:
    1. Many features have been introduced continuously to Object Pascal with extensions to Delphi and extensions to FreePascal. In reaction to criticism, Free Pascal has adopted generics with the same syntax as Delphi, provided Delphi compatibility mode is selected, and both Delphi (partial) and Free Pascal (more extensive) support operator overloading. Delphi has also introduced many other features since version 7,[6] including generics. Whereas FreePascal tries to be compatible to Delphi in Delphi compatibility mode, it also usually introduced many new features to the language that are not always available in Delphi.
  7. May 2020
    1. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice.
    1. All valid JavaScript code is also TypeScript code. You might get type-checking errors, but that won't stop you from running the resulting JavaScript.
    1. A standard-setting organization is an industry group that sets common standards for its particular industry to ensure compatibility and interoperability of devices manufactured by different companies.
    1. That app you desperately need in order to function? We probably have it. The vast software libraries of Ubuntu and Flatpak combine to make all of your tools available in a single location, called the Pop!_Shop.
  8. Apr 2020
    1. More information on the CC license compatibility chart https://wiki.creativecommons.org/wiki/Wiki/cc_license_compatibility

      The compatibility chart is an excellent resource for visually identifying the scope of resuse. Most importantly, this chart shows the product of remixing licenses. This is another resource that will be employed for future reference.

  9. Feb 2020
  10. Jan 2020
  11. Dec 2019
    1. Countless productivity apps and sites store your tasks in their own proprietary database and file format. But you can work with your todo.txt file in every text editor ever made, regardless of operating system or vendor.
    1. It doesn't use a database (unlike Keepass) and thus doesn't open all passwords at once. Just one at a time. Since it's just a directory of encrypted files, you can access your passwords with any PGP-compatible tool.
    1. uBlock Origin blocks ads through its support of the Adblock Plus filter syntax. uBlock Origin extends the syntax and is designed to work with custom rules and filters.
  12. Nov 2019
    1. Reason compiles to JavaScript thanks to our partner project, BuckleScript, which compiles OCaml/Reason into readable JavaScript with smooth interop. Reason also compiles to fast, barebone assembly, thanks to OCaml itself.
    1. Onivim 2 leverages the VSCode Extension Host process in its entirety - meaning, eventually, complete support for VSCode extensions and configuration.
    1. Specific to a testing framework (though we recommend Jest as our preference, the library works with any framework. See Using Without Jest)
  13. Aug 2019
    1. https://wiki.creativecommons.org/wiki/Wiki/cc_license_compatibility

      This is still the most helpful visual I have seen thus far to help explain and clarify compatibility of CC licenses.

  14. Feb 2019
    1. g likelihood or Bayesian probabilistic phylogene

      If you have a molecular data partition, you can just use total evidence approach and the standard 1-parameter Markov model.

      Potential synapomorphies will be compatible with the molecular tree and considered not likely to change. Potential homoiologies and symplesiomorphies are partly ("semi-")compatible with the molecular tree and, hence, considered less likely to change than highly homoplastic traits with (random) convergence.

      Just try out a couple of datasets, and infer the (Bio)NJ and ML trees and then compare the result with the strict consensus network (not tree) of all equally parsimonious trees and the Bayesian tree sample.

      Note that if you apply TNT's iterative character weighting procedure, what you effectively do is sorting the random convergences from parallelisms/ characters that are more compatible with the preferred tree.

    2. set; if this is higher, the tree 2can be considered to fit the data less well

      To test the fit between data and more than one alternative tree, you can just do a bootstrap analysis, and map the results on a neighbour-net splits graph based on the same data.

      Note that the phangorn library includes functions to transfer information between trees/tree samples and trees and networks:<br/> Schliep K, Potts AJ, Morrison DA, Grimm GW. 2017. Intertwining phylogenetic trees and networks. Methods in Ecology and Evolution (DOI:10.1111/2041-210X.12760.)[http://onlinelibrary.wiley.com/doi/10.1111/2041-210X.12760/full] – the basic functions and script templates are provided in the associated vignette.

    3. number of character states bracketed by a node could 28be counted, and those which do not optimize as symplesiomorphies of the clade could 29considered as a value of node suppo

      Why differentiating between symplesiomorphies and homoiologies? Both are traits equally exclusive to a subtree (a clade) and closely linked to each other.

      Pink is a symplesiomorphy of the ingroup, blue the homoiology Pic1 Vice versa, blue is the symplesiomorphy, pink the homoiology found only in the most derived (in absolute evolutionary terms) taxa Pic2

    4. In principle, I do sympathize with the general idea, but the laid out approach will have little use.

      The main drawback is that you can only define homoiologies using an external data set (e.g. the molecular "gold" tree). But when you have a reliable molecular tree, you can just go for total evidence approaches to select a more likely, in a mathematical and general sense, alternative without the need to make any prior destinction between your characters. Homoiologies will be inferred, like synapmorphies or symplesiomorphies or shared apomorphies (non-stochastically distributed convergences) on the fly.

      If you define the homoiologies on a inferred (e.g. parsimony) tree only based on a morphological data matrix (e.g. for an extinct group of organisms), you will inevitably misinterpret some characters, because your clades are not necessarily monophyletic. Homoiologies like symplesiomorphies may appear as (pseudo-)synapomorphies.

      The only application left would be that the molecular tree cannot resolve certain relationships, and we use more tree-compatible morphological characters to discern between alternatives. However, the first choice would then be to maximise the number of synapomorphies. Only if that would be the same for all alternatives, one could count the number of symplesiomorphies and homoiologies (as the distinction between both via a tree-inference is very tricky; and their are often just two side of the same evolutionary process).

      However, one could also just directly change to a network-analysis framework, which will pretty much solve all these problems at once.

      For further details see my (upcoming, March 4th) post at Genealogical World of Phylogenetic Networks

  15. Nov 2018