This one isn't actually /too/ complicated. It certainly uses some advanced techniques -- transitions, clip-paths, nth-child -- and I'm not sure (haven't checked) if or how it works in browsers other than Chrome, but the fact that you _know_ you'll have 30 shards greatly simplifies everything.
If you can have a designer draw up the basic design, then you can one-by-one take the shards & put them into place with CSS. From there you can set up some animations on specific shards to make it seem like everything's moving together. From there, you basically have one animal. It'd be time-consuming, but would work.
The css selector for a particular animal's shards start with a `.<animal>` class selector, so that you change the animal class in a parent and all the shards move into place.
It looks like they're still using some javascript to set "states", which seem to trigger animations. I'm honestly not sure why they decided to do that rather than just using keyframes with animations, though I imagine that it may have been that animations were firing before the transition between animals finished, which would have caused a little bit of weirdness.
I love woodworking as well, and have completed a few little projects since buying a house and finally having a garage/workshop.
But, if that's not something you have the space/money for yet, I think that cooking is a nice substitute hobby. There's a lot to learn with tools and technique, and you get the immediate satisfaction of seeing (and tasting!) your finished product.
Just be careful though -- I've injured myself many more times in the kitchen than in the garage.
Right. I actually wonder how self-driving Semis will handle such a situation.
Given that it's all math at that point, I wouldn't doubt if regulations surrounding minimum yellow-light timing are updated to more accurately represent the stop time of heavy loads. Otherwise it should be easy to prove in court that stopping in time would be impossible given the speed limit & weight restrictions (or lack thereof) in place at a given intersection.
You shouldn't be driving a vehicle through a non-freeway (i.e. a road with stop lights) at a speed where you can't stop in time. In many jurisdictions that is considered reckless driving. If your vehicle is too heavy then you (or the software) needs to slow it down.
I sincerely hope there will be such a technocratic solution to this problem. Recall that there was a trend in the late '00s where cities shortened the yellow light time so they could reap greater fines from red light cameras. Having a definitive length of time that yellow lights 'should' be will be helpful.
This is the standard thing that xenophobes do when talking about how bad immigration is. They tell someone to take a loot at X. Where X is a place the listener probably hasn't been to and doesn't really know anything about.
It's like if I was talking to a bunch of factory workers in Kentucky about how bad marijuana is and said "just take a look at Holland!" They'd have no fucking idea what it's like in Holland but someone claiming to be an authority just told them the situation was concerning.
Maybe he is a bigot. But you have a choice about whether you want to make the discussion personal and permanent (you are a bigot) or transient and focused on ideas (I think one of your assumptions is wrong).
The sky is blue but it's not necessarily productive to say so in every conversation.
Looking closer, I'm pretty sure that the non-TouchBar model is just the previous model.
It has the 4th gen processors where the TouchBar models have 6th gen processors. The non-TouchBar model also still has the "smaller" touchpad and the same ports & layout as the previous models. The body itself even has the same finish as the older model. So yeah, I'm pretty sure it's just the previous model.
Not sure where you're looking, the non-touchbar model is physically identical to the touchbar except that it has a function key row and two less ports. Definitely the new model, it's the same thickness, same screen, same trackpad. See the tech specs if you want to confirm: http://www.apple.com/macbook-pro/specs/
The numbers lack context in that they don't specify a rate, merely a value. It makes it sound like 70K women are attacked each year by undocumented immigrants, when the reality is that the number is closer to 1.27K per year since 1955. Let's do some back of the napkin math:
There are about 11 million undocumented immigrants in the US, meaning that the rate of sexual assault victims per undocumented immigrant would be ~0.012%. Meanwhile, in 2006, 300,000 college women were raped.[1] With 300 million people (in 2006), that puts the rate for the general population at 0.1% of victims per person. That's nearly 10x the rate of the undocumented immigrant population, and that's only including college-aged rape victims, rather than sexual assault victims of all ages as the 70K number claims to be.
Meanwhile, we have Trump who has no fewer than 4 woman claiming he sexually assaulted him. Divide that over the 70 years of Trump's life, and at 0.057 women-per-year you have a 1-man rate of 5.7% -- 57x the rate of the general population. Seems like Paul Ryan is targeting the right person, and that Breitbart is using bad logic.
The numbers don't claim to specify a rate - that was your inference.
Also, your numbers seem to demonstrate the exact dishonesty that you accuse Breitbart of doing.
The number cited for illegal aliens is the number of arrests.
The number you cite for the general population is a victimization survey which includes a lot of alleged rapes that were never reported to the police. (In fact, I can't even figure out if all of them meet the legal definition for rape.)
According to your report [1], 12% of rapes were reported to the police. If every single rape report results in an arrest (hint: they don't), that eliminates your 10x factor right there.
When reading Breitbart, you seem to draw incorrect inferences from cited statistics. And when digging up your own data, you also seem to draw incorrect inferences. Consider the possibility that the problem here isn't Breitbart.
(Note: I hate Trump. I favor open borders and think we should let Mexicans in even if they are more rapey than Americans. In fact I have nothing but positive feelings towards Mexicans - their food is tasty and their women are beautiful. I'm just pointing out bad reasoning.)
That's the problem. The people reading the site think there are 70k rapes a year by reading the headline, and that is the incorrect, and a problem. The site exists to put up data as such to incite hatred against immigrants.
We are now in a post-fact era. Watching the current idiocy of the Trump speech happening right now shows it in full force. Any factual data people don't like now is a "conspiracy".
You are correct about the arrested vs reported thing. I don't know how I missed that. Still, that brings them in line with the general population.
You're also right about Mexican food and women. (Full disclosure, I'm married to a Mexican woman.)
Perhaps, but while programming may be only 20% of CS, learning it probably takes up 80% of a student's time. Reducing that additional cognitive load during the first couple semesters could allow them to focus on other CS fundamentals and improve overall comprehension over the course of their degree.
And I honestly can't recall a single CS course where I didn't write an executable program after my first (CS 1301 at GT circa 2000, done using a pseudo-code language based on Pascal). Even my theory classes, I used programming to express/analyze the material discussed in class.
If you can have a designer draw up the basic design, then you can one-by-one take the shards & put them into place with CSS. From there you can set up some animations on specific shards to make it seem like everything's moving together. From there, you basically have one animal. It'd be time-consuming, but would work.
The css selector for a particular animal's shards start with a `.<animal>` class selector, so that you change the animal class in a parent and all the shards move into place.
It looks like they're still using some javascript to set "states", which seem to trigger animations. I'm honestly not sure why they decided to do that rather than just using keyframes with animations, though I imagine that it may have been that animations were firing before the transition between animals finished, which would have caused a little bit of weirdness.