component
Graal
component | Graal | |
---|---|---|
13 | 156 | |
2,068 | 19,807 | |
0.0% | 0.5% | |
0.0 | 10.0 | |
about 2 years ago | 2 days ago | |
Clojure | Java | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
component
-
A History of Clojure (2020) [pdf]
* Lifecycle management: Mount, Integrant or Component (https://github.com/tolitius/mount https://github.com/weavejester/integrant and https://github.com/stuartsierra/component)
-
Generic functions, a newbie question
When you start to have multiple stateful components (the database, the HTTP server, your Redis connection, a page cache, etc.), then you'll want to use a library like component that manages their (inter-)dependencies and provides a consistent notion of lifecycle.
- What makes Clojure better than X for you?
- Clojure needs a Rails, but not for the reason you think
-
[ANN] Reveal Pro 1.3.308 — sticker windows for system libraries (component, integrant, mount)
Today I released a new version of Reveal Pro — dev.vlaaad/reveal-pro {:mvn/version "1.3.308"} — that adds sticker integration for system libraries such as mount, component and integrant!
-
Printf(“%s %s”, dependency, injection)
I agree with the main sentiment from the article. Although I do think they are discussing Inversion of control more-so than dependency injection.
One of my first languages was .net and I was never able to really understand DI in that context that well.
Actually using javascript and ducktyping made me understand what it actually was.
I remember a .net job interview where I had to write a micro-service and opted to construct the dependency graph in the main function initialising "all" the classes there. Instead of discussing the pro's and con's of that approach they berated me for not using a DI framework (No I did not land that job, but in hindsight it was the most expensive job interview I've ever had. The room was filled with 8 developers going over my code).
The main thing the article glosses over is state. something people with a functional background hide from. But if you look at something like the httpclient in .net. I think it took the .net world like 10 years to start using the httpclient properly. Scope and lifetime of those kind of objects are important. managing connection pools, retry state, throttling or the incoming http request. DI does make that kind of thing easieR (I'm not saying it makes it better)
Look at clojure's component(https://github.com/stuartsierra/component), I'm not a clojure expert by far. But it is kinda DI/IOC in a functional language.
In closing we can agree that it is underused in the right places and overused in the wrong ones.
- Forcing engineers to release by some arbitrary date results in shipping unfinished code - instead, ship when the code is ready and actually valuable
-
How to pass components across functions
https://github.com/stuartsierra/component#no-function-should-take-the-entire-system-as-an-argument
-
There are a *lot* of actor framework projects on Cargo.
Yeah like I mentioned I'm not like super sold on the everything-should-be-an-actor paradigm, but I find value in DDD + a light implementation of Components (similar to stuartsierra/component).
-
Essential libraries?
https://github.com/stuartsierra/component for managing components lifecycles in projects
Graal
-
Java 23: The New Features Are Officially Announced
Contrary to what vocal Kotlin advocates might believe, Kotlin only matters on Android, and that is thanks to Google pushing it no matter what.
https://spectrum.ieee.org/the-top-programming-languages-2023
https://snyk.io/reports/jvm-ecosystem-report-2021/
And even so, they had to conceed Android and Kotlin on their own, without the Java ecosystem aren't really much useful, thus ART is now updatable via Play Store, and currently supports OpenJDK 17 LTS on Android 12 and later devices.
As for your question regarding numbers, mostly Java 74.6%, C++ 13.7%, on the OpenJDK, other JVM implementations differ, e.g. GraalVM is mostly Java 91.8%, C 3.6%.
https://github.com/openjdk/jdk
https://github.com/oracle/graal
Two examples from many others, https://en.wikipedia.org/wiki/List_of_Java_virtual_machines
- FLaNK Stack 05 Feb 2024
-
Apple releases Pkl – onfiguration as code language
Pkl was built using the GraalVM Truffle framework. So it supports runtime compilation using Futurama Projections. We have been working with Apple on this for a while, and I am quite happy that we can finally read the sources!
https://github.com/oracle/graal/tree/master/truffle
Disclaimer: graalvm dev here.
-
Live Objects All the Way Down: Removing the Barriers Between Apps and VMs
That's pretty interesting. It's not as aggressive as Bee sounds, but the Espresso JVM is somewhat similar in concept. It's a full blown JVM written in Java with all the mod cons, which can either be compiled ahead of time down to memory-efficient native code giving something similar to a JVM written in C++, or run itself as a Java application on top of another JVM. In the latter mode it obviously doesn't achieve top-tier performance, but the advantage is you can easily hack on it using all the regular Java tools, including hotswapping using the debugger.
When run like this, the bytecode interpreter, runtime system and JIT compiler are all regular Java that can be debugged, edited, explored in the IDE, recompiled quickly and so on. Only the GC is provided by the host system. If you compile it to native code, the GC is also written in Java (with some special conventions to allow for convenient direct memory access).
What's most interesting is that Espresso isn't a direct translation of what a classical C++ VM would look like. It's built on the Truffle framework, so the code is extremely high level compared to traditional VM code. Details like how exactly transitions between the interpreter/compiled code happen, how you communicate pointer maps to the GC and so on are all abstracted away. You don't even have to invoke the JIT compiler manually, that's done for you too. The only code Espresso really needs is that which defines the semantics of the Java bytecode language and associated tools like the JDWP debugger protocol.
https://github.com/oracle/graal/tree/master/espresso
This design makes it easy to experiment with new VM features that would be too difficult or expensive to implement otherwise. For example it implements full hotswap capability that lets you arbitrarily redefine code and data on the fly. Espresso can also fully self-host recursively without limit, meaning you can achieve something like what's described in the paper by running Espresso on top of Espresso.
-
Crash report and loading time
I'm also using GraalVM if that's of any help.
-
Quarkus 3.4 - Container-first Java Stack: Install with OpenJDK 21 and Create REST API
Quarkus is one of Java frameworks for microservices development and cloud-native deployment. It is developed as container-first stack and working with GraalVM and HotSpot virtual machines (VM).
-
Level-up your Java Debugging Skills with on-demand Debugging
Apologies, I didn't mean to imply DCEVM went poof, just that I was sad it didn't make it into OpenJDK so one need not do JDK silliness between the production one and the "debugging one" since my experience is that's an absolutely stellar way to produce Heisenbugs
And I'll be straight: Graal scares me 'cause Oracle but I just checked and it looks to the casual observer that it's straight-up GPLv2 now so maybe my fears need revisiting: https://github.com/oracle/graal/blob/vm-23.1.0/LICENSE
-
Rust vs Go: A Hands-On Comparison
> to be compiled to a single executable is a strength that Java does not have
I think this is very outdated claim: https://www.graalvm.org/
- Leveraging Rust in our high-performance Java database
-
Java 21 makes me like Java again
https://github.com/oracle/graal/issues/7182
What are some alternatives?
integrant - Micro-framework for data-driven architecture
Liberica JDK - Free and 100% open source Progressive Java Runtime for modern Java™ deployments supported by a leading OpenJDK contributor
reitit - A fast data-driven routing library for Clojure/Script
Adopt Open JDK - Eclipse Temurin™ build scripts - common across all releases/versions
mount - managing Clojure and ClojureScript app state since (reset)
awesome-wasm-runtimes - A list of webassemby runtimes
ultra - A Leiningen plugin for a superior development environment
SAP Machine - An OpenJDK release maintained and supported by SAP
awesome-clojure - A curated list of awesome Clojure libraries and resources. Inspired by awesome-... stuff
maven-jpackage-template - Sample project illustrating building nice, small cross-platform JavaFX or Swing desktop apps with native installers while still using the standard Maven dependency system.
Luxon - ⏱ A library for working with dates and times in JS
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten