Additionally, in places where there's loads of green energy, crypto mining captures excess energy and discourages innovation in energy storage.
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.
This is literally addressed in the article. All the other blockchain ideas also reward those with existing, large-scale, wealth in the real world (the way that Proof of Work rewards those that spin the most GPUs)
The italics are amazing - very visible and distinct from the regular font, making it a great tool for validation. E.g. it's very noticeable when a CSS rule is not italic all of a sudden (misspelled). It adds a nice layer on top of colors to distinguish between different states.
Spending time designing in photoshop and then "cheaply" "outsourcing" HTML and CSS development, aka your _actual_ website, is a terrible idea. There are people who implement designs well, and they are worthwhile to hire if you don't know browsers; they're certainly not cheap.
By all means, I would love to have element queries. They would definitely help in many cases. You would have to limit their use to just those areas of markup where container widths are explicit.
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.
Media queries are still necessary to lay out the page you've described. The primary containers of your pages all need to move around based on the size of the top-level container.
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.
you still have to base it off either the parent (.signup-page .testimonial) or a conditional that's only used on a particular page (.testimonial.compact). The media queries are sub-optimal but it's contained within .testimonial. Here's how it can look:
.testimonial {
media screen and (max-width: 900px) {
font-size: 0.8em;
}
&.compact {
media screen and (max-width: 1200px) {
font-size: 0.8em;
}
}
}
GWT is definitely not going to help the problem the author is talking about. GWT's "packaged" components still end up as the same markup and CSS. In most backend frameworks I'm talking about the Helpers, in GWT this would be some "View", or whatever isn't the presenter.
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.
This creates separate click areas for "change the name of this tag" vs "add an attribute". I find myself adding classes and attributes often, so I'm a proponent of <tag >.
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.
FF's web console has some nice resizing features to test responsiveness. They keep me coming back and trying aurora once in a while but the CSS property / value editor is currently lacking.
Either keyboard shortcut mappings for web console commands, or a simultaneous view of different responsive sizes would definitely be killer for responsive development.
Auto-complete for css properties and easier value editing (up/down arrows) would definitely be a huge help. With that, I could see myself switching to FF for CSS 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.
Python's Flask is a superb Sinatra clone, and Django's ActiveRecord equivalents are equally useful in Flask, especially for Mongo. Flask sits on top of Werkzeug, which is similar in power and use cases as Rack - middleware, fine-grain auth, etc.
Ok. I don't comment on Hacker News much, but this article sent me reeling. <rant> The sheer hypocrisy in this thing is unbelievable. First of all, TechCrunch has already stated their opinion on AirBnB, and even published follow-ups attacking the pro-AirBnB counterarguments. Fine. You don't like them. We get it, there have been like 10 posts including the words "scandal", "fiasco", and "the plot thickens", despite an almost total lack of actual information. Yeah, it's a shitty situation so let the police, EJ, and AirBnB work it out. You think they won't have a post-mortem? Please.
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>
If forrst users create anything like Orman Clark's premium pixels (http://www.premiumpixels.com/), it's probably very useful for inspiration and discussion. if you want a blog with deep discussions, then A List Apart is hard to beat.
Accessing your friends is not an extended permission as mentioned in another comment, any app you give permissions to can access your friends and get their ID's and Names.
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.