component
preplish
component | preplish | |
---|---|---|
13 | 9 | |
2,068 | 4 | |
0.0% | - | |
0.0 | 5.0 | |
about 2 years ago | 7 months ago | |
Clojure | Perl | |
MIT License | GNU General Public License v3.0 only |
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
preplish
-
Interactive GCC (igcc) is a read-eval-print loop (REPL) for C/C++
> what's wrong with that?
Why nothing at all, of course. A REPL need not be more than a way to test and explore syntax, functions, and logical structures.
> the user experience is REPL-ish and it can help some people learn the _basics_ of the language
PREPLISH exists for Perl ^_^
https://github.com/viviparous/preplish
-
online Perl editor
If this is for testing of syntax or of trivial code, it sounds like a good use-case for running a local REPL. (Example: https://github.com/viviparous/preplish)
-
Not Your Grandfather’s Perl
This is a simple REPL project and the readme lists other Perl REPLs.
https://github.com/viviparous/preplish
Perl's concise syntax makes working in a REPL a pleasure. Python has a REPL but the design of the language makes it expand both in length (for loops) and in width (tabs).
I am a recent convert to working in a REPL first to test programming ideas.
-
Has someone curated Perl data science resources somewhere? I've seen many such collections for other languages. Something like this, but with more modules and what they do:
I made this solution for some of my simple data wrangling: https://github.com/viviparous/preplish
- Is there any good reason not to use perl scripts in place of bash logic?
- Working with __DATA__ sections without Mojolicious
-
Acme-ConspiracyTheory-Random
I tried the module it in a Perl REPL (https://github.com/viviparous/preplish) and got the following ravings that are worthy of a US loony politician:
-
On Repl-Driven Programming
I agree with you that the immediate start-up and feedback is a great benefit to the coder. This is why I dislike complex, Rube-Goldbergian REPL systems.
There is a use-case for a throw-away interaction with a REPL. For example, how does $builtinFuncX work, or how would $data best be imported into a structure?
A REPL can also be a good initial approach to a more ambitious problem. In this case, a REPL can be good for focus and discipline.
If the second case is going to answer your concern and be constructive, it's necessary to be able to build the code for sharing and cleanly export the code for re-use.
I've had success tackling challenges using REPLs for Python and Perl [1] in both ways. But no tooling is going to solve the problem of a sloppy teammate who claims success just because "it compiles" and "it works on my box". A person who knows how to build good tooling goes further.
[1] https://github.com/viviparous/preplish
-
Interactive C++ for Data Science
It is Jupyter is a Rube-Goldbergian nightmare. Python is a memory hog. There are better solutions, to be sure.
A simple REPL is all that's needed to both do A-type and B-type data exploration. (I won't use the term "data scientist", it's an exaggeration in most cases.)
Python has a REPL, R has a REPL, Perl has PDL and both a simple REPL (https://github.com/viviparous/preplish) and a more complex one (https://metacpan.org/pod/Reply).
Jupyter should not be used as an IDE because it is the wrong tool for development. A-type data explorers just want a painless UI and may not care much about the horrible agglutination of incomplete/slow/broken solutions that Jupyter represents.
What are some alternatives?
integrant - Micro-framework for data-driven architecture
xeus-cling - Jupyter kernel for the C++ programming language
reitit - A fast data-driven routing library for Clojure/Script
tinyspec-cling - tiny spectral synthesizer with livecoding support
mount - managing Clojure and ClojureScript app state since (reset)
examples - Fully-working mlpack example programs
ultra - A Leiningen plugin for a superior development environment
transformers - 🤗 Transformers: State-of-the-art Machine Learning for Pytorch, TensorFlow, and JAX.
awesome-clojure - A curated list of awesome Clojure libraries and resources. Inspired by awesome-... stuff
jupyter - An interface to communicate with Jupyter kernels.
Luxon - ⏱ A library for working with dates and times in JS
slimux - SLIME inspired tmux integration plugin for Vim