HNHacker News
TopNewBestAskShowJobs

larzang

706 karma · joined July 4, 2014

submissionscomments
larzang··on How Much do you Need to Earn to Afford a Modest Apartment in Your State?
It is, click on a state.
larzang··on American Trailer Parks: The owners are getting rich
It's absolutely absurd to try to assert that overpopulation is the root problem with a straight face when you're dealing with a system with such radical inequality.

Yes, piling more people into the box of fighting for a single-digit percent of a single-digit percent of the wealth in the US is rarely great for anyone, but the root problem is not the people being added but the minuscule scraps they're forced to fight for while the rich get richer.

Barring outliers like NYC, the US is centuries away from even population density _parity_ relative to most of the rest of the world.

larzang··on A Bitcoin miner in every hand
And the end-users's motivation for ever purchasing anything with is... off-setting short term costs with long term costs that make payday loans look like a fair deal?
larzang··on How Eve Online went to the edge of apocalypse and back
It's extremely odd that the article completely fails to mention the real apocalypse that almost broke Eve, and was the real motivator for the establishment of the CSM years before the Summer of Rage: staff cheating. In an MMO, not having staff play the game often leads to a strong disconnect between the company's interpretation of the state of the game and the reality, but in an MMO like Eve where the entire game is built on forging long term interpersonal relationships on a massive scale, having staff play the game can present a great danger too.

The most successful of the early 0.0 power alliances was fueled in part by having a developer who revealed his identity to the alliance leadership, funneled limited rare items (blueprints) to them which were used to fund the alliance's growth, and abused their GM powers to threaten other alliances.

The revelation was a massive blow to the playerbase's faith in CCP and the CSM was established in large part to increase the transparency and communication between CCP and the playerbase, as some of the foul play was long-suspected but the concerns unheeded.

larzang··on Under the hood: Facebook’s cold storage system
Bulk content (when cloud storage might not be appropriate) is rarely important enough for reliability to be a concern, and home NAS is totally insufficient for reliability when it comes to truly important content as it does nothing for theft, fire, etc.

If my home media library gets wiped out by hardware failure, replacing it would be an annoyance but not a disaster. Anything that would be a disaster is covered by at least two cloud services.

larzang··on 210 Zappos employees – 14% of the staff – take buyouts after CEO ultimatum
Valve is the exception that proves the rule, i.e. you need a stable cash cow so large that your frequently-aimless often-delayed progress on anything else doesn't break the company.
larzang··on Ways to manage conflicts with cops in a medical emergency
A much larger and more frequent issue than police/emt conflict over the handling of medical emergencies is police being dispatched to medical emergencies as sole or first responders and handling it like... police.

There have been dozens of cases in the past few years in which police have been sent to medical emergencies and responded with unwarranted and fatal violence towards the people they should have been helping. That's not even counting cases like Kenneth Chamberlain Sr, in which there was no emergency, officers were notified of this shortly after arriving, and they proceeded to assault and murder a man who had done nothing wrong in his own home anyway.

Calling 911 for assistance for a mentally ill family member can literally be a death sentence, and that is an intolerable state of affairs.

larzang··on Microsoft Edge – The Browser for Doing
You can already do this with IE on Win8
larzang··on Ask HN: What is your Linux distro of choice?
Of course you can. You can install any DE you want on top of Mint, it's still Linux, and you can modify the appearance of the shipped XFCE or Cinammon DEs with themes.
larzang··on Ask HN: What is your Linux distro of choice?
Mint. I need Sublime + terminals + browsers to work, anything else is gravy, and Mint does the best job of providing sane defaults and making it easy to change the few minor things I do.

15 years ago I didn't mind spending hours (days weeks) tweaking config files to get everything about my distro absolutely perfectly customized, now I just want it to work out of the box and get out of my way so I can get real work done.

Cinammon also has the nicest workspace management of any desktop environment I've tried, which is a solid bonus since it's probably the DE-specific feature I interact with most on a day to day basis.

larzang··on Towards Realtime Deformable Worlds: Why Tetrahedra Rule, Voxels Drool
EQNext and Landmark are using a voxel engine. I can't speak to implementation on the EQNext side as it's not in a publicly testable form yet, but on the Landmark side it's been quite a while since we've seen any meaningful engine improvements and it's rather primitive in many respects.

Things like having to elaborate hacks to get sub-voxel shapes and imperfect precision with rendering intersecting edges seem like limitations of any voxel based design, while the crude handling of lighting and reflections and very short LOD distance seems to be intentional limitations for performance reasons (and understandable given average voxel counts in player-created areas).

