pidove | babashka | |
---|---|---|
9 | 117 | |
46 | 3,865 | |
- | 2.1% | |
0.0 | 9.2 | |
almost 2 years ago | 5 days ago | |
Java | Clojure | |
MIT License | Eclipse Public License 1.0 |
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.
pidove
-
Java JEP 461: Stream Gatherers
Streams is too complex for what it does and it doesn’t even parallelize well. Here is something that does roughly the same thing but I think is way better
See https://github.com/paulhoule/pidove
https://central.sonatype.com/artifact/com.ontology2/pidove
-
Java 21: The Nice, the Meh, and the Momentous
(1) It's a bit of a bad smell (which he points out) that records aren't being used much at all in the Java stdlib, I wrote something that built out stubs for the 17 and 18 stdlibs and that stood out like a sore thumb. I do like using records though.
(2) I've looked at other ways to extend the collections API and related things, see
https://github.com/paulhoule/pidove
and I think the sequenced collections could have been done better.
(3) Virtual Threads are kinda cool but overrated. Real Threads in Java are already one of the wonders of the web and perform really well for most applications. The cases where Virtual Threads are really a win will be unusual but probably important for somebody. It's a good thing it sticks to the threads API as well as it did because I know in the next five years I'm going to find some case where somebody used Virtual Threads because they thought it was cool and I'll have to switch to Real Threads but won't have a hard time doing so.
-
Ask HN: What problems do Generators solve in Java?
I think that guy just made up a generator class for fun. It’s not too different from the integrator except it doesn’t have a hasNext() method so it either returns results forever or it has to return a sentinel value like null or return an exception to end iteration.
Somebody could make the case that returning a sentinel value or an exception is a better API since there is no risk somebody else is going to call the next() method after you call hasNext() and next(). Writing a generator that wraps a generator is a little simpler than writing an interest or that wraps an iteration because you don’t have to write a hasNext() function, which can occasionally be awkward.
That generator library has a few functions, like map that work on generators, unfortunately the Java stdlib doesn’t come with anything like that. (There is the streams API but it is over-complicated.)
I’ll point out this library I wrote
https://github.com/paulhoule/pidove
which does a lot of what the Steams library does but it works on iterators without creating streams. If you like those generator examples you might like pidove.
As for Python it is kinda accidental that generators would up related to coroutines, that is, generators were an easy way to implement coroutines, later async/await and stuff like that got added.
-
Overinspired?
I find this alien to my point of view. On the other hand, my side projects aren't driven by FOMO but are more like the "special interests" of autistic people.
Most of the time I have three side projects going on, maybe two of which are really getting the attention they deserve and one that is languishing. (See my profile to see about my current three.) Occasionally I get inspired to spend 1-4 weekends on some sudden inspiration, of which
https://github.com/paulhoule/pidove
came to completion but
https://github.com/paulhoule/ferocity
probably won't. The project I'm working the hardest on now is something that I was baffled that it didn't exist 18 years ago but felt compelled to do something out because of the Twitterinsanity last December and it turned out the technological conditions right now make it the perfect time to work on.
-
JDK 20 and JDK 21: What We Know So Far
When I saw sequenced collections earlier I didn’t like the design but I completely approve of the latest revision. One nice thing about the process they use to develop Java is that they really do work and rework new features to make them great.
I just wish that instead of Streams they’d made something more like
https://github.com/paulhoule/pidove
-
I love building a startup in Rust. I wouldn't pick it again
... or you can just use a sane FP library like
https://github.com/paulhoule/pidove
Some people don't like the Lispy signatures so I did start coding up a version with with a fluent interface but didn't quite finish.
-
“I've never heard anyone say that they loved Java” (2001)
Inner classes are pretty useful.
This library contains a huge number of Iterables, each of which has at least one Iterator implementation.
https://github.com/paulhoule/pidove
It is convenient to let the Iterator be immutable and the Iterator be an inner class that gets its configuration information out of the Iterable.
(That said, if people really thought seriously about Iterator being a Supplier people might think more rationally about error handling. Also in a slightly parallel universe the Iterator would only have one method since remove() hardly ever gets used and having both hasNext() and next() methods is asking for bugs.)
- Show HN: Pidove, an Alternative to the Java Streams API
-
Ask HN: Working Offline for 8 Hours?
If you were programming in Python or many other languages you could download documentation locally.
In both Python and Java doing a mini-project I frequently challenge myself to only use the standard library. It's good for practicing HackerRank-rank style programming (the fun of single-file Java)
When I am waiting for builds I sometimes hack on this
https://github.com/paulhoule/pidove
because I don't really like the Streams API and want to perfect my mastery of generics and internal DSLs.
Now that I think of it, standard-library only for node seems like a good challenge for me because I code a lot of front-end Javascript but just barely know the node API.
babashka
-
A Tour of Lisps
It also gives you access to Babashka if you want Clojure for other use-cases where start-up time is an issue
https://babashka.org/
- Babashka: Fast native Clojure scripting runtime
-
What's the value proposition of meta circular interpreters?
I've tried researching this myself and can't find too much. There's this project metaes which is an mci for JS, and there's the SCI module of the Clojure babashka project, but that's about it. I also saw Triska's video on mci but it was pretty theoretical.
-
Adding Dependencies on Clojure Project the Node Way: A Small Intro to neil CLI
Created by the same guy who created babashka which is a way to write bash scripts, node scripts, and even apple scripts using Clojure. A very proficient and influential developer in the Clojure community. This is how borkduke's neil helps us:
- Babashka
-
Pure Bash Bible
Not what you asked for but there is Babashka for scripting in Clojure.
https://github.com/babashka/babashka
-
Critique of Lazy Sequences in Clojure
Clojure's lazy sequences by default are wonderful ergonomically, but it provides many ways to use strict evaluation if you want to. They aren't really a hassle either. I've been doing Clojure for the last few years and have a few grievances, but overall it's the most coherent, well thought out language I've used and I can't recommend it enough.
There is the issue of startup time with the JVM, but you can also do AOT compilation now so that really isn't a problem. Here are some other cool projects to look at if you're interested:
Malli: https://github.com/metosin/malli
Babashka: https://github.com/babashka/babashka
Clerk: https://github.com/nextjournal/clerk
-
Sharpscript: Lisp for Scripting
Being a Clojure addict, I guess I have to leave the obligatory link to Babashka too then: https://github.com/babashka/babashka (Native, fast starting Clojure interpreter for scripting)
-
Rash – The Reckless Racket Shell
which is now on hiatus. babashka: https://babashka.org
-
Are there any languages (that are in common use in companies) and higher-level that give you the same feeling of simplicity and standardization as C?
I've enjoyed babashka for scripting; which is close enough to clojure to allow using some/many libraries; but (probably) not for embedding.
What are some alternatives?
proposal-explicit-resource-management - ECMAScript Explicit Resource Management
janet - A dynamic language and bytecode vm
Reactive Streams - Reactive Streams Specification for the JVM
malli - High-performance data-driven data specification library for Clojure/Script.
project-loom-c5m - Experiment to achieve 5 million persistent connections with Project Loom virtual threads
joker - Small Clojure interpreter, linter and formatter.
ferocity - Write Java expression trees, statements, methods and classes with a LISP-like internal DSL
nbb - Scripting in Clojure on Node.js using SCI
Newt - Autogenerate a .Net (C#/EF Core) data project (class library with entities and data contexts) from a Postgres database, plus Graphviz and SQL.
clojure-lsp - Clojure & ClojureScript Language Server (LSP) implementation
gophercon22-parser-combinators - Simple parser combinator package as shown at GopherCon 2022
racket - The Racket repository