221–230 of 240 posts
Earlier quoted context omitted.
For Apple or for employees you mean? I would imagine that many people are going to apply. I would have loved to write Rust at Apple, if I ever got the chance to. And Canada is on my list of countries I would like to live in already anyway.
Not everyone who applies is qualified.
Earlier quoted context omitted.
Swift is not yet a zero-abstraction-cost language like C or Rust which might be one of their concerns.
C is far from zero-abstraction-cost. For example you can't do a generic qsort supporting user defined types with zero overhead, other than with preprocessor macros (ugly, unsafe, unmaintainable).
http://libredblack.sourceforge.net/
It supports a few modes of operation, including codegen, and preprocessor tricks. It’s clearly maintainable, given its age and continued use.
Your third complaint is that C with preprocessor macros is ugly. That’s subjective.
I think C++ is more elegant than C + macros, but the GTK people clearly disagree.
Earlier quoted context omitted.
C is far from zero-abstraction-cost. For example you can't do a generic qsort supporting user defined types with zero overhead, other than with preprocessor macros (ugly, unsafe, unmaintainable).
I think you've inverted the meaning of "zero abstraction cost" here. It's not that writing abstract code is well-supported and free; it's that the language basics aren't built upon a stack of expensive abstractions.
Earlier quoted context omitted.
Rust definitely does not share the simplicity of C. It is the equivalent of C++, not C. You can write code which you cannot guess the machine code, as soon as you use any of the abstractions, just like C++.
Rust’s standard library is about on par with C’s, though.
Earlier quoted context omitted.
Rust’s standard library is about on par with C’s, though.
Rust standard library is dramatically more useful than C’s. C doesn’t offer any kind of collections in its libraries. Every C project just grows its own differently broken hash maps and linked lists.
Earlier quoted context omitted.
Ah, is this your 45th account @gasthem_1? :P
No, on HN I usually just type something related to whatever is on my mind at the time. No prizes for guessing what it was this time.
In other cases it's probably because your new accounts are breaking the site guidelines. If you're sincere about wanting to use HN as intended, you're welcome to email hn@ycombinator.com and we'll look into it for you and be happy to help. But could you please not create accounts to break the site guidelines with?
doesn't Apple prevent engineers from having related engineering hobbies when they sign the contract ?
Earlier quoted context omitted.
Oh, I've always had plenty naysayers. If I ever paid any attention to them, I'd be a total failure.
I think D didn't gain the momentum because of GC. O/B system is interesting but makes the syntax ugly (at least in Rust's case). Had D gone with a (deterministic) ref counting like Swift and Vala, it would've been much more popular I think. Such memory management keeps the syntax cute :) while not sacrificing the determinism.
D doesn't change the syntax for O/B.
Earlier quoted context omitted.
IMHO it's worth learning at least to internalize the concept of ownership. Ownership in some form exists in most languages, but Rust makes it very explicit. It guides you towards clearly organizing program's data into isolated tree-like structures, instead of a web of everything referencing everything else. Like Lisp, even if you don't use it, it may change how you think about code. I see companies adopting Rust inte…
> Cloudflare writes most new code in Rust, I think you might be over-stating this. We do write a bunch of Rust though!
Converting code seems like an incredibly boring job.
That doesn't say the job is ONLY converting code. It says that code was converted, and new code will be in Rust.