egg
porter
egg | porter | |
---|---|---|
25 | 38 | |
1,239 | 4,145 | |
2.7% | 1.0% | |
6.8 | 9.9 | |
10 days ago | about 2 hours ago | |
Rust | Go | |
MIT License | GNU General Public License v3.0 or later |
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.
egg
-
An Introduction to Graph Theory
Maybe program optimization?
https://egraphs-good.github.io/
- The E-graph extraction problem is NP-complete
-
What is the state of the art for creating domain-specific languages (DSLs) with Rust?
For semantic analyzers, check out egg and egglog. They're custom data structures for representing compiler rewrite rules in a non-destructive way.
-
Ask HN: What is new in Algorithms / Data Structures these days?
E-graphs are pretty awesome, and worth keeping in your back pocket. They're like union-find structures, except they also maintain congruence relations (i.e. if `x` and `y` are in the same set, then `f(x)` and `f(y)` must likewise be in the same set).
https://egraphs-good.github.io/
(Incidentally, union-find structures are also great to know about. But they're not exactly "new".)
-
What are the current hot topics in type theory and static analysis?
I would add that Equality saturation/E-graphs has become quite a hot topic recently, since their POPL21 paper, with workshops dedicated to applications of e-graphs. They have even recently been added to Cranelift as an IR for optimizations.
-
Compiler Optimizations Are Hard Because They Forget
Egraphs solve the rewrite ordering problem quite nicely. https://egraphs-good.github.io/
Note that one solution to this problem is to use equality saturation (which, coincidentally, has a great implementation in rust!).
-
Modularity in IR representation and modification
Have you thought about trying to parallelize e-graphs? This way you can do a bunch of rewrite rules in parallel and then extract your desired graph at the end instead of having conflicts.
-
Any recommendations for good resources that show how algorithms and data structures are converted into fpga circuits
I think the equality saturation papers are a good start. A good start is egg. They have a presentation, a research paper and code you can play with. I think ultimately you want to translate arithmetic operations into logical operation that can be understood by the fpga. So I think it would be good to research how adders and multipliers are implemented in logic and ultimately include equalities between adders/multipliers with their logical counterpart. Note the this translation also depends on the representations of your numbers and their bit width.
-
Strategies for doing symbolic integration algorithmically
For rewriting, you may also find interesing equality saturation: https://egraphs-good.github.io/
porter
-
Open-source alternative to Heroku, Vercel, and Netlify
There's Porter, the "Kubernetes powered PaaS that runs in your own cloud".
https://github.com/porter-dev/porter
-
Porter Cloud – PaaS you can eject
Hi HN, this is Trevor and Justin from Porter (https://porter.run). We first launched on HN almost 3 years ago with our original product, which deploys your applications to your own AWS, Azure, or GCP account with the simple experience of a PaaS. (original launch post: https://news.ycombinator.com/item?id=26993421).
We’re excited to show you something new - we’ve built Porter Cloud (https://porter.run/porter-cloud), a hosted Platform as a Service (PaaS) that you can eject from. It works just like conventional PaaS’s that deploys your apps with a few clicks, but it lets you eject to your own AWS, Azure, or GCP account as you scale.
Since launching Porter in 2021, we helped migrate a lot of companies from a PaaS to AWS, Azure, and GCP. Most of these companies had gotten started on these platforms in the early days to optimize for speed and ease of use, but ultimately had to go through a painful migration to one of the big three cloud providers as they scaled and outgrew the original platform.
Interestingly, we learned that many startups that deploy on a PaaS are fully aware that they’ll have to migrate to the big three clouds at some point. Yet they choose to deploy on a PaaS anyway because outgrowing a cloud platform is a champagne problem when they're focused on getting something off the ground. This, however, becomes a very real problem when you start running into technical constraints and it is difficult to migrate your production environment while serving users.
We’ve built Porter Cloud so you can deploy the earliest versions of the product as quickly as possible, with a peace of mind that you can eject to the tried and true hyperscalers later. When you need to eject, you can follow a few simple steps to migrate your workloads to AWS, Azure, or Google Cloud with minimal downtime.
If you’re curious how it works, please drop your questions below. And if you’ve ever dealt with a migration from a PaaS to one of the big three cloud providers, we’d love to hear about your experience in the comments. Looking forward to it!
-
Show HN: Hatchet – Open-source distributed task queue
Yep, we're backed by YC in the W24 batch - this is evident on our landing page [1].
We're both second time CTOs and we've been on both sides of this, as consumers of and creators of OSS. I was previously a co-founder and CTO of Porter [2], which had an open-core model. There are two risks that most companies think about in the open core model:
1. Big companies using your platform without contributing back in some way or buying a license. I think this is less of a risk, because these organizations are incentivized to buy a support license to help with maintenance, upgrades, and since we sit on a critical path, with uptime.
2. Hyperscalers folding your product in to their offering [3]. This is a bigger risk but is also a bit of a "champagne problem".
Note that smaller companies/individual developers are who we'd like to enable, not crowd out. If people would like to use our cloud offering because it reduces the headache for them, they should do so. If they just want to run our service and manage their own PostgreSQL, they should have the option to do that too.
Based on all of this, here's where we land on things:
1. Everything we've built so far has been 100% MIT licensed. We'd like to keep it that way and make money off of Hatchet Cloud. We'll likely roll out a separate enterprise support agreement for self hosting.
2. Our cloud version isn't going to run a different core engine or API server than our open source version. We'll write interfaces for all plugins to our servers and engines, so even if we have something super specific to how we've chosen to do things on the cloud version, we'll expose the options to write your own plugins on the engine and server.
3. We'd like to make self-hosting as easy to use as our cloud version. We don't want our self-hosted offering to be a second-class citizen.
Would love to hear everyone's thoughts on this.
[1] https://hatchet.run
[2] https://github.com/porter-dev/porter
[3] https://www.elastic.co/blog/why-license-change-aws
-
Scaling Knative to 100K+ Webapps
Co-founder of Porter (https://porter.run) here - Porter is a platform that brings that easy PaaS experience to a k8s cluster that's running in your own cloud account (and manages it for you so you don't have to).
We are offering a credit program for early stage startups that you can apply for here, happy to fast track your application! https://porter.run/for-seed-stage-startups
-
Launch HN: Nullstone (YC W22) – An easier way to deploy and manage cloud apps
Co-founder of Porter (https://porter.run) here - we do not use Terraform under the hood. We moved away from an IaC based system earlier this year to better manage our users' infrastructure distributed across multiple cloud accounts. A decision that definitely turned out to be conveniently prescient :)
With this new system, we are also able to immediately reconcile drifts that occur in our user's infrastructure, which an IaC based system did not allow us to do.
-
Serving 250k Developers with One Support Engineer
Aptible hosts (and pays for) AWS resources on your behalf, similar to Heroku/Render/Railway. Last year, we built support for integrating Aptible into your own AWS account, but only a handful of existing customers are currently using that, and it's not available in the product by default. I'd be interested to learn why you prefer this model. If you're willing to chat about it, my email is in my profile.
Alternatively, have you checked out other PaaS-in-your-own-IaaS solutions like:
- https://porter.run/
- https://www.flightcontrol.dev/
- https://coolify.io/ (OSS, not managed)
These might not meet all your needs, and I think they're all relatively new.
-
Ask HN: Who is hiring? (November 2022)
Porter (YC S20) | Full Time | Full-Stack Engineer | NYC or Remote | https://porter.run
Hey HN, I'm Alexander, co-founder of Porter. We're building Heroku in your own cloud - we let users link up their own AWS/GCP, point to the code they want to run, and then put the rest of the hosting process on autopilot (CI/CD, SSL, autoscaling, zero downtime deploys, infra monitoring, etc).
We're hiring NYC-based or remote engineers that are passionate about building tools for developers. As we're a fast-growing seed-stage startup, you should be comfortable with regularly shifting priorities and iterating at a very high (daily) velocity.
Tech stack: Go, Typescript, React, Kubernetes, AWS
If you'd like to take a look at our codebase, we're open source - check it out at https://github.com/porter-dev/porter.
Open positions:
- Kubernetes Engineer: https://www.workatastartup.com/jobs/45970
- Full-stack Engineer: https://www.workatastartup.com/jobs/43716
Please apply by sending an email to jobs [at] porter [dot] run or applying through https://www.workatastartup.com/jobs/43716.
-
European cloud app platform?
https://porter.run is managed kubernetes on your own cloud with all the scaling built in. In theory, you could run this on your own cloud provider, and stay entirely within EU
-
Acorn: A lightweight PaaS for Kubernertes, from Rancher founders
How does this compare against https://porter.run/ ?
-
Ask HN: Are You Leaving Heroku?
Honestly you should checkout open source + self-host alternatives like porter (https://github.com/porter-dev/porter). I tried it in a project before and the developer experience was surprisingly good.
What are some alternatives?
prose - Microsoft Program Synthesis using Examples SDK is a framework of technologies for the automatic generation of programs from input-output examples. This repo includes samples and sample data for the Microsoft Program Synthesis using Example SDK.
coolify - An open-source & self-hostable Heroku / Netlify / Vercel alternative.
Symbolics.jl - Symbolic programming for the next generation of numerical software
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
Catlab.jl - A framework for applied category theory in the Julia language
engine - The Orchestration Engine To Deliver Self-Service Infrastructure Faster ⚡️
Dagger.jl - A framework for out-of-core and parallel execution
kubevela - The Modern Application Platform.
glow - Compiler for Neural Network hardware accelerators
rancher - Complete container management platform
StaticArrays.jl - Statically sized arrays for Julia
CapRover - Scalable PaaS (automated Docker+nginx) - aka Heroku on Steroids