There's no right not to be offended
HN user
quadratini
I'm enjoying it!
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.
Achieving 16:10 by taking a standard 16:9 resolution and making it less wide rather than making it taller is not better.
He's missing the point of Declarative vs Imperative and Virtual DOM vs Data Binding if he thinks it will circle back to jQuery.
It's right associative, normally :)
Javascript. ES6.
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.
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.
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.
Bad code leads to inconsistent behavior. Who would have thought.
Coffeescript is pretty damn ugly. For god sakes can people please use parenthesis when calling functions with arguments?
It's only lazy if it's part of a chain
Have you tried React? It embraces Javascript.
It pretty much comes down to imperative vs declarative thinking.
And his point still stands. This is news.
Very smart to use blank text nodes to get rid of those annoying script tags!
no.
What is crazygames and why is nothing happening on that page?
please properly indent the code snippents
It really doesn't deserve the real estate that it's taking up. Terrible decision imo.
YES. 1000+ commits is so useless. Also I wanted to look at the commit history and it was entirely unobvious that you can click "1000+ commits".
typical designer. they just look at static mockups and don't think about interactions. okay if you have the 2x2 icon, how will other icons move relative to it when the big icon is moved around?