- erikbye parentI read or heard somewhere at least 80% of CC is written by CC and Aider (before CC was mature enough)
- The title here is beginner developer, but the article states non-developer.
Nevertheless, dev docs are usually written for reasonably experienced developers, but new to specific framework/library.
These docs would be too long-winded if they were to account for non-devs/complete beginners.
Please, don't cater to that audience in your docs.
- Here's a few crappy phone pics from near Oslo on a night (evening, around 19 I think) it was very visible with the naked eye. 0.5 seconds exposure.
https://www.flickr.com/search/?sort=date-taken-desc&safe_sea...
- Our eyes definitely do not see "pretty much without the color". Born and raised in Norway I've watched more aurora borealis than I care to count. On many occassions you could see all kinds of colors and dancing lights with the naked eye, very strong and vivid, too. Important to be in a dark environment without light pollution. At the arctic circle during polar night you will see northern lights that almost match the most stunning photos you have seen.
- I don't get the "git has horrible user interface" crowd. Never had a problem understanding git or its commands. It's probably the least complicated tool in my box, and the one that has given me least trouble.
What exactly is so bad about the ux?
Are the ones having trouble people that's never used another CVS? Is it CLI aversion?
- > Ok, we're going from a bunch of complaints about Rust being bad for fast prototypes for indie development to the idea that Rust is bad at everything.
No, not at all, that's not what I meant. I think it's forte for now is better security at the cost of some performance and productivity (iteration speed).
- > Interestingly, all these companies are migrating some of their systems to Rust. This suggests that they find the language convincing enough.
I feel most large companies and some smaller ones are interested in trying out Rust, it's trendy. But time will show for which parts the switch was advantageous; and I'm very interested in the findings. The premise of the language is indeed convincing a lot of people. People do however, choose the wrong tool for the wrong job all the time, OP's article in point.
- Haven't used BeOS, but to clarify, I do have issues with Windows and performance, especially general input latency and responsiveness when compared to Linux, as I use both daily. But overall I think it's decent, and at the very least, not the fault of the language used, but more about legacy issues and technical debt. Anyone having worked with winapi and mfc knows the codebase is a mess.
- I agree, operating systems should have less out-of-bounds memory issues. Is that Rust's place? Replacing the parts of OS code where it's OK to sacrifice some performance?
Ada has a foothold for sure, but there's a surprising amount of C++ in military planes and weapon systems.
I didn't read [0], but the parts of Windows that's poorly performing is not the fault of the language.
- Rust... what is it good for? "Systems programming" ...
Rust is not good for raw performance. Neither for prototyping and iteration.
Personally I think operating systems (kernels) should be as performant as possible, and C/C++ has been good enough for decades.
Anyone really unhappy with Linux/BSD/Windows/macOS performance?
What systems are we talking about that benefits from Rust? Advanced weapon systems that should absolutely not fail? Controllers for air planes? Traffic controllers? Radar? Power grid?
Google, fb, amazon, etc. use C/C++ to squeeze the most performance out of anything I/O heavy, and security is not an issue that deep in the stack, that's not the exploitation layer.