I think this got blown up right now due to how accessible it was.
However, I think it's clear that Pandora's box is now wide open and that you cannot close it. Sure, you can turn off that Grok integration, but the AI image generation capabilities are now widely available for basically anyone to use.
I wonder whether it'd be better to just "accept and live with it". I agree that this can cause a lot of harm, but I don't see a way where this can be outlawed and prosecuted in such a way that there's a net benefit for society. In the EU many have been battling proposals like Chat Control for the past decades not because they want to protect sex offenders, but because backdooring societies privacy on a grand scale is likely far more detrimental than the impact of sex offenders. (And here we aren't even talking about "real" CSAM content.)
> I wonder whether it'd be better to just "accept and live with it".
Big tech's approach of move fast, break things, and gain a sh** load of money and influence has cost the world so much over the past two decades. So much so that the post-WWII rules-based international order is under threat. We're on the verge of sliding back towards a world where might make right and the powerful gets to kill, beat, steal, and sexually abuse whoever they want whenever they want. Worse, with the help of technology, they get to entertain the masses by turning those horrific acts into social media content.
It's largely due to the acts of big tech that we got into this mess. But instead learning from this biggest mistake of our generation and taking proactive steps to prevent further harm, you propose that we all suck it up and accept whatever our tech billionaire overlords want to further inflict on this world? WTAF.
> proposals like Chat Control
Are you seriously comparing banning tools for openly forging nudes and sex pics of people to backdooring people's private communications?
I feel like we are already past the point where influential people have to play by the same rules as everyone else. I dislike this as much as 99% of the population, but I don't realistically see a remedy given how our governments (EU) are operating.
> Are you seriously comparing banning tools for openly forging nudes and sex pics of people to backdooring people's private communications?
I am not comparing these two things; I mentioned Chat Control as tackling CSAM is one of its main selling points. These forging tools are in the open and banning access and use of them is practically impossible. You could force platforms into setting up filters for public content, but this won't stop the nudes from being shared privately and likely still being accessible on the web _somewhere_. Just look at the bs on tiktok that's been publicly accessible and growing for years now...
IMHO public content filtering won't help much and the following steps will likely involve tapping into people's private content and messages. And this is where I draw the line.
The introduction of hamburger menus broken many of the Alt+Letter shortcut workflows. Even to this day, GNOME applications are hard to fully control via keyboard.
I'll never understand how this can be deemed acceptable from an accessibility standpoint.
I am wondering whether this would actually be a helpful compile option in upstream rustc for quick prototyping. I don't want prod code to use this, but if I want to try things out during development, this could substantially shorten the dev cycle.
After a while, you just don't write code that would cause substantial borrow-checker problems, even when prototyping. I'd say the slow compile times are much more of an impediment for a practicing Rust prototyper than the borrow checker.
Sometimes, you just need to know if an idea will even work or what it would look like. If you have to refactor half the codebase (true story for me once), it makes the change a much harder sell without showing some benefits. IE, it keeps you from discovering better optimizations because you have to pay the costs upfront.
In Rust, it's a lot easier to refactor half the codebase than it would be in another language. Once you're done fighting the compiler, you're usually done! instead of NEVER being sure if you did enough testing.
I don't know either. Personally I can spend days or more on exploratory efforts that end up scrapped. My source code is usually version controlled, so I never have to worry about messing things up. But I suppose not everyone has this kind of time for stuff that isn't guaranteed to pan out.
Sometimes I will prototype an exploration in another crate or module so I can see if there are performance gains in a more limited application. Sometimes these explorations will grow into a full rewrite that ends up better than if I had refactored.
> Sometimes, you just need to know if an idea will even work or what it would look like.
I think what GP is trying to say is that the value of such exploration might be limited if you end up with something incompatible with "proper" Rust anyways.
I suppose it depends on how frequently "transition through invalid Rust while experimenting and end up with valid Rust" happens instead of "transition through invalid Rust while experimenting and end up with invalid Rust", as well as how hard it is to fix the invalid Rust in the latter case.
In my case, I was adding a new admin api endpoint, which meant pulling through a bunch of stuff that was never meant for the api and got in a fight with the borrow checker. For me, I just wanted to see if I broke something on a feature level (it was never meant to be exposed by the api after all), and I didn’t care about memory safety at that point. Refactoring it properly just to get memory safety just to see what would have broke, ended up breaking out of my time-box, so it never saw the light of a merge request. Had I been able to prove the concept worked, I would have opened a PR and against the open issue to find out the best way to refactor it “properly” into a right way. As it was, I would need to completely guess what the right way was without ever even knowing if the idea would work in the first place.
I guess that doesn't neatly fall into the categories I described, though I think it's closer to the former than the latter.
That being said, I think what you describe sounds like a case where relaxed checks could be beneficial. It's the eternal tradeoff of requiring strong static checks, I suppose.
Can't you usually just throw some quick referenced counted cells in there, to make the borrow checker happy enough for a prototype without refactoring the whole code base?
My first coding experience was through the StarCraft 1 map editor. It offered a text-snippet-based scripting system to build rudimentary logic. It was relatively easy to pick up thanks to its documentation and localization.
After that, I played around with HTML/CSS which led me to building things in PHP as this was the go to language for implementing logic on the web.
Tcc even supports that with `#!/usr/local/bin/tcc -run`, although I don't understand people who use c or go for "scripting", when python, ruby, TCL or perl have much superior ergonomics.
This was a relatively old project that used a C program as build system / meta generator. All you needed was a working C compiler (and your shell to execute the first line). From there, it built and ran a program that generated various tables and some source code, followed by compiling the actual program. The final program used a runtime reflection system, which was set up by the generated tables and code from the first stage.
The main reason was to do all this without any dependencies beyond a C compiler and some POSIX standard library.
I'd say it's completely irresponsible to not have such features, claiming it's about security, rather than implementing it behind a permission system that puts the end-user in charge.
It is implemented behind a permission system. KScreenshot works perfectly fine and so will most of the applications using PipeWire I guess, same that screen captures.
KDE is merely saying that some applications will have to be updated to use it so all of the current screenshot applications won't work out of the box.
No idea of why some commenters here are implying screenshots don't work in Wayland. It seems their knowledge is somehow stuck at the first proof of concept ten years ago.
I was talking in general. It's less about screenshots and screen recording, but more about drag-and-drop and global hotkeys like push-to-talk in Discord.
Screen recording like screen sharing works perfectly fine with PipeWire.
Global hotkeys are also supported perfectly fine. Applications just need to register with the compositor, which will transfer the key press to them. That's the feature working at it should. It prevents applications from hijacking keys when that's not what you want.
The issue is that Discord takes ages to ship anything on Linux and barely supports anything and the Linux community does it's best to keep supporting everything. Other plateformes would have just mandated the new way ages ago and be done with the transition by now.
Dang. I had forgotten Zenimax got scooped up by MSFT Gaming a few years back. It's not an unreasonable request, though I suspect it should be made directly to MSFT Gaming.
By number of acquired studios, Microsoft is one of the biggest publishers, hence even if XBox the console goes bust, they still have a big weight as Microsoft Game Studios and XBox brand.
Let's be real for a moment. I just looked it up and found a playlist for the full Handmade Hero series which contains 696 videos. Adding up the total duration of the playlist gave me a time of 4726711 seconds, or 1313 hours.
Even for the most passionate of developers, you're gonna have a hard time getting someone to commit even a fraction of that time towards educational content.
If you think there are any specific videos from the Handmade Hero series that are really worth watching, you should recommend them directly. But pointing someone to 1300 hours of content is an absurd suggestion.
You don't watch the full playlist from start to finish. You start and keep watching until "you get it". Most of the foundational stuff is of course at the beginning. Feel free to pick the topics you find interesting, like allocations, etc.
There's a sizable community around Handmade Hero which can point you to more specific topics.
However, I think it's clear that Pandora's box is now wide open and that you cannot close it. Sure, you can turn off that Grok integration, but the AI image generation capabilities are now widely available for basically anyone to use.
I wonder whether it'd be better to just "accept and live with it". I agree that this can cause a lot of harm, but I don't see a way where this can be outlawed and prosecuted in such a way that there's a net benefit for society. In the EU many have been battling proposals like Chat Control for the past decades not because they want to protect sex offenders, but because backdooring societies privacy on a grand scale is likely far more detrimental than the impact of sex offenders. (And here we aren't even talking about "real" CSAM content.)
reply