emitstop

It's only a matter of time though.

Fine by me. The real Gucci Mane is back out of prison, what do we need this one for.

Is there any reason they can't just go back to Google? I thought they only switched to Yahoo because the contract was up and Yahoo offered a deal they couldn't walk away from.

92 people per day isn't "uncommon". It might be statistically improbable, but that's not what uncommon means. It's a regular, daily occurrence for 92 real human lives every day.

This is the first fatality collision after 130 million miles of tesla's autopilot, so it's already above that bar.

Additionally, 92 people are killed in fatal car accidents in the US every day. So it's not as though this is some uncommon occurrence that autonomous vehicles would be unlikely to improve.

So all they determined was everyone already has the top installed (and often pre-installed) apps already installed? What a surprise.

Also I would love to install more apps but to do so I have to clear space on my phone, and the apps I already have are slowing my phone down and eating my battery. For me it's always a matter of resources.

Yeah and they have for a very long time too. I remember getting Safeway delivered like 10-15 years ago. And that was in a pretty small town too.

Yeah and I like how he goes in on 'Agile Gurus' and then at the end of the article plugs his continuous delivery conference like it isn't the exact same thing in a different hat.

I assume when referring to PSD-driven development you mean to say the process of having a designer design a non-responsive, static mockup which is delivered the the front end dev team? I think this is important to clarify because a lot of people tout Sketch as being the answer despite it having the exact same pitfalls and issues Photoshop does.

https://keminglabs.com/boxbox/dynamic-layout-engine/

Check out this demonstration. I really think this is going to be the next big step forwards for designers. I don't think they need to fully understand CSS, the box model, flexbox, the dom, inheritance, etc to deliver effective designs. They just need to be forced to follow these limitations of these things within the design tool itself.

I think the idea is to make every change the designer makes reflect a nearly identical change that the frontend devs are going to have to also make. For example, text color inheritance is a notoriously hard thing for a designer to grasp. If that was handled automatically for them, they are going to out of necessity, create a more code friendly color inheritance hierachy in their designs.

This problem is the bane of my existence as a css/html guy. However I don't believe the core problem is what you suggest. Forcing designers to just work within wireframes isn't going to work. Assets and wireframes is only a small part of what a designer does when creating a good user experience.

I think the solution is going to lie somewhere inbetween, with designers needing to expand their knowledge and working within tools that are based on how CSS and HTML actually function instead of a program that allows you to just place boxes wherever you want and hope its easy to code.

I've been following what these guys are doing over at BoxBox, they are onto something big I think. https://keminglabs.com/boxbox/

Terrible and flawed on so many levels I can't believe it

You're confused on the definition of startup. https://en.wikipedia.org/wiki/Startup_company

Generally newly created, but not necessarily. In 'The Lean Startup' by Eric Ries one of the primary examples is based around Intuit, which is a large publicly traded company.

Not surprised at all, there hasn't been any updates or improvements in awhile, especially for the desktop app, it's nearly unuseable with its current bugs. Seemed like Dropbox never put enough resources into it for it to really get off the ground.

I've switched to airmail for the time being, but I'm definitely going to miss snoozing emails to specific dates.

Well I think its an out of sight, out of mind kind of thing. Something commented out is generally something you know you'll want to be referencing again. Coming back to something in the future you/your teammates might not even remember/realize that the deleted code was ever there.

Until someone makes that, you should be able to just diff the two files, see what sections were removed and go based on that.

The methodology gives you the tools to have control over the cascade. You cannot avoid it entirely.

Edit: Also the point I was getting at was that cascade is a useful and powerful tool, just as the methodologies for controlling it are. We will also soon have a property that will eliminate the cascade entirely... all:unset;

I just think the problems and solutions listed in the talk are either non-problems or are things that could be solved in superior ways. And that it introduces more problems and limitations than it solves.

For many reasons, namely that we've already solved most of these "problems" years ago with simple concepts like OOCSS, SMACSS, and BEM. I suggest taking a look at this rebuttal. http://keithjgrant.com/posts/against-css-in-js.html

The reasons people are running into problems with global css scope is because they don't understand the basics of how to write effective and maintainable CSS. Seems like many front end devs nowadays grew up with css hand-holding libraries like bootstrap, and can't seem to wrap their heads around completely necessary things like taking account for CSS specificity and how the cascade works and how to use it to your advantage.

