arcterus
- 2 Posts
- 65 Comments
arcterus@piefed.blahaj.zoneto
Games@sh.itjust.works•Japanese game developers face ridiculously high font license fees following US acquisition of major domestic provider. Live-service games to take the biggest blowEnglish
17·2 months agoI’m guessing the problem is they want a relatively unique font to avoid looking the same as other games, and then once they’ve chosen their font they’re pretty much stuck with it unless they’re willing to change the look of their game (for live-service games at least). A number of the fonts there might work for new stuff though.
arcterus@piefed.blahaj.zoneto
Games@sh.itjust.works•Japanese game developers face ridiculously high font license fees following US acquisition of major domestic provider. Live-service games to take the biggest blowEnglish
2·2 months agoRealistically if a game company made their own font, they’d probably do that and then have to go through and piecemeal add more kanji that they used. Or just use hiragana/katakana for those words I guess.
arcterus@piefed.blahaj.zoneto
Programmer Humor@programming.dev•It was best as a silly toy language in the 1990's...English
61·2 months agoHave you ever looked at the original JS implementation? It looks nothing like what JS is today. Saying the bones were spat out in a couple weeks is like saying Linux was developed in a few months.
And yet working groups have spent literal decades trying to make JS less shitty. The fundamental basics of JS can’t be changed in backwards incompatible ways without breaking a huge number of websites. The Linux comparison is just wrong because Linux has broken backwards compatibility to fix problems. A better comparison would be Linux’s policy to never break userspace. Backwards incompatible changes to JS would break a bajillion websites, much like breaking userspace would break a bajillion programs.
TS transpiles to JS, and any JS is valid TS. Take any TS, remove the types (and some syntactic sugar) and you have JS. I feel like if you like TS but not JS, you just don’t like loosely typed languages. That’s just a preference. It doesn’t make a language bad.
JS is valid TS. TS is not valid JS. This is the fundamental point. TS essentially fixes issues that JS cannot fix without breaking the world.
Loose typing is fine if the language’s type system isn’t insane. I prefer static typing, but as long as the type system is coherent, it’s not an issue.
TBH IMO the only reason JS became popular is because it was provided by web browsers, and if you wanted to make your site do anything complex, you thus needed to use JS. This eventually led to the JS VMs being very fast, so Node was created, and now it’s all over since you can learn one language for web and server.
arcterus@piefed.blahaj.zoneto
Programmer Humor@programming.dev•It was best as a silly toy language in the 1990's...English
11·2 months agoI’m pretty sure most people do not like JS’s loosey-goosey, who-knows-what-ur-gonna-get type system, which is why TS is so popular. Not really surprising since the bones of the language were basically spat out in a couple weeks. TS is a custom type system on top of JS, meaning it’s not just JS’s type system expressed through strict typing. They added a bunch of useful features like discriminated unions and so on to make using TS more pleasant than raw JS.
TS is actually usable (although NPM and the environment built around it still suck). It’s inherited a bunch of weird shit from JS, but the type system generally makes them bearable.
arcterus@piefed.blahaj.zoneto
Programmer Humor@programming.dev•It was best as a silly toy language in the 1990's...English
18·2 months agoI mean, just the fact that you’re using TS instead of plain JS (and that TS even exists) should tell you that the language has issues…
arcterus@piefed.blahaj.zoneto
Programmer Humor@programming.dev•It was best as a silly toy language in the 1990's...English
231·2 months agoThe completely bizarre implicit type conversions, for one thing.
arcterus@piefed.blahaj.zoneto
Programmer Humor@programming.dev•It was best as a silly toy language in the 1990's...English
85·2 months agoFor something you’re getting paid for, sure. But if you’re contributing in your free time for fun or whatever, presumably you’d prefer to use a language you actually like.
arcterus@piefed.blahaj.zoneto
Programmer Humor@programming.dev•It was best as a silly toy language in the 1990's...English
37·2 months agoThis doesn’t really conflict with the post. They use and appreciate the software, so presumably it’s decent. You can write good software in any language, so it doesn’t prove that the language itself is good. IMO JS is a popular language, not a good language.
arcterus@piefed.blahaj.zoneto
Linux@programming.dev•moss is a Unix-like, Linux-compatible kernel written in Rust and Aarch64 assemblyEnglish
26·2 months agoI think the MIT license is fine for a lot of things, but the kernel isn’t one of them. It’s probably alright if it just stays a small toy kernel though.
Also, it says to look at
LICENSEfor more info, but there is noLICENSElol.
arcterus@piefed.blahaj.zoneto
Android@lemdro.id•Motorola ignores EU regulation on security updates for smartphones. Will this end well?English
6·2 months agoYeah, I’d be kind of surprised if it’s them, but then again most OEMs have issues with updates so who knows. If we were just talking about hostility to custom OSes, the choices have gotten pretty slim too (basically Sony, OnePlus, and Nothing, with some smaller OEMs and one-off unlockable devices from others).
arcterus@piefed.blahaj.zoneto
Linux@programming.dev•The ChromeOS of Linux: Basic use cases, impossible to break, ~1,000 happy(?) users, Nix based. Nixbook OS.English
8·2 months agoPerhaps I missed it, but skimming through the article, it doesn’t seem to explain that at all.
It also didn’t really explain how it’s functionally any better than the various atomic distros for basic users.
arcterus@piefed.blahaj.zoneto
Linux@programming.dev•sudo-rs Affected By Multiple Security Vulnerabilities - Impacting Ubuntu 25.10English
7·2 months agoNah, it’s just that a whole lot of people, me included, are tired of foolish “but Rust is safe!!!1” propaganda-like shallow screams, like kids getting a new toy.
Okay, and I’m tired of seeing every Rust-related thread filled with random idiots shitting on Rust for no real reason (often unprompted, with no actual argument other than “hurr durr stupid cult of rust bad hurr durr why use rust when c do trick”) and then go on about how the brilliant, genius, enlightened C programmers will save us with their 3000 IQ brainpower and never make mistakes. It’s just tiring. Every Linux discussion about Rust, every discussion about some software being rewritten in Rust (even by the original developers), every discussion even tangentially related to Rust ends up like this.
arcterus@piefed.blahaj.zoneto
Linux@programming.dev•sudo-rs Affected By Multiple Security Vulnerabilities - Impacting Ubuntu 25.10English
1·2 months agoYeah, what I was saying was that rather than the basic take URL and just put the file on the filesystem use case (which is in the common case not that difficult with stuff like
reqwestorhyper), the other use cases where you for instance use the library to process requests and their responses in non-default or potentially bizarre ways is more likely where there’d be an issue. When I said “extra processing” for requests, I was including for instance potentially dealing with TLS and interactions between underlying libraries and so on with all the various protocols curl supports.
arcterus@piefed.blahaj.zoneto
Linux@programming.dev•sudo-rs Affected By Multiple Security Vulnerabilities - Impacting Ubuntu 25.10English
9·2 months agoNow that you mention it this does sound suspiciously like every Rust-related Phoronix comment section I’ve seen
arcterus@piefed.blahaj.zoneto
Linux@programming.dev•sudo-rs Affected By Multiple Security Vulnerabilities - Impacting Ubuntu 25.10English
4·2 months agoTbh that specific case probably wouldn’t be a big deal. It’s all the extra processing curl can do for http requests and the like that’d be more dangerous to rewrite I’d think.
arcterus@piefed.blahaj.zoneto
Linux@programming.dev•sudo-rs Affected By Multiple Security Vulnerabilities - Impacting Ubuntu 25.10English
16·2 months ago> deliberately lies about content of article to shit on Rust
> gets called out
> “how dare you twist my words”So fucking childish lol. Could have just used a real article about a Rust vuln like this one but whatever.
At this point I feel like anti-Rust people are more cult-like than any pro-Rust people I’ve met.
arcterus@piefed.blahaj.zoneto
Android@lemdro.id•Google finally released the source code of Android 16 QPR1!English
31·2 months agoFucking finally. Also from a linked article about their apparent Android PC project:
Osterloh touched upon Google’s efforts to bring its AI stack to PCs. “This is another way we can leverage all of the great work we’re doing together on our AI stack, our full stack, bringing Gemini models, bringing the assistant, bringing all of our applications and developer community into the PC domain. And I think this is another way in which Android is gonna be able to serve everyone in every computing category.”
No one gives a shit about your AI crap, just stop ruining AOSP.
arcterus@piefed.blahaj.zoneto
Linux@programming.dev•sudo-rs Affected By Multiple Security Vulnerabilities - Impacting Ubuntu 25.10English
141·2 months agoAs expected, these all sound like logic bugs.
arcterus@piefed.blahaj.zoneto
Linux@programming.dev•sudo-rs Affected By Multiple Security Vulnerabilities - Impacting Ubuntu 25.10English
354·2 months agoWeren’t you the dude posting completely irrelevant articles? As I said before, no one reasonable thinks Rust programs won’t have bugs. Rust helps prevent a specific class of vulnerabilities. The rest is, as per usual, up to the programmer to avoid.
EDIT: I browsed your comments to verify. You were indeed the person posting the irrelevant articles about malware written in Rust being used to exploit other programs and using it to claim that software written in Rust was vulnerable.



I haven’t looked into how the tokens work, but IIUC that should only matter for node operators, not end users.