larzang··on As encryption spreads, U.S. grapples with clash between privacy, security
There's no need to even go back that far. The treatment of David Miranda, Manning's imprisonment, Kiriakou's imprisonment, Snowden's ensured imprisonment should he ever leave the safety of his current umbrella, continued harassment and infiltration of anarchist and leftist orgs in California and Oregon and elsewhere by all levels of law enforcement.

The FBI continues to disproportionately expend resources on environmental groups despite no cases of loss of life from green direct action, while admitting themselves that right-wing militias present a greater domestic threat than even the dreaded foreign terrorism they're so happy to prove they're protecting us from by spending years deliberately radicalizing and then entrapping harmless fools.

Law enforcement motivations cannot be ever trusted when it comes to your privacy.

larzang··on Gone in a Flash: The Race to Save the Internet's Least Favorite Tool
Well, restaurants and small businesses in general usually have websites that come about through the joining of customers who have no understanding of ux or the trade-offs that come with going for the showiest thing possible, and creators who are offsetting their low prices by pushing through jobs as quickly as possible and don't have time to go through the delicate dance of telling the customer that their desires are unreasonable and awful.
larzang··on Chelsea Manning is tweeting from prison
It's voluntary in that you can choose to work or you can choose to be thrown in solitary, beaten, and starved, until you stop refusing to work.
larzang··on Things you should know about PHP 7
Okay, sure, instead your new job is to play security and sysadmin for the DigitalOcean containers for all the small local business Wordpress sites for say $10 an hour.

Shared Hosting has many downsides, but it still fills an incredibly important niche for businesses for whom a web presence beyond a Facebook page is needed but real managed hosting is completely out of their price range.

larzang··on The new MacBook
Yeah, who on earth uses headphones with a laptop. Crazy.
larzang··on Web typography for non-designers
This article falls for one of my major designer pet peeves: using heading tags as style tags.

Having a fixed relative ratio of font sizes for h1-h6 makes no sense because heading tags (as all html) are structure, not style. They are used to indicate the relative importance of heading text within a page and/or section, and should have a semantic css class appropriate to their role applied.

Depending on how a page is structured, a h2 may be a section heading, or an article heading, or a page sub-heading, or many other things, and each of those roles may call for very different styling relative to a h1 page heading.

