Imagine gatekeeping caffeine

OP mentioned having used Linux for 4 weeks. If they are interested in learning more about Linux, I feel like even Arch would be a better next step.

I love NixOS and have been using it for over a year at this point but sometimes when things don’t work I feel like I’m banging my head against a wall. I’ve been using Linux for ~7 years now.

It’s not magic, it’s adoption rates. I’m not saying the money or resources are useless, but as it is right now, I think more people would benefit from actually trying to use rust in more large-scale projects (like R4L, windows, android, redox, servo, etc.) and using that experience to inform actual language development. I don’t think it makes sense to do a full revamp of the compiler until projects like those are actually proven. In the meantime it makes more sense to allocate funding/dev resources to those projects (or at least the open source ones)

revamp Rust to produce lightweight binaries, have a stable compiler and for it to be way quicker in compilation

It really isn’t that simple though. Rust’s compiler isn’t stable because the language itself is still being improved. This type of thing will only improve as adoption increases and real-world problems get ironed out. You can’t just throw money and devs at it and expect the problem to be solved.

It’s also not like the developers don’t care about compile time, but the nature of the language (strict compiler checks which catch things before runtime) will inherently lead to something slower that other languages’ compilers. There are probably still improvements they can make, but it’s not as simple as just deciding to rewrite/revamp it and expecting massive speedups.

But you’ll use AIs? I don’t think they are much better

Signal is private in that other people can’t intercept your messages, including signal. The signal app is open-source so you can be relatively certain it’s not tracking your decrypted messages, unlike closed-source apps like WhatsApp or Facebook Messenger or any other private social media.

Signal is not anonymous from an account standpoint, because you need a phone number to sign up, even if you can choose not to display it in your account.

If you have a weak sense of smell then you can’t taste them at all. I can taste most things fine though (la croix excluded) without them tasting bland. Smell definitely adds to flavoring but it’s not like it’s the only thing responsible for how you taste food/drinks.

They aren’t actually flavored at all, they’re just scented. If you plug your nose you can’t taste them

I’d say it is (was? It’s been ~a year and a half since I used it consistently but I’m guessing it hasn’t changed too much since then) moderately left by US standards but definitely not progressive left - you don’t have to go very far to find thinly-veiled sexism/racism/homophobia, though that might just be because a large portion of the people there are terminally online in a bad way. That being said, there are definitely also communities ranging from conservative to hardcore conservative as well but I actively tried to avoid those so I didn’t really see them in my feeds. The same is true with progressive communities but they tended to drift away from being actually progressive once they got to a certain size.

The date on this is 2017 so that would be pretty impressive if these were bots

Dots!

Hey how did you get into my cities skylines world?

They don’t work for discord in hyprland unfortunately, it only works when I have discord tabbed in (I tried passing the shortcuts in the hyprland config file)

AFAIK kde’s way of doing it is kind of hacky because it was called something like “legacy global keybinds” in settings but I switched off KDE a few months ago so I don’t remember the exact details.

Can we get actually working global keybinds in Wayland next? Or is that a chromium/electron problem?

Me going back to hollow knight, celeste, modded minecraft, and dead cells instead of buying new games

I’ve had a OnePlus 9 Pro since around when it came out in April 2021. Around 6 months later I installed AccuBattery and started trying to keep my phone between 20-80% battery. I still charge it to 100% sometimes, like when I think I won’t have access to a charger or will be out for a while, but generally I stick to it. It is also good to do a full charge (<15% to 100%) once every few weeks because it helps the battery stay calibrated and give accurate percentage readings.

In the 3+ years since then, my phone’s reported battery health has gone from a little over 90% to ~83-85%. I also almost exclusively use the 65w fast charger that came with my phone (I’m impatient) so that might be hurting my battery a bit more also. Here’s the graph of battery health over time that AccuBattery shows me

Tears of the Kingdom storyline has entered the chat

That’s entirely fair for the usecase of a small script or plugin, or even a small website. I’d quickly get annoyed with Python if I had to use it for a larger project though.

TypeScript breaks down when you need it for a codebase that’s longer than a few thousand lines of code. I use pure JavaScript in my personal website and it’s not that bad. At work where the frontend I work on has 20,000 lines of TypeScript not including the HTML files, it’s a massive headache.

This is the case for literally all interpreted languages, and is an inherent part of them being interpreted.

It’s actually the opposite. The idea of “types” is almost entirely made up by compilers and runtime environments (including interpreters). The only thing assembly instructions actually care about is how many bits a binary value has and whether or not it should be stored as a floating point, integer, or pointer (I’m oversimplifying here but the point still stands). Assembly instructions only care about the data in the registers (or an address in memory) that they operate on.

There is no part of an interpreted language that requires it to not have any type-checking. In fact, many languages use runtime environments for better runtime type diagnostics (e.g. Java and C#) that couldn’t be enforced at runtime in a purely compiled language like C or C++. Purely compiled binaries are pretty much the only environments where automatic runtime type checking can’t be added without basically recreating a runtime environment in the binary (like what languages like go do). The only interpreter that can’t have type-checking is your physical CPU.

If you meant that it is inherent to the language in that it was intended, you could make the case that for smaller-scale languages like bash, Lua, and some cases Python, that the dynamic typing makes it better. Working with large, complex frontends is not one of those cases. Even if this was an intentional feature of JavaScript, the existence of TypeScript at all proves it was a bad one.

However, while I recognize that can happen, I’ve literally never come across it in my time working on Typescript. I’m not sure what third party libraries you’re relying on but the most popular OAuth libraries, ORMs, frontend component libraries, state management libraries, graphing libraries, etc. are all written in pure Typescript these days.

This next example doesn’t directly return any, but is more ubiquitous than the admittedly niche libraries the code I work on depends on: Many HTTP request services in TypeScript will fill fields in as undefined if they’re missing, even if the typing shouldn’t allow for that because that type requirement doesn’t actually exist at runtime. Languages like Kotlin, C#, and Rust would all error because the deserialization failed when something that shouldn’t be considered nullable had an empty value. Java might also have options for this depending on the serialization library used.

As a TypeScript dev, TypeScript is not pleasant to work with at all. I don’t love Java or C# but I’d take them any day of the week over anything JS-based. TypeScript provides the illusion of type safety without actually providing full type safety because of one random library whose functionality you depend on that returns and takes in any instead of using generic types. Unlike pretty much any other statically typed language, compiled TypeScript will do nothing to ensure typing at runtime, and won’t error at all if something else gets passed in until you try to use a method or field that it doesn’t have. It will just fail silently unless you add type checking to your functions/methods that are already annotated as taking in your desired types. Languages like Java and C# would throw an exception immediately when you try to cast the value, and languages like Rust and Go wouldn’t even compile unless you either handle the case or panic at that exact location. Pretty much the only language that handles this worse is Python (and maybe Lua? I don’t really know much about Lua though).

TLDR; TypeScript in theory is very different from TypeScript in practice and that difference makes it very annoying to use.

Bonus meme: