poly VS teliva

Compare poly vs teliva and see what are their differences.

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
poly teliva
24 11
649 162
2.6% -
8.2 2.7
about 1 month ago 5 months ago
Go C
MIT License GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

poly

Posts with mentions or reviews of poly. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-04-13.
  • Looking for an Open Source project to participate in for Google Summer of Code
    1 project | /r/golang | 10 Dec 2023
  • GitHub Accelerator: our first cohort and what's next
    28 projects | news.ycombinator.com | 13 Apr 2023
    - https://github.com/TimothyStiles/poly: Poly is a fast, well tested Go package for engineering organisms.
  • These 20 startups are in 1st ever batch of GitHub OS Accelerator
    7 projects | /r/github | 12 Apr 2023
    Poly: Fast Go package for engineering organisms
  • Ask HN: Burnt out from big tech. What's next?
    2 projects | news.ycombinator.com | 9 Feb 2023
    You might want to look at computational biology. Jim Allison won the Nobel Prize back in 2018 for his work on immunotherapy for cancer and there's a lot of basic research work to be done to perfect this approach. Epigenetic clocks are really interesting too (see Steve Horvath's work). Also, there's synthetic biology, where you could, for example, explore this package that's written in Go: https://github.com/TimothyStiles/poly
  • Any corner cases for Needleman-Wunsch that should be tested?
    1 project | /r/bioinformatics | 3 Feb 2023
  • Where can I find well-written go code to learn from?
    14 projects | /r/golang | 10 Jan 2023
  • High-performance language recommendation
    3 projects | /r/bioinformatics | 1 Jan 2023
    Check out poly. It’s written in go and I’m using it for one of my projects too. The goal is that we should have high performance libraries that we can use knowing what people are working on the forks will give the community a leg up.
  • How is GO used in bioinfo?
    2 projects | /r/bioinformatics | 27 Dec 2022
    The most popular bioinformatic package I've seen in go is poly.
  • Software engineers: consider working on genomics
    6 projects | news.ycombinator.com | 19 Nov 2022
    I write synthetic biology software for a living and maintain this open source, Go package for engineering DNA that has high test coverage and a nice little dev community around it.

    https://github.com/TimothyStiles/poly

    A large part of my project's community are devs that want to get into the field but can't tolerate the ridiculously low pay, laughably bad management, disrespect, and what amounts to 40+ years of technical debt that's endemic to biotech software.

    I've had companies here in the Bay Area offer me 100K a year with a straight face. I've had companies during interview tell me they're looking for someone to help, "set up GitHub". I've seen job listings for low paid web dev positions require applicants to have PhDs.

    The reality is that except for a growing handful of places management straight up won't know the difference between IT and software engineers. It's what I call the naive buyers problem.

    The demand for software engineers in biotech is generated by naive buyers that don't know what they need, why they need it, or how to get it.

    Benchling and Recursion Pharmaceuticals have reputations in the industry of paying, "standard software salaries". So do the research divisions at places like deepmind/microsoft/google but in my experience there's even new multi-billion dollar institutes where senior management has never even heard the term devops.

    Most places advertise for "data scientist", positions or some analog, instead of software engineers. This is mostly because upper management has never met an actual practicing software engineer in a professional setting. Many come from academia where the culture and work requirements heavily disincentivize standard software engineering practices.

    It's also not uncommon for a biotech company to either have a very under qualified CTO whose main programming experience is what they learned doing ML research like stuff during their PhD or not even have one at all which has huge downstream consequences.

    This week a software engineer trying to make the switch to biotech actually DM'd me to ask why they were seeing a ton of data science / ML job positions but no software engineering / devops positions.

    They were worried that these companies were trying to save on costs by forcing their data scientists to create infrastructure but it's actually worse than that. Most of these companies aren't even aware that there's supposed to be infrastructure.

    Despite all of this the future is looking better and I'm starting to find new companies and positions that are well... reasonable. I learned about this thread from a friend at a party last night that works at one of these companies. There's a small, strong new wave of companies and developers out there pushing biotech software forward. Hopefully some (including myself) make it big while pushing the idea that better tech equals better biotech.

  • Ask HN: What interesting problems are you working on? ( 2022 Edition)
    29 projects | news.ycombinator.com | 16 Sep 2022
    It is more like the X Y Z W. However, the X Y Z W bits I am working on as well (https://github.com/TimothyStiles/poly , https://github.com/TimothyStiles/allbase , trilo.bio, freegenes.org). Going for fully automated "make bacterium X produce molecule Y", but still a while away (but surprisingly not THAT far off)

teliva

Posts with mentions or reviews of teliva. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-03.
  • Silver Bullet: Markdown-based extensible open source personal knowledge platform
    14 projects | news.ycombinator.com | 3 Dec 2022
    Thanks for reply and for have shared your project first!

    > I think we can refresh some the things that make it powerful with a fresh coat of paint, to make it more accessible to a “younger generation.”

    That's what scare me, again in general: I see regular small complaint of modern absurdity, posts like:

    - https://tiramisu.bearblog.dev/your-desktop-is-not-a-destinat... | https://news.ycombinator.com/item?id=33838697

    - https://mjg59.dreamwidth.org/61535.html

    - https://vermaden.wordpress.com/2022/02/07/epitaph-to-laptops...

    - https://rsapkf.org/weblog/q2z/

    - https://tomcritchlow.com/2022/04/21/new-rss/

    - https://jfm.carcosa.net/blog/computing/usenet/ | https://news.ycombinator.com/item?id=33510169

    - https://dianne.skoll.ca/projects/remind/ | https://news.ycombinator.com/item?id=28363453

    - https://github.com/akkartik/teliva

    - https://akiflow.com/

    - https://onezero.medium.com/the-document-metaphor-desktop-gui...

    - https://den.dev/blog/user-hostile-software/

    - https://www.charlieharrington.com/smart-phone-dumb-terminal/

    - https://mattmower.com/2021/08/02/what-we-lost/

    and COUNTLESS others, similarly many "new stuff"/innovations appear and are actually partial, limited and limiting solutions to problems already solved decades ago in a more broad and superior way.

    Emacs itself is a bit horrific in the sense that it's codebase is hard to be kept up by modern developers who have troubles knowing it, but at least represent the classic model. If we lost the memory of the past it will takes decades to reach the level of evolution we have already achieved witch is really a shame.

    Anytime I see new software, yours, LogSeq, some "new shiny file manager", Tiidly Wiki and so on, witch actually are a BIG effort to achieve something already existing with far less efforts thanks to an already made ecosystems who makes their development easier I have a sore smile: end users suffer from limits of modern software, DEVELOPERS suffer equally because craft something on top of modern systems it's equally terrible but we seems to be unable on one side to reach again a critical mass of users to being able to innovate again, on the other sides most people simply ignore the past so ignore what's lost.

    A stupid example: link an email in SB means essentially or support a specific MUA, tracking it's evolution since breaking changes might happen all the time or add an MUE inside SB. In Emacs it's just a simple function since anything is already there. In Plan 9 to cite a project often considered hostile from and to Emacs write an MUA is damn simple limiting mails to Plan 9 itself, an MUA it's just a specific viewer of some text stream read form some user-configured filesystems mounts and so on.

    The sore part is that's I can easy state the above, even in my poor English, but I have no practical solution because resurrecting the classic model for present times demand an effort ONLY a public funded body or a large community can made. We have dismissed "for business reasons" essentially all public research and we have essentially pushed to irrelevance all communities...

  • 10 Years Against Division of Labor in Software
    5 projects | news.ycombinator.com | 22 Jan 2022
    I question the need for scale in 90% of the places where the tech industry has cargo-culted it. Clearly I'm still failing to articulate this. Perhaps https://news.ycombinator.com/item?id=30019146#30040616 will help triangulate on what I mean.

    > Can you clarify what you see as the alternative? Implementing everything from scratch seems absurd and so costly that there’s no point in considering this an actual option.

    Not using, reimplementing and copying are the closest thing to solutions I have right now. You're right that they're not applicable to most people in their current context. I have a day job in tech and have to deal with some cognitive dissonance every day between my day job and my open source research. The one thing I have found valuable to take to my scale-obsessed tech job is to constantly be suspicious of dependencies and constantly ask if the operational burdens justify some new feature. Just switching mindset that way from software as asset to software as liability has, I'd like to believe, helped my org's decision-making.

    > We have probably invested dev-millennia into managing copies. This is exactly what source control does. This is not a new area of investment. Merging is a giant pain in the ass and very possibly always will be. Accepting merge pain better come with some huge benefits.

    Not all copying is the same. We've learned to copy the letter 'e' so well in our writings that we don't even think about it. In this context, even if I made a tool to make copying easier and merges more reliable, that would just cause people to take on more dependencies which defeats the whole point of understanding dependencies. So tooling would be counter-productive in that direction. The direction I want to focus on is: how can we help people understand the software they've copied into their applications? _That_ is the place where I want tooling to focus. Copying is just an implementation detail, a first, imperfect, heuristic coping mechanism for going from the world we have today to the world I want to move to that has 1000x more forks and 1000x more eyeballs looking at source code. You can see some (very toy) efforts in this direction at https://github.com/akkartik/teliva

    > It’s untenable to have, e.g., everyone who works on Windows be an expert in every part of the code.

    It's frustrating to say one thing in response to counter-argument A and have someone then bring up counter-argument B because I didn't talk about it right there in the response to counter-argument A. I think this is what Plato was talking about when he ranted about the problems with the newfangled technology of writing: https://newlearningonline.com/literacies/chapter-1/socrates-.... I'm not saying everyone needs to be an expert in everything. I'm saying software should reduce the pressure on people to be experts so that we can late-bind experts to domains. Not every software sub-system should need expertise at the scale at which it is used in every possible context. My Linux laptop doesn't need to be optimized to the hilt the way Google's server farms do. Using the same scheduling algo or whatever in my laptop imposes real costs on my ability to understand my computer, without giving me the benefits Google gets from the algo.

  • dwm
    8 projects | news.ycombinator.com | 14 Jan 2022
    There are options between those possibilities, though. Here's my preferred point[1] in the state space:

    It's impossible for people to effectively use software over the long term without learning about its internals. Software can help people learn about its internals.

    https://github.com/akkartik/teliva#readme

  • Ask HN: Who Wants to Collaborate?
    58 projects | news.ycombinator.com | 1 Jan 2022
    I work on ways to write programs that help outsiders understand their big picture (rather than insiders understand incoming contributions).

    The goal: you (any programmer) should be able to use an open-source program, get an idea for a simple tweak, open it up, orient yourself, and make the change you visualized -- all in a single afternoon.

    More details: http://akkartik.name/about

    What I have so far: https://github.com/akkartik/teliva

    Lately I'm spending a lot of time on the sandboxing model. It's nice to be able to download and run untrusted programs. How to permit this without letting them cause too much damage, by explicitly giving them arbitrarily fine-grained permissions that are still easy to take in at a glance.

  • A small, hackable, text-mode browser for the Gemini protocol. Built on my platform for small, hackable, text-mode apps.
    1 project | /r/BarbarianProgramming | 22 Dec 2021
    Main project page: https://github.com/akkartik/teliva
  • Mu: A Human-Scale Computer
    4 projects | news.ycombinator.com | 8 Dec 2021
    It's hard. Building Mu has given me more of a flavor for just how hard it is. Some limitations of Mu:

    * It still requires firmware. There's a whole lot of C down there. How deep do you want to go?

    * No mouse. This is just my own ignorance. I can't get the damn IRQs and interrupts figured out.

    * Doesn't work yet on real hardware. I live in Qemu. Debugging that is a whole new set of skills I need to learn.

    * No networking, almost no persistent storage. Mu has a very simple and slow driver for ATA disks, but that probably won't suffice on most real-world machine configurations. There's 0 network drivers right now. I probably need a dozen to get any sort of coverage.

    The stuff you mentioned around graphics and OS file dialogs, that feels easier once you're willing to put up with constraints like Mu's 1024x768 and so on. But yeah, there's major challenges on this road.

    Partly due to these challenges, I've actually started to hedge my bets and make some compromises. My new project is https://github.com/akkartik/teliva which doesn't try to eliminate C, just minimize it. Linux kernel, libc, Lua (12k lines of C), some libraries for https. A gemini client is actually on my todo list there. I think I have everything I need to build it.

  • Hacking the planet with Notcurses: a guide to TUIs (2020) [pdf]
    4 projects | news.ycombinator.com | 5 Dec 2021
    with chromatic backgrounds deserve whatever happens to them."

    That's a lot of cognitive dissonance in a work about UI design. Let's try to do better in making TUIs mainstream. That requires encouraging people to use the few features terminals _do_ provide.

    I've been doing a fair amount of ncurses hacking recently[1], and I prefer to always explicitly specify colors. People won't get their preferred colors by default, but they'll always get a legible configuration by default.

    [1] https://github.com/akkartik/teliva

  • Fork of Lua 5.1 to encourage end-user programming
    1 project | /r/lua | 15 Nov 2021
  • Teliva – an environment for end-user programming
    5 projects | news.ycombinator.com | 15 Nov 2021
  • Teliva: A Runtime for Text-mode Lua Apps that Supports Modifying them
    1 project | /r/BarbarianProgramming | 14 Nov 2021
    Repo

What are some alternatives?

When comparing poly and teliva you can also consider the following projects:

Raylib-CsLo - autogen bindings to Raylib 4.x and convenience wrappers on top. Requires use of `unsafe`

mu - Soul of a tiny new machine. More thorough tests → More comprehensible and rewrite-friendly software → More resilient society.

pg-mem - An in memory postgres DB instance for your unit tests

pharo - The Sources for Pharo

linaria - Zero-runtime CSS in JS library

dwm-flexipatch - A dwm build with preprocessor directives to decide which patches to include during build time

seq - A high-performance, Pythonic language for bioinformatics

awayto - Awayto is a curated development platform, producing great value with minimal investment. With all the ways there are to reach a solution, it's important to understand the landscape of tools to use.

m4b-tool - m4b-tool is a command line utility to merge, split and chapterize audiobook files such as mp3, ogg, flac, m4a or m4b

Rectangle - Move and resize windows on macOS with keyboard shortcuts and snap areas

full_spectrum_bioinformatics - An open-access bioinformatics text

Typesense - Open Source alternative to Algolia + Pinecone and an Easier-to-Use alternative to ElasticSearch ⚡ 🔍 ✨ Fast, typo tolerant, in-memory fuzzy Search Engine for building delightful search experiences