The thing about an IDE is how tightly integrated all of the tools are.

If you list the features individually, surely there’s a way to add most of them to your text editor of choice - but the downside is that they’re now all fairly independent features, may not work as thoroughly or covertly, and you might end up with a slower editor altogether.

Not to say IDEs are the peak of performance - but they tend to provide more robust tooling than is (easily) available in e.g. VSCode/emacs/neovim/whatever.

It’s like using a specialized power tool - it’s not the right tool for every job, it’s probably a bulkier package, but if you know how to use it an IDE can make your life a lot easier for the right workload.

Just wanted to give props to this super informative comment. Thanks for the write up and relevant links!

You could do HTMX and WASM, but they both have the same problem in that they generally replace elements in the DOM as opposed to interacting with existing elements in the DOM, and most rendering on both HTMX and WASM actually happens through JavaScript calls.

In either case you’re limited to only interact with the DOM at the level of abstraction that the framework provides through “behind the scenes” JavaScript calls which will always be a subset of the DOM manipulation that is possible by directly using JS. At least, until there’s a standard DOM access API for WASM.

It’s not a question of performance - it’s just the fact that you need to use JS to modify the DOM in WASM. Until there is access to the DOM from WASM, there simply will be a place for JS in nearly every web app and it’s not because it’s fast, it’s because there are still certain things just need to be done using JS.

My point is really nothing to do with performance and I agree with the video you’ve linked: WASM is fast enough today. Whenever you can truly stop using JavaScript, I’ll be the first in line. You can already use WASM and eliminate huge portions of JS - but for anything beyond a very simple UI, you always end up with something that needs to be called in JS.

WASM’s biggest holdback is that it cannot directly access the DOM. Until then, JS will still have a prominent place in building anything rendered in a browser.

deleted by creator

Honestly, “it’s better than JavaScript” is a pretty low bar.

I don’t like PHP because I think the syntax is ugly and I’ve only used it on systems that are old and a pain to maintain, but I’ll also very freely admit that I have absolutely not written enough PHP to have an informed opinion on it as a language.

I can’t imagine anyone but a total novice disagreeing with this.

I can understand finding pointers hard at first, but I can absolutely not understand trying to argue that they aren’t useful.

Can you clarify what you meant about types, then? Because I’m not sure I really understand your point there.

Mostly agree. I’m ok with single characters in a one line / single expression lambda, but that’s the only time I’m ok with it.

C# is what I primarily write at work, and it’s honestly great to work with. The actual business logic tends to be easy to express, and while I do write a some boilerplate/ceremony, most of it is for the framework and not the language itself. Even that boilerplate generally tends to have shorthand in the language.

I came across this one just yesterday and while it was convenient at first, I immediately got frustrated when I went to add some parameters and discovered it wasn’t actually curl

That’s a little pedantic, don’t you think?

Notice the “up to” in their offer. It’s likely commission based and inflated numbers to lure the developer into doing it - to trick them into thinking exactly what you’ve said here.

I’d imagine what they actually pay out after you cave is significantly lower, only then you’ve already sold out your users so you might as well leave their tracking in there.

“To get a base salary of $170k you know you need to work hard as an Engineer, this sucks.”

As someone who has worked as a UPS driver and now as a software developer, I can say that the UPS drivers definitely work harder than your average engineer.

That quote is also deftly ignoring the fact that you’re generally paid for the value you generate, not how hard to you work.

GitHub Copilot is just intellisense that can complete longer code blocks.

I’ve found that it can somewhat regularly predict a couple lines of code that generally resemble what I was going to type, but it very rarely gives me correct completions. By a fairly wide margin, I end up needing to correct a piece or two. To your point, it can absolutely be detrimental to juniors or new learners by introducing bugs that are sometimes nastily subtle. I also find it getting in the way only a bit less frequently than it helps.

I do recommend that experienced developers give it a shot because it has been a helpful tool. But to be clear - it’s really only a tool that helps me type faster. By no means does it help me produce better code, and I don’t ever see it full on replacing developers like the doomsayers like to preach. That being said, I think it’s $20 well spent for a company in that it easily saves more than $20 worth of time from my salary each month.

Out of all the modern browsers, it’s always Safari that I end up needing to write compatibility code for. I’m sure the app works fine on Firefox, they just haven’t tested it.

No problem! It is a lot of information at once but I’ve been having a great time playing it so I’d really recommend it to anyone who thinks it could be interesting.

The combat is fairly challenging - it’s easy for one or two bad moves (or bad luck) to kill your whole party in a battle. It also takes a bit to learn the combat system if you haven’t played D&D.

That being said, I love it. Once you get the basics of combat down and get used to playing carefully, it’s a lot of fun and you get to build out the character that you think is both effective and just cool - and there’s probably a way for you to succeed with whatever build you end up making.

If you don’t love turn based combat I’ll say that it will probably feel very dense at first. You end up with 4 different characters with different strengths and weaknesses and each with a bunch of different abilities that have different rules for when and how often you can use them. Turn based means you get the time to make an educated decision about what you want to do next, but it’s a lot of information to juggle.