This makes absolutely no sense. Front ends that include JavaScript still use css.
deleted by creator
no frills? javascript is frills
The only sites I can think of that don’t look like they use css are motherfuckingwebsite.com and bjarne stroustrup’s website.
Any site that uses JS for more than trivial things is going to be a disaster without styling of some kind.
deleted by creator
Maybe, but they don’t need to. You could write an HTML styling engine in JS if you wanted to.
sometimes
Personally I hate CSS and the last several websites I created had plenty of JS.
Problem: Oppenheimer, unlike JavaScript, was actually competent.
Would be funnier if it was just “JS” on the right, because obviously HTML and CSS are involved too, but JS is where all hell breaks loose
Mid 90s HTML pre CSS:
Now it’s: I AM THE FLEXBOX!
bro we’re on css grid now
Around flexbox is when I stopped caring about CSS, so it’s the last one I know. Is the grid better?
They’re both tremendously useful and have significant overlap in use cases. Grid isn’t going to replace Flexbox, it just has some capabilities that aren’t part of the Flexbox concept.
for some stuff absolutely, styling frameworks like bootstrap and others kludged together the concept of grid based designs. css grid just makes it official and more flexible.
What
I’m not sure either, fork bombs are a thing you could probably do in JavaScript, but I don’t know of a thing called an Atomic Bomb in programming? I think if you put lots of atomic operations you’ve just reinvented single threaded programming but with more overhead
JS is Touring complete. You can write anything in it, including SkyNet or whatever else you can think of that will destroy the world.
I want my world destroyed fast, thank you very much. Do you want them to stop mid-murder to prolong your pain because they’ve ran out of RAM?
Say no to JS Skynet, embrace C++ Skynet!
I don’t disagree.
If you’ve seen the Barbie movie, there’s a scene where America Ferrera rants about the paradoxes in the expectations on women. The whole “be strong but not pushy” thing.
That’s CSS.
Wait, I’m CSS?
I don’t get it.
CSS is coloring and styling in programming, Ma’am… It fits to describe the Barbie movie because of its vibrant colors
JS is about logic and calculations… More like science in Oppenheimer
But I’m not cascading though…
Not normally, anyways. 💖
I’ll have you know that CSS is Turing complete
deleted by creator
Ah, so that’s not Peaky Blinders.
Is this some highly sophisticated programmer humor that I’m too tech-illiterate to understand?
JS bad, please clap
👏
👏👏
👏👏👏
👏👏👏👏
👏👏👏👏👏
Little diddy bout Jack and Diane
The real question is since when CSS is good?
ITs NoT StRoNgLy TyPeD aNd Is ThErEfOrE gArBaGe
Give me one advantage of language that isn’t strongly typed
Fluent polymorphism via duck typing. It’s useful when you’re treating objects as a collection of properties, and therefore it’s not their type that matters but which properties they have. Types can still be used to label common collections of properties but it’s less painful to talk about objects that are “like an X but with/without certain properties,” or where some properties themselves have a different shape, etc. This is applicable to web APIs, not just because of JSON, but because it allows to define both very rigid and very flexible schemas without much overhead or repetition. See the OpenAPI specification.
It’s not a debate I care to have, I just think it’s funny that people want to build websites but hate how websites are built.
CSS is used to create the design, basically the look (colors, layout and so on), but no substance.
JavaScript is used to implement code and logic.HTML + JavaScript would typically (since you’re supposed to use CSS to create colors and design) look very dull, thus the black-and-white Oppenheimer.
document.querySelector('.whatever').style.color = "red";Don’t recommend, though.
Sure, but setting the .style attribute could really be argued as using CSS, just with a different interface. W3Schools refers to this as “inline CSS”.
How many people who post JS BAD memes could provide a single example of why it’s bad without looking it up?
It was made in 10 days, its type system is a mess, its syntactic shit, and there are just better replacements out there that will never see the light of day due to how big its already gotten
well if you consider its not finished yet, it was actually made in 27 years.
still not good tho
Coming from other languages I find the async by default thing annoying but I fully understand it’s necessary for web sites to render in real time.
Well, use typescript. There’s no excuse to use pure JS nowadays. It doesn’t solve everything, but it for sure solves 95%+ of JS issues.
Or use WebAssembly, I think it’s usable nowadays?
WASM knows kung-fu
I use it regularly (web dev). A lot of complaints and mockery stems from using it badly. None of the programming languages that are regularly the butt of everyone’s jokes force you to use them badly, they just allow you to. If you follow good practices, you’ll be just fine.
Many of the programming languages that are regularly the butt of everyone’s jokes don’t just allow you to use them badly, they make it easy to do so, sometimes easier than using them well.
This is not a good thing. A good language should- be well suited to the task at hand
- be easy to use correctly
- be hard to use incorrectly
The reality is that the average software developer barely knows best practices, much less how to apply them effectively.
This fact, combined with languages that make it easy to shoot yourself in the foot leads to lots of bad code in the wild.Tangentially related rant
We should attack this problem from both directions: improve developers but also improve languages.
Sometimes that means replacing them with new languages that are designed on top of years of knowledge that we didn’t have when these old languages were being designed.There seems to be a certain cynicism (especially from some more senior developers) about new languages.
I’ve heard stuff like: every other day a new programming language is invented, it’s all just a fad, they add nothing new, all the existing languages could already do all the things the new ones can, etc.
To me this misses the point. New languages have the advantage of years of knowledge accrued in the industry along with general technological advancements, allowing them to be safer, more ergonomic, and more efficient.
Sure, we can also improve existing languages (and should, and do) but often times for one reason or another (backwards compatibility, implementation effort, the wider technological ecosystem, dogma, politics, etc.) old quirks and deficiencies stay.Even for experienced developers who know how to use their language of choice well, there can be unnecessary cognitive burden caused by poor language design. The more your language helps you automatically avoid mistakes, the more you can focus on actually developing software.
We should embrace new languages when they lead to more good code and less bad code.
- be easy to use correctly
- be hard to use incorrectly
C++ has entered the chatWhich subset of C++ specifically? That thing’s ridiculously huge.
<span>Please enable JavaScript to use this app</span> document.getElementById("noscript").style.display = 'none';document.getElementById("noscript-info-with-bold-text").style.fontWeight = 'bold';document.getElementById("status__content__text").textContent="JS ecosystem is all hack upon hack upon hack upon hack. We love hacks, but don't want to relay on them to access my bank or watch a movie. Just send me a webpage, not a soup of obfuscated, impossible to edit scripts that assemble god sake app. That's the reason we can't have new browser engines anymore, try to disable one wrong thing and whole app breaks. Browsers are made as interactive documents viewers, not disposable operating systems.";The meme was not about bad or good… It’s about Colors (CSS = Barbie), and Complexity (JS = Oppenheimer)
WAT?
also, humans are really bad at rote memorization and this is a bad metric for you to use, in life.
Ask people on the street why NOx is bad. What about an easy one like methane? Or how about asking someone whether driving your car for 30 miles or eating a hamburger is worse for the environment (yes, its obviously the hamburger). Etc, etc, etc.
WAT
Reminded me of this: https://www.destroyallsoftware.com/talks/wat
that…uh…was the joke
deleted by creator
deleted by creator
Quite a few
Security concerns.
var bomb = [] for(var i = 0; i === -1; i++){ bomb.push(i) }what does 3 equals signs do
Identity. “A is literally B” instead of “A equals B”. This is necessary here in JS because if A is the string “-1” and B is the integer -1, JS evaluates A==B as true because reasons
because if A is the string “-1” and B is the integer -1, JS evaluates A==B as true because reasons
Interesting. If it were the other way around, I think I would have been fine with it (i.e.
==used for comparison with type like any other language and===without type). But as it stands now I would hate it if I had to write in JS (but I don’t so it’s fine).It’s not that bad, honestly, just something you get used to. When I switch to C++ after a while, I sometimes write
===and when I switch back to JS after some time, I occasionally forget to use===.In C++ it’s obviously an error and for JS I have my IDE set to warn me about
==. I think I’ve used==in JS (and PHP) intentionally once in the last ~5 years.Honestly, I think it actually makes some sense this way around. To me, in JS “==” is kinda “is like” while “===” is “is exactly”. Or, put another way, “equals” versus idk, “more-equals”. I mean, “===” is a much stronger check of equivalence than normal “==”, so I think it deserves to be the one with the extra “=”
2 equal signs will coerce the second operand into the type of first operand then do a comparison of it can. so 1 == “1” is true. this leads to strange bugs.
3 equal signs do not do implicit type conversion, cuts down on weird bugs. 1===“1” is false.
edit: it appears to be more complicated than that for double equals and the position of operands don’t matter. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Equality
wow that seems super useful, thanks
Doesn’t it widen the types regardless of position? Meaning 1 == “1” will be compared as strings, not numbers.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Equality
mdn goes into it more and it’s way more involved than I thought, looks like order of operand doesn’t matter. see the number to string section
It seems it is that way, which is weird. You should always convert to the widest type, meaning string for comparing numbers and strings. I just checked that
1 == "01"istrue, which means that “01” gets cast to an integer. And according to the document it might be that for example1 == "a"would basically be interpreted as1 === NaNwhich isfalse.
Removed by mod
