HNHacker News
TopNewBestAskShowJobs

nitsky

826 karma · joined April 7, 2011

submissionscomments
nitsky··on Stanford gets $1.1B for new climate school from John Doerr
Is investing in a university endowment the best way to put $1.1B to work combating climate change? How about investing in companies developing clean energy technologies?
nitsky··on Tailscale raises $100M
I'm a huge fan of Tailscale and the team I work with uses it daily, for free, to connect to our servers and each other's computers. Thanks!
nitsky··on The great VC pullback of 2022
> The worst time to join a company is when they say they are working on a funding round.

If the company is doing well, this can be the best time, because your stock will immediately appreciate significantly.

nitsky··on Deno in 2021
Then it would be fair to say ts-node is a typescript runtime, while node is a javascript runtime.
nitsky··on The Curse of NixOS
No, using flakes still requires enabling the “experimental feature”. The difference in 2.4 is that you no longer need to use a prerelease version of Nix to have the experimental feature available.
nitsky··on Mold 1.0: the first stable and production-ready release of the high-speed linker
I have been using mold every day for almost a year, and it has dramatically improved my quality of life by decreasing link times on the Rust project I work on from approximately 10 seconds to less than one second. This makes a big difference in keeping focus during the edit-compile-run loop. Thank you!
nitsky··on Rust 1.57
Hooray, custom profiles are now stable! This helps avoid rebuilds when toggling LTO and changing optimization levels.
nitsky··on Builder Pattern in Rust
I hope that one day the default struct field values RFC will be reconsidered: https://github.com/rust-lang/rfcs/pull/1806.

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(),
    ..
  };
nitsky··on Podman in Linux
I love podman. When you write a file to a volume from a container, the user that spawned the container is the owner. This is exactly what you expect, but with docker, everything is written as root. After many years, this has not been fixed:

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!

nitsky··on Seed – A Rust front-end framework for creating fast and reliable web apps
ts-rs did not exist at the time. Perhaps if it did, we would have chosen differently. Generating types with “cargo test” feels very hacky though.
nitsky··on Seed – A Rust front-end framework for creating fast and reliable web apps
I should add that we wrote a crate called pinwheel that uses futures-signals for fine-grained reactivity, uses the builder pattern to avoid macros entirely, and supports server rendering:

https://github.com/tangramdotdev/pinwheel

nitsky··on Seed – A Rust front-end framework for creating fast and reliable web apps
We chose to use Rust instead of TypeScript for the front end of https://github.com/tangramdotdev/tangram.

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.

nitsky··on Tailscale free for open source projects
Really impressive to see Tailscale employees recommending free alternatives to their own service!
nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
We definitely will be interested in adding converters to/from other formats.
nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
Thanks for the kind comment. We spent a lot of time trying to make the website feel hacker friendly, so programmers know that tangram is not made only for someone with a PhD.
nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
Unfortunately, tangram does not help here, it just adds yet another format to the list. The reason it needs its own format is because .tangram files include all the model reporting information that shows up in the web application.
nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
Yes! What we have in mind is this:

`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.

nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
You're right, CLI vs RStudio or IPython is not a big improvement. The real benefit here is that you can use your model from Go, JavaScript, Ruby, and other languages without having to include the Python or R ecosystems in your tech stack.
nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
Awesome, please let us know where you write them, we would love to read it!
nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
Thanks! At the moment, we do not have any ability to convert to/from scikit, but this is definitely something we would like to consider in the future. This would give users of scikit the ability to make predictions in production from their preferred language, and access to tangram's reporting and monitoring app.
nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
Hey, you are right, we should definitely add an "about" page to our site. In the mean time...

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.

nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
Great idea! We definitely want to do this. We have an open issue to track it: https://github.com/tangramdotdev/tangram/issues/28.
nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
There are a lot of similarities with vowpal-wabbit. The biggest difference is that tangram has libraries for a lot of popular languages (js, go, ruby, elixir, etc.), and has a web application for learning about your model and monitoring it in production.
nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
Cool! Let us know how it works for you, and open an issue on GitHub if you run into any trouble!
nitsky··on Show HN: Tangram – Train a model from a CSV file on the command line
Hi HN! We are Isabella and David, and we're excited to share Tangram, our attempt to make ML easy for programmers who are not experts. With Tangram, you train a model from a CSV file on the command line, use your model from one of many languages (so far we have libraries for Elixir, Go, JavaScript, Python, Ruby, and Rust), and learn about your models and monitor them in production from a web app. There's a video on our homepage (https://www.tangram.dev) and we're on GitHub at https://github.com/tangramdotdev/tangram.

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!

nitsky··on The Framework Laptop is now shipping
Are you considering OLED as well? The Dell XPS has that as an option and it is a serious draw, especially for coders who stare at a mostly-black screen all day.
nitsky··on The Framework Laptop is now shipping
My framework DIY edition is arriving tomorrow. I’m so excited! I’ll be loading NixOS on it. :)
nitsky··on Ask HN: What was your best passive income in 2020?
These days, with stock buybacks, a portion of stock price increases are actually dividends.
nitsky··on Next.js Live: Code in the Browser with ESM, ServiceWorkers, Replicache, and WASM
I understand, but it is not obvious this provides a performance benefit which outweighs the potentials slowdowns I mentioned above. I am concerned about the trend of JavaScript tools advertising how they are “blazing fast” without any benchmarks or serious technical analysis.
nitsky··on Next.js Live: Code in the Browser with ESM, ServiceWorkers, Replicache, and WASM
> Faster than local dev: Because it runs entirely within the browser, server responses have less latency than localhost.

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.

← PreviousPage 2 of 5Next →