5 ms·
I‘d love to see Apple joining. They already have the hand on LLVM and support things indirectly, but... There is no reason that serious things written in Rust
by anonyfox 6y ago
I‘d love to see Apple joining. They already have the hand on LLVM and support things indirectly, but...
There is no reason that serious things written in Rust can‘t coexist with app-y stuff in swift.
Seriously, I think we all would benefit enormously from some consolidation, especially on such a great foundation like Rust. Think investments like: compiler-optimizations like V8, portability like C, enterprise grade tooling like Java, productive libraries like Ruby, datascience libs like python, ... it would be great to have all of this in one coherent package.
Why? Instead of glueing together brittle and fragile things where the moving parts break within weeks, reinventing the wheel, we could finally focus on the actual things to build. Bonuspoints for Rust: every other techstack can leverage/profit directly, like when binding C stuff.
Everyone still can innovate like the past decades, languages and libs will be re-explored and reinvented and so on, but, really, a solid baseline would be a dream
- pjmlp 6y agoWe don't need monocultures.
- ironlenny 6y agoIf everyone uses the same language, they're all going to write the same bugs! /s
- Ygg2 6y agoWell, each language has a different tradeoff in terms of usability, performance and model. Like Brainfuck could program anything.
- Daho0n 6y agoThen Swift should be replaced by something more mainstream. Adding Rust would be less monoculture than what we have now.
- deleted 6y ago[deleted]
- roca 6y agoApple is using Rust somehow internally, they were advertising for network software developers with Rust experience a while back.
- zepto 6y agoPretty much everything you listed is stuff Apple is already doing with Swift, and although Rust is awesome for lower level stuff, and stretches up quite well, Swift really does cover more of the stack of abstraction. That said, I’d say Apple having Swift is part of the reason everyone else is getting involved with Rust. Rust is credible competition for Swift where nothing else is.
- reader_mode 6y agoI have not used Swift much but the use cases overlap more with C# than Rust IMO.
- afiori 6y agoHi, as someone interested in typography I am interested in how and why you wrote a ‘ (U+2018 LEFT SINGLE QUOTATION MARK) instead of a ' (U+0027 APOSTROPHE) or a ` (U+0060 GRAVE ACCENT)? Is it used by a language on your system? is it in your keyboard? Or maybe a conscious typographical statement of proper style? I wonder :) Personally I have had my dose of fighting with using multiple languages with incompatible keyboards layouts, I would like to hear your story (even if it has nothing to do with keyboard layouts)
- heraclius 6y agoI find a compose key (see Wikipedia) quite helpful for diacritics, em dashes, &c.—once you get the hang of it, it’s really quite fast and intuitive. One can even add new combinations.
- afiori 6y agoI recently left the linux world and with it the compose key... the most similar (native) thing windows offers are dead keys which I find deeply abhorring. I settled on switching keyboard layouts with Windows+space. I was more curious about the why than the how in a sense.
- htgb 6y agoI use Windows, and haven't used Linux for years. It's probably just a matter of time before I go back, and when I do I know I'll love the compose key. However, the workaround I use on Windows is Alt key combinations: I memorized the dozen or so patterns [1] I use the most. For example, `Alt + 0160` for non-breaking space, `Alt + 0150` for en dash, `Alt + 26` (and a few more) for arrows and `Alt + 0133` for ellipsis. It must seem crazy when you're used to the compose key. I haven't heard of dead keys as a workaround. How does it compare? (Wow, this is getting very far from the original topic…) [1] An important key to memorizing them is to see them as patterns on the numpad, rather than a sequence of digits.
- afiori 6y ago