1,479 Matching Annotations
  1. Dec 2019
  2. burnsoftware.wordpress.com burnsoftware.wordpress.com
  3. Nov 2019
    1. the main reason we built a new multiprocess architecture is that Chromium's multiprocess support was never contributed to the WebKit project. It has always lived in the separate Chromium tree, making it pretty hard to use for non-Chrome purposes.Before we wrote a single line of what would become WebKit2 we directly asked Google folks if they would be willing to contribute their multiprocess support back to WebKit, so that we could build on it. They said no.
    1. You want to write maintainable tests for your React components. As a part of this goal, you want your tests to avoid including implementation details of your components and rather focus on making your tests give you the confidence for which they are intended. As part of this, you want your testbase to be maintainable in the long run so refactors of your components (changes to implementation but not functionality) don't break your tests and slow you and your team down.
  4. Oct 2019
    1. espite the potential of emerging technologies to assist persons with cognitive disabilities,significant practical impediments remain to be overcome in commercialization, consumerabandonment, and in the design and development of useful products. Barriers also exist in terms of the financial and organizational feasibility of specific envisionedproducts, and their limited potential to reach the consumer market. Innovative engineeringapproaches, effective needs analysis, user-centered design, and rapid evolutionary developmentare essential to ensure that technically feasible products meet the real needs of persons withcognitive disabilities. Efforts must be made by advocates, designers and manufacturers to promote betterintegration of future software and hardware systems so that forthcoming iterations of personalsupport technologies and assisted care systems technologies do not quickly become obsolete.They will need to operate seamlessly across multiple real-world environments in the home,school, community, and workplace

      This journal clearly explains the use of technologies with special aid people how a certain group can leverage it, while also touch basing on what are the challenges which special aid people face financially.

  5. Sep 2019
    1. Las aplicaciones y archivos ejecutables

      La BNC no se responsabiliza por la preservación de aplicaciones creadas en Colombia. Esto es un punto a favor para proyectos como el de Grafoscopio que, por su infraestructura, está pensado para perdurar en un ambiente de programación que posibilita su preservación en el tiempo, Pharo. Sin embargo es un hueco en la memoria de la producción de contenidos digitales del país, la economía naranja en contexto de gobierno (2018-2022) y las defensas de la Dirección Nacional de Derecho de Autor a las industrias creativas (que incluye software en el marco de su protección) pero por las dependencias no hay garantías de preservarlas en el tiempo. Básicamente o los productores de software se hacen un lugar en el mercado o están destinados a perecer en el olvido en la memoria de la nación.

  6. Aug 2019
    1. I'm working full time on Material-UI since 2019. I was working on it during my free time before that. I hope that I can leverage my full-time involvement in the library to make it really awesome. You are right, the project is well-funded. We hope we can fund the time of more than 1 person full time in the future, with the current growth rate, it should soon be possible. We have 3 people working part-time on the project (Matt, Sebastian and Josh), plus the community behind us (+1,000 code contributors).
  7. Jul 2019
    1. At the design stage, when you discover problems, you can fix them easily by editing a few lines of text. Once the code is written, the cost of fixing problems is dramatically higher, both emotionally (people hate to throw away code) and in terms of time, so there’s resistance to actually fixing the problems. Software that wasn’t built from a spec usually winds up badly designed and the schedule gets out of control. 
    1. A tool to help determine weights (or a feature of a creditmap tool) seems most likely to be successful. Such a tool would likely have provide simultaneous views of the credit map and weights: one that allows a detailed view of any particular contriponent and its weight, and the other that provides a view (perhaps graphical) of the entire creditmap and weights.

      Great idea! Doesn't seem to exist yet, but it should also take in account the quality of each contribution (a few high-quality contributions can be more important than many low-quality contributions).

    2. Any product should list all authors (as currently listed as authors of a paper), all contributors (as currently listed in the acknowledgements of a paper) and all component products that have been used, including both publications and other products such as software and data (as currently either cited, acknowledged, or not included in a paper).

      Transitive credit's 1st element: credit (called "contriponent" - combination of contributors and components)

  8. Jun 2019
    1. total jerks. As the leader of a popular OSS project, in one way or the other you’ll have to confront with these people, and that’s maybe one of the most stressful things I ever did in the course of the Redis development.

      what's the way to shield yourself from that? This is stresfull mostly because this is not who he (or I) is... i.e. person equipped to deal with this kind of relations

    1. This is especially true for online gaming

      WASM is being used to run many demanding applications directly in the browser. Autocad is one important example where architects can use this application without installing a usually very heavy piece of software on their computers. They can access the Autocad suite from almost any computer only by logging into to a website. It is expected that a large part of the gaming industry will shift this way as well as many other services. One of the main advantages of this approach aside from a lack of a local installation is real-time software updates for any number of users. A new model of software building and execution will be based on WASM. WASM is also very good for blockchains. Search for the WASM section to learn more.

  9. May 2019
    1. By “Infrastructure” we mean

      ​The definition of "open infrastructure" (or the software component of open infrastructure) should include an explicit requirement for open-source code.​ Even an explicit recommendation short of a requirement would be better than the current definition, which is entirely silent the value of opening the code. The Elsevier acquisition of bepress (to use one example among many) would have been much less harmful to the community if the code had been open and user institutions could hold on to the platform, fork it if they wanted, take it in their own direction, and continue using it without becoming Elsevier customers.

  10. Apr 2019
    1. So in theory, one could imagine an organization that produces a different kind of document. Instead of a license for the source code, they would provide a way to say uh, let’s go with “Open Development Certified.” Projects could then submit for certification, they’d get accepted or rejected.

      This sounds a lot like the Apache trademark, to me.

  11. Mar 2019
    1. 6 Effective Strategies for Teaching Adults

      This article from Point Park University provides several methods one can use to help educate adults. Ideas presented include ensuring content is relevant, knowing the audience, igniting emotion in the audience, ensuring assignments are attainable, and providing constructive feedback. I find these especially helpful because of my work, which often involves teaching adults who are busy and sometimes uninterested in my content. The section that will help me most is "Encourage Exploration." Because I'm training on a software tool, I want learners to go into the software and make mistakes and learn from them. I want them to poke around! It can be difficult to convince a class of disgruntled 60-year-old men who are mad that things are changing to go play with a complex software tool like children. 7/10

    1. This is specific to Articulate Rise 360 (a rapid development tool) and features brief posts that keep the reader up to date on software changes, which are made frequently. Only a portion of each comment is visible on the main page (just as only a portion of an email is visible without clicking the email) but the subject heading is usually sufficient to describe the content of the post. rating 3/5

    1. This is associated with the e-learning development tool "Articulate Storyline." There are frequent blog posts and they are not limited to or exclusive to the Articulate products. Posts are brief and not all of the content will be new, but there are worthwhile tips to be had and they combine theory (not to the extent that an academic would) with practice. rating 3/5

    1. This page is not necessarily attractive to look at but it is a thorough presentation of various features of infographics. Features are organized by topic and generally presented as a bulleted list. The focus of the page is how to use infographics for assessment; however, the page is useful to those who wish to learn how to create infographics and to identify the software tools that can be used to create them easily. Rating 4/5

  12. Feb 2019
  13. Jan 2019
    1. For large-scale software systems, Van Roy believes we need to embrace a self-sufficient style of system design in which systems become self-configuring, healing, adapting, etc.. The system has components as first class entities (specified by closures), that can be manipulated through higher-order programming. Components communicate through message-passing. Named state and transactions support system configuration and maintenance. On top of this, the system itself should be designed as a set of interlocking feedback loops.

      This is aimed at System Design, from a distributed systems perspective.

    1. Grid devices can be nested or layered along with other devices and your plug-ins,

      Thanks to training for Cycling ’74 Max, had a kind of micro-epiphany about encapsulation, a year or so ago. Nesting devices in one another sounds like a convenience but there’s a rather deep effect on workflow when you start arranging things in this way: you don’t have to worry about the internals of a box/patcher/module/device if you really know what you can expect out of it. Though some may take this for granted (after all, other modular systems have had it for quite a while), there’s something profound about getting modules that can include other modules. Especially when some of these are third-party plugins.

    1. The Grid is based around ideas familiar to Bitwig Studio

      The continuity between these new modular features and the rest of the DAW’s workflow probably has unexpected consequences. Before getting information about BWS3, one might have thought that the “Native Modular System” promised since the first version might still be an add-on. What the marketing copy around this “killer feature” makes clear, it’s the result of a very deliberate process from the start and it’ll make for a qualitatively different workflow.

  14. Dec 2018
    1. OSS contribution takes time; I don't think anyone would contest that. Getting familiar with a project, finding out where you can fit into it, reading and responding to issues, testing and submitting patches, writing documentation. All of that requires a good deal of time.

      I reached out to a prominent OSS company preferring a "history of open source contributions" and put forward the idea that people who code for a living don't always have the opportunity. The response was surprisingly hostile:

      It doesn't exclude anyone. Zero chance I'm going to have a debate about it.

  15. Nov 2018
    1. how does misrepresentative information make it to the top of the search result pile—and what is missing in the current culture of software design and programming that got us here?

      Two core questions in one? As to "how" bad info bubbles to the top of our search results, we know that the algorithms are proprietary—but the humans who design them bring their biases. As to "what is missing," Safiya Noble suggests here and elsewhere that the engineers in Silicon Valley could use a good dose of the humanities and social sciences in their decision-making. Is she right?

    1. One quick trick for making it easier for debugging/understanding your threading macros is to put print statements in between some of the steps. The important thing to remember is that all the print functions in clojure return nil so you need to make a little helper function (I like to call mine ?) that prints and then returns the original input, like this: (defn ? [x] (prn x) x)

      debugging trick

    2. I don't think passing the entire http client is very idiomatic, but what is quite common is to pass the entire "environment" (aka runtime configuration) that your app needs through every function. In your case if the only variant is the URL then you could just pass the URL as the first parameter to get-data. This might seem cumbersome to someone used to OO programming but in functional programming it's quite standard. You might notice when looking at example code, tutorials, open source libraries etc. that almost all code that reads or writes to databases expects the DB connection information (or an entire db object) as a parameter to every single function. Another thing you often see is an entire "env" map being passed around which has all config in it such as endpoint URLs.

      passing state down the call stack configuration, connection, db--pretty common in FP

    3. Something that I've found helps greatly with testing is that when you have code with lots of nested function calls you should try to refactor it into a flat, top level pipeline rather than a calling each function from inside its parent function. Luckily in clojure this is really easy to do with macros like -> and friends, and once you start embracing this approach you can enter a whole new world of transducers. What I mean by a top level pipeline is that for example instead of writing code like this: (defn remap-keys [data] ...some logic...) (defn process-data [data] (remap-keys (flatten data))) (defn get-data [] (let [data (http/get *url*)] (process-data data))) you should make each step its own pure function which receives and returns data, and join them all together at the top with a threading macro: (defn fetch-data [url] (http/get url)) (defn process-data [data] (flatten data)) (defn remap-keys [data] ...some logic...) (defn get-data [] (-> *url* fetch-data process-data remap-keys)) You code hasn't really changed, but now each function can be tested completely independently of the others, because each one is a pure data transform with no internal calls to any of your other functions. You can use the repl to run each step one at a time and in doing so also capture some mock data to use for your tests! Additionally you could make an e2e tests pipeline which runs the same code as get-data but just starts with a different URL, however I would not advise doing this in most cases, and prefer to pass it as a parameter (or at least dynamic var) when feasible.

      testing flat no deep call stacks, use pipelines

    4. One thing Component taught me was to think of the entire system like an Object. Specifically, there is state that needs to be managed. So I suggest you think about -main as initializing your system state. Your system needs an http client, so initialize it before you do anything else

      software design state on the outside, before anything else lessions from Component

    1. Prezi is a productivity platform that allows for creation, organization, collaboration of presentations. It can be used with either mobile or desktop. Prezi integrates with slack and salesforce. RATING: 5/5 (rating based upon a score system 1 to 5, 1= lowest 5=highest in terms of content, veracity, easiness of use etc.)

    1. This means that software that deals with Internet must be actively maintained. If it is not it will become more and more useless in practice over time, however much it remains theoretically correct, not because it has bugs or security holes as such but because the environment it was designed to work in no longer exists and thus the assumptions it was built on are now incorrect.

      internet software decays

    1. The Moodle project

      Moodle is one of the largest open source collaborative platform used in the development of curriculum.

      Moodle is an Australian company and has various levels of subscriptions including one level for free. Overall I have found the site to be user friendly rich with demos, documentation and support including community forums. This site supports multiple languages and has an easy to use drop down menu for that selection.

      RATING: 5/5 (rating based upon a score system 1 to 5, 1= lowest 5=highest in terms of content, veracity, easiness of use etc.)

  16. Oct 2018
  17. Sep 2018
    1. E' altresì necessario accellerare la creazione di una struttura di certificazione del software nazionale che consenta di usufruire di tecnici che possano testare i software creati per la PA e assicurarne la conformità alle regole AGID e al GDPR (privacy by design). In tale ambito la capacità nazionale è attualmente molto limitata.

    1. In this singularity-free world, the future would be bleak for programmers. (Imagine having to cope with hundreds of years of legacy software!)

      I'm not really sure I agree with this. Regardless of whether Singularity eventually comes around or not, software will evolve. We have seen whole languages fall out of usage in the past, including Fortran, COBOL, ALGOL, etc. Developers will always be looking to get more efficient, and our current languages will either get abandoned or improved. New languages will come up and become the new standard. If anything, the future seems to be far more bleak for programmers/developers in the years after Singularity, rather than in the years leading upto it - after all, with the prevalence of docile, conscious machines,most of the work programmers do, everything from bug-fixing to data-analytics, would be done more quickly, cheaply and efficiently by the machines. In other words, in the world of singularity, programmers as we know them would no longer exist.

  18. Aug 2018
  19. Jul 2018
    1. Fully reproducible code is available in the form of jupyter notebooks (https://jupyter.org) with instructions to install all necessary software, download sequence data, assemble it, and run genomic analyses (https://github.com/dereneaton/Canarium-GBS) (DOI 10.5281/zenodo.1273357). For all genomic analyses in this study we used the ipyrad Python API and the ipyrad-analysis toolkit (https://github.com/dereneaton/ipyrad) which provides a set of wrappers around common genomic analysis tools to run highly parallelized analyses using simple Python scripts.

      Example of author sharing all code via jupyter notebooks in a github repo. They have archived to Zenodo and include both URLs in the text. Their analysis relies on an existing toolkit - it is not obvious from the manuscript whether this toolkit has been deposited anywhere.

      Journal: PLOS ONE Subject area: plant biology, ecology (check?)

    1. Source code of the model presented here is available on GitHub (https://github.com/lukasgeyrhofer/phagegrowth) (Payne et al., 2018) and its archived version is accessible through Zenodo: https://dx.doi.org/10.5281/zenodo.1038582 and https://github.com/elifesciences-publications/phagegrowth.

      Example of authors archiving their own code. The eLife process is to fork the author's repo to the eLife github repo to save a snapshot of the repo at the time of acceptance. The authors here have also chosen to archive to Zenodo (via the Github release --> Zenodo mechanism?). Both the Zenodo DOI and the eLife fork are included in the text as archive/snapshot copies of the original (also cited).

      Note the author's original repo is included in the references.

      Journal: eLife Subject area: ecology, evolutionary biology

  20. Jun 2018
    1. Acero F., Ackermann M., Ajello M. et al (Fermi-LAT) 2015 arXiv:1501.02003Preprint

      Starting in 2014-2015, AAS/IOP started linking to preprints in reference lists if they were the version cited by the author and an accepted manuscript did not at that time exist.

      Thus we now have built in "categories" for references, which could be expanded to include data/software sections.

    2. The most up-to-date version of the open-source package NPTFit may be found at https://github.com/bsafdi/NPTFit and the latest documentation at http://nptfit.readthedocs.io. In addition, the version used in this paper has been archived at https://zenodo.org/record/380469#.WN_pSFPyvMV.

      This is an example of incorrect software citation per the AAS Journal's policy. The Zenodo metadata should have been added to the reference list as a 1st class citation.

      It is also an example of an incorrectly typeset URL. URLs that come from DOIs should be typeset using the DOI string not the resolved URL. It should have read, "version used in this paper has been archived at https://doi.org/10.5281/zenodo.380469"

    1. Software: hotpants, PostgreSQL, realbogus (Bloom et al. 2012) scamp (Bertin 2006), sextractor (Bertin & Arnouts 1996), sncosmo (Barbary 2014), swarp (Bertin et al. 2002), matplotlib (Hunter 2007), numpy (Van Der Walt et al. 2011).

      The AASJournals now highlight software using a paragraph trailing the acknowledgements that lists all software used in the paper's analysis. The software doesn't need to be mentioned in the main text; context-free mentions can be placed here.

      The format is a 2 item tuple containing the short/common name of the software, and a citation or URL for the software.

      In principle this section could be data mined. At the moment it is just a free paragraph in the XML, but could be given more explicit markup to aide in data mining reuse and indexing.

    1. Software: Juypter notebook (http://jupyter.org), Jupyterlab (https://github.com/jupyterlab), VOspace (http://www.canfar.net/en/docs/storage), vos (https://pypi.python.org/pypi/vos), VirtualBox (https://www.virtualbox.org), JupyterHub      (https://jupyterhub.readthedocs.io/en/latest/), ipywidgets (https://ipywidgets.readthedocs.io), NuPyCEE (http://nugrid.github.io/NuPyCEE), NuGridSetExplorer (https://github.com/NuGrid/WENDI), hdf5 (https://www.hdfgroup.org), Cyberlaboratories cyberhubs (https://github.com/cyberlaboratories/cyberhubs), Cyberlaboratories astrohubs        (https://github.com/cyberlaboratories/astrohubs), Cyberhubs Docker repository (https://hub.docker.com/u/cyberhubs), Docker (https://www.docker.com), NOAO data lab (http://datalab.noao.edu), ansible (https://www.ansible.com), puppet (https://puppet.com), mesa_h5 (https://github.com/NuGrid/mesa_h5), Python (https://www.python.org), MESA (http://mesa.sourceforge.net), WENDI (http://wendi.nugridstars.org), OpenMP (http://www.openmp.org), MESA-SDK (http://www.astro.wisc.edu/~townsend/static.php?ref=mesasdk), MPI (https://www.open-mpi.org), gfortran (https://gcc.gnu.org/fortran), SuperLU (http://crd-legacy.lbl.gov/~xiaoye/SuperLU), OpenBLAS (http://www.openblas.net), mencoder (http://www.mplayerhq.hu).

      It would be better to see some of these going to bibliographic references instead of URLs though many of them do not list preferred citations.

  21. May 2018
  22. Apr 2018
  23. Feb 2018
    1. With sentiment analysis software, set for trial use later this semester in a classroom at the University of St. Thomas, in Minnesota, instructors don’t need to ask. Instead, they can glance at their computer screen at a particular point or stretch of time in the session and observe an aggregate of the emotions students are displaying on their faces: happiness, anger, contempt, disgust, fear, neutrality, sadness and surprise.

      Wha?

  24. Jan 2018
  25. Dec 2017
  26. Nov 2017
  27. Oct 2017
    1. The bug we ran into only affected certain releases of Postgres 9.2 and has been fixed for a long time now. However, we still find it worrisome that this class of bug can happen at all. A new version of Postgres could be released at any time that has a bug of this nature, and because of the way replication works, this issue has the potential to spread into all of the databases in a replication hierarchy.

      Not really a criticism of Postgres so much as it is a criticism of software in general.

  28. Sep 2017
    1. Singularity containers can be used to package entire scientific workflows, software and libraries, and even data.

      Very interesting, basically Singularity allows containers to run in HPC environments, so that code running in the container can take advantage of the HPC tools, like massive scale and message passing, while at the same time keeping the stuff in the container safer.

  29. www.softwareheritage.org www.softwareheritage.org
  30. Aug 2017
    1. Remember, PIMS were a hot market prior to Windows 3.0 - but most products were never ported to Windows because there wasn't enough revenue being made. This was because users would buy the hype, buy the product but weren't commited enough to get past the learning curve and dedicate time to maintaining data in it. So, most PIMs just became shelf-ware. And it wasn't because they weren't powerful or didn't have good interfaces - they did (as Grandview and Agenda easily demonstrate).
  31. Jul 2017
    1. In the case of Computer Software (what are referred to in this Policy as Non-Traditional Works as defined in Section B.5) in which the University has invested Extraordinary Resources (defined in Section B.6), the Creator shall own the copyright to such Non-Traditional Work; provided, however, that the University is entitled to share in the revenues generated by licensing copyrighted works created and owned by members of the Northwestern Academic Community when all three of the following conditions are met:
    2. ). In the case of Computer Software created by members of the Northwestern University Academic Community in the course of their employment the Creators shall grant to the University a perpetual, non-exclusive, royalty-free right and license to use, perform, display, copy, reproduce, modify and create derivatives of such works for all traditional, customary or reasonable academic or research purposes of the University.
  32. Jun 2017