Yeah that’s still gatekeeping though. Coffee is coffee regardless of what you put in it. Even if it’s gross according to my own individual taste, it’s still coffee. Saying anything else is just “better-than-you” gatekeeping.
Edit: it’s also nothing like your example at all, because coffee with creamer is still literally made with real coffee, while an apple jacks pop tart is almost definitely not made with real apples.
Imagine gatekeeping caffeine
OP mentioned having used Linux for 4 weeks. If they are interested in learning more about Linux, I feel like even Arch would be a better next step.
I love NixOS and have been using it for over a year at this point but sometimes when things don’t work I feel like I’m banging my head against a wall. I’ve been using Linux for ~7 years now.
It’s not magic, it’s adoption rates. I’m not saying the money or resources are useless, but as it is right now, I think more people would benefit from actually trying to use rust in more large-scale projects (like R4L, windows, android, redox, servo, etc.) and using that experience to inform actual language development. I don’t think it makes sense to do a full revamp of the compiler until projects like those are actually proven. In the meantime it makes more sense to allocate funding/dev resources to those projects (or at least the open source ones)
revamp Rust to produce lightweight binaries, have a stable compiler and for it to be way quicker in compilation
It really isn’t that simple though. Rust’s compiler isn’t stable because the language itself is still being improved. This type of thing will only improve as adoption increases and real-world problems get ironed out. You can’t just throw money and devs at it and expect the problem to be solved.
It’s also not like the developers don’t care about compile time, but the nature of the language (strict compiler checks which catch things before runtime) will inherently lead to something slower that other languages’ compilers. There are probably still improvements they can make, but it’s not as simple as just deciding to rewrite/revamp it and expecting massive speedups.
I think the idea is that you can eventually get an approximation of whatever wave-like curve you want by merging several pure sin/cos functions with varying amplitudes, wavelengths, and offsets
Fun fact: this is mostly how JPEG works - it uses fourier transforms to approximate an image in a way that takes up much less storage than storing information about each pixel.