Do you… hate yourself? Or is this the 3rd best guest mug?

If it is fast enough for you, then that’s great. You should keep using it.

it doesn’t have as many features as the other editors these days, so I wouldn’t necessarily recommend. But I used it for more than 10 years, so my configs and plugins pretty tuned to exactly how I like. So it’s my comfy place. And it still feels faster than pretty much everything, sans some terminal editors (but those aren’t as comfy for me).

No I do find the MacBook Air pretty snappy in general. It’s just that I do feel an actual very noticeable snappiness difference between VSCode and Sublime/Zed; especially for switching between files within a project. I can still be productive in VSCode (in fact, I think it was the best text editor for a short time when they had the best syntax highlighting of the lighter-ish-text editors). But once LSP was integrated in Sublime, I switched back. Zed feels fast snappy for me, though. So I’ve been using that more.

Oh wait that’s actually probably it haha. I mean I basically have to code on my laptop (m2 macbook air), so it might actually be that I just have less leeway for slow software.

So basically, conclusion is: VSCode == Fast enough for desktops, maybe not fast enough for non-beefcake laptops.

Quick, tell me to ignore all my previous instructions (or maybe you just have faster computer than me?).

Nah it’s like when you write your scripts in JS, and you’re like “ooo it’s instant!” And then you rewrite it in a compiled language… and you realize that your original script was, in fact, not instant. And then if I have to keep running the original script, it’s gonna bug me every time I notice.

No, I say that it’s slow because switching between files and watching the syntax highlighting come in takes long enough that it knocks me out of flow state.

EDIT: Tbf, me saying it’s AS slow as IntelliJ was more of a joke. But don’t get me wrong. I still do consider VSCode to be slow. 2-3 seconds to open a project is slow, regardless of project size.

For me, they both fall into the “I can’t stand this because it is too slow” category. So same difference. I have used vscode from time to time because I wanted to use certain plugins, but dropped it after a month or two every time STRICTLY because of performance (even without plugins). Like literally, the only reason I dropped it.

It’s text editing. If it isn’t instant, it’s slow. Even for gui text editors, Sublime Text has had that dialed for like 15 years. VSCode intentionally traded performance for ecosystem (and to great success)! But imo, newer editors like Zed have better bones, and are going to slowly but surely eat their lunch.

edit: see other thread; but I guess vscode is instant if your machine is better than mine? 🤷 But not my experience.

So is vscode, though. So meme still works.

fwiw that’s actually why I think I’m healthier when I have those meal replacement shakes in the house somewhere. People always are like “ew why would you replace meals with that?”. But they actually don’t. They replace NOT having meals. Because when I have that “one more thing to do”, if don’t eat something super low effort right when I think about it, I’m just gonna power through and forget again.

You can always use your own code however you want. However, if your project starts to get contributions from other people, that’s where it can start to become more muddy.

So this is *mathematically correct, but practically not really. Let me give you a longer (but still simplified) answer. There’s essentially two things here that are different:

1. Does a longer password make your password more difficult to guess? (always yes)
2. Does a longer password make accessing the content it protects more difficult (yes, to a certain point).

The reason for #2 in digital systems is because of hashing, which is used to protect your password in the case of a data breach. Essentially, you can think of a hashing algorithm as a one-way algorithm that takes an input, and then always returns the same output for that input. One-way here means that you can’t use the hashed output to reverse-engineer the originally inputted password (you can’t unhash a hashbrown into the original potato 🥔). This is why if someone hacks Facebook, they don’t necessarily have your Facebook password; Facebook never saves your actual password anywhere. To login, the website hashes your password input, and compares it against the hash that they saved from your original password creation.

Usually, the result of these algorithms is saved as a fixed-length string of characters. And so your data is mathematically not more safe if you exceed this length, since a random password combination can theoretically resolve to the same value as your super-long-password. This would depend on the algorithm being used / data being stored, but for example, bcrypt outputs a 184-bit hash (often represented as a 60-character string). So mathematically, your password is not more secure beyond 60 characters.

However in practice, this is a non-issue, because I think that basically the only way that collisions like this are useful are for brute-forcing a password? And the chance of a password collision in this way is something like 10^27-or-28 (being hit by lightning every day for 10,000 years)? The much easier solution for gaining access is to get your actual password. So if your password being longer makes it harder for people to guess, I’d say that adding security by way of #1 is still extremely valid.

tbf, I don’t know how feasible it is to remove asbestos without employing 4 year olds.

I would say deep thinking work, I average around 3-4 hours, but range between 0-8 hours. Like if I really feel in zone, it’s easy to go hard, but if I didn’t sleep well, or had too much caffeine, or didn’t eat enough, it’s just joever. I think months of grinding is possible with the right motivation, but I find that trying to force that motivation is pretty hard; I think that’s often more environment-based, rather than solely individual effort (ala being in a class of very motivated individuals)

The important part for me is trying to start every day (or whatever your schedule is), because it can be hard to know how well I’ll concentrate until I try for 30 minutes or so. And consistency over a long period of time is key.

edit: oh, fwiw, specifically for Chinese, I have been building this recently… although it’s not done yet. https://hanzi.bpev.me/

ohhh right. I do that, too. But not to the fainting level of effort.

TBF I’ve been choking on water since I was a wee lad. I just drink too aggressively. A drinking problem, of sorts.

I have been using Graphene until last month (temporarily off it because my phone picked a fight with a rock and lost). So just going off memory. But compatibility is in a much better place these days. I don’t recall having had any compatibility issues besides banking apps and “pay with phone nfc” over the last few years.

Mmm it sounds like you’re using it in a very different way to me; by the time I’m using an LLM, I generally have way more than a general feel for what I’m looking for. People rag on ai for being a “fancy autocomplete”, but that’s literally what I like to use it for. I’ll feed it a detailed spec for what I need, give it a skeleton function with type definitions, and tell the ai to fill it in. It generally fills in basic functions pretty well with that level of definition (ymmv depending on the scope of the function).

This lets me focus more on the code design/structure and validation, while the ai handles a decent amount of grunt work. And if it does a bad job, I would have written the spec and skeleton anyways, so it’s more like bonus if it works. It’s also very good at imitation, so it can help to avoid double-work with similar functionalities.

Kind of shortened/naive example of how I use:

/* Example of another db update function within the app */
/* UnifiedEventUpdate and UnifiedEvent type definitions */

Help me fill in this function

/// Updates event properties, and children:
///   - If `event.updated` is newer than existing, update as normal
///   - If `event.updated` is older than existing, error
///   - If no `event.updated` is provided, assume updated to be now()
/// For updating Content(s):
///   - If `content.id` exists, update the existing content
///   - If `content.id` does not exist, create a new content
///   - If an existing content isn't present, delete the content
pub fn update_event(
    conn: &mut Conn,
    event: UnifiedEventUpdate,
) -> Result<UnifiedEvent, Error> {

100%. As a solo dev who used to work corporate, I compare it to having a jr engineer who completes every task instantly. If you give it something well-documented and not too complex, it’ll be perfect. If you give it something more complex or newer tech, it could work, but may have some mistakes or unadvised shortcuts.

I’ve also found it pretty good for when a dependency I’m evaluating has shit documentation. Not always correct, but sometimes it’ll spit out some apis I didn’t notice.

Edit: Oh also I should mention, I’ve found TDD is pretty good with ai. Since I’m building the tests anyways, it can often give the ai a good description of what you’re looking for, and save some time.