text:
Nobles Victoria is now an officially accredited installer of DBI Sala evolution horizontal lifeline systems.
The evolution system from A Noble & Son is a permanent system that is ideally suited to applications such as roof maintenance, overhead cranes, operations in aircraft hangers, bridge maintenance, loading docks and any other application where tasks have to be performed at height.
Nobles is pleased to now be an accredited evolution installer, Nobles has been a long time distributor of the Capital Safety range of DBI Sala, Protecta and First fall arrest products and Nobles see the permanent horizontal lifelines as further extension of its service offering in this crucial safety area.
It is another service Nobles can offer customers and further enhances Nobles reputation as a one stop shop for lifting, rigging and height safety solutions.
The evolution system is designed with innovation in mind as it is ideal for every structure, favours movement along the line, effectively protects workers from falls and is discreet enough to blend into the building without compromising its aesthetics.


text:
What our clients are saying:
This workshop enhanced our colleagues' knowledge of one another and the activities encouraged us to get out of our cubes/shells and interact with one another. We enjoyed the opening energy builders!
Our facilitator was so energetic and really connected with my group well. They had such positive things to say after the event. The group had been through a longer, slower morning and this activity was absolutely perfect to re-energize them!
Thank you for being so flexible and working with us. This was a great workshop and really promoted teamwork. It was an excellent exercise and I will definitely recommend this to other team members in the future! Our facilitator was great!
Holiday team building contributions make a difference in the lives of others – and yours!
Your company may be planning a party to celebrate the end of a hardworking year – or kick start the beginning of a new one. People like to work with people they know so why not take this opportunity to enhance team cohesion and help your team connect in a relaxed atmosphere.
Research indicates that happiness increases with experiences, rather than things.
It's easy to see this correlation – think about that thing that you HAD to have – a car, a toy, whatever. Now think about some great experience – a trip to the Caribbean, a weekend in Las Vegas, tickets to see the Tonight Show starring Jimmy Fallon.
Now take a moment to think about which of those things sticks in your mind, now that they're long gone. Chances are, you value the experience and that memory far more than the small amount of time that you spent enjoying whatever the item was. You're not alone!
This is a prime opportunity to create a lasting memory for your team, and provide them with an experience, not just another ho-hum holiday party that will be quickly forgotten once everybody is back to work after the holidays. Since the end of the year and the dizzying array of demands bring so much stress, it makes sense to get a triple bang for your buck this holiday season:

subset: commoncrawl


text:
Saturday, October 19, 2013
She & Him, 42/52
14 comments:
how sweet, I hope she had a lovely birthday and that big brother is enjoying her gifts :DReplyDeleteReplies
She had a wonderful birthday with lots of fun gifts. Fortunately her brother is only interested in the one gift! ;)Delete
Oh many birthday hugs to her!! And I love his grin-- what wonderful kiddos!!ReplyDeleteReplies
Thank you so much Taby! :)Delete
Happy Birthday to a darling girl.ReplyDeleteReplies
Thanks Mom! :)Delete
Oh so perfect! Happy Birthday to Her!ReplyDelete
And it looks like He is playing/making those bracelets that are all the rage here! xoReplies
Thank you!Delete
Yes, he's playing with the Rainbow Loom. I think almost every kid around here has one Rebecca. :)
So sweet! Lovely blue eyes on the birthday girl! You have beautiful children. Happy birthday to your lovely daughter. xoReplyDeleteReplies
Thank you very much Karen. Yes, she has stunning eyes that come from her grampy. :)Delete
- AnonymousOctober 22, 2013 at 12:19 AM
Love this! Happy Birthday to your cute little "she."ReplyDeleteReplies
Thank you very much Kelli!Delete
Looks like she had a lovely birthday. I just bought that exact gift for my niece who turned 8 last week.ReplyDelete
Kate x
Kate at HomeReplies
I wish I had stock in that company. Every child around here seems to have one!Delete


text:
Sad (but not shocking) news today that Forrest J Ackerman has died. Dennis McLellan, one of the fine obituary writers in the country, writes about this true original:
Forrest J Ackerman, who influenced a generation of young horror movie fans with Famous Monsters of Filmland magazine and spent a lifetime amassing what has been called the world's largest personal collection of science fiction and fantasy memorabilia, has died. He was 92.
Ackerman, a writer, editor and literary agent who has been credited with coining the term "sci-fi" in the 1950s, died Thursday of heart failure at his home in Los Angeles, Kevin Burns, head of Prometheus Entertainment and a trustee of Ackerman's estate, told the Associated Press.As editor of Famous Monsters of Filmland, Ackerman wrote most of the articles in the photo-laden magazine launched in 1958 as a forum for past and present horror films.
"It was the first movie monster magazine," Tony Timpone, editor of Fangoria, a horror movie magazine founded in 1979, told The Times in 2002.
Timpone, who began reading Famous Monsters as a young boy in the early '70s, remembers it as "a black-and-white magazine with cheap paper but great painted [color] covers. It really turned people on to the magic of horror movies."
Primarily targeted to late pre-adolescents and young teenagers, Famous Monsters of Filmland featured synopses of horror films, interviews with actors such as Boris Karloff, Bela Lugosi and Vincent Price, and articles on makeup and special effects.
Famous Monsters reflected Ackerman's penchant for puns, with features such as "The Printed Weird" and "Fang Mail." Ackerman referred to himself as Dr. Acula.
"He put a lot of his personality into the magazine," said Timpone, who later became friends with Ackerman. "It was a pretty juvenile approach to genre journalism, but as kids, that's all we had."
One of our sister blogs, The Daily Mirror, has dug up a 2002 profile by Hilary E. MacGregor, one of my former colleagues here in the featrues sections of the Los Angeles Times. An excerpt:
Even here amid his diminished collection, it becomes apparent that the greatest part of Ackerman's collection is the man himself. He is full of tales of the birth of horror in Hollywood. He saw movies that have been lost forever. He attended Bela Lugosi's funeral. He attended not just the first World Science Fiction Convention in New York City in 1939, but nearly every convention since. As a teenager, he corresponded with the president of Universal Studios, Carl Laemmle, 62 times, until Laemmle wrote on his president's stationery, "Give this kid anything he wants." Fifteen-year-old Forrie Ackerman chose the sound discs to some of the greats of early cinema like "Murders in the Rue Morgue" and "Frankenstein."
(More from the 2002 Los Angeles Times feature on the late Forrest J Ackerman…)
Born and raised in Hollywood, Forrie is the ultimate fan. He is still an eager 12-year-old boy trapped in a gangly, 86-year-old man's body. He delights in bad puns and very silly jokes. He points to a casket covered in embroidered pillows in the front of his living room. "That's my coffin table," he says with a wink. "Room for one more … "
He is well-spoken and a master storyteller. He has an encyclopedic mind that holds data like a computer. He can rattle off obscure movie titles, forgotten movie stars, esoteric movie lore. His stories are what make his objects, much of which look like junk in an adolescent's bedroom, come alive.
There is Bela Lugosi's cape in the corner, from the 1932 stage performance of "Dracula" in San Francisco. And there, over the dining room doorway, are the seven great faces of horror cinema in life-size 3-D molds: Boris Karloff, Bela Lugosi, Lon Chaney Jr., Tor Johnson, Glenn Strange, Vincent Price and Peter Lorre.
Where others display china, Forrie displays models of dinosaurs, monster heads and a skull holding a serving bowl. Where others might hang paintings, Ackerman hangs a wall-size comic strip of Vampirella, which he created in 1958.
He walks back toward the bedroom with a mischievous look.
"You are over 21," he flirts, arching an eyebrow. "You can come into my 'badroom.'"
That whole article is well worth reading, and again, you can find it right here. I'll be posting more on Ackerman as the news ripples out.
R.I.P. Forrie…
— Geoff Boucher
Top photo : Forrest J Ackerman at his home in 1969. Credit: Jack Carrick / Los Angeles Times. Lower photo: Ackerman in 2002. Credit: Robert Gauthier / Los Angeles Times.


text:
The Rheumatology infusion center is located on the third floor of the Hux Cancer Center. The staff provides a variety of treatments under physician supervision. These include Remicade, Cytoxan, Orencia, Boniva, Rituxan and hydration therapy.
For more information, please call (812) 242-3005 or visit www.arthritis.org.
UAP Rheumatology
1711 North 6 ½ Street Suite 302 Terre Haute, In 47804
(812) 242-3005
Timothy Lenardo, M.D.
View bio.
Linda Grismer, M.D.
View bio.


text:
If you've ever found yourself trying to figure out what to say to a loved one near the end of his or her life, you know how challenging and uncomfortable it can be.
I found myself in that situation during the final days of my dad's life. He was an extraordinarily successful entrepreneur, but the long hours he'd spent working and the fact that he'd neglected his health had finally caught up to him.
Sitting by his hospital bedside, I wasn't sure what to say. I wanted to connect on a deep level. Speaking from my heart, I said, "Dad, it's been a privilege to have been your son, and I want you to know that I will spend the rest of my life practicing lessons I've learned from you and also teaching those lessons to others."
1. Measure yourself against yourself, not against others
My dad lay on the bed, head on his pillow, eyes closed. He didn't say anything, but I sensed he could hear me. "But," I continued, "I know as I do that I will spend the rest of my life comparing myself to you."
A few moments passed in silence before he responded, "Don't. Don't measure yourself against me. I don't know if you're more than I am or less than I am – I really don't – but it's not important. Measure yourself against yourself. It is enough."
His words were one of the greatest gifts he ever gave me. They contained such humility, wisdom and generosity. Here was one of the most successful and respected people I'd ever met, encouraging me to believe in myself. He knew I thought so highly of him and wanted to be like him, and he was helping me to believe in myself.
2. Make service an important part of your life
While speaking with many people who knew my dad, I learned of hundreds of acts of service he performed for them. Some of these were small like buying a refrigerator for someone or paying for a car repair or covering a medical bill. Others were large like paying off a mortgage or giving or lending money to people to save them from bankruptcy. His generosity extended beyond money, though. He also gave of himself, freely sharing his time and advice and frequently performing personal acts of service to others.
I wondered, "When did he have time for all that? Was it between negotiating NBA players' salaries or building new automobile dealerships?" My dad never told me of these acts of service – I figure he was either too busy performing them or too humble to share.
It hit me that providing service to others wasn't something my dad did after he became successful. Providing service to others (always with my mom as his partner) was how he became successful. It's whythe two of them became successful.


