Skip to content

Commit 5bbd932

Browse files
jameswardkoshachyzoobestik
authored
add gsoc-2023-kotlinx-benchmark (#53)
* add gsoc-2023-kotlinx-benchmark Co-authored-by: James Ward <[email protected]> Co-authored-by: Andrey Polyakov <[email protected]> Co-authored-by: Konstantin Chernenko <[email protected]>
1 parent 37c3cee commit 5bbd932

File tree

1 file changed

+39
-0
lines changed
  • src/pages/news/gsoc-2023-kotlinx-benchmark

1 file changed

+39
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
title: "Google Summer of Code 2023 – Enhancing kotlinx-benchmark's API and User Experience"
3+
date: 2024-01-09 10:00
4+
---
5+
6+
The Kotlin Foundation sponsored four projects for the Google Summer of Code 2023, and we are excited to announce the completion of a project to enhance the _kotlinx-benchmark_ library! JetBrains, a Kotlin Foundation member, provided mentoring support for this project.
7+
8+
The contributor to this project was [Henok Woldesenbet](https://github.com/wldeh), an aspiring software engineer and the mentor was Abduqodiri Qurbonzoda, a software developer working on Kotlin libraries at JetBrains. The project aimed to improve the [kotlinx-benchmark](https://github.com/Kotlin/kotlinx-benchmark) library API and user experience.
9+
10+
## Introduction
11+
12+
The _kotlinx-benchmark_ library is an invaluable open-source tool that facilitates the benchmarking of multiplatform code written in Kotlin. Despite its essential function, its user experience had some gaps, confusing users and lacking features that developers have come to expect from benchmarking libraries.
13+
14+
## Goals
15+
16+
The primary goals for the project were:
17+
* Infuse the library with clear and concise documentation, supplemented with practical usage examples. The absence of comprehensive documentation previously made using _kotlinx-benchmark_ challenging for many, especially newcomers.
18+
* Address user concerns and lint the library API, making it more intuitive and user friendly.
19+
* Refine the library's internals, including by enhancing integration tests, improving error feedback through refined validations and task descriptions, and streamlining the profiler's execution process.
20+
* Elevate the overall user experience, transforming the _kotlinx-benchmark_ from a budding tool into a robust library that the Kotlin community can rely on.
21+
22+
## Achievements
23+
24+
Here are the primary achievements made in the Google Summer of Code project:
25+
* **Documentation for increased accessibility**: Detailed documentation was added, ensuring that anyone, from novices to experts, could dive into, experiment with, and harness the power of the library.
26+
* **Improved error messages**: A library's UX is significantly influenced by the quality of its error feedback. Error messages were revamped, ensuring they are not only accurate but also instructive, guiding users towards solutions.
27+
* **Refined integration tests**: Comprehensive integration tests were added to ensure stability across a variety of use cases.
28+
* **Tech stack modernization**: The library was migrated to the latest versions of Gradle and JMH, and transitioned from Groovy DSL to the latest version of Kotlin DSL to optimize the build scripts.
29+
* **Streamlined profiler usage**: In response to feedback from our users, the process of running profilers was simplified, facilitating a smoother user experience.
30+
31+
## Next Steps
32+
33+
To further enhance _kotlinx-benchmark_, we are planning to:
34+
* Support the Android target and integrate the _androidx.benchmark_ framework into _kotlinx-benchmark_.
35+
* Implement an IntelliJ IDEA plugin to support running benchmarks with a click of a run button, the same way as running unit tests.
36+
37+
If you'd like to help continue improving _kotlinx-benchmark_, check out the [open issues](https://github.com/Kotlin/kotlinx-benchmark/issues) for ideas on where to jump in.
38+
39+
Thank you Henok and Abduqodiri for making _kotlinx-benchmark_ even better for Kotlin developers!

0 commit comments

Comments
 (0)