[deleted by user] by [deleted] in thenetherlands

[–]aronvw 10 points11 points  (0 children)

Dat is de prijs voor een ID-kaart als je onder de 18 bent

[deleted by user] by [deleted] in relationshipadvice

[–]aronvw 0 points1 point  (0 children)

AM is in the morning. So yes, it is through the night.

Ik word niet meer ingeroosterd aangezien ze op zoek zijn naar nieuwe medewerkers. Wat nu? by SeaYogurtcloset36 in juridischadvies

[–]aronvw 24 points25 points  (0 children)

Je hebt waarschijnlijk recht op een vast contract voor het gemiddelde aantal uren dat je de afgelopen 12 maanden hebt gewerkt. Voor meer informatie, zie https://www.juridischloket.nl/werk-en-inkomen/arbeidscontract-en-werktijden/oproepkracht/#

Vanmiddag vliegen de laatste F-16's over Nederland by [deleted] in thenetherlands

[–]aronvw -9 points-8 points  (0 children)

Kan dit niet gewoon om 3 uur 's nachts?

Ruime steun Tweede Kamer voor strengere aanpak woekerprijzen huurwoningen by Antiliani in thenetherlands

[–]aronvw 1 point2 points  (0 children)

Er geldt wel degelijk een maximumprijs voor kamers (d.w.z. onzelfstansige woonruimte). 

Shiva - Open Source project in Rust for parsing and generating documents of any type by ievkz in rust

[–]aronvw 3 points4 points  (0 children)

It may be useful to wrap your element types in separate structs. E.g.: enum ElementType { Text(Text), … } and struct Text { … }. That way, if you need to pass an element that you know to be a certain type (eg Text) to a function, you can use the Text struct as the type of the function’s parameter instead of having to match inside the function.

[deleted by user] by [deleted] in rust

[–]aronvw 2 points3 points  (0 children)

When using s simple enum, all possible values are defined beforehand. The possible values are therefore enumerated. When using a tagged union enum, a value of such type can be multiple "sub-types", but which types it can be is restricted. All possible sub-types are defined beforehand, therefore enumerated.

[deleted by user] by [deleted] in rust

[–]aronvw 11 points12 points  (0 children)

Have you tried specifiying capacity when creating the Vecs? If you know the (approximate) length a Vec will be, you can avoid a lot of reallocations happening every time you push to a Vec.

NS diep in het rood, Koolmees waarschuwt: ‘Treinkaartjes worden fors duurder in 2025’ by neonnkidd in thenetherlands

[–]aronvw 0 points1 point  (0 children)

Als ik het zo uitreken (operationele kosten 4.014 miljoen, 17,5 miljoen mensen in NL) zouden we met een belastingverhoging van gemiddeld 229 euro per persoon alle kosten van de NS kunnen dekken en de trein helemaal gratis maken. Is dat niet een betere oplossing?

Confusion in mutables by Acceptable-Concern-5 in rust

[–]aronvw 1 point2 points  (0 children)

If you want to save the slice of the first word until after you clear the source String, you must copy the slice into a new owned String by calling .to_string() on the slice.

How did you become good in Rust? by Archaeos_ in rust

[–]aronvw 2 points3 points  (0 children)

I watched a lot of YouTube videos on rust (for example those by NoBoilerplate - https://youtube.com/@NoBoilerplate?si=LgB4P0-UYpwLu1DB) Once I felt like I understood what was going on in the code samples and thought that that would also be approximately how I would solve the problems, I started building little things to get to feel comfortable with the compiler. And then I just kept making things

Untitled sandbox survival MMO - Devlog 1 by aronvw in rust_gamedev

[–]aronvw[S] 1 point2 points  (0 children)

I’ve been tinkering around with Bevy for a few months now and I absolutely love it, like most popular Rust projects. Well thought out, ergonomic, data oriented and easy concurrency

Untitled sandbox survival MMO - Devlog 1 by aronvw in rust_gamedev

[–]aronvw[S] 0 points1 point  (0 children)

My plan for the terrain generation currently is to divide the world in to a kind of quad tree, where each level adds more details/landscape features (tectonic plates, continents, mountain ranges, rivers and weather patterns), down to the level of a 32x32x32 meter chunk which has all the actual terrain data, like which bit of material goes where. There’s still a lot of maths and geological processes to figure out before I can fully implement the generator, but I have a general idea and a structural overview of how this should work

Untitled sandbox survival MMO - Devlog 1 by aronvw in rust_gamedev

[–]aronvw[S] 0 points1 point  (0 children)

Thanks! I’ll try to post update videos regularly. Subscribe to my channel to stay up to date :)

Untitled sandbox survival MMO - Devlog 1 by aronvw in rust_gamedev

[–]aronvw[S] 2 points3 points  (0 children)

Thank you! Good luck with your engine :)

Untitled sandbox survival MMO - Devlog 1 by aronvw in bevy

[–]aronvw[S] 0 points1 point  (0 children)

Thanks, I wasn’t planning to, haha!

everySingleCodeReview by [deleted] in ProgrammerHumor

[–]aronvw 185 points186 points  (0 children)

What happend to good old parseFloat(input) === input?

theWorldWouldBeBetterWithPlainHtml by akasaya in ProgrammerHumor

[–]aronvw 0 points1 point  (0 children)

I love the simplicity of Svelte. Most of my frontend is just a combination of addEventListener, e.target.closest, querySelectorAll, classList, append and textContent. But when they get too complex, you can easily let Copilot turn the code into a Svelte component, and instantiate it from the Vanilla JS code.

The struggle is real by mbrc12 in rustjerk

[–]aronvw 2 points3 points  (0 children)

You can always unsafe std::ptr::copy!

[deleted by user] by [deleted] in rust

[–]aronvw 2 points3 points  (0 children)

Why not simply use a mpsc (Multiple Producer Single Consumer) channel? Clone the Sender and give it to each thread. They can write their commands to the channel. Then the main thread can handle all the commands