ideogram VS leapp

> 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]

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

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

Summary:

Do you find yourself overwhelmed with work, requests, or complaints and in need of assistance to alleviate the pressure, enhance communication, facilitate organization, prioritize tasks, and foster greater trust and transparency?

Alternatively, I can work as a full stack developer.

AWS Community builder, AWS User group Leader, public speaker (https://www.youtube.com/watch?v=qdu58NAQfU0&t=271s)

Or perhaps you need both? =)

I have 4+ years of experience as a product manager and 8 in product development (before pm: agile coach, UX designer, and developer).

I've been the co-founder of the open-core company behind the OSS project Leapp (https://github.com/Noovolari/leapp)

Please feel free to reach out.

You can switch to saml2aws using the browser method instead of the Okta method and it will continue to work after the upgrade. There is also a really neat GUI tool to manage your session tokens that also works. https://www.leapp.cloud

Take a try to Leapp: https://github.com/Noovolari/leapp

Hello everyone, I'm the maintainer of an open-source DeveloperTool (https://github.com/Noovolari/leapp)

With a heuristic of 7000 users daily, I started feeling the need to have more information on how Users are using the project to improve it.

Is it the right thing to do to create a better Developer Experience and gain feedback for the end users?

On a side:

- For all your employees I can advice you Leapp as open-source project (https://github.com/Noovolari/leapp). It solve mayor of the problem listed here:

I am looking to manage Leapp (https://www.leapp.cloud/) from the StreamDeck. Leapp allows you to manage and switch between different Cloud Accounts (AWS, Azure, etc). Leapp has a command line interface which I could automate with a StreamDeck plugin. Unfortunately it looks like the only official SDK is the sandboxed JavaScript one. This means I cannot automate command line tools with it.

If you’re wondering if there is a tool that allows you to stop thinking about AWS credentials and where to store them in the right way, give a look at Leapp! It takes the responsibility of storing long-term credentials in the system vault, generating/refreshing short-term credentials, and placing them in the right place for the clients to use them.

Still, there is an elementary problem that we need to address, and it’s more on the operational side of things. Once we secured and implemented a tremendous multi-account strategy, how do people access AWS accounts? It turns out there is a fantastic open-source tool that lets you handle that with no effort, and its name is Leapp.

When you have to configure access to multiple AWS accounts using the Assume Role access pattern, it becomes difficult to get rid of all the Named Profiles configuration data and relationships. When you’ve to deal with a complex access scenario, tools like Leapp (https://www.leapp.cloud) come to the rescue! Leapp avoids you to specify relationships between Named Profiles in the config file, as the access methods are stored in the tool-specific configuration file.

Leapp Github repository