The single best thing I like about Zed is how they unironically put up a video on their homepage where they take a perfectly fine function, and butcher it with irrelevant features using CoPilot, and in the process:
Make the function’s name not match what it is actually doing.
Hardcode three special cases for no good reason.
Write no tests at all.
Update the documentation, but make the short version of it misleading, suggesting it accepts all named colors, rather than just three. (The long description clarifies that, so it’s not completely bad.)
Show how engineering the prompt to do what they want takes more time than just writing the code in the first place.
And that’s supposed to be a feature. I wonder how they’d feel if someone sent them a pull request done in a similar manner, resulting in similarly bad code.
I think I’ll remain firmly in the “if FPS is an important metric in your editor, you’re doing something wrong” camp, and will also steer clear of anything that hypes up the plagiarism parrots as something that’d be a net win.
Unless FPS means “files per second”, I don’t see why it would, past the point of usability. You can only type so quickly, and 50 frames is as meaningful as 144.
If you get to that point where frames per second does matter, you’re either the fastest typist known to mankind, or it might be worth finding a more efficient way of doing what you’re doing.
In many modern environments the second I start scrolling my eyes start to bleed. Yes, I want 60 fps min.
That was the first part.
The second part is about stability. 20 fps may be enough for typing, but it needs to be 20 fps all the time. Not the average between 1 and 60, it is makes IDEs unusable.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
The single best thing I like about Zed is how they unironically put up a video on their homepage where they take a perfectly fine function, and butcher it with irrelevant features using CoPilot, and in the process:
And that’s supposed to be a feature. I wonder how they’d feel if someone sent them a pull request done in a similar manner, resulting in similarly bad code.
I think I’ll remain firmly in the “if FPS is an important metric in your editor, you’re doing something wrong” camp, and will also steer clear of anything that hypes up the plagiarism parrots as something that’d be a net win.
If FPS is NOT an important metric in text editing, you are doing something wrong. Otherwise, good points.
Unless FPS means “files per second”, I don’t see why it would, past the point of usability. You can only type so quickly, and 50 frames is as meaningful as 144.
If you get to that point where frames per second does matter, you’re either the fastest typist known to mankind, or it might be worth finding a more efficient way of doing what you’re doing.
In many modern environments the second I start scrolling my eyes start to bleed. Yes, I want 60 fps min. That was the first part. The second part is about stability. 20 fps may be enough for typing, but it needs to be 20 fps all the time. Not the average between 1 and 60, it is makes IDEs unusable.
No need to update my screen when nothing happens. I use neovim, the pinnacle of editing.
Explain why