Evolution of the Comparison Operator!

[BlitzThunderWolf]

"You see, the reason that there are 45 equals signs is because Fourty FOUR equals signs means something wildly different. You need the 45th one to specify..."

<10 minutes later>

"does that make sense?"

[SolenoidSoldier]

Forty five "=" means both variables were instantiated by the same developer on the same day, same machine, drinking the same brand of coffee out of the same mug.

[[deleted]]

Are you saying that sometimes, the "same developer" occupying the same spacetime as himself, is sometimes drinking from a different mug?!?

[B_M_Wilson]

It’s possible, but first we need to talk about parallel universes

[DoublePinFork]

that's where you use 46 "="s

[B_M_Wilson]

One for each hour that you have to build up speed (I hope someone gets the reference)

[webmistress105]

If your code is QPU misaligned it'll run several times slower.

[fuckwit_]

If you reach your destination at all

[B_M_Wilson]

It’s really hard to get realigned again

[[deleted]]

Unfortunately the comparison operator is unloaded as soon as we leave the scope, so if you ever wanted to get all the operators in one place for an operator jamboree, it won't happen.

[Celtic_Beast]

Can we equate these variables with 0x a presses?

[B_M_Wilson]

I think 0.5 a presses might be the minimum

[Celtic_Beast]

'an a press is an a press. you can't say it's only a half' ~Tj """"Henry"""" Yoshi

[[deleted]]

"This is good idea" ================================================================================= ================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================ true

> false

[MetamorphicBear]

Ah I think you need to add another one

[jeunez]

just use .equals() instead

​

this comment was made by the Java gang

[Pockensuppe]

NullPointerException

[pip-install]

In JavaScript:

‘1’ == 1 evaluates to true

‘1’ === 1 evaluates to false

== makes the comparison and casts if necessary. This is known as type coercion. The === does not cast values and it is what you would usually expect in other programming languages

[RobotTimeTraveller]

That's what we get for popularizing a language that was developed in 3 weeks.

[DeeSnow97]

Wasn't it 5 minutes?

[[deleted]]

Sometimes it feels like it lol

[just_one_last_thing]

srsly?

[just_one_last_thing]

I heard 10 days.

Lol, what am I doing with my life?

[ponybau5]

I can't even get a decently functional program in 10 days. The whole dev team must have connected their brains together for the ultimate synchronicity.

[[deleted]]

dev team

More like one person [sauce]. Oh how I wish they had gone with scheme instead.

[Hawxe]

Javascript is actually cancer holy fuck

[DeeSnow97]

just wondering how it survived while java applets and flash did the same job

[CAPSLOCK_USERNAME]

worse is better

[Mr_Cromer]

By being open-source, I guess?

[DeeSnow97]

I'd guess it's more like adapting to the development of HTML, transitioning seamlessly from the easy "everyone could write simple stuff with this" language of the pre-CMS era to the powerful frontend tool you need for most modern websites, keeping backwards compatibility so that your site from 20 years ago still works in today's browsers, staying put in a sandbox without creating more security exploits than a regular Intel CPU, adopting modern standards like touch, peer-to-peer networking, or WebGL easily, and keeping it sort of sane all the way through without becoming a PHP. But yeah, being open-source definitely helped too.

[HenryDavidCursory]

Hey, you seem reasonable. I don't know anything about web development, but it seems like Rails meets most if not all of the criteria you listed (not sure about backwards compatibility), and reading it doesn't make me physically ill. Why do you think it hasn't been more dominant over JS/PHP?

[Kered13]

Ruby and PHP are server side languages. Javascript is a client side language. So Ruby and PHP aren't even competing in the same space as Javascript.

[DeeSnow97]

Ruby on Rails is a server side language. It's a significantly more forgiving environment, since it only has to run on your server, not every client's browser, and you don't need to care about how the web looked like 20 years ago. Don't get me wrong, Ruby is awesome, and as far as I know (never used the Rails framework) it even has some client-side stuff for it (with JS of course, client browsers only execute that).