text:
This story has been updated.
A federal trial sought by five Armenian American Glendale police officers who are suing the city for alleged discrimination and harassment has been pushed back again and now isn't expected to start until November.
Trial had originally been set to start in March in the case involving Officers Vahak Mardikian, Tigran Topadzhikyan, Robert Parseghian, John Balian and Benny Simonzad. It first was moved to July, and then earlier this month was pushed back again to November at the request of the plaintiffs.
The officers filed a joint lawsuit in 2010 against the Glendale Police Department and the city, claiming on-the-job discrimination, harassment and retaliation because they're Armenian.
In July 2012, a U.S. District Court judge ruled the officers could move forward with the lawsuit and refused to dismiss the claims, although some claims against certain police commanders were dropped.
Following that ruling, the city changed its legal counsel, a new judge was assigned to the case, and both sides met to discuss a possible settlement.
But the discussion proved to be futile.
Mardikian, Balian and Topadzhikyan filed a separate racial discrimination and retaliation lawsuit in March 2012 in Los Angeles County Superior Court. That case has been on hold due to the ongoing federal case.
A hearing on the status of case is scheduled on July 30.
Follow Veronica Rocha on Google+ and on Twitter: @VeronicaRochaLA.


text:
Israeli researchers have received $2.1 million to conduct a study on the genetic basis of schizophrenia, along with a team from the US.
The US National Institutes of Health has awarded a "Grand Opportunity" grant to a team of researchers at the Hebrew University of Jerusalem Silberman Institute of Life Sciences and the Feinstein Institute for Medical Research, New York, to conduct a study on the genetic basis of schizophrenia. President Barack Obama personally announced the awards.
It has long been known that schizophrenia – a complex brain disease marked by often-frightening hallucinations and delusions – has a genetic component.
The newly funded grant builds on prior gene-hunting efforts, but the sample study group is unprecedented in size, consisting entirely of 4,000 individuals (patients and controls) of Ashkenazi Jewish descent, recruited in Israel.
"The unique demographic history of the Jewish Ashkenazi population… should allow disease-related genetic signals to stand out more clearly in our analyses," says Prof. Darvasi from Israel. Additionally, this study will utilize the most advanced genetic technologies, which will permit examination of many more pieces of the genetic code than prior generations of research.


text:
Garth in the slanted rain says arms bend at the rainbow. 3 years growing: his own spectrum. Take off my feet, he yells. Bird need wings. Take out the stars. Give me some. In the wet grass he marks constellations: maple leaf, mushroom, twig. Footprint, he says: Rain
walk here. Where rain home? Question easy as water & already I can't answer.


text:
Adding a stained glass suncatcher to a window is a superb way to immediately increase the feel of any bedroom. Suncatchers can be found in all shapes, sizes, themes and designs. Many of the most fun suncatchers are the ones that resemble frogs, fish, bunnies, and other animals. Buying stained glass suncatchers takes a few guidelines that will help make sure you get the best quality artwork you want. No one loves to buy something online and then obtain it in the mail and recognize the workmanship isn't quite right. Follow these few recommendations and you'll end up buying only the very best suncatchers.
1 - Glance at multiple pictures: ideally owner will have pictures in a variety of lighting conditions. Stained glass suncatchers look quite several without light arriving through in comparison to when light from at the rear of. Make certain any pieces you take into account look very good in both types of light just in case you want to go the piece in the foreseeable future.
2 - Appropriate colored cup: among the hallmarks of badly made stained glass is certainly that the color of the glass used will not effectively reflect the palette of the designed theme. For instance, are the skies crafted from various hues of blue? A sophisticated artist will head to great lengths to make sure only the correct colors of cup are used.
Related post :
3 - Require close-ups of the part: if possible, require close-up photos of the stained glass artwork. Consider the top quality of the soldering particularly. Solder ought to be smooth without many dips or extra blobs. If a suncatcher has simple solder joints and lines, chances are great that the artist understands what he/she does!
4 - Uniform solder lines: be sure all of the solder lines will be uniformly thin. Random places with wider solder ensure that some bits of glass were cut also little and the artist didn't care plenty of to redo them. Solder lines ought to be the same width through the entire whole masterpiece of design.
Following these 4 recommendations is going a long way to assist you buy top quality stained glass. Finally, look at a few of the other stained glass created by the artist. If the different suncatchers are top quality, then you're in very good hands.
Stained GLASS Suncatchers For WINDOWS Decorations
4/ 5Oleh Lauren Miranda


text:
Szurek, Sarah
Assistant Research Scientist, Health Outcomes & Biomedical Informatics
Faculty, Institute for Child Health Policy
(352) 627-9143
2197 Mowry Road, 176
PO Box 100177
Gainesville, FL 32610-0177
- Ph.D., Anthropology, The University of Alabama
- M.A., Anthropology, The University of Alabama
- B.A., Anthropology, State University of New York, College at Geneseo
Professional Biography
Dr. Sarah M. Szurek is a medical anthropologist who holds a faculty position as an Assistant Research Scientist in the College of Medicine's Department of Health Outcomes & Biomedical Informatics and the Institute for Child Health Policy. Her research focuses on understanding the social and cultural factors that influence health outcomes among vulnerable populations. She has worked with Mexican immigrants in Alabama to examine how personal social networks affect diabetes risk, and with African Americans in Florida on projects related to racism, cardiovascular disease, and the local food environment.
Dr. Szurek currently oversees the Florida Health Kids Program evaluation, which examines the quality of care that children receive in the state.


text:
Blog – America
The denial and deflection that unites the cheerleaders of Trump and Corbyn
3 Mar 2017 by Dave Rich
American Jews have been rocked in recent weeks by a wave of anti-Semitic incidents, including bomb threats and cemetery desecrations. These kinds of attacks are not supposed to happen in the Jewish utopia of the United States, and suddenly the sense of insecurity felt by European Jewish communities in recent years seems to be making its way across the Atlantic.
Positioning Steve Bannon on the Fascism - Nationalism spectrum
23 Feb 2017 by Dave Rich
His admiration for 'Judeo-Christian values' might differentiate Trump's chief strategist from traditional European far right anti-Semitism, but stereotypes of Jews are still crucial to the global nationalist populism he champions.


text:
Glenn Reynolds has been writing lately about the cost of higher education, which he believes will be the next bubble to burst. I think he's right. A simple, inexorable law holds that if something can't go on forever, it won't. Collective forgetting of that law is what leads to bubbles. In today's Examiner, Glenn writes:
Assume that I'm right, and that higher education – both undergraduate and graduate, and including professional education like the law schools in which I teach – is heading for a major correction. What will that mean? What should people do?
Well, advice number one – good for pretty much all bubbles, in fact – is this: Don't go into debt. In bubbles, people borrow heavily because they expect the value of what they're borrowing against to increase. …
Right now, people are still borrowing heavily to pay the steadily increasing tuitions levied by higher education. But that borrowing is based on the expectation that students will earn enough to pay off their loans with a portion of the extra income their educations generate. Once people doubt that, the bubble will burst.
So my advice to students faced with choosing colleges (and graduate schools, and law schools) this coming year is simple: Don't go to colleges or schools that will require you to borrow a lot of money to attend. There's a good chance you'll find yourself deep in debt to no purpose. And maybe you should rethink college entirely.
Seems like sound advice. I think Glenn is right; as the father of four, I only wish the bubble had burst a little sooner!


text:
BINGHAMTON, N.Y. -- There were smiles outside the Skipjacks locker room last night -- a rare sight of late.
The Skipjacks, 1-12-0 in their previous 13 games, earned a 2-2 tie against the Binghamton Rangers when Steve Seftel scored his second goal of the season to tie the game with 5:31 remaining in regulation. Seftel returned earlier in the month from a knee injury and was playing in just his 10th game.
Although it wasn't a win, gaining a tie with the AHL Southern Division-leading Rangers might just help the fifth-place Skipjacks (23-30-7) get back on track.


