826 karma · joined April 7, 2011
If the company is doing well, this can be the best time, because your stock will immediately appreciate significantly.
This would allow a syntax more familiar to users of JavaScript, where fields with their default value can be omitted:
struct Person {
name: String,
email: Option<String> = None,
}
let person = Person {
name: "John Doe".to_owned(),
..
};https://github.com/moby/moby/issues/2259
This has made it impossible to use docker in scripts where root access is not available. Thank you podman!
This allows us to:
* Share code with our server written in Rust.
* Avoid keeping types in TypeScript in sync with Rust.
* Do server rendering without including a JavaScript runtime.
* Avoid maintaining a JS stack, including TypeScript, Prettier, ESLint, and a bundler.
Because we split our project into many crates, incremental build times are about 1-2 seconds on a linux desktop. This is not as convenient for quick iteration on UI/UX as hot reload with React, but on the other hand, code that type checks is more likely to run correctly.
Overall, I would say that the trade offs are not clear, even for our unique case where we have a server written in Rust.
I am hopeful that in the future, browsers will enable native DOM access from WASM, and the Rust compiler will support code splitting between multiple WASM entrypoints. When this happens, I think there will be a strong case to recommend Rust for more front end projects.
`tangram train --file data.csv --target price --date date`
This would predict the "price" column, using the date in the "date" column.
Internally, we can generate features from the date column like "hour of day", "day of week", "season", etc. that can help the model learn periodic patterns.
Thanks for the great suggestion.
David: https://www.linkedin.com/in/david-yamnitsky Isabella: https://www.linkedin.com/in/isabella-tromba/
I promise we exist and are real humans! But that is exactly what the aliens would say.
Over the past few months we have been working with a handful of early users. A team at a small company had a TensorFlow model deployed as a Flask service consumed by their Elixir app. They replaced it with a Tangram model because they didn't want to maintain a server separate from their monolith. A team of front end engineers at a large company was looking for a way to to train and deploy models on their own, without the overhead of involving their data scientists, machine learning engineers, or backend engineers. They trained a model on their own and embedded it directly in their React front-end with the Tangram JavaScript library that makes predictions with WebAssembly.
Tangram is written entirely in Rust, from the core machine learning algorithms, to the bindings for each language, to the front and back end of the web application. We have benefited from Rust's fast performance, strong typing, convenient tooling, and high quality libraries (serde, tokio, hyper, sqlx, and more).
We hope to make Tangram a sustainable business with the open core business model. The CLI and language libraries are MIT licensed, while the web application is source available, free to use for testing, but requires a paid license to use in production.
We would love to hear your feedback. Give it a try and let us know what you think!
Next.js Live seems very impressive, but this marketing line is scaring me off. It’s hard to imagine that running your app in webassembly within the browser has a measurable reduction in latency vs running on localhost. If anything, I would expect it to be slightly higher because of the overhead of interpreting/compiling wasm, and the slight performance hit of wasm vs native code.