73 karma · joined June 3, 2009
Rather than electricity prices being driven down by more green production and storage, there's this floor where it's better to just convert the energy into blockchain coin flips and heat.
news.yc doesn’t like the fact that its main craze for years has been outed as a global affliction, destroying the climate with impunity.
If it shows up in 18 places I bet you there will be two different contexts with the same container size, but different looks, and element queries won't help you at this point. You'll still need to tailor your CSS classes for different contexts.
If you could only rely on your parent, that would also be problematic - the size of a component would be dependent on its chain of parents. If you were reusing the same component within further containers, say 3 different pages, you might want two to look the same despite a size difference, and element queries don't help you anymore. You just need a .testimonial.compact class, have slitghtly different media targeting, and now you have two types of testimonials that you can use on further pages.
Element queries could also easily create strange loops that cause the threshold to be crossed recursively, if the parent bases its width on the child. This is the case with inline-block elements and the property-which-must-not-be-named.
.testimonial {
media screen and (max-width: 900px) {
font-size: 0.8em;
}
&.compact {
media screen and (max-width: 1200px) {
font-size: 0.8em;
}
}
}You would still need to use different CSS in the two cases mentioned, so it would be two different packaged components in GWT, two different Views. Maybe interiting from one another, but certainly far FAR more lines of code than a conditional / "modifier" CSS class. .testimonial.compact vs just a normal .testimonial, for instance.
Chrome's tools only show <tag>, and the only way to add a class requires two clicks on "tag", and then a click on ">", which is really wonky.
Either keyboard shortcut mappings for web console commands, or a simultaneous view of different responsive sizes would definitely be killer for responsive development.
The responsive features in the web console - which imho HAS to be monosopace - are also definitely exciting, and make me want to switch to FF.
This article, however, kills me. He bashes Huffington Post's decision solely on the title. With a title like "You know what's not cool? A Billion Dollars. You know what's cool? Basic human decency", TC is playing the same game here. Except they're even cheesier in their delivery.
The only other example of lack of "basic decency" presented in this article is AirBnB, which anyone coming from HN could probably see a mile away. Same quotes, same rhetoric. Could you possibly be caring about anything except getting more eyeballs on your site? Please, go watch some Alexis Ohanian talks. Make a good product. Engage people. Don't bash your own bread-and-butter techniques like you're on some higher moral ground.
The AirBnB guys made a big product, and it's been super convenient to me. They're reaching the point where their popularity leads to difficulty in control and direction. This just happens to be the same effect touched on in that Amy Winehouse article. Hey TechCrunch? You are getting really bad at journalism and your opinions are nothing but twitter fodder. </endrant>
Brushes, private rooms, etc? Probably still wouldn't be too useful, but a great proof-of-concept.
hahaha
If any of them want to listen to music with legitimate headphones, they have to buy adapters to fit the intentionally-small opening. It's the same for all their proprietary plugs and devices. They exclude other RAM and hardware manufacturers from their desktop, even those that produce better products at a cheaper price.