text:
"A website to the detriment of good film"
Custom Search
Badmovies.org Home
B-Movie Reviews
Reader Reviews
Capsule Reviews
TV Show Reviews
Rated R
Copyright 1975 Bryanston Distributors Inc.
Reviewed by
Andrew Borntreger
on 'a long time ago'
The Characters:
Mark Preston - William Shatner! Tries to best Corbus in a test of faith but loses and becomes an eyeless wonder.
Tom Preston - Tom Skerritt! He becomes involved when Mark disappears.
Corbus - Ernest Borgnine! High Priest of Satan on Earth, no big departure from reality there...
Julie Preston - Tom's woman, she's got these buggy eyes and apparently has some ESP.
Dr. Richards - Eddie Albert! Tom's friend and Mentor.
Danny - John Travolta! Cultist who you would never recognize without the credits - well maybe that chin.
Mrs. Preston - Matriarch of the Preston clan, her soul is demon fodder real early on.
The Plot:
Can you believe this cast? It's amazing! It's astounding! It scares the hell out of me! Who would have thought disco movie icon John Travolta would start out here, "Grease" was made before it but "The Devil's Rain" hit the box office first. Add Shatner to any plot with Satanists and it's going to be good, he sold something for his fame and it appears to have been the ability to speak like a regular human being.
The movie's premise is that all the characters are reincarnated forms of their ancestors who once worshipped the devil. Julie's character back then betrayed the group by stealing "the book" and they were burned at the stake. Now, years later, Corbus has risen again and only needs "the book" to secure his power.
Two reasons to see this film:
1) The cast! William Shatner, Tom Skerritt, Ernest Borgnine, John Travolta, and Eddie Albert in a goofy film about the Devil?
2) The last ten minutes of this film involves all the Satanists melting into what appears to be lime sherbet.
Though it's moderately painful, I would recommend you see this film just for the novelty of it.
Things I Learned From This Movie:
All the credits belong at a movie's beginning, accompanied by the screaming of lost souls.
William Shatner could overdramatize anything. Making waffles? No prob: "Got... ...to... ...make sure... ...batter, mixed... ...well."
Demonic rain will turn you into melted sherbert.
Cowboy hats look pretty gay on some people.
Every God-fearing man carries a shotgun into a church.
There's a good reason giant collars went out of style.
Dream sequences should be done through a serious red filter.
A Yamalka is about the least threatening thing you can put on the head of Satan's High Priest.
Satan worshipers are made of melted sherbert.
The Devil has a really weird looking TV and it is full of souls.
Don't tackle a group of thirty Satanists in hand-to-hand combat if you have a shotgun. Dumb Tom, dumb, dumb, dumb...
Never let a demon grab you by the forehead.
Stuff To Watch For:
5 mins - Man, this is bullshit, who the heck decided to lead off with the credits? Moron...
7 mins - William Shatner just came in out of a monsoon but he's perfectly dry.
16 mins - Now it's dry, I mean desert dry, and daylight?
28 mins - Oh! A chase scene on foot!
46 mins - Tom doesn't notice this guy he's holding down has no eyes until Julie points it out?
56 mins - Needed a disguise so you just pulled that black robe out of your ass didn't you?
61 mins - Nice, now make the gunshot match the muzzle flash.
68 mins - The altar cover says, "Rege Satanas" huh? Yah man, Satan's got the ganja man...
Audio clips in wav format
Starving actors speak out
William Shatner: "Corbus! God...damn...you!"
Julie: "I've seen churches like this in New England, it doesn't belong here."
Corbus: "Martin Fife! A curse on thee and thine forevermore. I will follow thee and thy descendents for all eternity."
Tom and Dr. Richards having a conversation in gibberish.
Click for a larger image
Scenes from the movie
Watch a scene
MPEG video files
- 2.0m
Corbus and Mark were having a contest of faith, but the latter had a little known talisman of Christianity hidden away. Faith is a .45 semi auto baby!
Leave a comment
Buy the movie
Stumble This Review
Digg This Review
Buy it from Amazon.com
(United States)
Buy it from Movies Unlimited
(United States)
Internet Movie Database
Write Comment
The Devil's Rain
Reply #33.
Posted on June 28, 2004, 07:53:51 PM by night heron
Poor john travolta imagine being in a movie this bad? i guess after being a hunk he thought that he could do it sorry
The Devil's Rain
Reply #34.
Posted on November 25, 2006, 04:09:49 PM by Skun
I just saw this movie after watching a genuinly creepy and moderately scary movie: The Amityville Horror. Devil's Rain was pretty hokey and the goat demon looked like a Troll Doll gone bad.
John Rinck,
Those symbols aren't triangles or Star Trek like symbols. That's supposed to represent the head of the Judas Goat. I think it's also supposed to be like an inverted Star of David.
The Devil's Rain
Reply #35.
Posted on November 25, 2006, 04:09:49 PM by lostgoth13
THIS MOVIE RULES!!! it does need to be at it's designated time, such as anytime after 1am. A true 70's classic how could you beat the casting? it has everything you would want from a super 70's movie bad sound,bad makeup and effects and best of all bad acting! at least the casting was great! at the top of my all time list. what other movie has what we all would like to do , tie william shatner to a upside down cross and offer him to satan.(but would he want him?) any movie that has anton lavey himself and ernest borgnine as a satanic high priest/goat gets my vote. a true materpiece.
The Devil's Rain
Reply #36.
Posted on November 25, 2006, 04:09:49 PM by mike viger
Saw this way back in '76. Scared the bejesus outta this 7 year old !!! As a kid I remember being completely transfixed by this movie. I, too, found the melting wax man at the beginning fricken scary !!! Satan's minions jumping from the back seat of the car driven by a woman made me s**t my pants. And the snake transformation around the guy's neck shocked me too. Oddly enough, I don't remember the cool finale. Must of been dragged off home before the end. Damn !!
The Devil's Rain
Reply #37.
Posted on November 25, 2006, 04:10:12 PM by Michael
Saw this movie a few years back and it blew me away. The best part would have to have been watching the opening credits and seeing travolta's name there, like he was a big time player in the film, and then watching the entire movie waiting for him to appear. I guess his melting abilities far exceeded the other cast's, for i could come to no other conclusion as to why his name was added to the credits with such reverence. All in all a good flick. Stands up well against other such classics as "I Spit on Your Grave" and "Seven Doors of Death". I only wish it were aired sometime before four in the morning.
Re: The Devil's Rain
Reply #38.
Posted on April 16, 2008, 09:18:37 AM by
Quote from: Michael on November 25, 2006, 04:10:12 PM
When Satan saw that William Shatner was involved with this "movie" even he gave it a thumbs down(or claw down... whatever)!!!!
Hehe, ya know whats kinda funny? That guy's name is SHATner. Hheheh, get it?
-ner!! HAHA!
Re: The Devil's Rain
Reply #39.
Posted on February 14, 2009, 11:37:00 PM by Kelly
Saw this at the movies when it came out,in the 70's Hollywood had a fascination with the Devil all because of Rosemary's baby's success,and I forgive the stupid scenes because if they were smart enough to jump in a car and keep going,we wouldn't have had a movie to begin with..lol
I think this movie could be re-made and be a hit at the Box Office,after all it's not a bad movie,it's just not "It's A Wonderful Life" that you can watch every freaking year.
Ernest Borgnine was great,but he was better as Dirty Lyle in Convoy a a year or two later.
Captain Kirk being killed off and not being one of the main Devils A** Kickers at the end was a shock to me in 75,and just who the heck was this guy Tom Skerritt? "Top Gun" was almost a decade later and before that he was just a crazed War Vet in Cheech and Chong.
All in all,you can probably catch the movie on TV somewhere at least once a year,and you should see it once,but only twice if you take your medication.
Re: The Devil's Rain
Reply #40.
Posted on March 28, 2009, 02:55:59 AM by annoymous
Always hope that the guys that made Mystery Science Theater 3000 would just tear this movie apart with a million Ernest Borgnine jokes and William Shatner mimics. Sadly not.
Share on Facebook
Subscribe by RSS
Subscribe by Email
Recommended Articles
How To Find A Bad Movie
The Champions of Justice
Plan 9 from Outer Space
Manos, The Hands of Fate
Podcast: Todd the Convenience Store Clerk
Faster, Pussycat! Kill! Kill!
The Human Tornado
The Educational Archives: Driver's Ed
Godzilla vs. Monster Zero
Do you have a zombie plan?
The Giant Claw
Earth is visited by a GIANT ANTIMATTER SPACE BUZZARD! Gawk at the amazingly bad bird puppet, or chuckle over the silly dialog. This is one of the greatest b-movies ever made.
Lesson Learned:
Osmosis: os·mo·sis (oz-mo'sis, os-) n., 1. When a bird eats something.
Subscribe to Badmovies.org and get updates by email:
B-Movie Reviews
Reader Reviews
TV Shows
Badmovies.org is owned and operated by
Andrew Borntreger
. All original content is © 1998 - 2014 by its respective author(s). Image, video, and audio files are used in accordance with
Fair Use
, and are property of the film copyright holders. You may freely link to any page (.html or .php) on this website, but reproduction in any other form must be authorized by the copyright holder.


text: I know very little about my father's side of the family. I had been to his parents house in Arkansas when I was a small child but I don't remember much about that visit. My uncle, Pete, and his wife, Hazel, visited in San Francisco once and I took them out to dinner. His son, my cousin, Edward, also visited once to San Francisco. Then years later, I would see my grandmother when she was in her nineties at Darlene's house, along with my aunts, Jessie and Faye. Pete came on a family cruise a few years after his wife, Hazel, died and he brought his girlfriend, Lou.


text:
Six days.
I haven't run in six days.
It's a different kind of streak and not one I'm at all happy with. It's now the longest consecutive period of time that I haven't run in the past two and a half years*! Tendinitis in early January and the Boston Marathon in 2013. Road2Hope Hamilton in 2012. All meant taking five days off running. Five days. Never six!
And given the persistent pain and noticeable limp in my right leg right now, it's a streak that could continue for some time.
What's going on?
Unfortunately, I'm not really sure. What started as a hip flexor strain, minor and manageable, has become an all-encompassing hip/groin (and the whole right leg really) issue. It's quite literally a pain in my ass! And sure, I probably should not have kept running these past few weeks. Rather, I should have sought treatment much sooner and taken some time off. We runners are just so damn stubborn. Stupid even!
So what?
Running is part of who I am. It's what I love to do. A day just isn't a day without a few easy miles on the MGT or a hard workout with the Lungs. It's about so much more than speed or fitness, competition or performance. It's about health and happiness, meaning and well-being, identity and belonging. And so, it's no wonder that I'm now feeling incredibly nervous, anxious, and excitable (irritable is probably the better word) without running. We really don't appreciate how much we need it until it's gone. Some call it an addiction. Right now, I tend to agree.
What now?
Be assured, I am well aware that a running injury is relatively minor and not really a 'big deal'. Alas, the world ("my" world even) will not end!
STWM is now less than 11 weeks away. My goal is to PB. To run fast. To run hard. To represent the Lungs. To raise some money for Alzheimer's. To enjoy the experience. And also, to win beer. To do so, I'd like to be running some 100 miles a week in preparation, including 32K long runs and long interval speed sessions. Instead, I'm stuck spinning on a stationary bike for 40 minutes at a time (because that's all I can't handle). I'm also stretching and squatting. Massaging and manipulating. Rolling, advil-ing and icing. Seemingly, to no avail. Pre-hab is looking pretty good right now. Rehab, not so much.
I could call it quits. I could bail on my goals and the race altogether. I could take the easy way out and enjoy the time off. Tell myself I need (deserve?) a break. But why? How? There's still so much time. 73 days. Time to rest, reassess, recover and regain. I'm not giving up. I'm just taking a different road. The road less traveled (and less run) it would seem.
Right now, I'll take it day by day. Later, week by week. If I don't run at all for a few weeks, that shouldn't be a problem. If I can make it to September feeling good again, I'm convinced I'll still have a shot. My next races are set to be the B&O Yorkville 5K in early September and the Army Run (Half) in Ottawa later that month. If I can maintain my fitness (spinning til I'm spun out) and recover from the injury, I'm sure I can still run a respectable marathon.
Yes, I may need to modify my goals. I will definitely need to modify my plan. But I won't quit. Not now. Not yet. There's still time. There's always hope. And there's a whole lot I can still accomplish.
We runners are so constantly looking forward. Setting new goals. Training for the next race. Rarely do we look back and reflect on how far we've come. What we've done. Instead of stressing about what we haven't yet done or possibly can't do, we should take the time to appreciate what we've been able to accomplish and the small successes along the way. Every step and every run is an important part of the journey. It all counts.
*Consistency is said to be key for distance running success. Dating back to Jan 1st, 2012, a span of 2.5 years (30 months), I have run just over 16,100K (10,000+M). In that time, I have taken (only) 75 days off running. That, I call consistency.


