ideogram
localForage
Our great sponsors
ideogram | localForage | |
---|---|---|
3 | 27 | |
277 | 24,255 | |
- | 1.0% | |
9.2 | 0.0 | |
3 months ago | 4 months ago | |
JavaScript | JavaScript | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ideogram
-
New CRISPR-based map ties every human gene to its function
> Where are the polished, powerful design tools for biology
User interfaces for biology have drastically improved over the last 10 years.
Domain-specific tools like genome browsers, protein viewers, or phylogenetic explorers [1-3] almost all look and feel a lot better than they did in 2012.
The biggest exception here is UCSC Genome Browser, which has an old-school design and web technology stack. That said, it's steadily added features over the years, has substantially sleekened UX in its periphery, and remains widely used.
There are also bespoke visual design resources for biology applications that are good and getting better, like BioRender and PhyloPic [4-5]. There are multi-tiered packages like Dash Bio that wrap biology components together. There's Blender biology community, too!
---
1. Genome browsers and components: https://jbrowse.org/jb2/, https://www.ncbi.nlm.nih.gov/genome/gdv, https://igv.org/app, https://eweitz.github.io/ideogram
2. Protein viewers: https://pymol.org/, https://nglviewer.org/ngl/
3. Phylogenetic explorers: https://clades.nextstrain.org/
4. https://biorender.com/
5. http://phylopic.org/
6. https://github.com/plotly/dash-bio, https://dash.gallery/Portal/?search=[Pharma]
-
Why IndexedDB is slow and what to use instead
I'm more interested in read speeds than write speeds. I have about 2 MB of data that I fetch, then parsed and transformed into a heavily nested object for easy look-up by various types of keys.
In my brief experiment, it was 12% faster to read from the web Cache API, re-parse and re-transform that heavily nested object than to read the fully transformed object via IndexedDB. That surprised me! My understanding is that IndexedDB does a structured clone as part of the read, which I suspect is the main cause of slowness of IndexedDB relative to the Cache API approach in my use case.
Related commits to reproduce that finding are in [1], specifically [2].
[1] https://github.com/eweitz/ideogram/pull/285
-
Ask HN: What are some tools / libraries you built yourself?
I created Ideogram.js, a JavaScript library for chromosome visualization [1]. Ideogram supports drawing and animating genome-wide datasets, enabling a variety of genomic views [3].
[1] https://github.com/eweitz/ideogram
[2] https://eweitz.github.io/ideogram
localForage
-
How to get core.async to play well with IndexedDB
Not really an answer but have you looked into https://github.com/localForage/localForage
-
I need help about what is my problem and how to google it
I may not be pointing you in the right direction but, please read about [IndexDB storage](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB\_API) method and packages like [localForage](https://localforage.github.io/localForage/) that use it under the hood.
-
Better Ways To Handle Data Storage on The Web Client
LocalForage: this is a wrapper around IndexedDB, WebSQL, LocalStorage, and SessionStorage with a way to define more interfaces (called drivers) *for additional storage solutions. It does a great job handling all your serialization needs, it is **asynchronous **and handles a large set of data types. Its **API resembles Web Storage API* and it is ridiculously simple to learn.
-
SvelteKit: Use local database in the browser
Depending on what kind of storage requirements you have, LocalForage might be a good fit. It provides a unified API to access WebSQL, indexedDB or localStorage.
- How to use Local Forage?!
-
Storing JSON data in project or fetching every time?
I find localForage is pretty helpful for this stuff https://github.com/localForage/localForage
-
[AskJS] Simple javascript database that can replace local storage?
localForage (https://localforage.github.io/localForage/) mirrors localStorage syntax, but uses IndexedDB in the background. If that's not supported, it uses WebSQL and then LocalStorage
-
Experienced JavaScript Developer Meme
This is why we have localForage.
- Where should I store images ?
What are some alternatives?
genetic-origins-heatmap - Use your DNA data (e.g. from 23andMe) to paint a global heatmap of your origins.
Dexie.js - A Minimalistic Wrapper for IndexedDB
GoJS, a JavaScript Library for HTML Diagrams - JavaScript diagramming library for interactive flowcharts, org charts, design tools, planning tools, visual languages.
store.js - Cross-browser storage for all use cases, used across the web.
absurd-sql - sqlite3 in ur indexeddb (hopefully a better backend soon)
PouchDB - :koala: - PouchDB is a pocket-sized database.
rupy - HTTP App. Server and JSON DB - Shared Parallel (Atomic) & Distributed
svelte-persisted-store - A Svelte store that persists to localStorage
lowdefy - The config web stack for business apps - build internal tools, client portals, web apps, admin panels, dashboards, web sites, and CRUD apps with YAML or JSON.
Cookies - JavaScript Client-Side Cookie Manipulation Library
fselect - Find files with SQL-like queries
LokiJS - javascript embeddable / in-memory database