Buckleyisms

4 ms·

1.
by Buckleyisms 11y ago
The point is that even showing up costs time and possibly travel expenses. Court proceedings are slow, so without a lawyer, you'll spend days of your time in court fighting the case. It's possible to defend yourself without a lawy
2.
by Buckleyisms 11y ago
Because that's just not how the legal system works, at least not in the United States (Kik Interactive is located in Canada, npm Inc. is located in the US, so it's possible for Kik to file a lawsuit against npm in the US.) Full di
3.
by Buckleyisms 12y ago
> I have no idea what the right thing to do is in this situation, but having all those possibilities gives the compiler a better chance of producing faster code. When you introduce message passing, you basically forbid all of those optim
4.
by Buckleyisms 12y ago
This is true, and why I also filed bugs asking for a robust reflection and dynamic method compilation. Thankfully, they were duplicates. But not all of the cases can be accomplished using these techniques, and even those that can, it's
5.
by Buckleyisms 12y ago
I described that radar rather poorly. If you look at what I described in the radar, I basically want them to ship the swift compiler as part of the core OS, and an eval function would compile its argument and load it into the current proces
6.
by Buckleyisms 12y ago
From the linked Wikipedia article on Dynamic Dispatch: > C++ compilers typically implement dynamic dispatch with a data structure called a virtual table that defines the message to method mapping for a given class (C++ as such has no not
7.
by Buckleyisms 12y ago
I suppose it depends on what you intend to use Swift for. My argument is that Swift will be primarily used to write high-level apps. For these apps, message passing is almost never a bottleneck. Swift is not going to replace the optimized C