Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

April 2024 #116

Closed
3 of 7 tasks
kawogi opened this issue Mar 17, 2024 · 7 comments
Closed
3 of 7 tasks

April 2024 #116

kawogi opened this issue Mar 17, 2024 · 7 comments

Comments

@kawogi
Copy link
Collaborator

kawogi commented Mar 17, 2024

ToDo

  • [#] Settle for a date and location: Wednesday 2024-04-10, 19:15 CEST at C4 (default: first Wednesday each month)
  • Send "Save the Date" info (with link to this ticket)
  • Basic Agenda (default: Open Space)
  • Final invitation (deadline 2023-04-10 T - 1 week)

Invitation draft

This Month In Rust, April

(The meetup will likely be held in German but we'll switch to English if needed.)

Dear Rustacean,

our next Meetup will be on Wednesday 2024-04-10, 19:15 CEST.

You're new to Rust, tried it out with some private projects or are already working professionally with it for years? You're in good company! Whether you want to speed up your python code, write a web service, need interop with your C++-codebase, cross-compile for a microcontroller, write an emulator, … we've got you covered!

We commonly open up with a brief summary of noteworthy changes in the Rust ecosystem. Be it updates to the language itself, public events, its impact on other projects and languages, …

After that we often have volunteers talking about specific topics or personal projects, but in general the remaining time is about whatever you want to talk about!

Always wanted to know why Rust is harder to learn than other popular languages or why it lacks a certain feature? When is it appropriate to rewrite a project in Rust? Is the compiler really that slow and are the binaries really that big? Do all those safety guarantees have an impact on the performance? Fetch a drink and let's find it out.

You can register here.

See you soon!

Yours,
Florian and Kai


If you have a topic you'd like to talk about, please let us know in advance. This way we can make sure there's a time slot for you and maybe announce it officially. Thank you.

Rust News

  • Rust 1.77.0
    • Blog Post
    • Release Notes
    • C-string literals: c"hello world" with type &'static CStr
    • async functions can now be called recursively (if their type does not become recursive as a consequence)
    • offset_of!(StructName, field)
    • strip by default in release profiles (libstd is shipped with debug symbols)
  • Rust 1.77.1
    • Disables stripping for MSVC windows (apparently always uses a separate file anyway)
  • Rust 1.77.2
    • CVE: Command arguments not sufficiently escaped on Windows
    • Windows API + cmd.exe weirdness
    • Context
@kawogi
Copy link
Collaborator Author

kawogi commented Mar 18, 2024

@Florob I won't be able to attend on the 3rd of April.
I could be there on the 10th of April, but if any preparation from my side is needed I have to complete it during the course of the upcoming week.

Maybe just an open space with an improved description?

@Florob
Copy link
Collaborator

Florob commented Mar 18, 2024

@kawogi I'd be more than happy to move it up to the 10th. That way I also don't have a meeting immediately preceding the meetup. I'll confirm with the space tomorrow, but since the conflicting meetup no longer exists I don't think it'll be a problem.
We can try open space with improved description. Would you want to draft an invitation for that?

@Florob
Copy link
Collaborator

Florob commented Mar 21, 2024

Forgot to update this issue. As expected we can do April 10th.

@kawogi
Copy link
Collaborator Author

kawogi commented Mar 23, 2024

@Florob I took the liberty to suggest something completely new from scratch and your feedback is appreciated.

The general structure is (even though it's mostly obvious):

  • metadata (date, topic)
  • appetizer
  • agenda (transitioning from formal to open space)
  • invitation
  • footer

I tried to include some common topics, interests and pre-Rust experiences to make it easier for people to check whether this their cup of tea and maybe lower the bar to participate. The examples aim to make it interesting, yet generic enough to not have the obligation to prepare anything specific.

If we have a talk to offer it should easily fit into the draft without having to re-write the most of it.

I removed the COVID-disclaimer because the topic didn't come up in the recent months. OTOH I added a general invitation to support us with talks.

I removed the markdown-codeblock so that it's easier to preview on GitHub.

I moved the language selection algorithm to the top to hopefully lower the barrier for people who feel their English skills might not be sufficient.

@kawogi
Copy link
Collaborator Author

kawogi commented Mar 23, 2024

Do you want to permanently move to the second Wednesday if that's less stressful for you?

@kawogi
Copy link
Collaborator Author

kawogi commented Mar 27, 2024

@Florob Can I get your feedback soon?

@Florob
Copy link
Collaborator

Florob commented Mar 27, 2024

@Florob Can I get your feedback soon?

@kawogi Sorry, my days have been rather long lately. I like the text. Thank you for putting in the time. I'm not entirely sure what the general part and the meetup specific bit is, but we can discuss that at another time.

Do you want to permanently move to the second Wednesday if that's less stressful for you?

I thought about that, but since one is "every other week" and the other "every nth Wednesday" it turns out that wouldn't really change much long term.

@kawogi kawogi closed this as completed Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants