I didn't see any Dell, System76, Asus or HP laptops that were all metal and on par with a MacBook, only an Asus netbook.
319 karma · joined April 8, 2016
I didn't see any Dell, System76, Asus or HP laptops that were all metal and on par with a MacBook, only an Asus netbook.
It bugs the hell out of me that I can't buy a non-apple metal computer.
I'd come to work and a bunch of stuff was already done, etc.
So I'd say, try and make sure that you don't get so caught up in new stuff that you're no longer productive with old stuff. That can also be very frustrating.
I see Angular's directives as a pure convenience compared to most every templating engine I've used across languages, never considered it something that makes it accessible to non-programmers. I'd actually think someone who only knows html/css would be more thrown off from a page with random, unsanctioned (by W3C), tags and attributes that may or may not reveal what they actually do.
As a programmer I don't want to write long templates, I seriously prefer Jade/Pug for that reason. When I can't use them for a client I typically use them to do all initial work, compile them to HTML, then make whatever minor changes from there.
Consider ng-for:
<div data-ng-for="y in x">
<h1>{{y.title}}</h1>
</div>
The ASP.Net solution is a pain, a function with HTML string template to dynamically add elements to a "runat" div.This PHP example seems more idiomatic, at least to me, yet takes more to write
<?php foreach($x as $y){ ?>
<h1> <? echo $y->title; ?> </h1>
<? } ?>
The JSP style is kinda similar to Angular, again maybe more idiomatic at first glance but still not as quick/simple to write <c:forEach items="${x}" var="y">
<h1>${y.title}</h1>
</c:forEach>
The jQuery/plain JS solution, especially before ES6 is not preferable by any means, especially beyond this simple example. var body = document.getElementsByTagName("body")[0];
[...].map(function(y){
body.innerHTML +=
"<div>"+
"<h1>"+y.title+"</h1>"+
"</div>";
});
Unlike all the other solutions, angular has 2 way data binding so when you programmatically add elements to the array in ng-for, they are added to the DOM without a reload.So, is the goal of a programmer to simply write more code? If so, then Angular is definitely not for programmers.
Is the goal of a programmer to solve problems? If so, Angular is definitely a tool for programmers.
I kinda just stopped reading Google news rather than try to fix it (:
I'd argue that the state should own historic artifacts so that they can be held in common. That way no one individual can claim ownership, retain the right to destroy it if they wish, and prevent others from viewing/studying it.
Of course the state isn't going to let me or you handle it, but they'll obviously give access to research institutions and whatnot who will publish their findings. Hobby Lobby dude might not do the same and as a private owner, he retains the right not to.
Super nice IMO
Is there anything that comes close to this in scope/quality for any other platform?
Guess they're simply JSON apis. I don't really care to parse XML so I guess I won't be getting any REST from my apps.
I think 2560x1440 is probably the ideal resolution for the time being, looks good enough, no need for a graphics card, cheap monitors, etc.
Isn't that the point? The demo seems like it'd be a lot easier, less verbose, and probably less brittle, than using cUrl/xpaths or otherwise parsing that HTML yourself.
http://www.huffingtonpost.com/entry/venmo-cuba-sanctions_us_...