I said it a while ago and it’s getting much closer now: Linux will become the OS for people who want to game on a Mac. With all the work going into this, hopefully the devs are getting nice donations. They seem to be doing a better job than Malus at getting games to run.
Even the creators of languages don’t know their own languages 100%. I wouldn’t even call them the limit. So, I’m good enough in my main language that a lot of code doesn’t surprise me. And I try very hard to write code that others can understand as well when in a team.
That’s worthy of a bug report…
What do the accounts do? I’m not sure what they are…
Growing up with too much available goods makes people like this. People throw away food like it’s nothing, it was only a matter of time until people did this with phones.
Are what point do they stop pretending and just make it a pure linux platform with a different packaging format for any linux app to run in? They are doing it with CROS (or whatever the new Chrome on Linux OS is being called) and maybe it’s time to do it with Android. Running a VM just seems quite wasteful.
You know, if they used the PR workflow with a CI that enforced standardised commit messages, this could be quite easily solved? Forcing everything through a mailing list seems to create more work for maintainers…
Not sure I understand this. Is it a watch clippy? Or a completely new tool? If it’s new, what does it provide over clippy?
Your post is nearly the epitome of Chesterton’s Fence. You don’t seem to understand why Rust looks the way it does, works the way it does, why it exists, what it’s used for, and what problems it solves, but you’re very happy (or not, which is probably why you wrote this post) to trash it.
There are many responses to your comments that explain things quite well, yet, from what I see, you do not seem to concentrate on those.
And what I quoted is just the icing on top. It looks very much like you have one style of programming and approaching problems (the PHP style of “if it runs, it’s good”) and apply it to every problem. You have used a hammer your whole life and every problem looks like a nail. You can build a good many things with duct tape, nails, and a hammer. It might all do the job well enough for your standards or purposes and at times it might even be the perfect tool for a task.
But now you’ve discovered a screw driver, tried to hammer in a nail, and gotten quite frustrated that it didn’t work well. Instead of considering using a screw, you have tossed aside the screwdriver and decided to yell expletives into the ether.
The ether has responded with explanations, but you have chosen to ignore them all and staunchly hold on to your “screwdrivers are shit” conclusion. Had you said “I’m just blowing off steam, don’t take this seriously”, that’s what it would’ve been. However, you seem quite serious. Or, as I said before, you’re just trolling.
Oh but in rust you learn more about computers/low level concepts, you’re just not good at coding”
Who cares? Coding is a tool to get shit done and I think devs forget this way too often, like if one works easier than the other why does learning lower level stuff matter?
This is pure junior energy. Or trolling, I honestly can’t tell.
56 characters is ridiculous 😂 We’re not in the hole-punching era of computing. We have screens with resolutions that can easily fit 200-300 characters horizontally. My wraps across nearly everything are 100 characters.
Even code at 80 characters I find a joke from the era of 80 character terminals forcing people to have variable names like mCar, pItm, ctx, ptc, hln, vln, l for list, m for map and so on. Sure, it fits in 80 characters, but you might as well be reading obfuscated code.
You know that comment does nothing?
What did you actually do?
These changes are amazing! F-Droid could be provided on Google Play, Aurora Store could officially access the google store without worrying about rotating accounts, alternative payment methods could finally be proposed by side by side google pay in a single app…
But what about the appeal? What does that mean for the implementation date? Will that still be 1 November?
I blocked Lemmy.ml due to many users there continuously glorifying Russia and China. Moving away from Lemmy.world is probably good for the network, and I’ve never heard of lemdroi.id . Due to the spam of USAian news on All, it’s also a place I avoid. This would’ve thus completely passed by me.
It might be worth proposing as an addition. I think we all know that batching is better for the network and processing. Parallelization might work now, but the network grows (and it probably will), large servers might have more than ~6 activities/second to send.
They can hire? I thought they were in danger of getting wiped out by legal costs. Have charges been dropped?
Oh great, thanks for the run down! That clears things up 👍
It would be great I’d this got to a point where one could “just” buy any GPU without worrying about CUDA. Really amazing project.
Python has a Global Interpreter Lock (GIL) which has been a bane and a boon. A boon because many basic types are thread-safe as actions happen in lock step. A bane because despite having multiple threads, there’s still a master coordinating them all, which means there is no parallelism but concurrency. Python 3.13 allows disabling the GIL, but I cannot say much to that since I haven’t tested it myself. Most likely it means nothing is really thread safe anymore and it’s up to the developer to handle that.
So, in Python, using multiple threads is not a surefire way to have a performance boost. Small tasks that don’t require many operations are OK for threading, but many cycles may be lost to the GIL. Using it for I/O bound stuff is good though as the main python thread won’t be stuck waiting on those things to complete (reading or writing files, network access, screen access, …) . Larger tasks with more operations that are I/O bound or require parallelism (encoding a video file, processing multiple large files at once, reading large amounts of data from the network, …) are better as separate processes.
As an example: if you have one large file to read then split out into multiple small files, threads are a good option. Splitting happens sequentially, but writing to disk is (comparatively) slow task that one shouldn’t wait on and can be dedicated to a thread. Doing these operations on multiple large files is worth doing in parallel using multiple processes. Each process will read a file, split it, and write in threads, while one master process orchestrates the slave processes.
Of course, your mileage may vary. I’ve run into the issue of requiring parallelism on small tasks and the only thing that worked was moving out that logic to a cython and outside the GIL (terrible experience). For small, highly parallel operations, probably Python isn’t the right language and something like Rust should be explored.
Anti Commercial-AI license