Seems like you read the first two sentences of my post and stopped there, so you completely missed the point.
It’s not JS that is the problem. It’s an issue of client resource use. That would be true no matter what language is being used.
Seems like you read the first two sentences of my post and stopped there, so you completely missed the point.
It’s not JS that is the problem. It’s an issue of client resource use. That would be true no matter what language is being used.
That’s not necessarily special to JS. It’s special to client-side code. A mobile app writing in swift could do this. A cli tool written in any language could do this.
This isn’t an argument against JS, it’s an argument against misuse of client resources.
Except that all of those produce HTML. They are all HTML websites.
PHP stands for “PHP Hypertext Preprocessor” because it is a Preprocessor of HTML (HyperText Markup Language).
If we are talking about browser performance, none of those technologies that you mentioned execute on the browser at all and are therefore irrelevant to Firefox’s performance compared to another browser.
From a browser’s perspective, every website is HTML, CSS and JavaScript.
Can you give an example?
The person you are replying to is talking about pink sky being built on bluesky, and you equate that to Lemmy being based on Reddit. One is a hard technical dependency, and the other is a conceptual inspiration.
You are engaging in an equivocation fallacy, and I think you know that. You even try to sneak it in by switching to a different but similar word (built->based) with a different meaning, then you switched back again to “built” while using the term in the same way you used “based”, then you start using other phrasing to obscure it even more. You are gaslighting with word games to try and get people to not notice your fallacy. It’s super dishonest.