I was bitten by this this week. Tried to reuse my installer to install OS X El Capitan on a MBP without redownloading it over my super-fast 2Mbps internet connection.
First, I try to install it by just copying the installer app - "can't be verified".
Then I make a bootable USB stick using DiskMaker X - "can't be verified". I run an integrity check on the installer - all good.
I then try running `/path/to/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB-STICK --applicationpath /path/to/Install\ OS\ X\ El\ Capitan.app --nointeraction` - "can't be verified".
Finally I give up and the system is installed via the App Store. The download fails once, it finally completes, and I am left clueless as to why I couldn't reuse the old installer.
An "expired certificate" error message would have saved me many hours. It's unfortunate for the user that Apple puts so little emphasis on letting them be their own tech support.
You have invites? I'd love one, KeyBase seems awesome but I couldn't find an invite. If you don't mind, could you send me one by email at [email protected]? Thanks :)
IIRC, Nginx can use sendfile too, it's just not there by default because the transfer happens entirely in kernel space and hence you cannot apply filters like gzip on the response (correct me if I'm wrong).
I'd love something similar to be part of Cargo, maybe as an option in the manifest. Like the author, I've learned to guess when the codegen starts, but having this information displayed would be useful.
I'm glad to know there is ongoing work on a tracing GC. Rust has many strengths aside from lifetimes and ownership (algebraic data types, sane generics, strong module support, very strong type system), so a few features to make it more usable for use in contexts where performance isn't as important as expressivity would be very nice to have.
Rc and Arc aren't exactly GC types... they are just reference-counted pointers, Rc being akin to C++'s shared_ptr. I get that in a sense, this is garbage collection, but certainly not full-featured like the ones you find in other languages.
While I agree with some of your arguments, namely that "popularity and merit are not the same thing", I think saying that Mozilla is "trapped in a pseudo-C++ mindset" and that its new browser would ideally be written in Nim is plain wrong.
The fact that using Rust to write a simple website isn't very handy doesn't mean it's a bad language.
Web development simply isn't its primary focus: this is a systems programming language we're talking about. The mere fact that it is being considered for writing web apps is impressive since Rust is supposed to be a better C++, not a better Ruby, Python or Node.js.
Rust mainly emphasizes performance and safety. This means all the 'magic' that happens in a dynamic language is exposed to the programmer, and has a cost: the code is more verbose, and seemingly simple things are more complicated.
I think announcing a product on April 1st is a genius strategy. They can see if customers want it or think it's a joke; if nobody likes the product, they say it's for April Fools, if, on the other hand, people like it, they launch it for real.
Since a few people mentioned Vagrant: can I use it to set up a production environment locally, with all the system dependencies, configuration files, and then pushing it to production?
If so, is this the recommended approach?
First, I try to install it by just copying the installer app - "can't be verified".
Then I make a bootable USB stick using DiskMaker X - "can't be verified". I run an integrity check on the installer - all good.
I then try running `/path/to/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB-STICK --applicationpath /path/to/Install\ OS\ X\ El\ Capitan.app --nointeraction` - "can't be verified".
Finally I give up and the system is installed via the App Store. The download fails once, it finally completes, and I am left clueless as to why I couldn't reuse the old installer.
An "expired certificate" error message would have saved me many hours. It's unfortunate for the user that Apple puts so little emphasis on letting them be their own tech support.