I love it because software written in rust tends to be straight up better. because it makes it so easy to make your code parallel, because it makes it easy to be user friendly by design, people actually go that extra mile. because it’s so easy to pull in a dependency to do something you’d be too lazy to do in C, the tools can get a bit big but they tend to work really well. I’ll take a rust CLI app over a python CLI script any day, and I’ll especially take it over software written in C. most people don’t care as long as the tool works, but you can definitely feel the difference of the language it’s written in in its design and performance.
Good software can come from almost any language, but yeah there’s just something about rust CLI tools. I’ve pretty much always had issues with incorrect file type associations on Linux, until I started using handlr. exa (or eza?) is great too. Just like ls but better in every way.
I don’t believe that only 800 people played on Linux. It makes no sense to me in the grand scheme of things. I have a personal YT channel with only 108 subs and my random low effort video on how to get League running on Steam Deck has almost 70k views which is nuts and there are many other much better videos than mine with many more views. If only 0.1% of those people are active players that would still make a lot more than “800” figure. I know this is just a random speculation but 800 is just waaaay too low.
Good riddance, spent several years hooked to League. That being said, the fragmentation argument is bullshit, they could ship a read-only container in a flatpak and it’d run everywhere.
Kernel level is a huge risk and it doesn’t guarantee anything, especially in the age of Ai cheats and network mitm cheats
That’s the point. A read only container to keep low hanging fruit at bay, and flatpak to distribute without having to repackage to every distro under the sun.
I don’t fuck with the game, the game doesn’t fuck with my system.
If you’re not using tz_database or equivalents for literally all date-time logic, if 24 or 60*60 are constants defined in your project… you’re doing it fucking wrong. I don’t know how many times we need to break out the idiot club, but date, time and timezones are extremely complicated - unless your business is primarily concerned with them you must use a library or service.
From my very basic understanding, yeah that’s basically what it does. However it accounts for a whole lot more into adding or subtracting from UTC. Timezones aren’t absolute, they’re political. Timezones have weird rules, and history that needs to be somehow expressed in the code to get the right time. That’s what’s sets tz_database apart from just looking at a map and saying it’s +7 UTC.
“By extending the length of the days, Pedersen hopes that more people will be inspired to move to the remote region. Ensuring that the area is populated is “more important than ever” in light of Russia’s war against Ukraine, Pedersen added.”
Yup. Imagine the ads for this:
Move here and age slower (disclaimer: you might have to change your birthday because we needed to remove some days from OUR calendar.
I feel the same way about Haskell. Every program I’ve used is either a “Look at what else Haskell can do!” example, or an endorsement of universal packages whenever I have to update 200 haskell modules.
↑ This. Haskell makes it super easy to get good CLI filters. All you need to do is interact and process the string it gives you. You’ll automatically get streaming behavior because of laziness without lifting a finger.
interact is (String → String) → IO (), a function that takes a String → String (a function that takes a string and returns a string) and returns an I/O operation (which is a separate type since Haskell doesn’t have side-effects). The function you give it will receive all of stdin as a string and its output will be stdout. The magic comes because Haskell uses cons-lists that are lazy in their spine — the list doesn’t actually exist until you look at it. This means that, from your perspective (probably not how this is actually implemented), the list you return is iterated character-by-character, and each character that gets printed only waits for the characters it needs, allowing the rest of the stdin list to remain unevaluated.
The symmetry calendars (Wikipedia) use a leap week each several years, which seems like a reasonable way of doing it
Apparently the author of those calendars thought that would bring on board the people who believe days following an unending sequence is important - those who think their holy day has to be an actual whatever-day not one out of sequence due to intercalary days
Ahh, that makes sense. Here I was thinking it would be fun to have a day or two every year that weren’t any day of the week.
The leap week is a little bit of an unsatisfying solution since it means solstices and equinoxes will shift around a lot more. Also not as likely to get governments and employers to be willing to treat them as holidays.
I highly doubt we’ll move from our current calendar anytime soon. Its flaws aren’t bad enough to justify the effort, but I would really love a more symmetrical calendar. And payroll folks would probably love it too. Hourly and salary structures would be a lot more in sync.
On the other hand the calendar is always the same, years always start on a Monday, months start on a Monday
You could have a permanent calendar, except that religious holidays and astronomical events (solstices, equinoxes, best day for planting tulips) would move around
My birthday would vanish as it’s towards the end of one of the middle months; my mother’s birthday would only happen in leap years as it’s late in the last month
Birthdays on the new calendar would always fall on the same week day (though people born under the old calendar could celebrate on the day that it would be had the old calendar continued, or choose the same day number and month, or choose the corresponding day in the first year (or whatever) of the new calendar and stick to that month and day number)
Almost all of this would be true if we celebrated a day (or two) each year that were outside of the months and weeks, except events tied to points in our orbit would stay put a lot more. We would still have the same calendar every year. In your version we have a full extra week every 6 or so years, in mine every year we have a dedicated New Year’s Day that isn’t in a regular month or a day of the week, and every 4 or so years (same rules as now) we have 2 New Year’s Days.
Though I would argue for Sunday being the 1st day of each month/year. IMO weekends should be like bookends, one on either side.
Edit: your Wiki link contained a link to the International Fixed Calendar, which I’ve been inadvertently arguing for. This is almost identical to what I’ve been proposing, except they put the leap day at the end of June. But it fixes the major disadvantage of your system: that a year isn’t a year. In your system 1/1 is never one year away from 1/1. In mine it is within leap day drift, just like the current calendar.
A long while back riot used to be a fun sorta disruptive thing that was pretty healthy overall. It was awkward and fun. That was before it was purchased though. Now riot exists to make money for big china. It isn’t that company anymore. It’s a facade.
You can’t fix it, nor can the employees.
Riot is a skinpuppet that has no autonomy. Unlike the employees though, we have the choice to leave that failing franchise and move on. Rootkits aren’t acceptable and that needs to be the standard. It wasn’t okay when Sony tried it in the name of anti-piracy and it’s still not okay now. No person should be okay with installing a black box with greater admin rights than they have on their own machine. That is not okay. It is security heresy. That blog uses hand waving and bullshit to sell the concept to people that don’t know any better. And honestly? That’s almost just as bad as the rootkit itself.
A rough translation is:
Be a good drone and put the slave collar on. It’s good for you. Don’t ask questions, you don’t need to know why. Just do it. You are the product and you have no rights.
I disagree that they went downhill post-purchase. They were shit from the very start when pendragon decided to burn one community to promote his own in the name of capitalism.
They had their issues, sure. But most studios will have burned bridges in their wake. Not a hard and fast rule of course.
When I refer to downhill I’m looking directly at the slippery slope that is changing from profit as a target to profit above all else. When you sell a company regardless of who you retain - there will be a value shift as the head drives the body. The existing cracks got worse and new ones formed. People that care the most generally give up, leave, or both and the whole thing falls in on the void left by those support’s absences.
You may be right that a shift in ideal started then. I’m not terribly familiar with the story so I’ll defer to you on that.
lemmy.ml
Hot