fidodo

joined 1 year ago
[โ€“] [email protected] 36 points 1 year ago

"we organized to all quit at the same time"

"Noooooo! Not like that! ๐Ÿ˜ญ๐Ÿ˜ญ๐Ÿ˜ญ"

[โ€“] [email protected] 23 points 1 year ago (2 children)

But they're both Walt Disney, so does this say that he did character voices while masturbating?

[โ€“] [email protected] 2 points 1 year ago

Thanks! This is a super helpful answer!

[โ€“] [email protected] 3 points 1 year ago (1 children)

Can you be more specific? I'd like to know what it's missing.

[โ€“] [email protected] 7 points 1 year ago

Ah just as God intended.

[โ€“] [email protected] 5 points 1 year ago (1 children)

I think you're misunderstanding what I mean. Early Access is a newer term for getting paid access to a game early. Open beta is an older term but was used for free access to a game early for testing purposes. They used to have different meanings which is why early access was created as a new term to distinguish it from a beta. Calling paid early access a beta is intentionally misleading.

[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago)

In that case you will love typescript. I'm not sure what other imperative languages have both type inference and structural typing.

[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago)

My opinion is you should use it when it's useful, but not when it's unnecessary. Their main use case is when you need to couple the functionality of functions to a shared state, and it's particularly useful when you have multiple interdependent functions that need to be tied to multiple codependent states.

I find it relatively rare when I really need to use a class. Between first class functions and closures and modules and other features, I find JavaScript has a lot of tools to avoid needing classes. Classes add complexity so I only use them when the complexity they add is less than the complexity of the task they're needed for.

[โ€“] [email protected] 4 points 1 year ago* (last edited 1 year ago)

You should check out "post modern JavaScript explained for mammoths"

[โ€“] [email protected] 18 points 1 year ago (4 children)

It used to be called early access. At least it wasn't a misleading term.

[โ€“] [email protected] 2 points 1 year ago

At the end I said at the volume of consumption we have. If everyone switched to wild game we'd instantly go from over population to over hunting and that's not sustainable. You wouldn't be able to support the volume with pasture raised without deforestation either. Raising your own animals also wouldn't match the volume that people eat meat currently either. Even if we were more efficient with the meat we use I still think we'd be orders of magnitude off. I'm not totalitarian anti meat, I just don't see any path to sustainability without huge decreases in consumption. The things you pointed out are great, but I think we can't mislead people into thinking that will be enough for them to not have to change their eating habits.

[โ€“] [email protected] 2 points 1 year ago

Yes, it's still a transpiler, I'm not saying it isn't, but what I mean is that it doesn't add any functionally specific to the typescript language. There's a transpiler for TS that doesn't even do any type checking at all and just does the type stripping and back porting. But of course, that's not why people use typescript. All the features that are actually important to typescript could be done through a linter instead. If type annotations were added to JavaScript you could get most of typescript's features with linting rules and just handle back porting in a more standard way.

view more: โ€น prev next โ€บ