4 ms·
> it seems bizarre to me that he lists Javascript as an example of a language that is restricted and unable to do various things. * No exceptions (practically)
by fiedzia 10y ago
> it seems bizarre to me that he lists Javascript as an example of a language that is restricted and unable to do various things.
* No exceptions (practically)
* no built-on ways of providing abstractions
* No concurrency at all for a very long time
* No way of dealing with binary data
Those things were added later (classes, webworkers, arrays) when they became absolutely necessary. But it started and lived for a very long time as very minimal language.
> I have never once run into a problem that isn't easily solvable with Javascript.
Swallowing errors. Code quality. Solvable with typescript and others, but I wouldn't call it "easily sovlable".
- inimino 10y agoIf you think JavaScript didn't have ways of providing abstractions until classes were added, you don't know JavaScript.
- spion 10y agoI think Promises cover the first two nicely; they are an abstraction that gets you back exceptions. Also interestingly enough, one that would be impossible to write in Go. Not sure what you mean by "no concurrency". Perhaps you meant "no parallelism"?