larzang··on 1Password on Linux
Keepass 2.x handles merges for you just fine. The mono version of Keepass 2.x is ugly and a little clunky compared to KeepassX or the windows version of 2.x, but it's good enough.
larzang··on Lenovo Caught Installing Adware on New Computers
Clevo makes high quality laptops that are also very reasonably priced when bought barebones from the right vendor (they don't do direct consumer sales). Sager, System76, FalconNW, and a whole bunch of other boutique laptop companies are actually selling rebadged/modified Clevos.
larzang··on The Worst Way to Fire Someone: I Was There
Doing it live isn't necessarily better.

On May 14, 2007, the staff of Sigil Games Online were told to meet in the parking lot at 4:30PM and to take with them what they would need for the rest of the day. The employees were told that the launch of the game had not gone well, the company was in financial trouble and they were selling the company to Sony Online Entertainment. Director of Production, Andy Platter, then told the employees "You're all fired."

larzang··on How the iPad Went from Massive to ‘Meh’ in 5 Short Years
I wonder what the sales numbers look like if isolated solely to commercial/education/government purchases. The small business I work for is one of a number in the area that has transitioned to an iPad solution (Square stand) for all our POS needs in the last year, and there are a lot of other business use cases where tablets make far more sense than the alternatives, much more so than for people at home.
larzang··on Next Week's Bloodbath At IBM Won't Fix The Real Problem
My father was a PM at IBM who was hit in one of the smaller rounds of layoffs in 92 leading up to the big one in 93. He worked at the Westlake campus in DFW at the time. The entire project he was on was cancelled and all of its staff were cut, and it was just one of many. Personal metrics didn't enter into it, it was just a question of whether you were lucky or unlucky in project assignment at the time.

Over those couple of years IBM went from using almost all of the sizable campus it had built to just one small section, renting out the rest. DFW was otherwise undergoing massive growth at the time though, so the cuts were readily absorbed by Dell, MS, and many others (my father went to AMR). It wasn't like in the early 2000s when virtually everyone in DFW was downsizing or closing and as a fresh college graduate I was competing for entry-level jobs with admins with 10 years at MS.

larzang··on Sass Guidelines
I have to really disagree about extend. Yes, it's easy and potentially disastrous to misuse extend erratically, but used sanely there should never be side effects and your compiled css should be smaller than otherwise.

Regarding side effects, they're easy to avoid if you structure your main file in a logical way. For generic extension, your library of base classes (both actual classes and silent classes) should be included before your components which extend and build on them, therefore any inherited styles come before (and can therefore be overwritten by) the extending component but never the other way around. When extending a component, the extending objects should always be in the same file and come after (e.g. .gallery followed by .gallery-foo and .gallery-bar which both extend .gallery). If full blown objects/components are related enough to extend, they're related enough to be in the same file.

Avoiding extend compiled file size bloat mostly comes from sane nesting behavior that you should be following regardless. Adding single selectors to an extended rule is almost always going to be smaller than inlining/mixing that rule, even for simple rules.

Discoverability is always going to take a hit with extend, yes, but in my opinion dryness, single-point-of-change, and compile size are far more important than in-file discoverability, assuming your project layout is sane. Extend in sass isn't really any different than using traits in oop languages, it's an incredibly useful pattern when employed correctly.

larzang··on Sass Guidelines
I have to really disagree about extend. Yes, it's easy and potentially disastrous to misuse extend erratically, but used sanely there should never be side effects and your compiled css should be smaller than otherwise.

Regarding side effects, they're easy to avoid if you structure your main file in a logical way. For generic extension, your library of base classes (both actual classes and silent classes) should be included before your components which extend and build on them, therefore any inherited styles come before (and can therefore be overwritten by) the extending component but never the other way around. When extending a component, the extending objects should always be in the same file and come after (e.g. .gallery followed by .gallery-foo and .gallery-bar which both extend .gallery). If full blown objects/components are related enough to extend, they're related enough to be in the same file.

Avoiding extend compiled file size bloat mostly comes from sane nesting behavior that you should be following regardless. Adding single selectors to an extended rule is almost always going to be smaller than inlining/mixing that rule, even for simple rules.

Discoverability is always going to take a hit with extend, yes, but in my opinion dryness, single-point-of-change, and compile size are far more important than in-file discoverability, assuming your project layout is sane. Extend in sass isn't really any different than using traits in oop languages, it's an incredibly useful pattern when employed correctly.

larzang··on Sass Guidelines
I have to really disagree about extend. Yes, it's easy and potentially disastrous to misuse extend erratically, but used sanely there should never be side effects and your compiled css should be smaller than otherwise.

Regarding side effects, they're easy to avoid if you structure your main file in a logical way. For generic extension, your library of base classes (both actual classes and silent classes) should be included before your components which extend and build on them, therefore any inherited styles come before (and can therefore be overwritten by) the extending component but never the other way around. When extending a component, the extending objects should always be in the same file and come after (e.g. .gallery followed by .gallery-foo and .gallery-bar which both extend .gallery). If full blown objects/components are related enough to extend, they're related enough to be in the same file.

Avoiding extend compiled file size bloat mostly comes from sane nesting behavior that you should be following regardless. Adding single selectors to an extended rule is almost always going to be smaller than inlining/mixing that rule, even for simple rules.

Discoverability is always going to take a hit with extend, yes, but in my opinion dryness, single-point-of-change, and compile size are far more important than in-file discoverability, assuming your project layout is sane. Extend in sass isn't really any different than using traits in oop languages, it's an incredibly useful pattern when employed correctly.

larzang··on Sass Guidelines
I have to really disagree about extend. Yes, it's easy and potentially disastrous to misuse extend erratically, but used sanely there should never be side effects and your compiled css should be smaller than otherwise.

Regarding side effects, they're easy to avoid if you structure your main file in a logical way. For generic extension, your library of base classes (both actual classes and silent classes) should be included before your components which extend and build on them, therefore any inherited styles come before (and can therefore be overwritten by) the extending component but never the other way around. When extending a component, the extending objects should always be in the same file and come after (e.g. .gallery followed by .gallery-foo and .gallery-bar which both extend .gallery). If full blown objects/components are related enough to extend, they're related enough to be in the same file.

Avoiding extend compiled file size bloat mostly comes from sane nesting behavior that you should be following regardless. Adding single selectors to an extended rule is almost always going to be smaller than inlining/mixing that rule, even for simple rules.

Discoverability is always going to take a hit with extend, yes, but in my opinion dryness, single-point-of-change, and compile size are far more important than in-file discoverability, assuming your project layout is sane. Extend in sass isn't really any different than using traits in oop languages, it's an incredibly useful pattern when employed correctly.

larzang··on Sass Guidelines
I have to really disagree about extend. Yes, it's easy and potentially disastrous to misuse extend erratically, but used sanely there should never be side effects and your compiled css should be smaller than otherwise.

Regarding side effects, they're easy to avoid if you structure your main file in a logical way. For generic extension, your library of base classes (both actual classes and silent classes) should be included before your components which extend and build on them, therefore any inherited styles come before (and can therefore be overwritten by) the extending component but never the other way around. When extending a component, the extending objects should always be in the same file and come after (e.g. .gallery followed by .gallery-foo and .gallery-bar which both extend .gallery). If full blown objects/components are related enough to extend, they're related enough to be in the same file.

Avoiding extend compiled file size bloat mostly comes from sane nesting behavior that you should be following regardless. Adding single selectors to an extended rule is almost always going to be smaller than inlining/mixing that rule, even for simple rules.

Discoverability is always going to take a hit with extend, yes, but in my opinion dryness, single-point-of-change, and compile size are far more important than in-file discoverability, assuming your project layout is sane. Extend in sass isn't really any different than using traits in oop languages, it's an incredibly useful pattern when employed correctly.

larzang··on Sass Guidelines
I have to really disagree about extend. Yes, it's easy and potentially disastrous to misuse extend erratically, but used sanely there should never be side effects and your compiled css should be smaller than otherwise.

Regarding side effects, they're easy to avoid if you structure your main file in a logical way. For generic extension, your library of base classes (both actual classes and silent classes) should be included before your components which extend and build on them, therefore any inherited styles come before (and can therefore be overwritten by) the extending component but never the other way around. When extending a component, the extending objects should always be in the same file and come after (e.g. .gallery followed by .gallery-foo and .gallery-bar which both extend .gallery). If full blown objects/components are related enough to extend, they're related enough to be in the same file.

Avoiding extend compiled file size bloat mostly comes from sane nesting behavior that you should be following regardless. Adding single selectors to an extended rule is almost always going to be smaller than inlining/mixing that rule, even for simple rules.

Discoverability is always going to take a hit with extend, yes, but in my opinion dryness, single-point-of-change, and compile size are far more important than in-file discoverability, assuming your project layout is sane.

larzang··on Sass Guidelines
I have to really disagree about extend. Yes, it's easy and potentially disastrous to misuse extend erratically, but used sanely there should never be side effects and your compiled css should be smaller than otherwise.

Regarding side effects, they're easy to avoid if you structure your main file in a logical way. For generic extension, your library of base classes (both actual classes and silent classes) should be included before your components which extend and build on them, therefore any inherited styles come before (and can therefore be overwritten by) the extending component but never the other way around. When extending a component, the extending objects should always be in the same file and come after (e.g. .gallery followed by .gallery-foo and .gallery-bar which both extend .gallery). If full blown objects/components are related enough to extend, they're related enough to be in the same file.

Avoiding extend file size bloat mostly comes from sane nesting behavior that you should be following regardless. Adding single selectors to an extended rule is almost always going to be smaller than inlining/mixing that rule, even for simple rules.

Discoverability is always going to take a hit with extend, yes, but in my opinion dryness, single-point-of-change, and compile size are far more important than in-file discoverability, assuming your project layout is sane.

larzang··on Sass Guidelines
I have to really disagree about extend. Yes, it's easy and potentially disastrous to misuse extend erratically, but used sanely there should never be side effects and your compiled css should be smaller than otherwise.

Regarding side effects, they're easy to avoid if you structure your main file in a logical way. For generic extension, your library of base classes (both actual classes and silent classes) should be included before your components which extend and build on them, therefore any inherited styles come before (and can therefore be overwritten by) the extending component but never the other way around. When extending a component, the extending objects should always be in the same file and come after (e.g. .gallery followed by .gallery-foo and .gallery-bar which both extend .gallery). If full blown objects/components are related enough to extend, they're related enough to be in the same file.

Avoiding extend file size bloat mostly comes from sane nesting behavior that you should be following regardless. Adding single selectors to an extended rule is almost always going to be smaller than inlining/mixing that rule, even for simple rules.

Discoverability is always going to take a hit with extend, yes, but in my opinion dryness, single-point-of-change, and compile size are far more important than in-file discoverability, assuming your project layout is sane.

← PreviousPage 5 of 6Next →