lihaoyi

9 ms·

121.
by lihaoyi 2y ago
Even if you break up a codebase, you need selective testing. Let's say you have 100 small repos, and make a change to one. How confident are you in the changed repo's test suite that you can guarantee there are no bugs that will a
122.
Faster CI with Selective Testing(mill-build.org)
1 points by lihaoyi 2y ago|0 comments
123.
Faster CI with Selective Testing(mill-build.org)
3 points by lihaoyi 2y ago|0 comments
124.
Faster CI with Selective Testing(mill-build.org)
45 points by lihaoyi 2y ago|49 comments
125.
by lihaoyi 2y ago
Last time I posted this 7 years ago I wrote > Note that while Mill's first target is Scala builds (as an alternative to SBT) there isn't much reason why Mill shouldn't be usable for other JVM/non-JVM languages too. No
126.
Faster CI with Selective Testing(mill-build.org)
2 points by lihaoyi 2y ago|0 comments
127.
Understanding Selective Testing(mill-build.org)
1 points by lihaoyi 2y ago|0 comments
128.
Why use a monorepo build tool?(mill-build.org)
1 points by lihaoyi 2y ago|0 comments
129.
by lihaoyi 2y ago
In contrast, my Metascala JVM ( https://github.com/lihaoyi/Metascala ) is indeed metacircular, and can interpret itself 1 and 2 layers deep (each layer 100x slower than the layer before!)
130.
Why use a monorepo build tool?(mill-build.org)
1 points by lihaoyi 2y ago|0 comments
131.
Why use a monorepo build tool?(mill-build.org)
9 points by lihaoyi 2y ago|1 comments
132.
Why Does the Mill Build Tool Use Scala?(mill-build.org)
4 points by lihaoyi 2y ago|0 comments
133.
by lihaoyi 2y ago
Not quite 500$/month, but my book https://www.handsonscala.com/ is still making 300-400/month 4.5 years after releasing it. Not a lot of money compared to silicon valley FAANG salaries, especially given the amount
134.
by lihaoyi 2y ago
I don't doubt your experience, I can only provide mine. I've seen one rollout from the inside (~1000 engineers), performed one rollout myself (100-1000 engineers), and talked to ~10 other companies trying to do their own rollouts
135.
by lihaoyi 2y ago
Empirically speaking, unless you are already a Bazel expert or are lucky enough to hire one, most orgs I've seen need at least 3-5 full-time engineers to become experts in Bazel and about ~1 person decade of engineering to roll it out
136.
by lihaoyi 2y ago
Bazel does a lot of non-obvious things that other build tools don't, that become important in larger codebases (100-10,000 active developers): - Automatic caching of everything. In most build tools, caching is opt in, so the core build
137.
by lihaoyi 2y ago
Starlark is definitely a mixed experience IMO, from my 7 years working with it in Bazel On one hand, having a "hermetic" subset of Python is nice. You can be sure your Bazel starlark codebase isn't going to be making network
138.
by lihaoyi 2y ago
ScalaRx and Scalatags actually works a lot like React.js, in user-facing experience even if not in implementation. Unfortunately I was just a college kid and couldn't push it the same way the pros at Facebook could push react!
139.
by lihaoyi 2y ago
The basic idea is if you have n ways your page can display, with the old PHP/CGI whole page refresh model you needed to write n endpoints, but every interaction required a slow and disruptive whole page refresh With pre-react single pa
140.
by lihaoyi 2y ago
We've been doing the O(n) thing forever with PHP and CGI since 1995, the issue is that it required constant whole-page reloads and was a poor experience that got worse the more interactive your webapps got. React let you do the same th
141.
by lihaoyi 2y ago
The fundamental magic of react is that it lets you write code that renders O(n) UI states in a functional manner (i.e. by returning the HTML you want) rather than O(n^2) UI state transitions in a mutable manner (by mutating the page via nes
142.
by lihaoyi 2y ago
All this is actually covered in the article > These benchmarks were run ad-hoc on my laptop, an M1 10-core Macbook Pro, with OpenJDK Corretto 17.0.6. The numbers would differ on different Java versions, hardware, operating systems, and f
143.
by lihaoyi 2y ago
Notably, the benchmarks I provide are all single-core. You can get more if you modularize the project and spread out the load over multiple cores, and some of the other pages linked from the OP go into more detail
144.
by lihaoyi 2y ago
I don't think anyone checks their artifact signatures. I've changed signatures several times over the past few years (every time I get a new laptop I forget to copy over my keys) and haven't heard a peep from anyone using my
145.
by lihaoyi 2y ago
Don't worry, I wrote this article about Java but my day-to-day work is Scala. We're lucky if we can crack 4,000 lines-per-second-per-core on my pretty vanilla Scala projects x_x
146.
by lihaoyi 2y ago
The benchmarks in the article do use the Gradle daemon, but not the Maven one, mostly because mvnd isn't the default. For Gradle, if you turn off the gradle daemon, it gets even slower than the numbers presented going from 4+ seconds t
147.
by lihaoyi 2y ago
Author here, hope people find this article interesting!
148.
How Fast Does Java Compile?(mill-build.org)
4 points by lihaoyi 2y ago|3 comments
149.
How Fast Does Java Compile?(mill-build.org)
2 points by lihaoyi 2y ago|0 comments
150.
by lihaoyi 2y ago
I went and dug up the original code that caused an issue. Here it is: https://github.com/python/cpython/blob/v2.7.1/Lib/cgi.py#L60... Python's std lib `cgi.FieldStorage` object was falsy if it

More ›