Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pietroalbini
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
Ferrocene 24.05.0
(ferrous-systems.com)
3 points
by
pietroalbini
2y ago
|
0 comments
2.
▲
by
pietroalbini
3y ago
We're working on that! Expect more news around it in the coming months.
3.
▲
Open Sourcing Ferrocene
(ferrous-systems.com)
77 points
by
pietroalbini
3y ago
|
19 comments
4.
▲
Security advisory for Cargo (CVE-2022-46176)
(blog.rust-lang.org)
7 points
by
pietroalbini
4y ago
|
0 comments
5.
▲
by
pietroalbini
4y ago
Note that this is just a first draft of the ferrocene spec, we aim to get it to a finished state by the end of the year!
6.
▲
by
pietroalbini
5y ago
The crates.io index is hosted on GitHub, but the application/API is hosted on Heroku (so in the us-east-1 AWS region) and the downloads on S3/CloudFront. And yes crates.io is currently impacted.
7.
▲
by
pietroalbini
5y ago
It's this research that prompted GitHub to show warnings, they didn't appear as of yesterday.
8.
▲
Rust 1.49.0
(blog.rust-lang.org)
241 points
by
pietroalbini
6y ago
|
111 comments
9.
▲
Rustup 1.23.0
(blog.rust-lang.org)
104 points
by
pietroalbini
6y ago
|
5 comments
10.
▲
Rust 1.48
(blog.rust-lang.org)
410 points
by
pietroalbini
6y ago
|
117 comments
11.
▲
Rust 1.46
(blog.rust-lang.org)
391 points
by
pietroalbini
6y ago
|
150 comments
12.
▲
by
pietroalbini
6y ago
Mozilla has had to reduce its investment in Rust significantly, but it’s not abandoning Rust. Mozilla has committed to financial and logistical support while we get the foundation up and running, and we expect they will become a sponsor onc
13.
▲
by
pietroalbini
6y ago
This is still a open question! We made no decision on the name yet.
14.
▲
Rust 1.45
(blog.rust-lang.org)
491 points
by
pietroalbini
6y ago
|
218 comments
15.
▲
by
pietroalbini
6y ago
That flag shouldn't be documented: it's completly unsupported and meant to be used only by the compiler. Please don't rely on it :)
16.
▲
Five Years of Rust
(blog.rust-lang.org)
293 points
by
pietroalbini
6y ago
|
125 comments
17.
▲
by
pietroalbini
6y ago
> to be able to block merging PRs on changes that accidentally impact LLVM's performance, like is currently the case for rustc. rustc's CI doesn't prevent merging PRs that impact performance: while the reviewer can request
18.
▲
Rust 1.41.1
(blog.rust-lang.org)
6 points
by
pietroalbini
7y ago
|
0 comments
19.
▲
Rust 1.41
(blog.rust-lang.org)
46 points
by
pietroalbini
7y ago
|
2 comments
20.
▲
by
pietroalbini
7y ago
Yeah, that's why I'd prefer for the Rust Foundation to be as lean as possible, explicitly excluding raising donations for the whole project and paying developers from its scope. Funding development could then be done by other enti
21.
▲
by
pietroalbini
7y ago
There are people inside Mozilla paid to work on the project full time. Not all of them are on the core team though.
22.
▲
Rust – Reducing support for 32-bit Apple targets
(blog.rust-lang.org)
32 points
by
pietroalbini
7y ago
|
18 comments
23.
▲
by
pietroalbini
7y ago
Well with RHEL 8 you can get a pretty up to date rustc, as they update the version in their stable repos every three months (so every two releases): https://developers.redhat.com/blog/2019/11/07/support-l
24.
▲
by
pietroalbini
7y ago
Rust doesn't have LTS releases. Editions are both a way to market the new features introduced in the past years as a "bundle" to outside users, and a way for us to introduce some breaking changes for the users opting into t
25.
▲
by
pietroalbini
7y ago
Yeah, I only counted releases implementing new features, not every single one (both for Rust - even though we have few point releases - and for the other languages). Also some compilers don't have a fixed release schedule, which made g
26.
▲
Shipping a compiler every six weeks
(pietroalbini.org)
184 points
by
pietroalbini
7y ago
|
21 comments
27.
▲
Async-await on stable Rust
(blog.rust-lang.org)
1102 points
by
pietroalbini
7y ago
|
380 comments
28.
▲
Rustup 1.20.0
(blog.rust-lang.org)
217 points
by
pietroalbini
7y ago
|
20 comments
29.
▲
by
pietroalbini
7y ago
Microsoft is already sponsoring our CI on Azure Pipelines, so there would be no need to do that.
30.
▲
by
pietroalbini
7y ago
By the way, we don't actually run our CI on AWS. We use S3 to store caches and build artifacts, but all the builds run on Azure Pipelines at the moment.
More ›