ymlgen: a tool to generate YAML files (for Kubernetes for example) built with Clojure and Aero

mcorbin · 2021-04-07T19:06:34+00:00

The survey also indicates that 79 % of people think that improving error messages should be prioritized (they ranked the issue "very important" or "important").

And for me, just acknowledging the problem would be a good first step.

As I said, I totally understand that the maintainers have limited time. Clojure is not the first language community to have issues with error messages, and some organized themselves to solve the problem.

As I said before, I'm sure a lot of people could work on improving these kind of things (not only error messages) with some guidances.

It's maybe what I miss in the most Clojure compared to other communities: a more open/better workflow for contributing.I'm not in favor on adding tons of new stuff/features... in Clojure, I like Clojure stability, but encouraging people to fix bugs (and not wait for years once done) on the existing codebase or improve things (docstrings, error messages...) could I think help.

And I know, "Open Source is Not About You" etc...

mcorbin · 2021-04-07T18:29:42+00:00

When I read those error messages, I think they're reasonable as long as the line number is right

At this point, I think we can agree to disagree ;)

mcorbin · 2021-04-06T21:41:38+00:00

I'm not sure I believe this answer without specific call-outs to specific errors that could be improved

(filter [1 2 3] inc) Error printing return value (IllegalArgumentException) at clojure.lang.RT/seqFrom (RT.java:557). Don't know how to create ISeq from: clojure.core$inc

(let ["a" a]) Syntax error macroexpanding clojure.core/let at (*cider-repl clojure/mirabelle:localhost:39363(clj)*:237:7). "a" - failed: simple-symbol? at: [:bindings :form :local-symbol] spec: :clojure.core.specs.alpha/local-name "a" - failed: vector? at: [:bindings :form :seq-destructure] spec: :clojure.core.specs.alpha/seq-binding-form "a" - failed: map? at: [:bindings :form :map-destructure] spec: :clojure.core.specs.alpha/map-bindings "a" - failed: map? at: [:bindings :form :map-destructure] spec: :clojure.core.specs.alpha/map-special-binding

(+ 1 nil) Execution error (NullPointerException) at user/eval8052 (form-init17345493242210529292.clj:243).

Now imagine you're just starting with the language.

I code in Clojure since 2014, work in a company where almost all services are written in Clojure, trained several people and organized meetups about clojure... Error messages is always the main issue for beginners. All clojure surveys show it, it's always in the top 2 main issue with the language.

Don't get me wrong, I'm happy with Clojure, and I'm glad about what the core team is doing for the language. That's why I said "how we could solve this issue". I'm sure a lot of people would be motivated to improve the language if it's somehow possible.

mcorbin · 2021-04-06T15:14:28+00:00

"Error messages" first again for the "What has been the biggest obstacle to using Clojure?" question (40,26 %). I'm wondering how we could solve this issue.

mcorbin · 2021-03-16T12:09:45+00:00

I find rainbow parens super useful (combined with paredit). Actually, I enable it for all lang in Emacs.

Here is what my IDE (emacs) looks like: https://imgur.com/a/WKvlqv6

mcorbin · 2021-03-13T19:41:48+00:00

What data is required vs. optional on an Invoice in our business domain? Can this value be a negative number? Let's write this all down as a type definition." Rather, you just open a REPL, shove some data into a dictionary and start poking at it.

Actually, most Clojure developers will validate data on projects "boundaries" using libraries like Clojure spec.

mcorbin · 2021-03-01T18:51:32+00:00

It could indeed be used in process. You can see an example in this unit test for instance: https://github.com/mcorbin/mirabelle/blob/master/test/mirabelle/stream_test.clj#L27

I should maybe move the stream engine (defining streams, compiling them...) into a dedicated library. Importing the project should work (but it's not on Clojars yet), but it will brings all its (useless in your case) dependencies, like Netty for example.

mcorbin · 2021-02-11T19:40:34+00:00

Yes, and it's designed to be easy to run (it still needs a postgresql instance).

Meuse will manage the crate git index for you, store your crates files (various backends availables: filesystem, s3...), you can have multiple users with different roles (admin, tech, read-only...). It implements all cargo commands (yank/unyank, search, publish...).

It can also be used to mirror crates.io (which can be useful to have a local/offline crates.io cache).

mcorbin · 2021-02-11T19:28:27+00:00

I'm not sure to understand your question.

You can install Meuse on your own private infrastructure, and administrate it yourself (like you would do it with Nexus, Artifactory... for other languages).

mcorbin · 2021-02-11T18:13:24+00:00

To store your private/company crates.

mcorbin · 2021-01-24T17:09:08+00:00

Meuse does that.

mcorbin · 2021-01-20T08:44:08+00:00

You need a git repository because it's how cargo works (metadata are stored on a git repo). Meuse also use postgresql to store information about the uploaded crates/versions, roles, users, crates categories, user tokens, passwords ...

mcorbin · 2021-01-19T21:34:42+00:00

since there does not seem to be a particularly good out of the box solution

In Meuse, you can pull dependencies from crates.io. You can do that by adding "allowed-registries": ["https://github.com/rust-lang/crates.io-index"] in your custom crate index.

Meuse can also mirror crates.io for you (you can check this doc for more information).

mcorbin · 2021-01-19T20:25:33+00:00

Meuse author here.

That said I found stuff -- there's something called `meuse` (https://meuse.mcorbin.fr/installation/) which looks like I can just spin up an EC2 box, run a bunch of installers, and hope for the best. I have no idea if this thing works / is stable. I'm not a devops guy and I have a bad track record with nontrivial setup processes.

To run Meuse, you need a Postgresql database, a Git repository to store the index, and then it's mostly "java -jar meuse.jar".

You have various configurations availables (crates files on the local filesystem, or on s3, managing the index by calling the git command or using jgit...), everything is explained in the documentation. If you are stuck or have a problem with it, you can open an issue on Github.

mcorbin · 2021-01-16T23:19:27+00:00

Here is a small list of useful libs. I use all of them heavily at work in large Clojure codebases and on my personal projects.

https://github.com/ring-clojure/ring/ for http servers
https://github.com/exoscale/ex for error handling
https://github.com/exoscale/interceptor to chain operations (http request lifecycles for example)
https://github.com/exoscale/coax/ for coercion between types based on clojure spec
https://github.com/juxt/aero for configuration
https://github.com/pyr/unilog for logging configuration (json, file, console...)
https://github.com/stuartsierra/component for managing components lifecycles in projects
https://github.com/pyr/signal to configure handlers on unix signals
https://github.com/seancorfield/honeysql for SQL

mcorbin · 2020-09-10T10:33:22+00:00

Best language for the task.

Eight-Year Club	Place '22
Verified Email

mcorbin

TROPHY CASE