Cojen

5 ms·

1.
by Cojen 5y ago
...and now that NPE has a "helpful" message, I've generally found it to be almost a non-issue these days. During development, I can usually figure out the problem immediately just from the message and I don't need to exa
2.
by Cojen 5y ago
I think the best thing we have is the new `record` feature. You can declare a small public record before the method with the return type, and by using the `var` keyword, the caller doesn't need to repeat the type declaration.
3.
by Cojen 6y ago
Is there a C->JVM compiler out there that's any good and actively maintained? What are the major problems that come up with this approach?
4.
by Cojen 6y ago
The last commit to this project was over 8 years ago. Any plans on getting this thing moving along again? Was there anything learned from this project that can aid development of similar projects?
5.
by Cojen 6y ago
This is true, however I think that the perceived "viral" nature of the GPL gives the impression that patent invalidation can easily spread around to proprietary projects as well.
6.
by Cojen 6y ago
One word: patents. GPLv3 has wording which suggests that you need to give up rights to patents when you contribute. If you're a large company, with a large patent portfolio, this becomes an expensive endeavor. Either you give up patent
7.
by Cojen 6y ago
Jim Gray disagrees: https://arxiv.org/ftp/cs/papers/0701/0701158.pdf
8.
by Cojen 6y ago
I'm not familiar enough with Go to understand why this is a challenge. What point are you trying to illustrate with the challenge? Is this easy or hard, and how does this compare to Loom and Structured Concurrency?
9.
by Cojen 6y ago
From what I can tell, async system calls are used whenever possible. A blocking call on a socket doesn't make a blocking system call, thus permitting the carrier OS thread to go do something else. As for file I/O, things are a bit
10.
by Cojen 6y ago
Are virtual threads preemptable? If not, then one use for OS threads is when running a bunch of compute intensive tasks and you don't want worry about stalling everything else. I suppose in that case you could just use a separate execu
11.
by Cojen 6y ago
Does this example fully answer the question? Does this allow the tasks to be scheduled deterministically? If I'm very careful and write the tasks such that they make blocking calls at specific locations, then yes. Otherwise, is there a
12.
by Cojen 6y ago
Such a decision would also screw over EU airlines that still depend heavily on Boeing.
13.
by Cojen 6y ago
That's cool, I hadn't thought of that. But does it identify "hot"/"cold" files that might benefit from being converted automatically to/from the compressed format? That would be a very nice feature to
14.
by Cojen 6y ago
Reading over the comments here makes me chuckle a bit because it proves the author's point: "Error handling is hard". I don't think any silver bullet solution has been invented yet. I'd like to see error handling su
15.
by Cojen 6y ago
NTFS requires that files be manually converted to the compressed format. They're uncompressed in parts as requested, but this is only kept in RAM. I'm not aware of any built-in background task that converts files to/from the
16.
by Cojen 6y ago
I guess it all depends on what side you're coming from. When I was in school, I studied MIPS from the perspective of a compiler writer who's only casually interested in hardware design. Having learned a couple of CISC designs befo
17.
by Cojen 6y ago
I found this to be a good read, but I wish the author discussed the pros/cons of bypassing the file system and using a block device with direct I/O. I've found that with Optane drives the performance is high enough that the e
18.
by Cojen 6y ago
Is it just me or did anyone else think that the bottom of the dish was a solid concrete surface? I was surprised when I saw the pictures of the damaged dish and wondered how such a giant hole was created!
19.
by Cojen 6y ago
I've found that coding in a "C-like style" offers great performance too. Are there any languages that target the JVM and are designed for higher speed? If it enforced the "C-like style" at the language level, perhap
20.
by Cojen 6y ago
I found this to be a good read, but I wish the author discussed the pros/cons of bypassing the file system and using a block device with direct I/O. I've found that with Optane drives the performance is high enough that the e
21.
by Cojen 6y ago
This makes me wonder how it's possible how to replicate data without being eventually consistent. I can't transmit data faster than the speed of light. It seems that the definitions here need more clarity, because eventual consist
22.
by Cojen 6y ago
The definition of "eventually consistent" is somewhat vague in this respect, or at least easily misunderstood. When updates are streamed and applied sequentially, "eventual" is easily determined as the number of messages