lerno

I would say that it is volatile mix of very non-pragmatic constructs and lots of real constraints that creates the problem. If you want to see how to build a pragmatic language - look at JAI.

Consciousness is typically understood as "the one that experiences". The failure of reductionism to explain it can be demonstrated by an example: You accidentally burn your finger on the sto…

If you use the wsdl for discovery, then you are doing something that's rather dangerous as there are no guarantees what that method does or that it is correct -> use documentation instead. If …

The "point" of SOAP is to have an autogenerated API layer + objects on client and server side. The problem is that this does not actually help much in validating data sent or received. In ad…

I agree, Chinese simplification was extreme, whereas the Japanese simplification tried to retain the idea of the original character. Possibly, an additional political motivation of the simplification …

This is the release that makes you go "people were insane to think that Swift 1.1 was anything near usable".

I'd have to check in detail, but just looking at the profiler, about half of the time is in the actual setter code and half in bounds checking. One would think that bounds checking is a faster op…

I am not sure of the exact behaviour. I only read something Lattner wrote as a comment on very slow behaviour when passing things back and forth into CoreGraphics that relied on bridging Swift arrays&…

From what we're told, copy-on-write doesn't happen unless it has to (i.e. the compiler discovered that we use it elsewhere). In any case, the issue here with debug builds does not seem to be…

The conversion is only supposed to happen once, but there was a bug (don't know if it is fixed yet, it was discovered quite a while ago), which made the Swift <-> ObjC NSDictionary conversi…

Actually, a Swift array is pretty much identical to a C array. You get an unsafe pointer to that array and treat it exactly as it was one. NSArray on the other hand is toll-free bridged to a CFArray. …

No, but we have been told that the performance characteristics of the native Swift array should be the same as an array in C. Judging from what the compiler team at Apple regularly write in forums and…

In theory Swift's arrays are little more that a c array + length, and this is how we have been encouraged to use them. The issue here is nothing about "managed code", but about how the …

We've essentially been told to use Swift arrays as we would C arrays, so your analogy is flawed. Another premise for Swift is that it should be usable for low level, high performance programming …

This problem has been understood and resolved by a number of thinkers. The Buddha, lots of buddhist masters, then we also have people like Eckhart Tolle who clearly realise it. The problem is that con…

I see some programmers that work at it, but after 5 years their level is just as it was when they started out. At the same time, there are others who grow their skill at an amazing rate, going from al…

Here are some observations that may or may not help you: Average programmers tend to: * like new projects * want to build "new things" * not like fixing bugs * not like reading code * …

Interestingly, Swift may not even be a "better C++" for all domains dominated by C++: The memory model is strictly ref-counted which is unsuitable for certain tasks (e.g. high perf game prog…

I wonder what's really best / possible. Most teams / companies start up homogeneous to some extent. Also, there is plenty of conflicts possible even in a homogeneous team - it's ju…

Regardless of whether you agree or not, it's very interesting in that it's challenging the merits of things we take for granted as being "good".

Wrong. TCP has a lot of behaviour you can't work around. UDP is what you write it to be. When experiencing packet loss not due to bandwidth, TCP will delay recovery compared to what UDP can achie…

Personally I went all-in on Swift. Unfortunately I found that the sceptics were largely right about Swift: The safety features did not make the code more safe, but caused new classes of bugs. Runtime …

I tried to hunt down the statement but without success. If I didn't imagine it, then I'm fairly sure it was in the Apple dev forums. However, I did find a posting where someone said they had…

Incidentally the problem is much smaller than in a statically typed language with containers. Compare the difference between a Java list prior to generics and afterwards. Using it in Java was an orgy …

"How does that analogy make any sense?" Well, I told you that the blog forms a narrative, of which the entry forms a part. His reasons for reaching the conclusions in this entry is based on …