Technology
News community around technology, social media platforms, information technology and governmental policy surrounding it.
What doesn't fit here?
The core of the story has to be technology focused.
- If article mentions "AI" in a sentence and then talks about business economics that doesn't make it tech news.
- Gaming is too many layers removed from technology. There are many dedicated communities that are a better fit for it.
- Transporation is too many layers removed from technology. EVs while use many cool technologies have many dedicated communities that are a better fit for it.
- Entertainment is too many layers removed from technology. While sometimes it can fit here, business or cultural aspects of it are a better fit for dedicated communities.
- Cybersecurity. While it heavily focuses on technology, most of the time it's too technical for most people who are not already invested in it. Should be posted in a dedicated communities unless it has broader connection to other tech areas.
Post guidelines
Title format
Post title should mirror the news source title. If you don't like the title of article, look for an alternative source instead of editorializing it.
URL format
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
[Opinion] prefix
Opinion (op-ed) articles must use [Opinion] prefix before the title. Opinion articles refer to articles that their publisher doesn't explictly endorse.
Country prefix
Country prefix can be added to the title with a separator (|, :, etc.) if the news is from a local publisher who doesn't clearly mention the country.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
7. Instance rules may apply
If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.
Companion communities
!globalnews@lemmy.zip
!interestingshare@lemmy.zip
Icon attribution | Banner attribution
If someone is interested in moderating this community, message @brikox@lemmy.zip.
view the rest of the comments
Rust apps seem to always be on the heavy side, maybe depends how much debug info they leave in
Indeed, they’re probably shipping a backtrace symboliser, and since there’s no system-wide equivalent of libc to link against, they’ll be including the entire Rust standard library with the binary too.
My other hunch is the Krisp noise cancellation ML model is a huge chunk of the memory footprint.
Krisp shouldn't be running when you ain't on a VC tho, I neve use VCs tbh and still get crazy numbers
I once played around with reverse engineering a Rust program. I compiled the optimized version of the standard "hello world" program which somehow turned into 50,000 lines of assembly.
It looked like it copied over dozens of functions from libc and the data section was filled with every single possible error string "file not found", "connection timed out", etc. as if there was a possibility of hello world generating an access denied error.
Was your C
hello worldprogram statically linked? I believe Rust includes its libraries whereas the typicalhello worlddoes not. Static linkage generally brings in large amounts of unused code.Rust has static linking, you get the necessary (and some unnecessary) parts of the standard library in your binary instead of the user having to install the library the way you have to have a libc installed. Makes for fatter binaries but much easier compatibility.