I was worried at first when I read they were “reducing” all the documentation comments from new tsconfig files and making users rely on editor autocomplete to somehow find and get the right settings.

But after looking at their new tsconfig example, it still has all the settings that users care about and looks like what everyone eventually turns their tsconfigs into anyway

It’s not about caring, it’s about the lawyers making the argument javascript’s genericness easier

Imagine if god showed up one day and said: “It’s actually Jod” then left

Try this link on an iPhone: https://jpegxl.info/resources/jpeg-xl-test-page.html

The future is webp JPEG XL…

And telling software patents to burn in hell.

They told you to use “ed”

You missed the joke

I really want to switch from VSCode to Helix but not having a file tree is a deal breaker.

Luckily there’s been a lot of work on adding a plugin runtime with one of the proof-of-concept plugins being a file tree. Assuming the plugin runtime comes out this year in a helix release, and adding on a year for the community to settle on the first wave of plugins while giving them time to mature, I can see myself using helix fulltime in 2027 (before Microsoft has enshitified vscode enough to be unpleasant to use).

For a complicated project I get it, github’s PR system is kind of bad (horrible branch based workflow and no stacked diff support resulting in increased churn) compared to the alternatives.

That’s why we have tools like Graphite to add stacked diff support on top of github, and other devs creating new VCSs because git still hasn’t made it’s interactive rebase and merge conflicts easy enough to handle for juniors and it should be simpler.

I’m conflicted by this release.

On one hand it has a common sense feature where the editor shows what changes in a file are already staged which will be good because it’ll help people separate their code changes into different commits for unrelated changes (as opposed to just shoving everything into a single unmanageable tangled commit), but then it’s adding all this ai slop which pushes users to just put all the slop into a single commit anyway.

I really want to switch to helix, but its plugin system is still being developed.

Plugins mean we get a file system tree, LSPs, and integrated version control, the three things that turn an editor into an IDE.

Polonius

“Well it’s about damn time” smokes cigar

Yes, I know it’s not out out yet, but we’re nearly there

^ this

Using AI leads to code churn and code churn is bad for the health of the project.

If you can’t keep the code comprehensible and maintainable then you end up with a worse off product where either everything breaks all the time, or the time it takes to release each new feature becomes exponentially longer, or all of your programmers become burnt out and no one wants to touch the thing.

You just get to the point where you have to stop and start the project all over again, while the whole time people are screaming for the thing that was promised to them back at the start.

It’s exactly the same thing that happens when western managers try to outsource to “cheap” programming labor overseas, it always ends up costing more, taking longer, and ending in disaster

Well… Assuming that it’s not using bits of typescript that will be deprecated in TS 6 and removed in TS 7 (the native go implementation)

This is why you’re meant to comment your code.

Your code tells you “what”, your comments tell you “why”.

Here’s a good review of comments in the redis codebase: https://antirez.com/news/124

I would advise against using pixels for margin/padding since it’ll have issues for users who have different zoom/text sizes than you do.

Stick to rem for margin and padding.

If you’re still early days with css, it’s worth pointing out that you should use a “css reset” file. It will solve problems for you that you don’t even know exist yet.

Does everyone who’s following the old account automatically refollow you when you do that?

It doesn’t port over any old comments/posts, but I’m pretty sure that when anyone @'s you, it’s forwarded to the new account.

IMO it’d still be useful to be able to use an identity you control, like a domain name.

Mastodon already does this

It’s worth pointing out that while ActivityPub doesn’t currently support account migration (although there are proposals in the works for how to do this), Mastodon does have a weak form of support right now.

You can create a new account on another mastodon instance, then you’re able to point your old account to your new account.

I think the more important question here is why are you using the internet without an adblocker?

But to answer the lesser question, stick this in a pinned tab and download what you need: https://devdocs.io/offline

I wonder if the slowdown in non-ai features this release was influenced in some way by their migration away from AMD modules to ES modules.

Putting myself in their shoes and taking codemods into account, I wouldn’t want to make a big feature and have to worry about AMD/ES module concerns. Why do that when instead I could get a bunch of checking and smaller (but non headline) tasks out of the way and get back onto the larger features in 1-2 months after the ES modules are proven to work and I don’t have to worry about rolling back changes.

Either that, or sometimes by statistical eventuality we end up with changes (which all take a different time to be completed) just not being released within a small period of time.

There’s no official announcement per se, but the windows version is built with .net which has been getting better linux support over the last two years.

There are unofficial instructions to run it through wine on their issue tracker.