Farm: Fast vite compatible build tool written in Rust

So, I decided to try this for a real-world project and compare the results. This is for a full production build with no cache, taking the best of three runs each.<p>Vite:<p><pre><code> 2166 modules transformed. built in 28.21s </code></pre> Farm:<p><pre><code> [ Farm ] Build completed in 13350ms FULL EXTREME! Resources emitted to .&#x2F;dist. [ Farm ] Public directory resources copied successfully. </code></pre> So that is 28.21s vs. 13.35s, or a 53% decrease in build times. This is certainly neat, but I&#x27;m not sure whether it is worth the dependency on a new player.

I have mixed feelings about this project. It appears the author primarily aimed to rewrite Vite in Rust and then found justifications for doing so. From my experience, Vite is already sufficiently fast for most needs. Adopting a new and potentially unstable project for marginal performance improvements doesn&#x27;t seem justifiable.

Serious question: does anyone here work for a BigCo who uses Chinese software like this in production? Do your InfoSec teams sign off on it?<p>What&#x27;s the risk of downloading what&#x27;s supposed to be a release binary of this off GitHub, where the release binary includes something nefarious not found in the open codebase, that steals your company&#x27;s source code when you use it to compile?<p>In today&#x27;s geopolitical climate, how does anyone trust non-Western projects?

So, we have rspack, turbopack and now Farm, all written in Rust.<p>There is also Vite, of course , which is already quite fast and very popular.<p>What&#x27;s the differentiator between those?

Why aren’t we comparing to ESBuild?

I love how they compare the loading times by making the bars in the graph render as slowly as their benchmark measurement. Really delivers the message why the faster compilation time is worth it, instead of just showing a static graph with numbers.

Note in the benchmark, it is comparing a React JSX project using @vitejs&#x2F;plugin-react (Babel based) instead of @vitejs&#x2F;plugin-react-swc (SWC based).<p>I made the exact same point two years ago when Turbopack came up with a similar benchmark: <a href="https:&#x2F;&#x2F;github.com&#x2F;yyx990803&#x2F;vite-vs-next-turbo-hmr&#x2F;discussions&#x2F;8">https:&#x2F;&#x2F;github.com&#x2F;yyx990803&#x2F;vite-vs-next-turbo-hmr&#x2F;discussi...</a><p>The point is if we want to compare bundler performance, we should keep all the non-architectural variables consistent across all implementations. Otherwise we are not comparing apples to apples.<p>PR submitted to update the benchmark: <a href="https:&#x2F;&#x2F;github.com&#x2F;farm-fe&#x2F;performance-compare&#x2F;pull&#x2F;11">https:&#x2F;&#x2F;github.com&#x2F;farm-fe&#x2F;performance-compare&#x2F;pull&#x2F;11</a>

A WeChat link under &quot;community&quot;.<p>Without wanting to make this specifically anti-chinese, I really wonder whether that makes it better or worse than only having the Discord link.<p>I find Discord as a community platform already quite questionable. Now add to that the simple fact of fragmenting your community into two... I&#x27;m not convinced.

I’ll have to look at this over the weekend. I’m very excited to see improvements in dev UX in the JS ecosystem. I’d have a very hard time adopting this in prod tho, being so new.<p>Are any large projects using it? Corporation sponsors?

For the current farm, in order to be more compatible with the front-end ecosystem, we have chosen to be compatible with the vite hook and options. But in fact, the biggest performance problem lies in the communication problem between js and rust. For example, if a vite plug-in uses a hook to obtain the entire resource pot, the entire communication will consume more than 10 times the time, so the future path of farm should be if we Avoid these problems and create farm rust plugins

I would love to use it as a test but there is too much of a commitment in that it is not a drop in replacement for vite nor is there anything in the way of a doc or help for &quot;migrate from vite to farm&quot;.<p>I stopped at &quot;create&quot; - I rather &quot;install and convert&quot; in a branch to try stuff out.

Where does money come from in Farm Inc.?

&gt; This page crashed. &gt; &gt; Error creating WebGL context.<p>I&#x27;m sorry, but WebGL probably shouldnt be a requirement for your front page to display any content at all. I disable it for privacy hardening and switch browsers to opt-in. Additionally, low-power clients may struggle with rendering and sink battery in mobile devices.<p>The docs work fine, if anyone else runs into this and wants to read about the project.<p><a href="https:&#x2F;&#x2F;www.farmfe.org&#x2F;docs&#x2F;why-farm" rel="nofollow">https:&#x2F;&#x2F;www.farmfe.org&#x2F;docs&#x2F;why-farm</a>

Is it like a drop in replacement? I’m working with a semi-legacy codebase that takes over a minute to compile and copy with YALC, so if this can squash that time to something more reasonable I’ll be extremely happy.

The scrolling is jumping around like crazy on iOS

Do I need a different npm package for this on ARM Macs vs my colleagues on Windows boxes?

Can someone with expertise in frontend development help me understand the proliferation of similar tools in the field?<p>What specific optimizations do these tools offer that others can&#x27;t, and why can&#x27;t the slower tools simply adopt these optimizations in future updates?<p>Is this a result of a lack of consensus within the community, leading to the creation of new forked tools, or is there a larger strategic context that I&#x27;m missing?

Is it copyrighted to a fake company? I&#x27;m not seeing a &quot;Farm, Inc&quot; in EDGAR search.

Any tool that wants to replace esbuild for me will have to write as good, or better, release notes. The cost of broken tooling and bad change logs (in other words, bad versions) are many orders of magnitude more expensive than the cost of staying on esbuild.

It looks promising, just a side a note: pink on white background was really hard to read, especially on phone screens.

idk if its just me but their website is falling apart on mobile

I would rather have V8 JIT improvements and code caches, than the whole RIIR.<p>Maybe instead of using nodejs, use Go, Spring, Quarkus, Micronaut, ASP.NET, Axiom...