You must log in or # to comment.
No, the C++ should fear you!
Your example is just brainfuck but somehow even worse
Less fucked-up than Javascript.
This diagram is nonsense. JavaScript programmers know to simply never use
==but to use===instead. Half of JavaScript is like this. Oh, there’s a feature, but it behaves in a super weird way so we don’t use it to avoid the weirdness.Where’s the
==operator? Because they also have the exact same problem.The recommended ESLint rules catch most of the bad stuff, and these days this is all you need in your ESLint config to enable them:
import {defineConfig} from 'eslint/config'; import js from '@eslint/js' export default defineConfig([ js.configs.recommended, ];There’s one use case where
==is still commonly used:== nullmatches bothnullandundefined. Lint rules that block==usually allows thenullcase as an exception.So you’re saying the jank has become structural?
I wonder how much bandwidth is wasted on the extra
=, since it survives minification 😅But if every single comparison used in a file is a triple =, then any compression algo worth its weight in salt will compress that bloat away during transmission
The real issue is all the precious precious RAM those extra = use on the client device once received and unpacked!
Gzip (any properly configured static server will serve compressed assets) probably compresses them down so probably a single extra byte per file
IIRC modern linter rulesets generally just outright error if you do anything remotely like this.
For those needing help the code is:
using namespace std; int main() { while (true) { cout << 'e'; cerr << 'e'; } return 'e'; }Anyway, my opinion: c is the best thing to ever exist, and c++ is evil
No. I don’t find it a particularly nice language to work with, but there’s no reason to fear it. Just make sure you know what you’re doing if/when you use it.
So yes
No
