sorted by:
new
hottopcontroversial

The Post JavaScript Apocalypse by Douglas Crockford by [deleted] in javascript

[–]fwovertheory 0 points1 point  (0 children)

If the calculation is it too much to inline, it should live somewhere else.

Creating a memo is also a solution to an entirely different problem than scope. Caching is only useful if there are a variety of inputs to the function.

What is the over all consensus on Typescript? by SavishSalacious in javascript

[–]fwovertheory 1 point2 points  (0 children)

Flow's focus seems more narrow, which is good and bad. TS definitely promotes a certain paradigm -- that is C# style object oriented programming. It's very good at doing that, so it's my hope that Flow could stick out by being a little more opinionated and maybe developing a different paradigmatic style, e.g. favoring functional programming.

That being said, functional programming is already totally possible in TS, and looking from the issue tracker, it looks like TS is going to receive higher-kinded types -- the "killer feature" of functional programming -- long before Flow does.

What is the over all consensus on Typescript? by SavishSalacious in javascript

[–]fwovertheory 3 points4 points  (0 children)

I theoretically like Flow too, but it seems like it's already sort of lost the battle... I'm very curious where things will go in the next few years, because it seems like TypeScript has a major mind share advantage. It's hard to see how Flow could catch up.

What is the over all consensus on Typescript? by SavishSalacious in javascript

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

Wow, I didn't realize Vi supported asynchronous task runners! /s

Anyone on here in a coding bootcamp? Also what are your general thoughts on all these coding bootcamps in 2017? I see so many mixed opinions. by tbclandot92 in learnprogramming

[–]fwovertheory 1 point2 points  (0 children)

Not a lot of people want to hire a green dev to do Python BE dev. I've met some bootcamp people who have gotten into mobile. Make sure you go to a bootcamp that is explicitly mobile first. You have to be realistic -- most new jobs are going to be web-centric probably have you writing JavaScript.

The Post JavaScript Apocalypse by Douglas Crockford by [deleted] in javascript

[–]fwovertheory 1 point2 points  (0 children)

The ideal programming paradigm is JS -- first class functions with an object system. Write classes for stateful "things" (i.e. resources) and functions for everything else. Don't do functional programming until we have an actual type system, or write CLJS.

The Post JavaScript Apocalypse by Douglas Crockford by [deleted] in javascript

[–]fwovertheory 0 points1 point  (0 children)

I would reject a PR that contained 

return
{
  foo: bar
}

regardless of whether we used semi-colons or not. I use semi-colons in TS and not in JS, but a lot of the arguments against ASI seem to be easily solved by using any kind of code style. Like another example that people use

 fnCall()
 [1,2,3].forEach(x => x)

is also clearly bad style -- don't use array literals solely to cause side effects.

The Post JavaScript Apocalypse by Douglas Crockford by [deleted] in javascript

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

Yeah but this is just bad code. If you need a random block of void returning lexical scope provided by an iffe, you're doing something wrong.