Search
Items tagged with: Rust
@folkertdev is presenting about zlib-rs in his talk 'Compression Carcinized: Drop-in Compatible Compression in Rust' at the @gosim conference in Beijing on Thursday:
"Data compression is used when loading almost anything on the web. This talk is about how we implement zlib-rs and other compression algorithms in Rust so that they are drop-in compatible with their C equivalent."
The GOSIM Conference | October 17-18 - Beijing, China
The GOSIM Conference, October 17-18 - Beijing, China. A confluence of minds from various spheres of the open-source domain, offering a deep dive into the world of open source technology trends, strategies, governance, and best practices.china2024.gosim.org
🐸 📺 Live-Streams (+Re-Live) – FrOSCon 19 (Free and Open Source Software Conference)
streaming.media.ccc.de/froscon…
Programm und "Thematische Schwerpunkte
Wir bieten Vorträge zu aktuellen Entwicklungen aus dem gesamten Bereich der Freien Software und Open Source. Regelmäßig mit dabei sind z.B. die folgenden Themen:
- Betriebssysteme
- Entwicklung
- Administration
- #Sicherheit
- Rechtliche Fragen
- Desktop
- #Bildung
- Cloud
Jedes Jahr haben wir auch besondere Schwerpunkte. Für 2024 sind das:
- In #Rust we trust – Memory safe languages
- Grow your own – Open Source #Pflanzenbau
- #SBOM – Lieferkettensicherheit in OSS
- Thinking outside the stack – eBPF und Freunde
- Bridging the Gap between politics and reality – Lobbying für freie Software
- AI AI, captain – #LLM, machine learning & Co."
In the fresh report "Investing in #Rust" by Shane Miller yours truly is quoted several times.
https://www.lawfaremedia.org/article/investing-in-rust
Investing in Rust
U.S. public policy can help facilitate market adoption of a relatively new, efficient, and safe programming language called Rust.Default
Heute stellen wir Ihnen unsere neue Rubrik 5 Fragen zu... vor. Den Anfang machen wir mit 5 Fragen zu #Rust an den Software Engineer Daniél Kerkmann!
Lesen Sie in unserem Beitrag, warum wir bei #Opentalk auf die #Programmiersprache Rust setzen, welchen Einfluss Rust auf unsere technische Architektur hat und Antworten auf drei weitere spannende Fragen 👇
https://opentalk.eu/de/news/5-fragen-zum-einsatz-der-programmiersprache-rust-bei-opentalk
#OpenSource #digitaleSouveränität #techstack #tech #programming #RustLang
5 Fragen zum Einsatz der Programmiersprache Rust bei OpenTalk
Erfahren Sie von unseren Expert:innen in jeder Folge Wissenswertes zu aktuellen Themen rund um Videokonferenzen und digitaler Souveränität.OpenTalk
A few days ago, I started working at cargo-rpmstatus, a utility to check the #packaging status of the dependency tree in #fedora repositories.
Now it is also available via Copr.
$ dnf copr enable dmorawetz/cargo-rpmstatus
$ dnf install cargo-rpmstatus
Check it out and please provide me some feedback to plan the next steps.
https://github.com/dmorawetz/cargo-rpmstatus
GitHub - dmorawetz/cargo-rpmstatus: cargo-tree for fedora packaging
cargo-tree for fedora packaging . Contribute to dmorawetz/cargo-rpmstatus development by creating an account on GitHub.GitHub
Rust 101 - 1: Course intro
Introducing the Rust 101 series and how to install Rust.
Rust 101 is a series of videos explaining how to write programs in Rust.
How to install Rust: https://rustup.rs/
Slides: http://artificialworlds.net/presentations/rust-101/0-intro
Exercises: https://101-rs.tweede.golf/0-install/mod.html
Follow the "Exercises" link to find the other tools you might want to install to follow along.
The course materials for this series are developed by tweede golf. You can find more information at https://github.com/tweedegolf/101-rs and you can sponsor the work at https://github.com/sponsors/tweedegolf . They are released under the Creative Commons Attribution Share Alike 4.0 International license.
This series of videos is copyright 2023 Andy Balaam and the tweede golf contributors and is released under the Creative Commons Attribution Share Alike 4.0 International license.
GitHub - tweedegolf/teach-rs: A modular, reusable university course for Rust
A modular, reusable university course for Rust. Contribute to tweedegolf/teach-rs development by creating an account on GitHub.GitHub
Finally decided to learn rust... Any tips or warnings before I really start?
Hm...I'm getting the impression that #Rust is increasingly met with a refusal by some people (it's an almost _hateful_ attitude sometimes).
I wonder why. Of course there are a lot of layers to it, but one is definitely that Rust has gotten a lot more exposure to people and so there are just a lot more potential `match`es that lead to Err(()) and that's Ok(()) (sorry, pun intended).
But I wonder, if there's more to it than what meets the eye (feeling excluded/alienated/left behind?).
What’s the most idiomatic way of testing that a #Rust function returns the correct error enum variant? I’ve been using this pattern as it doesn’t require the error enum to be PartialEq:
Edit: Thank you everyone for suggesting the matches! macro (https://doc.rust-lang.org/std/macro.matches.html), which I somehow wasn’t aware of 🤦🏻♀️
matches in std - Rust
Returns whether the given expression matches any of the given patterns.doc.rust-lang.org
What are the alternatives to VS Code and Jetbrains' IDEs?
I'm asking because I don't like Jetbrains' push for AI and don't want to switch to Code.
Day 36 of #100DaysOfRust
Oh well, now I've moved on from "Hello, world!" in #development with #Rust to a simple form #web page. In that sense I've learned a lot, although very slowly, because I'm not mentally fit today. I still learn a lot every time I do the #RustLang. Well, then I'll configure the #Helix editor first so that I like it and it's easy for me to use 🧬🦀
Day 35 of #100DaysOfRust
Today I didn't make as much progress as I would have liked in learning #Rust. I was recommended to change the #web framework (see comments from Toot above), I followed the tip! So I only have a rudimentary understanding of #RustLang, I had to read up on it, whether it was me or not I don't know - thanks a lot @mo8it for your help! I have at least typed "Hello, world!" and run it correctly. Albeit slowly, but progress is being made🦀
Day 34 of #100DaysOfRust
Wow, today I finished the #Rust basic course and immediately started with the first lesson on #ActixWeb and programmed "Hello world!" & "Hey there!". I was immediately very #motivated and will continue accordingly. But the first thing I'm thinking about is what the interactive #website should be. Because only with one goal is the motivation to learn #RustLang available ⚙️🦀
Day 33 of #100DaysOfRust
I continued learning #Rust today and am almost at the end of the basic course. It's "tedious" for me now because I don't really understand it yet. That means I'll have to look at a lot of things again in the future to deepen my #knowledge. On the other hand, it is fun to #program a web server to learn the program #procedure more directly. But I knew from the start that you don't learn #RustLang in a hurry 🦀
Day 31 && 32 of #100DaysOfRust
Yesterday I was only able to learn a little more, but I finished a chapter. Today I finished a chapter in which I set up a very simple #web server using #Rust. It's really exciting and I was able to deepen my knowledge of #RustLang. It's really fun and #motivated me. Of course, learning is not finished after the basic course, but it prepares you to learn in practice and expand your knowledge 🦀
Day 30 of #100DaysOfRust
I'm getting closer to complete basic #Rust learning and it's getting more difficult for me. Well, I was also told that 'traits' is a strange thing that you don't always have to use. It's good that I know about it, but if I really use it then I'll probably have to read up again. The other side for 'advanced types' and I'm not kidding myself about that. I only really learn it after when I use #RustLang, not just when I'm learning 🦀
Day 29 of #100DaysOfRust
I have now returned to learning #Rust in addition to the workload between the #holiday's. Today I learned how to integrate C solutions, for example, via an '#Unsafe Rust'. I hope not to have to use it in the future or even use libraries that need it - the #future will tell. But still, it's good to have this #knowledge, for use or for criticism. I certainly don't have the #RustLang learning foundation behind me before the end of this year 🦀
Day 28 of #100DaysOfRust
I didn't learn _ but their use as well as _meaning and what @ does what where. I worked on this chapter for a relatively long time, but in my opinion it was a profound #Rust specialty that allowed me to use it in a targeted manner. Slowly but surely I'm coming to the end of learning the basics of #RustLang, I'll learn how to use it in the next selected project. But first complete the current basic learning! 🦀
Day 27 of #100DaysOfRust
Yesterday I took a break from learning #Rust. Today I continued learning #RustLang in the morning. Then I did the #37c3 watched some interesting shows #online. Now doing the two things in parallel is almost impossible for me, so I'm getting to the end of the introductory course a little slower. That's OK for me, both are very lively. Tomorrow will be similar 😃🦀
Day 26 of #100DaysOfRust
I found time today to continue learning #Rust. Although I knew that #RustLang is not fundamentally object-oriented (#OOP), I learned this approach today. It seemed a bit strange to me and I didn't quite understand it. Maybe you should go over that paragraph again. Basically, I know that for future projects, I need to look back and see how I solve the problem. That's the case in any #programming language to solidify your skills 🦀
Day 25 of #100DaysOfRust
I was celebrating with my family before #Christmas (yes, it's already here today) and I was still learning #Rust. Two things were illuminating for me: The capitalization is relevant, I knew it before but I really had to find it before I went through the corresponding tests. Secondly, I learned 'traid objects', a cool way of working. I got further than expected and learned on #RustLang what I can use for the next project 🦀
Day 24 of #100DaysOfRust
Today I made exciting progress in learning how to program #Rust. How to deal with data when you have to / should edit and change / adapt several at once. That was really fun and I tried out a little more than just the given code. Tomorrow I'll continue and maybe take a break to learn #RustLang because of the holidays 🦀
Day 23 of #100DaysOfRust
Phew... I'm 3/4 of the way through the basic course at #Rust. It's taking me longer than I thought but it's not too bad. I also realize that after the basics, the learning really begins in a project. For the subsequent #RustLang project, I've already given it some thought. So far it's going well and I've decided to learn all the basics before I start a project 🦀
Day 20 && 21 && 22 of #100DaysOfRust
The day before yesterday, yesterday and today I worked more to learn on the #Rust basics. I found it more difficult because I am not yet familiar with it. But I'll see how I implement this in the project. In my planned project, I will really learn what to use where and how exactly. Only then will I really learn the #RustLang practice 🦀
Day 19 of #100DaysOfRust
Today I learned more about #Cargo and better understood how to use it in my project. I also had another look around on https://crates.io to see what was available that I was interested in.
I'm already relatively far along in my learning #Rust but certainly not finished yet. I think I should first learn the #RustLang basics completely, then start a project and then keep checking back. It's definitely not boring for me! 🦀
Day 18 of #100DaysOfRust
What I didn't quite understand yesterday, I realized today why this exists. Put simply, this is just a function that is only used at one logic point and is a nameless function. Even as I delve deeper and deeper into the subject of #Rust, the more I see that it is only through a real project that we really #learn how to handle and use it 🦀
#100daysofcode #learning #coding #rustlang #project #code #understand
Day 17 of #100DaysOfRust
Today I had learned more #Rust in detail again but had difficulties understanding certain things in detail. Well, there is that and I may have to repeat it again. Despite everything, I am positive about it. I now have about half of the basic learning behind me, but I will only see it efficiently when I start my first #project. Only then will I really be able to learn #RustLang in practice. That's life and knowledge, not smart aleckery 🦀
Day 16 of #100DaysOfRust
I got further with learning #RustLang today, but not as far as I would have liked. So that I really understand the reason for the #Rust code, I took the time to understand it completely. It was still positive for me to combine all the details I've learned so far and create something working. At least mentally it was a success. Not just an action that can do something, but a program with its own tests 🦀
#100daysofcode #learning #code #understanding #like #programming
Day 15 of #100DaysOfRust
Yesterday I was unfortunately unable to continue learning #Rust due to my schedule, but today I was able to do so all the more. Today I got through the #RustLang training very comfortably. All the #code tools I #learn'ed earlier were used together in the chapter and at the end they were neatly divided into files. It is getting closer and closer to the development of real programs. […] 1/2
Day 14 of #100DaysOfRust
First of all, I didn't make as much progress today as I would like, but that's normal and shouldn't be criticized, because learning is progressing.
Before, I had only learned basics and code was generally short. Now I'm in the middle of learning a similar example, but it's a whole program. This is fun and shows me how the code methods are connected together 🦀
#100daysofcode #learning #learn #code #rust #rustlang #fun #progressive