emccue

9 ms·

61.
Publish a Java library without Maven or Gradle(mccue.dev)
1 points by emccue 4y ago|0 comments
62.
by emccue 4y ago
Oof, fixed
63.
by emccue 4y ago
Yeah, sorry. I would have used .startVirtualThread more if I wasn't under the impression that I needed to do Thread.currentThread().interrupt() when catching and re-throwing as a RuntimeException. So I was choosing between the noise of
64.
by emccue 4y ago
Can you elaborate more? What is the distinguishing factor?
65.
by emccue 4y ago
Aight. I only started doing this recently after this advice here https://discord.com/channels/544924237773668373/930457954346... I'll clear it from the examples
66.
by emccue 4y ago
The example I think is compelling is JDBC. Nearly all SQL Database access goes through it and it won't be rewritten in any practical time scale. It can't be meaningfully async without a rewrite and kotlin's coroutines can&#x2
67.
by emccue 4y ago
Okay this is cool. I think mechanically the plans for ScopeLocals can be a part of implementing a scheme like that. Either way - I need to read this thoroughly in the morning.
68.
by emccue 4y ago
Can you elaborate more? All of the parts that throw `InterruptedException` are handling the thread interrupt cancelation mechanism. There is also the example with the atomic boolean quit flag. I'm not convinced that Go has any unique m
69.
by emccue 4y ago
No, I understand how Loom limits the amount of stuff on the stack. Its just I thought threads always had those large stacks. Based on what the top person said, I'm thinking that they don't get a large stacks until they cross some
70.
by emccue 4y ago
Hypothetically there is a version of "static Java" that could start to encroach upon Go's domain. This may or may not come out of Project Leyden, but I think for the reason the other commenter gave GraalVM isn't exactly
71.
by emccue 4y ago
Here is the part where I admit that I am an idiot and don't actually know. All I do know is that in Java I cannot create this many threads and in the talks given about Project Loom this is given as the explanation as to why. https:&#x
72.
by emccue 4y ago
True, but I didn't write any of the Go here. Somewhat out of my wheelhouse
73.
by emccue 4y ago
Yeah - ConcurrentHashMap makes the most sense. I left it off just because I thought it would be easier to see the parallel with the Go code.
74.
Go's Concurrency Examples in Java 19(mccue.dev)
151 points by emccue 4y ago|114 comments
75.
by emccue 4y ago
Datalevin is good, but its more useful in the same realm as sqlite
76.
by emccue 4y ago
In this respect XTDB has a more directly useful model
77.
by emccue 4y ago
Feel free to reach out via any of the contact info on my github. The more the merrier chasing this magic dragon.
78.
by emccue 4y ago
I think this is true - you will have an easier time not blazing new trails in general - but the need of ledger-like functionality isn't the distinguishing factor. Preserving the history of all changes isn't just for reconstructi
79.
by emccue 4y ago
As the world stands today, it makes sense to use Datomic if you are writing code on the JVM and are willing to pay for the database and associated support. In a hypothetical future world where the data model and query approaches have more w
80.
by emccue 4y ago
If anyone is interested, I am attempting to revive an open source clone of Datomic called EVA. As is the original codebase works fine, its just unmaintained. My hope is to clean up the code, make an HTTP layer for a remote peer, and make a
81.
Java's Options for Options(mccue.dev)
3 points by emccue 5y ago|1 comments
82.
Magic Bean: Automatic Java Beans without compiler hacks(github.com)
1 points by emccue 5y ago|0 comments
83.
by emccue 6y ago
To be clear, I'm no stranger to Lisps. I use Clojure a ton for personal stuff and on occasion have found ways to sneak it in to production. The difference there is that Clojure isn't responsible for giving a wide enough ecosystem
84.
by emccue 6y ago
Weird nitpick, but "No Makefiles required" is an odd selling point to me. I haven't seen or used a Makefile in eons, and I would wager a decent chunk of programmers never needed to. I'm not sure how to describe the feeli
85.
by emccue 7y ago
This is why I like transparent sql libraries like https://www.hugsql.org/ Just writing sql and maintaining and testing it like regular code is a perfectly reasonable thing to do. Not to mention that having sql be callable a
86.
by emccue 7y ago
Oof magoof