text:
Cowboys approaching ride horses into a stable. Cattle graze. Oil wells and military airfield from overhead. Distant view of Dallas Texas city skyline. Night view of streets and signs in Amarillo Texas. Daytime view of a tall skyscraper building and wide street in Houston Texas with cars and traffic View of the Hotel Nimitz in Fredericksburg Texas. Downtown Fort Worth Texas city street with shops, offices, and cars. Downtown area in Pampa Texas. Street corner view in Kerrville Texas. Two different views of The Alamo and surroundings in San Antonio, Texas. A water tower and oil rigs in Kilgore Texas. Downtown area of El Paso, Texas from elevated view. Street view in downtown Beaumont, Texas. Downtown view in Wichita Falls, Texas. Downtown San Angelo Texas views. Distant view of the city of Austin Texas from an elevated position, and then in downtown Austin featuring the State House Capitol building. Cattle, sheep, and sorghum farming views. Rice fields and Turkey ranches. Many oil rigs and oil wells. A busy shipyard in Texas making ships for World War II war effort. A sprawling aircraft factory. Oil rigs pumping oil. Farmer on tractor plows wheat field. View of rice harvesting (Massey Harris Self Propelled Harvest Brigade). Men stack magnesium bars. Magnesium factory next to ocean in Texas. Hand cotton picking and view of a mechanical cotton picker. Tractor pulling sorghum harvester. Sulfur mining and Helium plant in Amarillo. Black clouds in sky from burning natural gas in making synthetic rubber for war effort. Cliff of sulfur dynamited and loaded by train crane. Cowboys herd cattle and view of Fort Worth Stockyards and Exchange. Angora goat farm and turkey farming. War time workers manufacturing. Alabama and Coushatta Native American Indian village with flag of service stars for men in the war. Indian children with elder and Indian logging camp. Campus of University of Texas and State Capitol in Austin. Well dressed women exit Dallas department store.
A USAAF B-17F is seen where it crash-landed in the desert near Biggs Army Air Field, El Paso, Texas, on February 18, 1943, in World War 2. The film was shot some time later when salvage operations are underway including removal of engines. As the camera pans around the plane, a bent propeller is seen in the sand. The tail number 25326 is seen, identifying it as Boeing B-17F Flying Fortress, 42-5326, of the 351st Bombardment Group, 511th Bomb Squadron, with home base at Biggs Field. The camera focuses on the plane's empennage.
Report from Texas: Texas' contribution to World War II on both battlefield and home front. Horsemen gallop across the terrain. Man on horse with cattle. Texas increases its production of synthetic rubber, magnesium, sulphur and agricultural products. Factories and industries. Construction work underway. An airfield. Soldiers march. Views of Dallas, Houston, Fredericksburg, Hotel Nimitz, Ft. Worth, Kerrville, Pampa, San Antonio, Kilgore, El Paso, Beaumont, Wichita Falls, San Angelo and Austin.
United States General James Franklin Bell and a motor cycle squadron go to the International Bridge to meet U.S. prisoners from the 10th Cavalry "Buffalo Soldiers" held by Mexico. The prisoners stand in line at Carrizal. They had been released by Mexican Constituionalist Army leader Venustiano Carranza Garza 10 days after the battle between U.S. forces and Mexican federal soldiers at Carrizal. Officer gives instruction to prisoners.
Scenes from the life of U.S. General John J. Pershing. View of a low adobe style building backyard or courtyard area, possibly Fort Bliss near El Paso Texas. U.S. Army 8th Brigade troops under Pershing's leadership, moving out on horseback and on foot during the Mexican Punitive Expedition in search of Pancho Villa. Tanks rolling by during World War I and scenes of a military graveyard. Troops in formation marching down New York City streets on the way to war. The 1918 armistice celebrations with jubilant people celebrating. General John J Pershing presenting an award to a soldier and in conversation with the soldier. General Pershing reviews the AEF cavalry troops. General Pershing passes in an open car surrounded by a large crowd. General Pershing mounted on horse back moves by in a parade. People gathered along the roadside watch. General Pershing dressed in a suit, poses for the camera inside.
Released United States prisoners in Cebu, Philippines Islands. Prisoners stand in line and receive Red Cross packages from Filipino Red Cross workers. Prisoners stand and pose, tent in the background. Man with beard walks. He shakes hands with soldiers. Hugh A Keyes, El Paso, Texas receives haircut. (World War II period).


text:
Attachment Parenting is not Indulgent Parenting. Attachment parents do not "spoil" their
children. Spoiling is done when a child is given everything that they want regardless of what they need and
regardless of what is practical. Indulgent parents give toys for tantrums, ice cream for breakfast, allow
their infants to forward face before they're physically safe doing so. Attachment parents don't give their
children everything that they want, they give their children everything that they need. Attachment parents
believe that love and comfort are free and necessary. Not sweets or toys.
The "attachment" comesfrom their being allowed toattach to us, not from usattaching to them.
Attachment Parenting is not Clingy Parenting. I do not cling to my children. In fact, I'm pretty
free-range. As soon as they can move they usually move away from me and let me set up a chase as they crawl,
run, skip and hop on their merry way to explore the world. Sure, I carry them and hug them and chase them and
kiss them and rock them and sleep with them. But this is not me following them everywhere and pulling them
back to me. This is me being a home base. The "attachment" comes from their being allowed to attach
to us, not from us attaching to them like parental leeches.
Attachment Parenting is not Selfish Parenting. It is also not selfless parenting. We are not doing it for
us, and we are not doing it to torment ourselves.
The child and the parentare allies, not adversaries.
Most of the negative things that I hear about "attachment parents" are completely off-base and
describe something that is entirely unlike AP. AP is child-centric and focuses on the needs of the child.
Children need structure, rules, and boundaries. Attachment Parents simply believe that the child and the
parent are allies, not adversaries. And that children are taught, not trained.
Sarah Sprague is a computer programmer turned mom to three. One profession always goes by the book and the other
seldom ever does. After finding that many of the "things we are told" about parenthood and children
simply make for stressed out parents and miserable children, she has embraced the ideals of attachment parenting
with the joy that comes from listening to one's heart and instincts. Sarah's other writings on motherhood can be
found at nurshable.com.


