Develop a BSD distro with a desktop environment and a modern web browser, and set it out for a million end users to use with a $50k cash prize for the first exploit, and you'll be paying out in a day, tops.
We already have that. You mentioned it in your second sentence.:-)
And before you bleat on about the line that says you don't need a runtime, the only programs that can do without the Rust runtime would either be trivial, toy programs or would be in environments that have to reinvent the Rust runtime library routines. Sort of like how the Linux kernel doesn't use a libc runtime like glibc but does reimplement many of the C standard library routines itself.
You're joking, right? Every language has a runtime. From the Rust documentation:
Rust includes two runtime libraries in the standard distribution, which provide a unified interface to primitives such as I/O, but the language itself does not require a runtime. The compiler is capable of generating code that works in all environments, even kernel environments. Neither does the Rust language need a runtime to provide memory safety; the type system itself is sufficient to write safe code, verified statically at compile time. The runtime merely uses the safety features of the language to build a number of convenient and safe high-level abstractions.
That being said, code without a runtime is often very limited in what it can do. As a result, Rust's standard libraries supply a set of functionality that is normally considered the Rust runtime. This guide will discuss Rust's user-space runtime, how to use it, and what it can do.
1 What is the runtime?
The Rust runtime can be viewed as a collection of code which enables services like I/O, task spawning, TLS, etc. It's essentially an ephemeral collection of objects which enable programs to perform common tasks more easily. The actual implementation of the runtime itself is mostly a sparse set of opt-in primitives that are all self-contained and avoid leaking their abstractions into libraries.
The current runtime is the engine behind these features (not a comprehensive list):
And you overestimate how much people are going to care, but that's pretty typical of language hipsters. Every new language claims to solve all the problems of its predecessors. It's going to need far more of a pitch than that to get businesses to sink the years and countless amounts of money needed to rewrite all their software in Rust.
A third possibility is that the NSA and their friends abroad might have pressured the manufacturers to remove these security features.
Which is not a possibility since my company ships hundreds of USB drives out with hardware write switches every week. They are extremely easy to find and buy.
Slashdot Mirror
I'm pretty sure Stallman would not support your assertion that purchasing from Amazon is "freedom".
I'm pretty sure the AC was making a sarcastic, joke post. A person who was being serious wouldn't sign their post with "SJW".
Yeah, because installing a whole other OS just to build Firefox is totally a useful suggestion. Oh wait...
Good to see that Arch users are still ever vigilant in being the most obnoxious and attention whoring Linux users on the planet.
For that matter, why does my toaster need internet access?
Because companies need you to be a good little consumer whore and buy worthless junk you don't need.
It's not orthogonal. You presented the "modern languages" as the panacea which they clearly aren't.
Presenting an implicitly typed multiparadigm language as the alternative is strawmanning though.
So you want examples for programs written in Python, C#, Java, etc? Or are you going to keep moving the goalposts?
HP runs the event.
Dice.com.
But...but...it's all the fault of extensions!!! Firefox is flawless!!
HP is the one who runs the event and offered the rewards. You act as if they are being forced to do so which they aren't.
Yes, but you aren't an "Internet of Things" seller.
Develop a BSD distro with a desktop environment and a modern web browser, and set it out for a million end users to use with a $50k cash prize for the first exploit, and you'll be paying out in a day, tops.
We already have that. You mentioned it in your second sentence. :-)
Yeah, it seems the AC doesn't understand what a runtime really is.
And before you bleat on about the line that says you don't need a runtime, the only programs that can do without the Rust runtime would either be trivial, toy programs or would be in environments that have to reinvent the Rust runtime library routines. Sort of like how the Linux kernel doesn't use a libc runtime like glibc but does reimplement many of the C standard library routines itself.
MEMORY SAFETY
As do countless other languages.
NO RUNTIME
You're joking, right? Every language has a runtime. From the Rust documentation:
Rust includes two runtime libraries in the standard distribution, which provide a unified interface to primitives such as I/O, but the language itself does not require a runtime. The compiler is capable of generating code that works in all environments, even kernel environments. Neither does the Rust language need a runtime to provide memory safety; the type system itself is sufficient to write safe code, verified statically at compile time. The runtime merely uses the safety features of the language to build a number of convenient and safe high-level abstractions.
That being said, code without a runtime is often very limited in what it can do. As a result, Rust's standard libraries supply a set of functionality that is normally considered the Rust runtime. This guide will discuss Rust's user-space runtime, how to use it, and what it can do.
1 What is the runtime?
The Rust runtime can be viewed as a collection of code which enables services like I/O, task spawning, TLS, etc. It's essentially an ephemeral collection of objects which enable programs to perform common tasks more easily. The actual implementation of the runtime itself is mostly a sparse set of opt-in primitives that are all self-contained and avoid leaking their abstractions into libraries.
The current runtime is the engine behind these features (not a comprehensive list):
I/O
Task spawning
Message passing
Task synchronization
Task-local storage
Logging
Task unwinding
And you overestimate how much people are going to care, but that's pretty typical of language hipsters. Every new language claims to solve all the problems of its predecessors. It's going to need far more of a pitch than that to get businesses to sink the years and countless amounts of money needed to rewrite all their software in Rust.
Because they lack any historical perspective like most language hipsters.
Rust? Pssssssh. Everyone knows all the language hipsters have already moved on to Nim.
What a joke. "Modern" languages allow all sorts of security exploits through. Such as this hilarious one involving Ruby on Rails.
Wrong. MySQL is ANSI. You just set a flag in my.cnf, and it is.
And most people don't set it. So trying to claim it is ANSI because of an optional flag that next to no one uses doesn't really cut it.
Yeah but they still got you to click the inane Dice.com clickbait.
What's infuriating is that USB drives used to come with hardware write switches and now you can't find them anywhere.
That's funny since a two-second Google search showed where I can find them on Amazon and Newegg.
A third possibility is that the NSA and their friends abroad might have pressured the manufacturers to remove these security features.
Which is not a possibility since my company ships hundreds of USB drives out with hardware write switches every week. They are extremely easy to find and buy.
The person who owns the site has full editorial control. Start your own site to talk about Mikee if it's such a big deal.