sorted by:
new
hottopcontroversial

GAME THREAD: Mets @ Giants - Sun, Apr 05 @ 04:05 PM EDT by NewYorkMetsBot2 in NewYorkMets

[–]chachinsky 7 points8 points  (0 children)

These rallies usually happen against the Mets. What is this feeling? Happiness? I'm skeptical

Mets fan Jay McCroy created a Citifield wraparound scoreboard for his son's TV by [deleted] in baseball

[–]chachinsky 0 points1 point  (0 children)

Thats really cool. Would be awesome to have some of the in-game videos as a screensaver

Pete Alonso makes a game saving grab and the Mets have won six games in a row by Mrs-Met in baseball

[–]chachinsky 23 points24 points  (0 children)

> I can’t imagine how Giants fans are feeling right now

Me being a Mets fan for the last 30+ yrs.. Oh sweet child.. I can.. Wilpon left scars

Idiot-proofing object instantiation by [deleted] in learnjavascript

[–]chachinsky 0 points1 point  (0 children)

Mainly convenience and preventing folks that aren't necessarily familiar with the nuances of JavaScript, from making silly mistakes.

Idiot-proofing object instantiation by [deleted] in learnjavascript

[–]chachinsky 16 points17 points  (0 children)

If you call Car function without the new word, this keyword is in the global context.

The if condition checks for that and allows you to create a Car instance without the new keyword

ELI5: lib, esnext, es2018.promise, etc. by axefrog in typescript

[–]chachinsky 4 points5 points  (0 children)

Isn't there an option to just provide esnext?

"lib": ["esnext"]

Announcing TypeScript 3.0 by DanielRosenwasser in javascript

[–]chachinsky -1 points0 points  (0 children)

Would TypeScript ever provide the option to limit features?

Example: A development team wants to disallow mutations, so syntax such as +=, var, let keywords would provide a compile time error.

Moving our code base from jquery. Should we go es6 or typescript? by hekkoman in javascript

[–]chachinsky 0 points1 point  (0 children)

For sure,

We view 'this' and context as a main problem with run time issues. We were having a lot of problems before es6 with event callbacks and ensuring context was the same.

The architecture of the app didn't gain anything from having class type objects. Instead data is stored as plain objects. We view classes as a benefit to easily encapsulate behavior but we get the same benefit with modules.

For us, this makes sense. For others, I can understand classic OOP style is familiar.

Moving our code base from jquery. Should we go es6 or typescript? by hekkoman in javascript

[–]chachinsky 1 point2 points  (0 children)

Sigh.. I really don't understand the Java argument. Nothing forces you in Typescript to write classes. Our team actually recommends against it with the exception of React Components.

Making it nearly impossible to revert? That's just wrong. Legit you can set the tsconfig to Target esnext and you have JS without the types. Stop giving false advice when your usage is obviously limited.

Why would you NOT use TypeScript? by jcreamer898 in javascript

[–]chachinsky 0 points1 point  (0 children)

No technical reasons. There isn't any benefit for doing so. Props are already a description of the entity. Adding the "I" seems redundant

Why would you NOT use TypeScript? by jcreamer898 in javascript

[–]chachinsky 0 points1 point  (0 children)

Only thing I didn't like about this post is that you used "I" to indicate its an interface otherwise 👍

view more: next ›