Just starting to realize how out of touch HN readers are with CSS. This mindset does not belong in a conversation about CSS in 2015.

If you can select to copy its no different than a screen reader. There's is 0 usefulness to this, and it's embarrassing that it's on the front page of hacker news right now.

Seriously, this is the stupidest thing I've ever seen. Why are people pretending this would be useful in any way at all?

I see how its a fun exercise in CSS and everything, but actually providing it as a download as if people will use this productively is stupid.

As someone who spends a lot of his time playing around with drum machines, I couldn't figure out how to use this. I was only able to make lines without laying down any individual notes. Not sure what I'm missing here?

Also another thing to note, is that setting up the key triggers in alphabetical order like that is odd and really unintuitive. The standard for most digital audio workstations is to line up the top two rows of qwerty keys like they are piano keys (qwerty row = black piano keys, home row = white piano keys), and use 'z' and 'x' to change the octave.

Glad to help! Feel free to shoot us an email if you end up integrating us somewhere, we're very excited to see what people will do with these!

That'd be a great balance, and something we're going to look into. It does however, complicate the conversion script so as to not accidentally replace Unicode characters contained within the <img> tags, so it'd require a fair amount of testing.

Hey, thats a great idea! We went ahead and just added it to our json file, as "category_order". :)

Hey, we actually aren't trying to create a new standard, that would be awful and not what we're trying to accomplish. We're closely following the emoji standard published by Unicode, which all of the other major emoji sets follow as well.

Most implementations of emoji on the web use Apple or Twitter's emoji sets, which are not open source and may put you at risk of copyright infringement. Native implementation is fairly great on mobile at the moment, however desktop is another story, often displayed as just black boxes(most notably in Google chrome).

Some more info on the unicode emoji standard: http://www.unicode.org/faq/emoji_dingbats.html

Hey sorry for the confusion,

Some of the FAQ questions are geared towards the general public, check out our github page for more detailed development info: https://github.com/Ranks/emojione

Unicode has set a standard for all emoji sets to follow, but if you want to implement them on the web, native desktop display varies drastically depending on the users device, and in a lot of cases there is no support at all (Chrome on windows).

This is especially useful for sites that accept input from mobile devices, ensuring that any emoji inputted from a phone will display correctly on desktop. Twitter has something similar in place using their own proprietary emoji set.

We did forget to include Linux's variant in the homepage graphic, however it is included on our full comparison table (Symbola): http://www.emoji.codes/family

You can store just the unicode characters to the db if you wish, the conversion script can convert both unicode, shortnames, as well as ascii text :-) to the images/svgs.

Storing the :shortnames: was just our suggestion because we've found that many web stacks aren't setup to handle multi-byte/UTF-8 characters by from the get-go. Doing it this way is an easier over-all approach, but by all means feel free to take our tools and customize to your own needs.

@font-face would definitely be the ideal solution, and hopefully something we can implement once the browser support is there, but at the moment we're trying to go for the most universal approach.

In our git repo we provide a list of all the emoji, their category, keywords, shortnames etc in json format.

https://github.com/Ranks/emojione/blob/master/emoji.json

Hey, if you check our family table here: http://emoji.codes/family

The "native" column shows what your device will show by default just using the unicode characters, and in chrome on windows (fairly high demographic) they almost entirely display as black boxes. Every device is going to interpret them differently.

We're aiming to provide a full color set that closely follows the unicode standards, translates well to Twitter, Apple, Microsoft etc's proprietary sets and is freely available and modifiable to anyone who wants to implement them into their web or mobile app.

Really? C'mon man have some self control for god sakes. It's a video game on a phone.

I'm not particularly fond of micro-transactions, I cannot stand the way intellectual property is handled in this country (US), and I dislike rip-off artists such as Zynga/King.

However, all King is doing here is playing ball with current IP legislation, protecting whatever trademarks they can. There's hundreds of games that are exactly the same in every category of gaming, just because King has the capability to create a high-quality successful series of mobile games (which are based off of extremely common gaming concepts) does not mean they are horrible people.

People get up in arms when these large corporations sue eachother over intellectual property. Why does the HN community have this double standard whenever a "little guy" can be made out to have been harmed? Just because you're the first person to think of a popular idea doesn't mean you own it forever.

Patent/Trademark/Copyright legislation is very clearly all bunk in the age of the internet. Get mad at the stupid laws, not at the people taking advantage of them.