HackerTrans
TopNewTrendsCommentsPastAskShowJobs

pnoel

no profile record

Submissions

Show HN: Open-Source Infrastructure for Vector Data Streams

github.com
4 points·by pnoel·3 anni fa·2 comments

What I Learned Building Whist (Mighty Competitor)

philippemnoel.notion.site
1 points·by pnoel·3 anni fa·1 comments

[untitled]

1 points·by pnoel·4 anni fa·0 comments

CEOs for CS

ceosforcs.com
3 points·by pnoel·4 anni fa·0 comments

Hiring for Systems Engineers

tryfractal.notion.site
2 points·by pnoel·5 anni fa·0 comments

comments

pnoel
·3 anni fa·discuss
Must be some dirty ETL pipelines :')
pnoel
·3 anni fa·discuss
Yes it does :)
pnoel
·3 anni fa·discuss
That's a nice diagram! Yeah that's roughly it. We'll be adding support for more sources of truth in the future to expand coverage, like the ones you mention but also NoSQL like MongoDB
pnoel
·3 anni fa·discuss
Good question -- the primary difference is the method of integration with Postgres. ZomboDB is a Postgres extension, which limits their compatibility with Postgres serivces like AWS RDS, while Retake is compatible with any service where you can enable logical replication
pnoel
·3 anni fa·discuss
* If the “real-time server” goes offline temporarily, will it catch up on any newly added rows in the interim?

Yes, we're built on top of Kafka

* Do you intend to emit any OpenTelemetry metrics? I’d like to monitor lag in production.

We don't have that yet, but open to it

* Will I be able to deploy this as a single container on ECS/Kubernetes?

Yes
pnoel
·3 anni fa·discuss
In December 2022, we shut down Whist after ~3 years. For those who didn't know us, we were a Mighty competitor, building a cloud-streamed browser.

I spent a long time reflecting on what happened, our successes and mistakes, and compiled them in a post-mortem. A few people close to me read it and some found it insightful, so I figured I'd share it with the wider community.

A story on hard-learned lessons that feel obvious in hindsight. Here's to hoping my mistakes can save you some!
pnoel
·4 anni fa·discuss
Whether you have 1 cloud tab or 100 cloud tabs, the resource utilization on your machine will be the same. If you open more local tabs, though, those will take up RAM/CPU on your machine.
pnoel
·4 anni fa·discuss
Charging a subscription fee is the primary way for which we would pay for cloud compute time -- but we're thinking there will be a version of Whist which will have very limited amount of compute time and be free (a sort of free trial if you will)
pnoel
·4 anni fa·discuss
Noted, we'll keep this in mind as we go forward then
pnoel
·4 anni fa·discuss
You absolutely can!
pnoel
·4 anni fa·discuss
Exciting! We'll be onboarding users on macOS in the second half of July, and Windows will follow in August or September
pnoel
·4 anni fa·discuss
We haven't implemented what you describe yet, but we've verified that basic accessibility support works for the Whist browser. We'll be making sure that Chrome's accessibility support is fully covered on Whist cloud tabs before general availability
pnoel
·4 anni fa·discuss
We'll look into it, our team cares heavily about privacy and if we judge that this is a valuable way to protect our users we will definitely implement it
pnoel
·4 anni fa·discuss
The basic version of Whist (with limited cloud tabs usage), will be free, forever.

For full cloud tabs support, we'll be charging a subscription fee as an add-on on top of the browser. We're still figuring out exactly what the pricing tiers will be, but we expect it to be in the 10-15$ range.
pnoel
·4 anni fa·discuss
Potentially! We could make this happen, it probably wouldn't even be that much work. It's more of a question of whether enough people/companies would be interested in self-hosting, which is something we'll keep an eye out for
pnoel
·4 anni fa·discuss
The Whist privacy guarantee is that we've engineered our system so that no one, not even us, can see what's going on in your cloud tabs. We'll be releasing a blog post about how our system is engineered, stay tuned!

Privacy is also one of the reasons we've decided on the hybrid approach. Websites with sensitive information (your bank, etc.) can be used on local, incognito, or Tor tabs, all of which are not offloaded to Whist's servers and run 100% locally.
pnoel
·4 anni fa·discuss
Whist and Mighty are similar in that they are browsers that offer cloud-offloading.

Whist differs by being built in a native browser on your computer, rather than being fully offloaded to the cloud, and supports both local and cloud tabs (so that you can adapt your workflow based on which web apps you are using, how strong your Internet is, etc.)

For more details on the exact differences with Mighty and with other browsers, we have a comparison chart on our website
pnoel
·4 anni fa·discuss
If you are on macOS, you'll get access to Whist in the second half of July. If you're on Windows, it will likely be in August or September :)
pnoel
·4 anni fa·discuss
Yes! Whist will support all native Chrome features like history sync-ing :)
pnoel
·5 anni fa·discuss
Whist | Systems Engineer, Performance Engineer | NYC/Remote Full-time/Fixed-Term (i.e. 6mo) |

https://www.whist.com/ Whist is building the world's fastest browser by streaming it from the cloud. Load pages instantly. Use 10x less memory. Enjoy complete privacy. Whist is a supercharged version of Chrome that runs in the cloud.

Jobs page: https://whisthq.notion.site/Whist-Job-Board-a39b64712f094c77...