And of course, it's hosted on the site run by the company that's going bollocks to the wallocks with ai and GPL violations, because we hate humanity. Yep.
Still, interesting development. Not sure if this will be a LibreOffice or a Glimpse yet, but time will tell.
Addendum: Yeah, this isn't exactly new. Gotta love the HN hype cycle ;)
This December, instead of doing the Advent of Code, I will try to pack “100 days of SwiftUI” inside the last 31 days of the year. I’ve never written any Swift, and my only mobile experience was with React Native in 2017, so this should be fun!
Hi! Do you do #gamedev in #rustlang (#bevy or not) and have cool gameplay footage to show off?
I've gotten a request from the #RustNL organizers for clips to roll between talks! This seems like a fun idea, so I'm putting out a call for short, appealing gameplay clips with some form of credits on them. Get them to me (maybe post them as a reply?) within the next 24-48 hours and I'll get them to the organizers.
#RustLang / #Cargo builds seem to run very slow on my #Framework AMD system. They didn't take anywhere near as long on my old Intel system. Looking at btop it only seems to use one thread during #compile, am I missing something?
I understand that shadowing in scope change is a good practice and an idea, but on the same level 🤯
Does it have any reasons to have a feature to initialize new variable with the same name in the same scope?
I'm so confused why my #rust function takes so long to return. I have an Instant::now() before the call, I have an Instant::now() in the very start of the method, it does a lot of stuff, I println the method's Instant elapsed.as_micros(), return the Result<Vec<T>> with one small item in it, and finally println the outer Instant elapsed.as_micros(). I'm seeing an extra 7,000 microseconds between both of them. Why?? #rustlang
Any suggestions on how to do proper performance tuning with Rust would be appreciated.
I generally like #rustlang but I think every project developer should be forced to use it on a Raspberry Pi with 4GB RAM... had to build Vaultwarden (https://github.com/dani-garcia/vaultwarden) on one, and man,,, after 15 minutes compilation is no longer running because the device went OOM and now is so hot the fan is louder that a datacenter server...
Just to be clear, I think this is a Rust problem, not a project problem.
Decided to try and compare the general base program size of several languages. I wrote a handful of Hello World programs, and stripped them of everything. Here's the final results in KiB:
It's time for a #bevymergetrain before I go stare at the sun 🤩 After a bit of time catching up on my own reviews, @bevy has 10 open community-approved PRs in the backlog. Interested in #gamedev, #rustlang or #foss? Come see how the sausage is made as I go over my reasoning for what to merge and why.
Current status: I opened about 100 links to articles and threads from Google results comparing #ruby, #golang and #rustlang and I'm planning to read them 🫠
(no, I'm not really considering Go, mostly just trying to convince myself that I'm not making a mistake starting to learn Rust and not Go 🦀😛)
I'm trying to decide if the simplicity of just making every struct field public in #rustlang, actually worth the risk of people/future me, not using the constructors and/or adding mut and changing the validity guarantees that come with using constructors or transformers that are accompanied by the struct.
New blog post: on that time when I decided that if being able to panic one Rust program is good, then a feature that lets you panic other programs would be better, right?
No, really, it's awesome. Here's Hubris's oddest syscall.
Happy #bevymergetrain :) The other maintainers have been doing a great job staying on top of our #rustlang PRs for #bevy, so there's only 7 in our backlog to review and merge this week. I've been busy and stressed with life in the past week, so it's much appreciated. Let's take a look!
Super exciting to have the bandwidth to start putting my plans into motion. I decided that I want to do a daily status update in engine-dev, and let folks track my current areas of focus using a GitHub project board.
It's fascinating to me looking at beginning language guides and thinking "what does this say about the culture of the language"
When I was delving into #OCaml it was (with affection) "here's hello world and here's a dense academic paper on implementing event systems in OCaml 5!"
#Java guides used to be centered on the assumption that you were a web programmer looking to do applets, even long after that assumption died.
#RustLang generally seems to assume a background in programming w/ a CLI.
I got #diesel running in #RustRover with #rustlang. The experience is what you'd expect from an ORM—pretty smooth and nice. I like this. I'll have to use this with a web app next.
It also works great with the built-in database tools in RustRover.
Sometimes I wish that rustc had a database of small breaking changes that affect only a handful of crates, so that we could on the fly patch them going forward. Things like "we now correctly check for lifetimes in assoc types" can technically be a breaking change that affects a handful of crates, but I want to ensure that building a project from today in 15 years doesn't require a compiler tool chain from today.
I guess this is the windows backwards compatibility approach. #rust#rustlang