text:
ASUS Rampage IV Extreme Review
Each time I look at a ROG offering from ASUS, there are features that just set the bar that one step higher for the high end user and even sometimes head and shoulders above the crowd. With this iteration, built for Intel's latest SB-e socket 2011 processors and X79 chipset, the bar is raised several notches. At stock speeds and similar overclocks, it is going to give you the same performance you will see with boards offering less richly appointed feature sets, with all things being equal. But that's where the similarities end. Even though my 3960X is limited to just short of 4.8GHz (yeah, I know, it's lame), it was a very easy road to get to the end of the rainbow, even though I did not get the pot o' gold I was hoping for. What I mean is, that even with this beautiful and fully capable piece of hardware, I still could not coax more than a few more MHz from my CPU. That does not mean I did not try! The CPU was the limiting factor here. When it came to memory overclocking, the Rampage IV Extreme is equipped to get the most that your CPU has to offer, with speeds in excess of 2400MHz. Just over 2400MHz is the limit for the test chip. Is the board capable? Yes it is, but that has to be tempered by the luck of the draw on the CPU. Manual overclocking was easily reminiscent of the socket 1155 motherboards — set the clock and multiplier, up the voltage, test, wash, rinse, and repeat. Even using the CPU Level Up tool in the AI Suite II utility proved fruitful with a bump up to 4.25GHz that was fully stable.
So what gives the board its capability to attract a rabid user base? Reputation? Yes! Looks? Hell yeah! Performance? Of course! The one thing that really sets it apart is the unique feature set that is designed for the gamer and extreme user. For the gamer, there are the four PCIe 3.0 ready 16x slots that support both NVIDIA's Quad SLI along with AMD's Quad CrossFireX configurations at 16x/8x/8x/8x, to get the most out of the available graphics horsepower that can potentially be installed. Adding a fourth card limits availability of the connectivity at the bottom of the PCB, but there are sacrifices to be made for four video cards. ROG Connect and ROG iDirect are tools that allow the gamer to have a connected device, be it a small laptop or even an iPhone/iPad, connected via Bluetooth to make changes to clock speeds and voltages. They are both tools I have played with that really are easy to use and functional. Not much is cooler than walking into the house and turning on your machine with your smart phone. The only downside is that an Android-specific update for a tool was not included, although RC Bluetooth is an option. Adding USB 3.0 for faster data transfers leaves more time for gaming.
When it comes to the extreme/hardcore benchmarking user, ASUS has thrown in everything, including the kitchen sink. You get its Digi+ II fully digital power delivery system with a 8+3+2+2 phase design, enhanced motherboard cooling, Voltminder LEDs, and ProbeIt voltage check points. But wait, there's more — VGA Hotwire to adjust voltages on volt modded video cards, PCIe 16x switches to isolate installed video cards, LN2 mode jumper and Slow mode switches, Go Button and Q-Reset for helping along an on-the-edge clock speed, quad-channel memory with preset memory profiles in the UEFI BIOS for both Elpida and PSC modules, and onboard power and reset switches for use when the board is out of a chassis, as is the case (pardon the pun) when extreme overclocking. The OC Key is one of the most functional tools included with the Rampage IV Extreme — the tool has no overhead and allows the user to see many of the options available in the BIOS in an on screen display. This allows the user to tweak and apply changes while running benchmarks to hopefully deliver higher scores by tweaking the settings for each part of the benchmark. The BIOS includes Tweakers' Paradise sections to get that last tweak needed for benchmark overclock stability. For the rest of the user base who has to have a "Halo" board, the features and performance are there with plenty of USB 3.0 connectivity, Intel LAN, 7.1 HD sound, and the UEFI BIOS that offers 2.2+TB support and stunning good looks, in addition to the hefty feature set listed above.
Now to get all this goodness, it will cost you a few pennies. The Rampage IV Extreme is going to set you back just about $450, easily putting it at the top of the cost food chain, slightly ahead of EVGA's Classified, which is less feature rich. Besides the price drawback, there is not one reason to not look at this motherboard for your build. It has got all the things needed to make it a must have board, from its good looks that go so well with the black cases out on the market, to the excellent BIOS that just works and features excellent failed OC recovery, to the full suite of overclocking tools and utilities. It really does have it all.
- Rich feature set
- Performance
- Overclocking tools
- X-Socket
- Looks
- Price


text: On 12 Jun 2003 12:52:47 +0200 Petter Reinholdtsen <email@example.com> wrote: > > [Gaudenz Steinlin] > > 1. mkfs.ext2 and mkfs.ext3 are files of size 0 instead of links > > to mke2fs. Deleting these files and creating links made partconf > > work > > Bug #196508. Probably a bug in busybox tar. I just checked in changes to busybox tar to convert hard links to symlinks. Not the same thing, but maybe good enough. I wasnt sure about waldi's patch as it adds non standard modes, but maybe in the long term something like that will be needed. Glenn I


text:
FOUR EVERY SEASON: "It doesn't get any classier than this," read the advertisement for The Four Seasons restaurant that appeared in the New York Post last week. And right now, it doesn't get any cheaper, either. The full-page ad was promoting a $59 prix fixe, celebrating the eatery's opening in 1959, which will be offered during lunch and dinner in the Pool Room for all of 2009. Amusingly, Post food critic Steve Cuozzo slammed the deal two weeks earlier, writing about the roasted guinea fowl: "So weak a dish is a sure sign that the kitchen's heart isn't in its bargain menu. The parched bird — a moisture-shy creature requiring care so it doesn't emerge bone-dry — reflected the pattern at the $59 meals I had, when three entrées in four were shocking letdowns."
Four Seasons co-owner Julian Niccolini insisted the ad's placement was not a reaction to Cuozzo's review. "Absolutely not." And he added, "I was very disappointed because he ate all his food, and he didn't say anything while he was here" — as if it's standard procedure for a critic to notify a restaurateur in advance of writing a review. "But they're there to sell papers; they're not there to help us out." Niccolini also said the special prix fixe isn't a sign the restaurant's high-powered clientele are cutting their lunch bills in these tough economic times. Only his decision to run this particular advertisement in the Post, rather than The New York Times, was. "It's not that expensive," he said.
This story first appeared in the February 3, 2009 issue of WWD. Subscribe Today.


text:
MANHATTAN — Federal prosecutors will be allowed to use conversations recorded from wiretaps in their case against the Newburgh Four.
Defense attorneys for the men — James Cromitie, Onta Williams, Laguerre Payen and David Williams — had tried to get US District Court Judge Colleen McMahon to suppress the information, arguing FBI Special Agent Robert Fuller used false information in his application to authorize the wiretaps. The recordings are said to contain conversations about a plot to shoot down military planes at Stewart Air National Guard Base in New Windsor and blow up synagogues in the Bronx. The men were arrested on May 20 in the Bronx with what they thought were powerful explosives. The bombs were actually fakes supplied by the FBI.
Defense attorneys tried to block the wiretaps after they received a copy of a memo that described a meeting between Fuller and Stewart security personnel in which Fuller warned security that Cromitie would probably be scoping out the base but was unlikely to do anything without the informant's help.
The meeting happened before the application for the wiretaps. Defense attorneys said that proved Fuller misled a judge in the wiretap application by making it look like Cromitie was actively dangerous. Prosecutors have said defense attorneys have misinterpreted the memo.
McMahon filed her order on Wednesday denying the defense attorneys' request.
The trial of the four men is set to restart in mid-August.
Federal judge rejects plea of Newburgh 4
MANHATTAN — Federal prosecutors will be allowed to use conversations recorded from wiretaps in their case against the Newburgh Four.


text:
Last night "Saturday Night Live" did a pretty good job sending up the most recent presidential debate, especially the Long Islanders in the town hall whose questions were chosen, according to Fake Candy Crowley, based on "the severity of their accents."
The most biting satire came when a women asked what President Obama and Mitt Romney would do to get dangerous assault rifles off the streets.
"Nothing," said Fake Romney.
"I also would do nothing," chiped Fake Onama.
Reality was only slightly less comical, with Obama saying why even worry about assault weapons when so many people in his hometown of Chicago are using your garden-variety handgun, while Romney said basically that guns don't kill people, single-parent households kill people.
It all got even less funny today:
Three people were killed and four wounded when a gunman opened fire at a suburban Milwaukee spa Sunday, Brookfield Police Chief Dan Tushaus said.
A manhunt was underway for the suspect, Radcliffe Franklin Haughton, 45. An improved explosive device was found at the Azana Salon and Spa, Tushaus said.
Police, sheriff's deputies and a bomb detection team were on the scene, Brookfield Police Lt. John Beth told the Associated Press.
To be clear, we don't know what weapon was used in today's carnage. We do know that Wisconsin has some of the weakest gun laws in the United States, and that it was just 10 weeks ago, and a mere 20 miles away, that a man with a semi-automatic pistol killed six worshippers at a Sikh temple and wounded a police officer.
We also know that whatever comes out in the end about today's mass shooting in Wisconsinj, our leaders will do nothing. And that is no joke.


text:
Tag Archives: Freakers Ball
Sub Swara Podcast 18
We're back with another monthly podcast! This one comes from Dhruva on the heels of Halloween. We'll be playing in LA at Expansion and SF at Freakers Ball this weekend so check the Shows page for details You can subscribe … Continue reading
Posted in Blog, Home Feature Tagged Anneka, Buraka Som Sistema, DJ G, Expansion LA, Freakers Ball, Girl Unit, Halloween, Knight Riderz, lana del rey, Lunice, Modeselektor, Monkeytown, NastyNasty, Radiohead, San Francisco, SBTRKT 1 Comment


text:
If you thought Qualcomm's keynote at CES earlier this year was out of control, just wait til you see this new commercial from the CPU maker (and if you haven't seen the company's insane CES performance yet watch it here). The new commercial imagines what today's world would be like if smartphones didn't exist but we still had mobile access to Twitter, Email, Angry Birds and more; it doesn't really makes sense but somehow I don't think that's the point.
There's not much more to say besides the obligatory musing on how much we really do depend on our smartphones nowadays. I'll leave the rest to Qualcomm though, so check out the company's hysterical commercial above, or if you don't have time you can scroll through some screenshots below.


text:
Gas Station ATGs
Fuel Depot ATGs
Skid-mounted Site ATGs
Tank Truck ATGs
Chemical Plant ATGs
Leak Detection System
Automatic Tank Gauge Probes
Automatic Tank Gauge Consoles
Tank Monitoring Software
Tank Gauging Optional Device
Company News
Industry News
Windbell Profile
Windbell Culture
Windbell Honors
Become A Dealer
The CLS200 series leak sensors are optical type, and they are specially designed for double-wall tanks, can detect and identify air, water and fuel in the interlayer.
● Can detect and identify air, water and fuel in the interlayer
● Explosion-proof design, safe and reliable.
● Compact structure, easy installation and maintenance.
Add:No.9, Changchun Rd, High-tech Development Zone, Zhengzhou, China 450001


text:
The Changelog – Episode #282
The Impact and Future of Kubernetes
with Brendan Burns and Gabe Monroy
From KubeCon + CloudNativeCon 2017 — Brendan Burns (Kubernetes co-founder) and Gabe Monroy (creator of Deis) joined the show to talk about the origin, impact, and future of Kubernetes and cloud infrastructure.
Command Line Heroes – A new podcast about the epic true tales of the developers, hackers, and open source rebels revolutionizing the tech landscape from the command line up. Presented by Red Hat.
Google Cloud Platform Podcast – Google Cloud Platform weekly podcast is where Google developer advocates Melanie Warrick and Mark Mandel answer questions, get in the weeds and talk to GCP teams, customers, and partners about best practices—from security to machine learning and more. Hear from technologists all across Google about trends and cool things happening with our technology.
DigitalOcean – DigitalOcean has new, highly competitive droplet pricing! A flexible $15 plan where you can mix and match RAM and CPUs resources. Updates to CPU-optimized Droplets. Per-second billing (coming soon). New accounts get $100 is hosting credit to use in your first 60 days.
Fastly – Our bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform.
Notes & Links
"If Kubernetes let's you not think about your machines, I think in many cases people don't even want to have machines, this move towards serverless containers and the orchestration of serverless containers is the next really important part of what we're doing." — Brendan Burns, co-founder of Kubernetes
- Kubernetes
- Deis
- Follow @KubeCon_ on Twitter for updates on the conference
- Go Time #63: Changelog Takeover – K8s and Virtual Kubelet
Let's kind of give an intro to both of you. You're both well-known, but we're gonna start with you - give a back-story of who you are to Kubernetes, so to speak.
Sure. So I am one of the original creators of Kubernetes, one of the people who wrote the original prototype that sort of was the pitch vehicle that got everybody involved in saying that we should do this and started to set the ground rules for the project, and been involved from the beginning, sitting on the IRC channel, talking to people, going out to conferences and meetups and king of hitting the pavement for a long time, to kind of drum up a lot of interest...
You know, I look around at this conference and there's a lot of really interested people, and it wasn't very long ago that I had a lot of people asking me why the heck they should be interested in this thing... So it's an interesting turnaround.
How long ago was that point of view?
I don't know, it depends--
Two years, three...?
[00:03:42.04] Certainly two years ago, but even a year, a year and a half ago I think you ran into people who were still -- and then obviously still, throughout, there's a lot of people who haven't necessarily... If their thing is working for them, that's great, there's don't need to change. But definitely early on there was a lot of... I think people were just sort of still kind of getting used to the cloud and virtual machines and traditional tools like Chef and Puppet, and all of the sudden all this new stuff -- it's like, "Oh, I have to learn all this new stuff? What am I gonna do there?"
That was an interesting time, doing a bunch of meetups. It was a lot of fun though. It was a lot of fun to get out of your shell and go and meet with a bunch of different people from different places, different experiences, get to know them and get to know the kind of products they want you to build.
So for the listener's sake, it's safe to say that you've been here since the beginning.
Yeah, I would say I've been here since the beginning. I think a lot of the technology stretches back further than that...
Because it's from experience, inside of Google...
It's from stuff that's been in the Linux Kernel since 2008, and work that's been done on the Linux Kernel... And even further back. I did this talk a while back about sort of like the history, and you can point back to chroots in UNIX in the late 1970's as sort of being the beginning of containers. It's important to point back and know that this is not an original idea; this is a collection of tools that have put together a lot of different ideas that people have had over the years. Now I'm a distinguished engineer at Microsoft, and running a lot of the container and dev ops stuff that Azure does.
Very cool. And Gabe, what's your history with Kubernetes specifically?
So I kind of came at it from a different angle from Brendan. My history really comes from the developer experience angle. I was doing some consulting in New York, and 2008 happened and it kind of evaporated overnight, and I took all the commonalities that I was seeing around all the different companies that I was working with, and it was all around deployment automation being on fire everywhere... So I started a company called OptiMend, building tooling to make deployment automation easier; basically, running around and adding on early CI systems and Debian packaging and a bunch of stuff to automate software delivery, at a time when that wasn't commonly done.
From there, I sort of evolved a sort of PaaS and created this project called Deis, which turned out to be really popular. It was more or less Heroku, but running on your own servers, which was a very common refrain we were hearing from people back in 2009, 2010 timeframe. But I had the interesting experience of having to replatform the container-based -- actually, early involved in the container ecosystem, close with Solomon, and it was one of the largest external contributors to the Docker project for a while, just before it became popular... Only because we needed it for the Deis project.
What ended up happening over time was every orchestrator that we tried to platform it on just didn't work, and something was wrong... That eventually led me to Kubernetes. I think the first time I ever talked to Brendan was about extending the Kubernetes API. I'll never forget... I was on a plane or something, and I think you said--
SREcon. It was Dublin. Going to SREcon in Dublin, and I'd done this stuff--
And you did the TPR -- first pass at TPR, the extension model, on the plane. He's like, "I'm gonna push this branch up, you guys take a look at it." And me and Matt Butcher (the architect on Helm) were super excited to work with him on it. So from there, I ended up joining Microsoft by way of an acquisition seven months ago, and now I'm sort of Brendan's counterpart on the PM side, working on the Azure containers portfolios - the AKS, the ACI, the servers broker stuff, dev tooling... Lots of different things we've got in the hopper.
I think it's interesting the perspectives here. You represent the end user, so to speak, to a degree; a user of Kubernetes to build a platform on, pre-Kubernetes even, trying different platforming tools, different orchestrator tools to build Deis on, and eventually... You know, my perspective from it isn't as a user with Deis, but it seemed like Deis was trying to catch some steam, but it caught a lot of steam with Kubernetes. That's what really solidified in making it easy to use.
[00:08:14.01] I think it was one of the first PaaS platforms to realize that the future came in replatforming on top of container orchestration. I think now, a year and a half, two years later it seems obvious, with Cloud Foundry and with OpenShift and others replatforming on top of container orchestration. I think Deis really saw that early, and I think that caught a lot of attention.
Yeah, one of the interesting things to me is how the developer experience of the time when Deis was popular is kind of falling out of favor, in a lot of ways; Twelve-Factor is pretty limiting, and Kubernetes opens up a lot more opportunities. So we ended up kind of shifting our focus to things like Helm and Draft and Brigade and some of the newer stuff that's a little bit more Kubernetes native in this disposition, and I think what you're seeing from Brendan with Metaparticle is taking that jump a little bit further.
I think it's really tricky with developer experience, because on the one hand you want to be innovative, but if you go too far, you're gonna lose people; if you don't innovate enough, people are gonna be like, "Well, that's not compelling enough for me to drop whatever my current thing is." I think Deis definitely hit a sweet spot in kind of where it was at the time, but I think in a way we've kind of, as an industry, move on from that a bit, right?
Yeah, I think that's the case.
What's the state of Deis right now? I know it was in acquisition seven months ago... What's the state of the company, the project? Because it's like a company, and then a project in the same, which is somewhat confusing to most people.
Yeah, it's an open source project, and what's really cool to me is we've spent a lot of time trying to put proper governance around it, and even small things, like semantic commit messages so we could write changelogs... A lot of that stuff to really just try and get a community of maintainers to step up. What I'm really excited about - there's a group called Team Heffy or whatever, who is sort of taking on the Deis workflow project and driving it in a new direction. I'm really excited to see that work taking off. It's been highly active.
And I would say the Deis team itself, the engineering team from the company has been -- they are a core part of the Azure Container Service team at this point, responsible for a lot of the engineering work that went into the AKS launch that we did recently, as well as the open source projects that we've launched recently Kashti, this GUI for Brigade... It's a workflow engine. The Draft tooling that we announced a month or so after the acquisition... So that whole team is contributing to both the core Azure container's experience, as well as open source tooling that makes Kubernetes better, regardless of where you're gonna run it.
And even things like the Open Service Broker, which interestingly derived -- we started thinking about it first at Deis as a PaaS thing, because it was a Cloud Foundry-ism, and when we were platforming on top of Kubernetes, we were like "Well, there's really a better way to solve this in Kubernetes." That linked us up with Red Hat and Google, and we all kind of worked together. I'm really excited to see things like the Open Service Broker stuff landing, not just from Microsoft, but also from folks like Google and Red Hat. Everyone's talking about this, because it's a pretty important part of the modern stack.
Was that announced here at the conference?
It was, yeah.
I didn't catch that announcement. Can you give me kind of an overview of what that is?
Yeah, sure. The general idea is, you know, just because you can run something in a container doesn't mean you should, right? So things like data stores... Often the operational characteristics of a hosted cloud service - Azure Cosmos DB, for example - are gonna be much appealing to a container-based equivalent. And yet, people wanna be able to use the Kubernetes APIs to manage that stuff, so how do we build a bridge between Kubernetes and this world of Azure services? Or even on-prem services, Oracle databases, things like that.
[00:11:57.14] The Open Service Broker API has some verbs, provision, deprovision, bind, unbind and give me the catalog and that's basically the broker, that's it. And so what we did was we built a set of Kubernetes resources and Kubernetes controllers that can manage the lifecycle of apps, and what you get at the end of it is a Helm chart where you can Helm-install Wordpress, and it looks and feels just like any other Helm chart that you would install, but where there would be a MySQL container, you instead have Azure database for MySQL. But the lifecycle management of the tooling is exactly the same.
Very cool. Let me go a little further back in the past... How many years has there been since the public birth (of some sort) of Kubernetes? How far back does it go?
It was about three and a half years; it will be four years next June.
Four years. So I think pre-call -- I don't know if those made it into the actual audio that will go to the listeners' ears or not, but Brendan, when you said you remember a year, a year and a half back even(ish) when people were still questioning Kubernetes, and we're a point now where to me - and maybe everyone else is thinking this, too), Kubernetes has won. You've got a conference that was 1,000 people last year, 4,200 people this year, significant growth, a lot of buy-in from worldwide partners, members in the CNCF and so forth, so it's definitely won. Can you kind of, as somebody who's been there since the beginning, shed some light on kind of where you came from and where you're at now?
Yeah, it's really incredible to see; it's humbling, I would say.
Did you expect it? Is it a surprise to you? I know you're good and the team behind you is good...
I don't think you can ever expect this kind of stuff.
Right. This is a shift.
You have to go into it and believe that you're gonna work hard and hopefully the right things are gonna happen, but I don't know that you ever take it for granted. There was a moment -- I really actually remember a distinct moment about a year and a half ago, I would say (maybe a year and three quarters ago) where I kind of felt the wind. It's like the wind switched from being in my face to being at my back. It was sort of just this intuitive sense of, like you've crested the hill... And you're not done, but it's getting easier.
I still think that there are a lot of people out there who are thinking about container orchestration and still sort of wondering "Where's the value prop for me?" So I think that we're still talking about container orchestration, but I don't think we're gonna talk anymore about what container orchestrator to use. I think we kind of always knew that that was gonna happen for some API.
At some point, someone was gonna --
Someone was going to -- it just doesn't make any sense, right? If you were a monitoring company, if you were a developer, you don't want there to be multiple APIs, you want there to be one API, because then you know... You know, I remember we had this discussion, and Gabe knows this, because he actually took Deis and platformed it on a bunch of different orchestrators before they chose Kubernetes.
We talked to people and they said "Which one am I supposed to target? I'm a monitoring company, which one am I supposed to target?" We don't have those conversations anymore, and I think everybody's happier, the developer ecosystem is happier for having that. I kind of always said there would be sort of a POSIX standard here, and I think that's what we're seeing emerge... And now the exciting thing is "Okay, if this is a commodity, if every public cloud has this as a service, what do we build next? What do we build on top?" So I think that's the other exciting part - we can finally sort of put the orchestration API behind us. It was never intended to be the final API. We need to start thinking about 'What are the layers we build on top?", and that's really exciting to me.
Do you have any insights into what's next then?
Well, so Metaparticle, that I talked about yesterday, is something that I think is important.
That was interesting. Do you wanna give you a breakdown real quick for those who didn't catch your talk?
Sure. Metaparticle is actually an independent open source project at Metaparticle.io. It's really trying to, I would say, bring distributed systems to people who might not otherwise be distributed systems developers. Another way that I've said it before is like "Visual Basic for the cloud." How do you have an experience where you can think about the concepts of cloud-native computing, but not necessarily the details of "Hey, there's this YAML file here, and there's this Kubernetes object..."
[00:16:17.29] Maybe I just describe my system as having four replicas, and I want you to take care of ensuring that -- you know, in code I'll say I want four replicas, and you take care of figuring out how to deploy it, how to put a load balancer in front of it, and stuff like that.
I think that there's always been this inevitable trend in configuration management - and actually, we talked about this a lot with the Helm team - around like... Configuration management gets more and more programmatic, and eventually it turns into like a bad programming language, and I think that at some level we should just admit that (as some people said) configuration is code, and I think we should admit that like "Well, if configuration is code, maybe you should just write it in a real programming language." There's all of this tooling around unit testing that we've built, all of these practices around writing software code, that don't extend into the way we configure and deploy our applications at all. I don't think that anybody -- someone pinged me and said "I was just starting to think about what it meant to unit-test a Kubernetes config", right?
It's kind of crazy that we have 20 years of people thinking about unit-testing code, and yet we're having to reinvent it for configs... Like, why? We should just go to a place where there's frameworks, there's UI, there's all of the kind of stuff that we expect - code conventions, all of this stuff - and then we can express that in code.
I think if you do that, not only do you end up with a better system with one source of truth, but you actually also build a more accessible system. You can have people who might otherwise just be front-end Javascript programmers, who are starting to think about deploying distributed systems. I think it's the only way that we scale the industry to the number of systems that need to be built.
So I think it's maybe like Kubernetes at the beginning, it's an experiment, it's an idea; I wanna start a conversation, start a community. I don't know that it will be the one, but I think something like it will be the way that we build systems in the future.
This question is more for either of you really, just kind of teeing off what you said there, it's how we got here - can you go back into the history of Kubernetes and the community? Not just the technology, but the community, the impact... How did we get here? What were the right recipes that other open source would-be's of Kube-- maybe there's not a repeat, but there's somebody out there looking to what you all have done around the technologies, around the community, around the governance, even around joining CNCF, and Google's perspective, and now Microsoft's perspective on containers...
I can talk about that a little; I'll start it, and then Gabe can give his perspective as well. I was a student of the FreeBSD Linux course in the early 2000's, and what I was thinking about community and technology and how technologies win, I thought a lot about that. And you know, I think Linux in that world won, because it was friendly and open and it was an ecosystem that you could build on. There are no technical reasons why it won, I don't think. It won because of the community that it built, and it won because of the ecosystem that developed around it, and then the technology came afterwards. People were like, "Oh, okay, it's won. Let's go in and harden security, let's go in and do all of these things."
So that was part of it - it was that it's not okay to just build a community, you have to build an ecosystem. You have to do a good job of sort of telegraphing what you are and what you're not, and staying to your commitments and saying, "You know what, this is the line where Kubernetes stops, and this is the line where--" and I think we did that with Helm, actually. I had conversations with Gabe where we said configuration management, package management is something that Kubernetes is not gonna do; we're not gonna pull that into the core. That's gonna be a project that lives on top, gives space for an ecosystem to develop around you...
[00:19:58.15] I also think I went into it with a real humble attitude, a real "every single question is important" kind of attitude. I think that's incredibly important also. It makes it a welcoming community. I'm really proud of the community that we've developed; I think it's pretty unique, honestly, and in tech in general, in terms of the degree to which it welcomes people in. I think that's critically important, and it was (I hope) a big part of the success as well. I don't know.
What do you think about the perspective, since you kind of come at it as a developer, user experience implementer, kind of end user perspective... Because you weren't involved in the creation of Kubernetes, you were involved in building something like a PaaS and needed an orchestrator the entire time, and here comes Kubernetes. Can you kind of show your perspective on that?
It's interesting to me, one of the things -- before I joined Microsoft, I would pull up a quote from the Borg paper. A lot of these systems are sort of inspired by the way Google is managing infrastructure internally. And in the Borg paper, right in the first part of it, they call out the reasons why they built it, and there's three things they call out. The first is they wanted to empower developers for self-service. They wanted developers to be able to deploy these large clusters without having to involve ops, for example.
The second thing is they wanted to build software that was extremely reliable and resilient to underlying infrastructure failures. And the third thing was that they wanted to be able to throw hardware at the problem to scale out. So if there was a scale event, or they needed distributed workload, they could just add capacity and everything would take care of itself. And what's interesting to me is I think that though not all companies operate at that scale - Microsoft scale, Google scale, that kind of scale - those three things are still important to everyone, especially as... You know, the reality is there's only so much compute power you can pack into one server; as you get the benefits of distributing this stuff out and self-healing infrastructures that eventually converge, declarative models for how you wanna manage this stuff - this really impacts folks who are operating at the 20 server scale, as well as a many-thousand server scale.
I was enticed by that proposition, and I think that we still have a lot to go on that first thing, the empowering developers, and I think that my big takeaway from this conference, including not just Brendan's keynote, but also Kelsey this morning, and Michelle Noorali actually at the keynote before, talking about "Look, Kubernetes is still hard for developers."
So I still think we've got a ways to go there, but the good news is that on the other dimensions I think we're actually in a pretty good place. Brendan and I actually were joking the other day that when we start talking about enterprise security features like RBAC, and policy and governance, you know the project has moved on from its phase... So I think that's a good thing to see, because it means things are maturing.
Let's talk about the acceptance of it and who's using it, because I think at this conference my eyes were opened to a different type of user which I really hadn't considered, but I'm not as close to this project as you guys are... But it's like you've got people who are accepting the cloud, and then you've got traditional IT, which is present here more than I've ever seen at maybe the tech conferences I've gone to over my years.
I see a huge presence of actual IT, not just cloud application developers who ship to the cloud and are in this new world, where sort of like old school virtual machines and behind the scenes, behind firewalls - that IT is present here, looking to new ways where Kubernetes is taking over what they had done before... And in some ways they're kind of scared of it.
Well, I don't know; I would hope that they're not, in the sense of actually--
Well, not so much scared... Let me clarify what I mean by "scared" - it's that it moves so fast; they're used to deploying and chilling down and just sort of maintaining, not in a bad way, but that sort of like the older IT world, you know? And that's not here with Kubernetes. Kubernetes is fast-moving.
Yeah. You know, we've talked a lot about how much it needs to slow down; I think that there's a component of like once you're starting to talk about those enterprise features, you're also starting to talk about "it's great to have a three-month release cycle, but if half your customers aren't gonna adopt your three-month--"
...what's the point of releasing?
What's the point...? But I would also say I think that as much as we talk about Kubernetes empowering developers, I think Kubernetes actually also really empowers operators, even traditional machine operators, because the whole purpose of the technology is to provide this abstraction boundary between the developer and the machine. So just like I can deploy apps and not care what machine they land on, that makes a reliable app.
I can upgrade machines and know that I'm not gonna impact customers. If I'm an IT ops and I wanna roll a new kernel, I don't have to go talk to all my application owners and convince them, and try and say "Hey, please, could you reboot your app? We need to do this security migration..." - no, I just go through the cluster, one by one, do the upgrade, reboot the machine, do the upgrade, reboot the machine, and then I know that the Kubernetes infrastructure will move those end user applications around, so they won't even notice. They won't even know that I went into the software upgrade across my entire OS. That's a hugely empowering thing for a traditional IT developer.
I think that separation of concerns is actually one of its real strengths. We think of it as being developer-oriented technology, because at the end of the day it's a developer-oriented API, but the abstraction boundary and the isolation, the decoupling works in both directions. So I actually am not surprised at all that there are more traditional IT people here; if I were them, I would adopt this in a heartbeat, because it's gonna make my life dramatically easier.
Okay. Gabe, do you have anything on that?
[00:29:37.15] Yeah, one of the big things that we're seeing from those traditional IT folks is the desire to lift and shift workloads into containers. I've been present for some pretty shocking -- the idea that you could go take a bunch of existing legacy Windows applications and in a few days get those things wrapped up in containers, moved over to an orchestrator and get all the benefits of, you know, the self-healing system, node failures, the workloads are gonna move around, the applications are much more resilient, you don't need to go back and decommission a bunch of old servers and hardware, maybe you throw a cloud move into the mix... I mean, that stuff is really enticing to traditional IT orgs, and these are the things that container orchestration makes possible... So I definitely agree with Brendan, there's a lot to like here.
I think we have to be conscious that container orchestration is sufficiently generalized that sort of modern cloud-native microservice development that we associate that with Kubernetes very closely, there's actually a lot of other uses for this stuff, IoT being another one. Lots of different things; machine learning... There's lots of different things that you can use this for. I think we're just scratching the surface of that.
Yeah, and I think that's definitely the case that I see people with... Maybe they're running a binary that they don't even know how to recompile, from an old version of Linux, and suddenly, with containers, they know that they can upgrade the kernel, but keep that whole thing working, and package up all the libraries and all the... They can effectively run Red Hat 4 binary on top of a modern Linux operating system. That's hugely compelling for a lot of IT operators.
So what do you say then when you said before about slowing down, in a press conference yesterday - neither of you were there, I don't believe; I didn't see you there at least - a fellow asked the question of LTS-ing Kubernetes, to the point where some IT can, like you had said, implement it, there's a new release, have some sort of schedule where this will be supported for a while, you can kind of depend on certain APIs, you can build upon certain things... Is there any conversations around that kind of slow-moving pace, or-- not slow to the point where you're not innovating and moving fast, but to the point where your release cycle can actually adopt some users?
I don't think that we've -- we haven't had the conversation about a formal LTS. We do back-port patches, important patches, not just to the previous release, but actually several releases back... So we do do some of the sort of more longer-term support things that you might consider, into the past releases. But that probably buys you a year, maybe... You know, conservatively, that would buy you a year before mostly the project would throw up its hands and say "Sorry, you should upgrade."
I do think we're gonna have to do that kind of stuff. I mean, I think maybe looking at the way that Ubuntu does long-term support, with a long-term support release, and then a bunch of smaller releases along the way that you can use if you want, but they're not the long-term support releases may be the kind of model that we need to move to.
I do think though that in the move to cloud one of the things that I think you're seeing is a move towards more auto-upgrading systems. One of the analogies that I draw is people used to update their browsers; now people don't update their browser, the browser just updates itself.
Yeah, I don't even think about that anymore.
Nobody even thinks about it, right? You couldn't even tell me -- I guarantee you can't even tell me the version of the browser you're running.
Yeah, like who knows?
That's how many versions there have been...
That's how much you pay attention to it, right?
So I think there's a degree to which if we're good about backward compatibility and we're good about making sure that what you did last year still works, people aren't gonna care as much about what version of it is, in an AKS world where we're delivering the Kubernetes API as a managed service. So I think it's a little bit of both. I think we're gonna have to do some of that, but I think also as people enter into this service, Kubernetes as a service world, maybe they're not as worried about that stuff.
Maybe let's talk about something you mentioned yesterday in your keynote which I thought was pretty interesting... It was this being able to scale to 100,000,000 developers. We'll link up to your keynote on video, but can you give like maybe a two-minute overview of what you meant by scaling to that? ...the scale at which GitHub is moving and open source is moving and what that means for...? Because we said earlier, one of the key components of successful Kubernetes cloud native is community, and that means more developers.
[00:34:08.14] For sure, and I think one of the reasons we've invested -- I mean, Gabe mentioned about third-party resources... I sort of worked on third-party resources before we even hit 1.0... Because it was clear even then -- I didn't try and merge it until after 1.0, but it was clear even then that extensibility and enabling people to build and integrate with Kubernetes without being in the core of Kubernetes was gonna be critical to our success. We were already seeing the strain points of the community, and we were -- I don't even know, probably at 100 contributors at that point, not the thousand plus that we have now.
So that's a big push - making sure that we can effectively continue to innovate and iterate on the ecosystem without having to change the core codebase as much, and that's a huge part of scaling. But I also think that we have to start considering that the people who we are trying to appeal to are not necessarily gonna be distributed systems experts, right?
I think up to this point we've basically assumed that you have some degree of experience with delivering reliable systems at scale, if you're gonna come play in the Kubernetes world. If we're gonna go forward from here, we have to not make that assumption, and maybe separate out... Maybe if you're in the core, you need to do that. But if you're building on top, you should be able to consume abstractions that make sense to you at the level that you wanna build at.
Brendan and I talk a lot about this idea - from my PaaS heritage, it's easy for me to color it all in PaaS, but talking about this idea of verticalized pass. I think that part of getting to 100 million developers is gonna be crafting a set of experiences that are unique, that are targeted at different audiences. Some are gonna be GUI-based, some are gonna be CLI-based, some are gonna be editing code in an IDE, and others are gonna be... Who knows, right? But there is no one-size-fits-all answer to all the problems that we're gonna need to solve going forward, so I think approaching this thoughtfully, with an eye towards principled architecture of the different layers is what's gonna allow us to set up a really resilient foundation in order to build the type of experiences that frankly society is depending on us to build.
Yeah, for sure. And I think someone once said the most important thing in any project is knowing what you are not; it's not knowing what you are, it's knowing what you are not. And I think if you set those things up the right way and you resist the urge to try and become everything then you build the right layering and you build the right modularity. I think that's one of the guiding posts we try and live to.
Maybe in closing let's talk to those out there who've heard the term 'cloud native', they've heard the term Kubernetes, they've looked at orchestration, they've looked at containers, but they've never really taken that first step -- they've dabbled with containers, but they've never really taken the adoption to even cloud.
What are some good resources that you all point people to often to kind of get those first steps to get that a-ha moment? Because both of you have a - not so much you, but Gabe, you have a first day that you touched Kubernetes, and you were like "This is amazing." So where do you send people to to kind of get that original a-ha moment with Kubernetes, and to say "This is what you should do."
Well, there's a couple things... I think the first thing for me is the 12-factor - it's not directly related to Kubernetes, but I think it was a really important moment in the development of how you would build software in a way that is friendly for the cloud. I think reading through that - it doesn't take very long...
What is it called?
[00:37:51.01] 12factor.net is the website, and it's actually pretty dated, but it's held up quite well over time, I'd say. And then the other -- I don't know if there's a research for this, Brendan; you might know... But the thing for me that really hit home with Kubernetes was the idea of declarative infrastructure that has control loops that reconcile desired state and current state... These self-healing systems, and how all of Kubernetes is basically a series of objects that are representing desired state, and then a series of controllers that are enforcing that desired state, and pushing the world towards that state over time.
It was the first project I'd ever seen that had that kind of architecture that deeply. I actually think that was part of the extensibility model, because really what you do with the extension model is you say "Well, here's a new type of resource, and I wanna run another controller that's gonna enforce that sort of state." And there was a level of elegance and simplicity to the whole model that -- it was just different than anything else that was out there. Everything else felt cumbersome, complex in comparison.
I think the only thing that was weird/awkward about Kubernetes was the networking model, but shockingly, it only took a few months for everyone to realize that the Kubernetes networking model was actually the right one, and then everyone started adopting this IP per container, IP per pod kind of model. Once that's sort of behind you, you're left with this core of Kubernetes... It's actually really quite beautiful and really quite elegant in my view.
One last one before we go... This podcast speaks to developers, so you've got people out there that are thinking "How can I get involved?" Not so much just using Kubernetes, or getting involved in CNCF, or the different places they can go to, or the different projects involved in CNCF... But what about contributors for open source? I hear there's a contributor ladder... I think its' CNCF Global, at the TOC level, but not so much at a Kubernetes level. What do you do to get new contributors? What's the onboarding ramp? How do you adopt new developers into the project?
I think it's a variety of things, one thing I would say is that the Slack channel is super active... And it's separated - we have a separate channel for users versus developers. Some people go and ask "How do I deploy apps?" questions on the users channel, but if you wanna go do coding, there's the developers channel. We try and mark a bunch of the GitHub issues with things like "Help Wanted." Some of that stuff is sometimes dated, and we don't probably do as great a job curating that as we could, but that's a good place to start.
I would also say though that we're reaching a place where there is so much in the ecosystem that often times a great way to get started is in one of the ecosystem projects. I've been doing a lot of work lately on client libraries in different languages - working on the Java client library, the .NET client library, the TypeScript client library... And that's nice, because it's an important part of the ecosystem, but it's a separate project from the main project, so it's an easier thing to wrap your head around, and maybe it's even in a language that you're familiar with, as opposed to Go, if you haven't had a chance to look at Go. So I think there's a variety of different places where you can find access points.
I would say with the main Kubernetes project, be persistent and patient. We really do want and value the contributions. We know that it's messier and harder in places than it probably ought to be, and in fact there's a SIG contributor experience - it's a special interest group for contributor experience - that's just kind of continuously trying to make it better. That's where things like the contributor ladder comes out of, and some of the messages that the bots chat back to you on your GitHub issues, and stuff like that. We definitely welcome people to come in and contribute, and figure out the place that works best for them.
Very cool. Anything else that I didn't ask that you guys are like, "Man, I wanna share this to this community listening to the show"? What didn't I ask you?
One thing that I'm kind of excited about that we announced at the conference is this thing called the Virtual Kubelet.
I've heard about this... Erik St. Martin is a friend of mine, he runs GoTime; he was part of the hack team that's been here for a week doing that, I think. I've got some of the back-story on it.
[00:42:05.08] Yeah, Erik helped out quite a bit on that effort, actually. And what's cool about it to me is that it's really evidence of Kubernetes' staying power, because we didn't have this concept of a serverless container runtime like what we shipped with Azure Container Services back in July; it was the first major cloud provider to come out with anything like that. And we knew when we launched it that people were -- yes, they were gonna want to use it directly; containers in the cloud is pretty nice, easy...
Container Create turns out to be a nice experience for doing simple stuff. But we also knew folks were gonna wanna use the Kubernetes API, so we shipped a connector that basically bridged the two things; immediately, Hyper.sh, who had a similar product, they forked the connector (the connector-friendly fork), wrote their own runtime. Since then, Brendan and I were like, "Oh man, there's probably something we should do here", and there's actually a lot of meaty problems that we don't know how to solve yet. How do you attach volumes to a serverless container? How do you manage load balancers, scheduling affinities and things like that?
There are a lot of open questions, and I'm really pleased to see the reception to the Virtual Kubelet has been tremendous, and it looks like we're gonna have pretty much all the major clouds (and startups) who have these serverless container runtimes working together on this codebase that we're gonna be donating upstream to the Kubernetes ecosystem. I'm really excited to see that come to fruition.
Yeah, for sure. Over the next few years, I think one of the things we're definitely gonna move to is -- you know, if Kubernetes lets you not think about your machines, I think in many cases people don't even wanna have machines. So this move towards serverless containers and orchestration of serverless containers I think is the next really important part of what we're doing.
So listeners, I know we've just barely scratched the surface on this Virtual Kubelet, and I'm sure that in a future episode of GoTime Erik will go deep on what's going on there, so tune into a future GoTime episode. But for now, fells, thank you so much for your time, I appreciate it.
Absolutely, thank you so much.
Thanks for having us.
Our transcripts are open source on GitHub. Improvements are welcome. 💚


text:
Pregnant Kim Kardashian: Sears Appearance with Sisters!
Kim Kardashian shows off her pregnancy curves during an appearance at Sears to promote her line Kardashian Kollection at Willowbrook Mall on Saturday (May 4) in Houston, Tex.
The 32-year-old pregnant reality star was joined by her sisters Kourtney and Khloe.
PHOTOS: Check out the latest pics of Kim Kardashian
"My fab fashion pieces end Sunday @ebaygiving w/ @auctioncause, proceeds support Life Change Community Church!" Kim tweeted later in the day.
The day before, Kim, Kourtney, and Khloe were spotted flying out of LAX Airport.
25+ pictures inside of Kim Kardashian appearing at Sears with Kourtney and Khloe…