barteo
Joined 9 years ago
Karma
1
Submissions
4
Member since
Jan 31
Recent submissions
Comment · 1 hour ago
Comment · 4 years ago
Hi HN,
For a long time, we had been annoyed by the constant stream of commercial results when using search engines and we felt we are going deeper and deeper into the information bubble. We came up with the idea to take the search results from multiple sources to reduce the influence of the single company on what we see in the responses. This is how onBroom was born, currently it is still in beta.
How does it work? Whenever you make a query in your favourite search engine, onBroom extension runs the same search in multiple search engines. Then, it analyses received results by identifying the wage of each returned link to page, taking into account: - number of search engines that returned it - its position in every search engine
And finally, it gives you merged and filtered results presented in the overlay sidebar.
For now we use 4 most common search engines (Google, Bing, Yahoo and DuckDuckGo), but we plan to add more sources soon. Also we wan’t quickly to support other browsers too.
Any feedback appreciated.
Why I built it: most Kotlin tools, like linters, KSP and the language server, are built on kotlinc's frontend, so they're only as fast as it is. A fast frontend could make room for:
- Linters that run in milliseconds instead of seconds
- A fast language server
- Much faster KSP annotation processing
- Quicker builds in CI, where every run starts a cold JVM
- Fast feedback for coding agents, which compile and fix code in a loop many times per task
I measured big gains in both speed and memory against kotlinc 2.4.21, running warm as in the Gradle daemon:
- kotlinx-coroutines-core: 2.50 s → 159 ms (16x)
- Ktor core modules: 2.32 s → 226 ms (10x)
- kotlinpoet: 1.23 s → 97 ms (13x)
- Memory: ~1 GB → ~100 MB
What it doesn't do yet:
- A few language features aren't supported
- No warnings, and only the errors that type checking finds, so some invalid code compiles
- JVM only, no Gradle plugin or IDE support
- Passes 95% of kotlinc's box tests
It's a prototype, but I plan to keep working on it until it's useful for a wide range of real projects.
Benchmark details and how to repeat them: https://github.com/barteo/kotlin-compiler-go/blob/main/docs/...