- It runs in the browser
- Web developers know it already so we might as well
- Job security
- its not COBOL
😂😂😂👍
It’s* not
If you are understood buy you’re audience, you have spoken correctly. Correcting someone’s grammer is pointless
I dunno what correcting someone’s grammar has to do with paying off your readers. Sounds expensive.
This isn’t speaking, but writing (or typing). Using ‘correct’ spelling & grammar helps ESL speakers read the language as well as those relying on text translation software. Some folks make typos & it’s fine to make mistakes but it’s also strange to act like it’s just as easy to understand. Apostrophes have a specific meaning & many folks rely on them for understanding.
I’m learning a foreign language now & I can tell you it is a massive stumbling block when you run into what you think is a new word, but is ‘just’ a misspelling.
My issue with this account is not its corrections, but if you want to be the correction bot, at least get the typography right too.
'is as ASCII holdover & it should be’.
- Ubiquitous; insane amount of libraries and probably some of the best documentation of any language
- JS lambda function syntax is nice
- You can call it “Java” to enrage other programmers
- You can compare numbers against strings without wasting time converting them
Array(16).join(“wat” - 1) + " Batman!";
JavaScript: :wide eyed and smiling: Sure why not! You’re the boss!
Python: Sighing and downing half a bottle of Advil: Sure. Why not, you’re the boss.
The scripting language formerly known as Java.
If you’re living in 2002 and not using the strict equality operator, that’s on you
But what if I don’t want strict comparison? What if my frontend contains a text field for a numeric input and I wanna manually check against each possible valid input value
if (input_val == 1) {...} else if (input_val == 2) {...} else if...without having to convert it first or check that it’s actually a number or fix my frontend?(I’m sure there are valid use cases for non-strict comparison, I just can’t think of one right now)
why wouldn’t you just convert inline?
(Number(input_val) === 2)Converting would mean you could use a switch statement with your example rather than an if else ladder
switch(Number(input_val)) { case 1: doTheFirstThing(); break; case 2: doTheSecondThing(); break; case 3: doTheThirdThing(); break; }If you’re looking for good code, you missed the point of my comment 😄
If I was looking for an enumeration of valid inputs, I’d make it a selection box rather than a text field that’s supposed to contain a number and give the selections reasonable names. If I want an integral quantity, I’d use a number input field.
If I have no control over the frontend, that means I’m writing a backend in JS for a bullshit frontend, and no amount of good coding practice is going to salvage this mess.
I’m also blessedly far away from WebDev now. I work in Data Analytics and if I ever have to do any of this for a living, something has gone very wrong.
Converting texts into numbers or dates still haunts me though - fuck text inputs for numbers and dates.
You’ll find an npm package to help you count up to 2.
(I recently learned - maybe here - that the is-even package has over 170k weekly downloads)
Oh boy, this actually made me laugh out loud
What’s even wilder is if you look at the code of that package, all it does is include the is-odd package and then return !is-odd. And the is-odd package isn’t much better, it does some basic checks on the input and then returns n % 2 === 1.
I thought I was missing something. JS is one of my main languages and I always just write the is-odd function myself since it’s like 10 characters. It boggles the mind that is-even has 176k weekly downloads
To be fair having a name can make things easier to read. I get that
i % 2 == 0is a common pattern and most programmers will quickly recognize what is happening. ButisEven(i)is just that much easier to grok and leaves that brainpower to work on something else.But I would never import a package for it. I would just create a local helper for something this trivial.
Exactly what I would do if I had to reuse it, especially now since I know that adding a package would actually add 2. It all just seems so…inefficient
Even if the code isn’t reused adding names to sub-expressions can be very valuable. Often times I introduce new functions or variables even if they are only used once so that I can give them a descriptive name which helps the reader more quickly understand what is happening.
Also there are 40-something packages depending on it, so I guess it gets pulled automatically when they are used.
I’ve always looked at stuff like that as much more along the lines of performance art than anything else.
This must be a “hold my beer” kind of joke and someone wanting to see how far they can take it.
Is-even continues to be the best joke in the industry
deleted by creator
- It has the simplest multi-threaded implementation: no threads!
- You can goof off while your build system takes 20 minutes to rebuild a non-compiled language
node_modules size of a Linux distro
- it’s easy to make fun of
- it makes every other programming language look better in comparison
- It runs in browsers
- If you hate your co-workers, then they will also feel your pain.
It leads to typescript
You get surprises from npm
You get suprises from npm
I spent way too long today figuring out why my app was doing something that it’s NOT supposed to do on weekends.
I read Luxon’s docs (pretty cool lib tbh) again and again, and tried everything I could think of to get isWeekend to return a sane result.
Turns out I was pulling a somewhat older version of Luxon, where isWeekend didn’t exist. In any sane language, I expect I’d get a huge warning about a property that doesn’t exist, but alas…
Typescript helps me keep my sanity, but juuuuust barely.
If isWeekend doesn’t exist, then the weekend doesn’t exist, so it’s naturally false.
That’s why JavaScript gets pushed so hard - it’s part of the capitalist agenda to keep us working 7 days a week
That’s fair. Typescript has to cook with the existing js ecosystem.
Weren’t you getting runtime errors for the function not being found?
No, they were probably getting false every time
Falsy* because it was undefined
However, their IDE should have highlighted it as an unknown property. Guess this guy is coding in notepad or vi.
Yep, thanks for correcting me. In fact, if they write something like
if (day.isWeekend) {...}The block will never be executed with the old version of library
Yeah that’s exactly what I think happened to him. He needs a better IDE and/or needs to stop copy/pasting code from stackoverflow or documentation that doesn’t match his library version.
My dude, you need to understand that all that anger and resentment, it is not you. It’s the years of JavaScript poisoning your mind.
In any case, that goes to my point. I would have to be saved by my IDE, when any sane language will blow up in your face as soon as you try to run it.
I don’t know how luxon works, but isWeekend could be a property instead of a function
It is. It also happens to be undefined, and checking that for truth is how I was bitten.
- It at least feels slightly little bit like lisp.
- Shit I’m f*ed
… ah right, it runs on any browser. Lame
- It’s not PHP.
- I don’t know. I didn’t think I’d get this far.
- It’s not PHP
- It’s already implemented in browsers
PHP has gotten really good over the past few versions, actually. Lots of really great stuff has been added, it feels like it resembles rust more every release lol
PHP10: We now allow interop with Rust!
PHP11: We now allow writing code directly in a .php file and compile it with rustc.
Can’t forget the intermediate step of PHP 9: PHP borrow checker
- Ubiquity
- Easy adoption for those familiar with C family of languages
awaitandasyncOver what?
Death by wasps
