fix rust language

remotes/1693055039339581669/master
Igor Laborie 5 years ago
parent 1f10d40b0f
commit 166a818266
  1. 11
      content/sessions/rust_as_a_high_level_langage.md
  2. 2
      static/api/site.json
  3. 23
      static/schedule/schedule.ics

@ -13,4 +13,13 @@ videoId: null
presentation: null presentation: null
draft: false draft: false
--- ---
If the new React Context API and Suspense killed Redux (they didn't), surely Hooks kill the need for a form library, right? Well, not exactly. Managing form state is more than just holding your current values in state; it's about sync and async validation errors, and much more! But that doesn't mean that Hooks are irrelevant to the situation. Hooks make building forms in React easier than ever before. The singe most important feature of Rust is memory safety. Writing code with performance of C++, at a typical development cost, and with guaranteed absence of certain classes of memory safety related vulnerabilities is something that was not possible before.
However, all popular managed languages with garbage collection take memory safety for granted, so this aspect of Rust doesn't bring anything new to the table, if you already use Java or Go. Nevertheless, Rust can be an interesting choice as a high-level language, and this talks explains way.
The focus of the talk is fearless concurrency. Data races are a pervasive and unsolved problem in languages like Java and Rust's guaranteed thread safety is a liberating experience for application development. We also touch on some other benefits of the language for high-level tasks:
* predictable performance due to absence of garbage collection
* control over the memory layout of objects, which gives you extra performance if you need it
* module (crate) system that, at the language level, prevents dependency hell
* additional correctness guarantees, like the absence of iterator validation or strict control of error conditions

File diff suppressed because one or more lines are too long

@ -433,12 +433,23 @@ TRANSP:TRANSPARENT
CATEGORIES:_wtf CATEGORIES:_wtf
END:VEVENT END:VEVENT
BEGIN:VEVENT BEGIN:VEVENT
DESCRIPTION:If the new React Context API and Suspense killed Redux (they di DESCRIPTION:The singe most important feature of Rust is memory safety. Writ
dn't)\, surely Hooks kill the need for a form library\, right? Well\, not e ing code with performance of C++\, at a typical development cost\, and with
xactly. Managing form state is more than just holding your current values i guaranteed absence of certain classes of memory safety related vulnerabili
n state\; it's about sync and async validation errors\, and much more! But ties is something that was not possible before. \n\nHowever\, all popular m
that doesn't mean that Hooks are irrelevant to the situation. Hooks make bu anaged languages with garbage collection take memory safety for granted\, s
ilding forms in React easier than ever before. o this aspect of Rust doesn't bring anything new to the table\, if you alre
ady use Java or Go. Nevertheless\, Rust can be an interesting choice as a h
igh-level language\, and this talks explains way. \n\nThe focus of the tal
k is fearless concurrency. Data races are a pervasive and unsolved problem
in languages like Java and Rust's guaranteed thread safety is a liberating
experience for application development. We also touch on some other benefit
s of the language for high-level tasks:\n\n* predictable performance due to
absence of garbage collection\n* control over the memory layout of objec
ts\, which gives you extra performance if you need it\n* module (crate) sy
stem that\, at the language level\, prevents dependency hell\n* additional
correctness guarantees\, like the absence of iterator validation or strict
control of error conditions
DTSTART:20191003T110000 DTSTART:20191003T110000
DURATION:PT40M DURATION:PT40M
LOCATION:SII LOCATION:SII

Loading…
Cancel
Save