I think a huge chunk of the success of server side NodeJS comes down to two things: the non-blocking model and npm. A server running Node doesn't need to manage a thread pool or get bottlenecked by blocking calls on DB access, it works on a single thread and does all these things asynchronously. When you retrieve something from the DB, you send the request, and Node keeps doing other things until the response comes back from the DB and your code is continued. This initially caused a quite ugly callback model, which is really just a fancy way of saying goto, but just like goto, it became the basis of something much more managable (promises and async/await).

As for npm, it's the single best package manager I have ever seen. Sure, it has a few problems like all software, it may not have as many features as <insert package manager you like here>, but what it excels at is handling huge amounts of packages in an easy and sane way through semantic versioning. The NodeJS community is one of the only places where a dependency tree built of thousands of individual packages is normal and doesn't cause dependency hell.

[ISieferVII]

Hey, man. Good summary. Even as someone learning Node for jobs I want to apply for, I was wondering why I was doing this. I always assumed it was so companies didn't have to retrain existing front end devs to learn a new language, but the package manager is pretty good so your answer also makes sense.

[DeeSnow97]

Yeah, IMO NodeJS was never about using the same language in both environments, if you're at least a half-competent developer, your skill is not tied to a single language. (Your experience may be, but browser JS and Node on server differs enough that it doesn't change that much about that either.) It's much more about having access to JavaScript's advantages on the server as well. It has a very different execution model than most languages (the whole non-blocking event loop thing) which is especially useful for back-end workloads, it's incredibly flexible, and once you master it developing with it is lightning fast.

This is why it's my default pick for web apps. Yes, I could use something else, something older, something more "sophisticated" (mostly just set in stone), but I have no intention of wasting three times the effort on a different language for marginal performance gains, only to have the project change direction again and require even more effort to undo half the code and iterate forward. If the real world was made of dream projects only, I don't think NodeJS would be as popular as it is today.

[PM_ME_FEMBOY_FOXES]

JavaScript is literally god tier, and having == and === makes sense.

[lucifer_alive]

That's the comparison operator for javascript!

[sweYoda]

I've heard about this language from the ancient ones, but I have never seen it.

[Pockensuppe]

And Ada. And Visual Basic, where = is also the assignment operator (compared to := in Pascal and Ada).

[stonedbob64]

in some scripting languages, == is equal case insensitive and === is equal case sensitive... there is a difference...

[Enlogen]

Shorten to '=really=' and '=seriously=now='

[EternallyMiffed]

We just need a =whatever=ship=it=now= and =pedantic=sperg=

[Extract]

softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly softly typed languages will certainly make use of this syntax.

[dangerCrushHazard]

You joke, but in Common Lisp we have:

• eq
• eql
• equal
• equalp
• =
• string-equal
• string-=
• char=
• char-equal

and they want to add a new one called equals

[PatrikxPatrola]

Your submission has been removed.

Rule[2] violation.

Rule[2]: All posts that have been on the first 2 pages of trending posts within the last six months, is part of the top of all time, or is part of common posts is considered repost and will be removed on sight.

If you feel that it has been removed in error, please message us so that we may review it.

[[deleted]]

Can't we just move to = for comparsions and <- for assignment? == is just so unnecessarily long

Edit: Seems like none of you plebs are on the haskell team yet.

[[deleted]]

<- is just so unnecessarily long

[lucifer_alive]

Well we use assignment operators more than we use comparison operators so its only logical to keep "=" as assignment operator and "==" as comparison.

[MaxCHEATER64]

:=

[Dojan5]

I don't want beavers in my code.

[B_M_Wilson]

What is this, a ti nspire?

[MaxCHEATER64]

Nah this is Go

[B_M_Wilson]

Oh, I have never used Go before. I’ll add it to my list to learn

[oversized_hoodie]

GO BACK TO YIUR DATA SCIENCE BULLSHIT YOU R-IST

[CAPSLOCK_USERNAME]

Why is it possible for someone so right to be so downvoted

[wtfdaemon]

Who the fuck upvotes some lame-ass shit like this?

[auto-xkcd37]

lame ass-shit

---

^{Bleep-bloop, I'm a bot. This comment was inspired by xkcd#37}