gavinking

9 ms·

61.
by gavinking 12y ago
Well both are wrong. You don't clap on two and four; you click your fingers. I thought everyone knew that...
62.
by gavinking 12y ago
Cheers!
63.
by gavinking 12y ago
It's there now, I believe.
64.
by gavinking 12y ago
Yes, I understand. What I mean is a whole tutorial that shows a ceylon client in the browser calling a ceylon sever running on vert.x.
65.
by gavinking 12y ago
That's exactly right. Ceylon and Rust are both new languages, with, it seems to me, a fair amount of similarity in terms of overall philosophy, but they target quite distinct usecases. Ceylon -> VMs, Rust -> systems programming.
66.
by gavinking 12y ago
Oh yeah, we definitely need to write this now that vert.x's Ceylon integration just released it's 1.0 version!
67.
by gavinking 12y ago
As a further clarification, when I said: "there are a bunch of operations that I would love to add to ceylon.language, but can't, because they are simply unimplementable in JS", I don't mean that those operations aren&#x
68.
by gavinking 12y ago
I would say that Ceylon is heavily guided by the constraints of wanting to always do The Right And Elegant Thing, and not unduly compromise on that in light of the nature of the underlying VM. _Which_ VM doesn't quite enter into that q
69.
by gavinking 12y ago
OK, sure, thanks for your comments :-)
70.
by gavinking 12y ago
>> but that it isn't one of the top two concerns of the language: i.e. it's possible and maybe kind of easy, but certainly not seamless. << Well it's certainly _a_ top concern, and one we've invested a huge a
71.
by gavinking 12y ago
Well it is somewhat better because it occurs immediately when the null value passes from Java code with unsafe null into Ceylon code with safe nulls. Having the compiler produce an actual error in this case seems wrong and excessive, since
72.
by gavinking 12y ago
Well it all depends how you handle `null` at the boundary between the two languages. In Ceylon, we let you write either: String str = javaObject.javaMethod(); or: String? str = javaObject.javaMethod(); In the first case,
73.
by gavinking 12y ago
FTR, Ceylon's Java interop is _excellent_, especially in this latest release, and Ceylon makes it absurdly easy to use the Java SDK directly from Ceylon. Indeed, the Ceylon compiler's Java backend is actually built on Open JDK - t
74.
by gavinking 12y ago
Yes, that's right, to confirm, it does run on Java 8, but we don't yet take advantage of any Java 8 features of the VM. (We first need to rebase the compiler backend on the Java 8 compiler, which could take some work.) FTR, we hop
75.
Does Google think you’re famous?(washingtonpost.com)
1 points by gavinking 12y ago|0 comments
76.
by gavinking 12y ago
Exactly, thanks!
77.
by gavinking 12y ago
Mutability is a great tool; it dramatically simplifies certain algorithms, and dramatically improves performance of others. But it comes at a cost, and there are situations in which it is inappropriate. So the language should force you to t
78.
by gavinking 12y ago
In Ceylon even local variables must be explicitly annotated `variable`. The reason for that is that a local variable could be captured by an anonymous function or nested function, and escape from the local scope, so it's exactly the sa
79.
by gavinking 12y ago
FTR, the whole declaration section vs initialization section stuff really boils down to this: You can't declare mutually-recursive methods before initialization logic in the body of a class. You have to declare them _af
80.
by gavinking 13y ago
> I was merely pointing out that although it is a user definable type, the language specification does mention its existence Sure, the language spec _mentions_ Null, in order to define the syntax sugar X? and exists x. But that doesn&#x2
81.
by gavinking 13y ago
> But aren't you pretty much focusing on implementation details here? No, not at all, I'm talking about the ability to abstract over things. Can I write a single higher-order function that operates over functions with any -arit
82.
by gavinking 13y ago
> Correct me if I am wrong, but there doesn't appear to be anything linking the nullability of the return value based on the possible emptiness of the input value. Sure there is. The second type parameter of Iterable encodes that, s
83.
by gavinking 13y ago
> The idea that the object graph I see in scala corresponds 1:1 to the object graph I see in java for the same object is comforting Surely. Not merely comforting, but useful. But it entails deep compromises in the design of the type syst
84.
by gavinking 13y ago
> Oh, now I'm a bit confused ... are you really saying that you think that the version with the unreadable and cryptic signature, which is non-extensible in any way and repeats all of Java's mistakes is a good solution (or the
85.
by gavinking 13y ago
> Sounds like HList. Maybe. I have never heard of HList until today. > Do you avoid instantiating a JVM object for each entry? Yes, a tuple, at the VM level is just a wrapped array. Our compiler backend does magic with certain languag
86.
by gavinking 13y ago
Oops, thanks. Appreciated. How I wish hn supported markdown :-/
87.
by gavinking 13y ago
Don't get me wrong, I don't mean to belittle scientific computing, which is after all, a big part of my background (I'm a mathematician by training).
88.
by gavinking 13y ago
> One of the next versions of Java will ship with a module system. I certainly hope so, since we always planned to replace JBoss Modules with Jigsaw when that becomes possible. But we still don't know if the Jigsaw module system wil
89.
by gavinking 13y ago
> using maven Brrrrr. > What is the problem I'm supposed to be having that OSGi would be solving? Because I've never seen it. The problem OSGi solves is having two versions of the same module as part of the same assembly. Th
90.
by gavinking 13y ago
Ah, OK, fair enough, well, Bastien and Matija have recently been making very good progress on the IntelliJ plugin for Ceylon, and since we expect to be able to reuse quite a bit of underlying code from the Eclipse plugin, we hope to somethi

More ›