quadratini's comments

quadratini | 11 years ago | on: The new MacBook

Going from 1920x1080 (16:9) to 1920x1200 (16:10) is better because you get more vertical estate. But you seem to suggest that 1728x1080 (16:10) is also better. Aspect ratio does not automatically make a resolution better lol.

quadratini | 11 years ago | on: The new MacBook

Achieving 16:10 by taking a standard 16:9 resolution and making it less wide rather than making it taller is not better.

quadratini | 11 years ago | on: Ask HN: What's the problem with AngularJS?

It was a rhetorical question. I understand why we need to use a special version of setTimeout or a special HTTP module, but the fundamental problem is that Angular's "reactive javascript" abstraction leaks in a way that you're forced to do it the Angular way.

React's abstraction also leaks, which is evident when it doesn't automatically know to update itself so you have to call `setState`. But I'd choose this set of leaky abstractions over Angular's. Plus it makes it easy to spot all the places where the UI can change which is a huge plus for debugging. The beauty of React's set of abstractions is that it doesn't force you to do things a certain way (use $http, use $timeout) or use observables which embraces mutability.

Also to further my point that Angular (and any other framework that provides templating) doesn't embrace javascript, every time you use `ng-repeat` you're not doing javascript. You can't put a debugger in the middle of the loop to check the scope. You can't use Immutable-js because `ng-repeat` loves arrays. (Ok you can convert the immutable to an array before hand, but then when it changes you'd have to incur an expensive rerender of the list) You can't use static analysis tools.

quadratini | 11 years ago | on: Atom now using Io.js

Ever need to peek inside a browserify'd bundle with inline source maps to check transformations (e.g. 6to5)? Those can easily be over 2MB.

quadratini | 11 years ago | on: Ask HN: What's the problem with AngularJS?

Angular abstractions leak everywhere: http://stackoverflow.com/questions/18826320/what-is-the-hash... http://stackoverflow.com/questions/16935766/run-jquery-code-... <- "You might need this timeout to be sure its run after DOM render." wat

- You have to do everything the "angular way". Timeouts, intervals, http, modules, angular.toJson. It's a pain. Why can't I use the regular setTimeout, or ES6 or Common JS modules, or JSON.stringify?

- You end up having to dig inside the source code to debug issues with Angular.

- You basically HAVE to understand the digest cycle.

- Its way of doing templating is crippled in the sense that it's not as expressive as javascript.

- Honestly I think it's for people who doesn't like javascript and its ecosystem (npm).

React isn't alike angular because that's the point. React embraces javascript whereas Angular doesn't. If you want a http library use one of your choosing from npm, like axios. You want to use Common JS modules? Go ahead.

page 1