1. I would argue there are no "real alternatives". The two most proximate alternatives in feature space are Ibis and Snowpark.
- Ibis because while it can target multiple engines (as we state in our docs, we are built on and heavily reliant on Ibis), it aims to be "single engine, single session" in its execution in that nothing is expected to persist beyond the current session and an Ibis expression can only have a single engine. We want to be multi-engine and have some artifacts durable across sessions (by way of caching)
- Snowpark because it is sort of "multi-engine" by way of external functions or python stages, but locked to Snowflake. In some sense, we want to be Anypark: Snowpark like functionality but centered on whatever engine of choice is desired and performant interop with any other engines.
2. We don't have anything I would hold out as benchmarks yet. We don't aim to be "best in class" / the "fastest engine", we aim to be "in class" for as many operations as possible (we use the word performant). Our goal is to make it easy for an org to choose whichever engine(s) they feel most performant in when they consider the full space of {developer,computation} x {time,cost}. However, Hussain has demonstrated how having information from the "whole pipeline" available but execution deferred can allow for specialized optimization by way of predicate pushdowns (https://ibis-project.org/posts/udf-rewriting/)
Thanks for your interest and please feel free challenge any of the above or point us to anything you think we might have overlooked!
Yes, "we" are out of core to the extent that the engines used in the deferred expressions we execute are out-of-core (our "batteries-included" engine is a modified Datafusion).
We have previously demonstrated the capability of doing iterative batch training by way of our "batteries-included" engine. I'll try to post a reference later but need to run now due to family obligations.
A non trivial amount of on boarding is because "this is the most efficient information to ensure these learning agents have as they navigate their environment seeking rewards"
I don't think never worry about it again is quit correct
What if someone registers with my old number?
If someone were to register with your old number on a new phone, then they will have an empty message history. Your contacts will also be made aware of a safety number change if they start messaging with the old number.
I think it is correct that on the surface it is credentials. I also think it is correct that the underlying property is social networks and a particular culture / mindset.
Ultimately, I think the "phonies" need to be addressed directly because I believe they are effectively a cabal.
I also think it requires the broader culture to take active steps to help make this happen: work harder to think about what bad behavior is and take action to avoid / penalize it.
FWIW, I have traveled in the finance / startup circles and kept looking for "better places" but have come to the conclusion that they are few and far between and the issue is the business culture and the broader culture that celebrates it.
Altana is building a shared artificial intelligence platform to help governments, financial institutions, corporations, and logistics providers map and manage global flows of commerce, capital, data, and more. We have built the Altana Trade Knowledge Graph, the world’s most comprehensive representation of global commerce activity. This data asset covers more than 40% of cross-border transactions, corporate ownership registries in over 100 countries, the global movements of goods, illicit web activity, and more. Built on this foundation, our proprietary machine learning technologies and products are designed to help customers manage risk, automate otherwise labor-intensive investigations, and better manage cross-border flows.
Hiring for: Data Scientist, Machine Learning Engineer, Data Engineer
See also: https://altana.ai/careers/
For Machine Learning Engineer or Data Engineer, email dan@altanatech.com
For Data Scientist, email jobs@altanatech.com
Mr. Pottinger later said that the scenario would have involved him representing a victim, settling a case and then representing the victim’s alleged abuser. He said it was within legal boundaries. (He also said he had meant to type “No client lawsuit is actually involved.”)
Such legal arrangements are not unheard-of. Lawyers representing a former Fox News producer who had accused Bill O’Reilly of sexual harassment reached a settlement in which her lawyers agreed to work for Mr. O’Reilly after the dispute. But legal experts generally consider such setups to be unethical because they can create conflicts between the interests of the lawyers and their original clients.
Mr. Pottinger later said that the scenario would have involved him representing a victim, settling a case and then representing the victim’s alleged abuser. He said it was within legal boundaries. (He also said he had meant to type “No client lawsuit is actually involved.”)
Such legal arrangements are not unheard-of. Lawyers representing a former Fox News producer who had accused Bill O’Reilly of sexual harassment reached a settlement in which her lawyers agreed to work for Mr. O’Reilly after the dispute. But legal experts generally consider such setups to be unethical because they can create conflicts between the interests of the lawyers and their original clients.
- Ibis because while it can target multiple engines (as we state in our docs, we are built on and heavily reliant on Ibis), it aims to be "single engine, single session" in its execution in that nothing is expected to persist beyond the current session and an Ibis expression can only have a single engine. We want to be multi-engine and have some artifacts durable across sessions (by way of caching)
- Snowpark because it is sort of "multi-engine" by way of external functions or python stages, but locked to Snowflake. In some sense, we want to be Anypark: Snowpark like functionality but centered on whatever engine of choice is desired and performant interop with any other engines.
2. We don't have anything I would hold out as benchmarks yet. We don't aim to be "best in class" / the "fastest engine", we aim to be "in class" for as many operations as possible (we use the word performant). Our goal is to make it easy for an org to choose whichever engine(s) they feel most performant in when they consider the full space of {developer,computation} x {time,cost}. However, Hussain has demonstrated how having information from the "whole pipeline" available but execution deferred can allow for specialized optimization by way of predicate pushdowns (https://ibis-project.org/posts/udf-rewriting/)
Thanks for your interest and please feel free challenge any of the above or point us to anything you think we might have overlooked!
Best Dan