Earlier quoted context omitted.
This is interesting, I knew a workplace where open source contributions are fine as long as its not on company PC and network.
No, as far as I know, at Apple, this is strict - you cannot contribute to OSS, period. Not from your own equipment nor your friend's, not even during a vacation. It may cost you your job. Of course, it's not universal for every team, but on teams I know a few people - that's what I heard. Some companies just don't give a single fuck of what you want or need, or where your ideals lie. I suspect it's not just Apple, I…
Closing this as we are no longer pursuing Swift adoption
251–260 of 332 posts
Re: Closing this as we are no longer pursuing Swift adoption
#252There's no way to say this without sounding mean: Everything Chris Lattner has done has been a "successful mess". He's obviously smart, but a horrible engineer. No one should allow him to design anything. Edit: I explained my position better below.
People are correct I didn't explain my position. LLVM: Pretty much everyone who has created a programming language with it has complained about its design. gingerbill, Jon Blow, and Andrew Kelley have all complained about it. LLVM is a good idea, but it that idea was executed better by Ken Thompson with his C compiler for Plan 9, and then again with his Go compiler design. Ken decided to create his own "architecture…
The latter is definitely a defining capability of Anders Hejlsberg. (C#/Typescript designer)
Re: Closing this as we are no longer pursuing Swift adoption
#253Earlier quoted context omitted.
The best tool for the job is the one you know and love.
It depends. Many languages are a poor fit for certain use cases, and some are bad at everything beyond a very specific niche. Some are rather unpleasant to write any kind of substantial UI with.
Re: Closing this as we are no longer pursuing Swift adoption
#254Re: Closing this as we are no longer pursuing Swift adoption
#255Earlier quoted context omitted.
In the last years, simplistic languages such as Python and Go have “made the case” that complexity is bad, period. But when humans communicate expertly in English (Shakespeare, JK Rowling, etc) they use its vast wealth of nuance, shading and subtlety to create a better product. Sure you have to learn all the corners to have full command of the language, to wield all that expressive power (and newcomers to English are…
Not sure how I feel about Shakespeare and JK Rowling living in the same parenthesis! Computer languages are the opposite of natural languages - they are for formalising and limiting thought, the exact opposite of literature. These two things are not comparable. If natural language was so good for programs, we’d be using it - many many people have tried from literate programming onward.
I don't see a case for "complex" vs "simple" in the comparison with natural languages.
Re: Closing this as we are no longer pursuing Swift adoption
#256Earlier quoted context omitted.
> In the end it came down to Swift vs Rust, and Swift is strictly better in OO support and C++ interop Why not D?
Why not rust? It's popilar, in wide adoption, with wide support, without the baggage of C++. What'e the downside?
> Swift is strictly better in OO support and C++ interop
So I guess from their point of view that’s why not rust.
I don’t have a horse in the race.
I was genuinely interested in why they didn’t even consider D given they already ruled out rust for those particular reasons, for which it seems D would fulfill nicely.
Re: Closing this as we are no longer pursuing Swift adoption
#257Earlier quoted context omitted.
In the last years, simplistic languages such as Python and Go have “made the case” that complexity is bad, period. But when humans communicate expertly in English (Shakespeare, JK Rowling, etc) they use its vast wealth of nuance, shading and subtlety to create a better product. Sure you have to learn all the corners to have full command of the language, to wield all that expressive power (and newcomers to English are…
Perlis's 10th epigram feels germane: > Get into a rut early: Do the same process the same way. Accumulate idioms. Standardize. The only difference(!) between Shakespeare and you was the size of his idiom list - not the size of his vocabulary.
Here's a Python rut:
n = 20 # how many numbers to generate
a, b = 0, 1
for _ in range(n):
print(a, end=" ")
a, b = b, a + b
print()
Here's that rut in Raku: (0,1,*+*...*)[^20]
I am claiming that this is a nicer rut.Re: Closing this as we are no longer pursuing Swift adoption
#258Earlier quoted context omitted.
In the last years, simplistic languages such as Python and Go have “made the case” that complexity is bad, period. But when humans communicate expertly in English (Shakespeare, JK Rowling, etc) they use its vast wealth of nuance, shading and subtlety to create a better product. Sure you have to learn all the corners to have full command of the language, to wield all that expressive power (and newcomers to English are…
Not sure how I feel about Shakespeare and JK Rowling living in the same parenthesis! Computer languages are the opposite of natural languages - they are for formalising and limiting thought, the exact opposite of literature. These two things are not comparable. If natural language was so good for programs, we’d be using it - many many people have tried from literate programming onward.
Re: Closing this as we are no longer pursuing Swift adoption
#259Earlier quoted context omitted.
Maybe? I feel like there's been lots of efforts to migrate large C++ codebases over the years, and few actually complete the migration. Heck, Google is even making Carbon to try to solve this.
migrating any large project is going to be billions of dollars worth of labor. Language isn't a large factor in that cost, you can save few tens of millions at most with a better language.
I'm struggling to think of a larger factor
Re: Closing this as we are no longer pursuing Swift adoption
#260Earlier quoted context omitted.
migrating any large project is going to be billions of dollars worth of labor. Language isn't a large factor in that cost, you can save few tens of millions at most with a better language.
Can you give me some reasoning behind this statement ("language isn't a large factor in the cost of migrating a large project")? I'm struggling to think of a larger factor