jackmoore

“We trust the companies we work with,” Alec Asbridge, director of regulatory compliance at Georgia Department of Agriculture, said earlier this month. “We don’t see any reason they would submit information that wasn’t truthful.”

I feel like this statement makes Asbridge unsuited for his job as director of regulatory compliance. Willful obliviousness implies a conflict of interest.

What will this will cost once it's out of beta? Do you have any plan to open source the codebase?

jQuery is still much more pleasant to use than native methods when working with collections of DOM elements. If you do much DOM manipulation, you'll end up writing helpers that replicate aspects of jQuery to grease your workflow. The real issue is that trying to manage state by directly manipulating the DOM becomes a nightmare as the project grows, and newer frameworks can mostly take care of that for you.

So jQuery is still wonderful at what it does, but there isn't much reason to be directly manipulating the DOM now that there are alternatives.

I think this is true too, but it depends on how efficiently the utility company runs their business, and how much profit margin they are allowed to extract.

Utility companies aren't competing directly with each other for the lowest price, so in practice there could be a lot of places where, while less efficient, it's cheaper for home owners to have their own means of power production.

Maybe build in some system for followers to sponsor the accounts they like.

I see you are getting some negative feedback, haha. I think the main problem at this point isn't due client-rendering, but the large prerequisite files. Gzipping your JavaScript would trim a MB or more. Putting the static assets on a CDN (or enabling gzip yourself) would cut the render time by 2/3rds.

Semantic UI adds 700KBs of CSS, which seems like a lot more than your site should need. Even if this were a static rendered site, the browser would delay rendering anything until the CSS was downloaded.

Just wanted to remind folks that you can support the EFF through AmazonSmile.

Saying it's cheap, tacky, and childish definitely sounds cultural, since all of those are emotional rather than practical reasons. A photo can add a lot of important information what you are buying.

I would say try to be more objective because you may be missing out on opportunities to actually improve things.

Sure you can... there is no reason why those JavaScript styles can't be outputted to a css file in your preprocessing step.

I'm surprised voter turnout isn't lower. Unless you live in a swing state, or Maine or Nebraska, voting for president is a waste of time. If you are in a swing state, it still might not matter unless you are in a swing district. It's a terribly broken voting system.

I don't think anyone is claiming that vertical farming needs to disrupt all traditional farming. Vertical farms would bring food production to urban areas, where the people are. That benefit would be lost on growing livestock fodder.

I believe Netflix's Falcor, which seems very similar to Relay, uses JSON.

A lot of things may factor into that. Even if the increased police numbers are 100% responsible, we would still have to have a discussion about the diminishing return on that investment in order to maximize social good.

Agreed. I mainly use React these days, and directly modifying the DOM is starting to feel dirty.

DOM inconsistencies aside, a big advantage jQuery has over native API is that it is just as easy to work with multiple elements as it is single elements.

Modifying your example:

    var d = document.querySelectorAll('div');
    d = Array.prototype.slice.call(d);
    d.forEach(function(el){ el.classList.add('new') });

Vesus:

    $('div').addClass('new');

I think this needs some text outlining it's differentiation from Zepto. Why would I use this instead of Zepto?

> I should fork the library and annotate every method with its vanilla Javascript equivalent

To save you some work: http://youmightnotneedjquery.com/

That was a beautiful response.

I appreciate this comment. I think people hand-wave away the difficulties of running a small garden. Yes, sometimes things go great but often you are dealing with pests and diseases that require time, knowledge, and capital to resolve. If you can't make that commitment, then you just won't have any yield for that crop that year.

Self-sustainable living is an interest of mine, and one of my peeves is seeing folks on YouTube or Reddit posting tutorials on how to build a home hydroponic garden when it's clear that they have just finished building it. If you can keep it running for a couple of years, then that's when I would be interested in hearing more about it.

To be fair, we don't know how much worse the text was prior to bringing an editor on.

In fairness, this time it was submitted by the author and he is responding to comments.

Even though it feels very fad-ish because it's been used as a buzzword/bandwagon, I don't feel like it's actually a fad.

My view is that that digital design has matured to the point where designers no longer feel they have to wow users with lots of effects and visual flourishes, allowing for a more purpose driven design. My hope/opinion is that is here to stay.

Webstorage is a bit handicapped for SPAs. There is a 5MB size cap, and you can only store strings. It's nice as a cookie replacement, but the limitations hurt for anything more advanced. IndexedDB resolves these issues while also being fairly well supported.

I second drinchev's comment. You have no way of knowing what all potential contexts people are going to want to use buttons for. Applying styling to the bare element means frequently resetting those styles. It's always better to extend than to reset. I use button elements for any control that is handled via JavaScript. Only a minority of buttons I use are actually for form submission.

Nothing is always an option. Including anything that is unhelpful dilutes focus on the things that are.

I use Sip, a free osx app, give it a shot: https://itunes.apple.com/us/app/sip/id507257563?mt=12

I thought the same thing, then noticed the only files in the repository are the readme and info for contributing. I'm not sure where the actual project source is.

That's a lot of open issues…

That's really interesting, how did you get these statistics (do you work for Bloomberg, or do they have this publicly available somewhere)?