Buck joined The Neighborhood Dining Group in 2013 as Chef de Partie at Husk Charleston. He recalls his first night in the Husk kitchen as an explosion of flavor and a connection with food on a visceral level, of which he had always longed for. Under the direction of Chef Sean Brock, Buck learned the importance of a symbiotic relationship with local farmers, the land and the thick heritage of the Lowcountry. Quickly, Buck found a voice through his culinary creations that would help diners return to a time of greater food integrity, honesty and purity, a cornerstone of the Husk philosophy. At Husk Charleston, Buck was promoted to Sous Chef, followed by Executive Sous Chef before being named Chef de Cuisine in Husk Greenville.


text:
"Mechanism of White Supremacy"?
I don't even know who it was I overheard on a talk radio program being broadcast at a local restaurant— maybe Rush Limbaugh or Sean Hannity?— but anyway, they were interviewing some Black Caucus-type people about the riots and the man kept referring to the "Mechanism of White Supremacy" over and over, but he never got down to identifying exactly what this "mechanism" is or describing how this machine works.
Well, we have found the "mechanism" and it's entire history— ready for the review and response of all Americans. It's called Municipal United States citizenship, or in the words of the now completely irrelevant 14th Amendment, "citizens of the United States".
These "citizens" are slaves owned by the Municipal United States Government.
When the rats abolished private slave ownership, they enshrined public slave ownership.
Former plantation slaves were the first victims of this travesty, but in 1933, FDR opened the floodgates of a new ruse to include all the white employees and dependents of the Municipal Government, too.
So how did you (or I) become misidentified as a Municipal United States citizen?
We were given the "gift" of a Municipal citizenship—- without our knowledge.
This complimentary "gift" citizenship status is literally "the" Mechanism of White Supremacy— only it should more properly be called "Mechanism of Corporate Supremacy", because it has been applied to all Americans without respect to color or creed.
To better visualize this— pretend that someone gave you a house in Manhattan without telling you a thing about it.
Does owning a house in Manhattan make you a New Yorker? No.
Does it make you a CITIZEN of NYC? No.
But so long as you don't know that you now own a house in Manhattan, you can't speak up and say so, can you?
So now they start sending you bills related to this "gift" HOUSE in Manhattan— disguised as property taxes and utility bills and all sorts of other charges.
What if you don't want or need a HOUSE in Manhattan and don't want to act as an absentee landlord and certainly don't want to pay for all the taxes and other expenses related to this "gift" property?
That you don't even know you own? And get no benefit from? That costs you thousands of dollars every year? And that gives foreign courts an excuse to address you and subject you as a slave to their foreign courts?
Well, I think you'd want to give that "gift" right back to the perpetrators, right?
Or, if you weren't terribly fond of Cousin Jack, you might give him the gift.... who knows? Maybe he wants a HOUSE in Manhattan.
The HOUSE in Manhattan is the STRAWMAN Municipal Trust operated by the Municipal United States Government in your NAME.
You don't want it, you don't need it, and so long as you hold onto it or fail to control it, you are liable for it.
This is the "Mechanism of White Supremacy" that has been used to oppress black Americans since 1868 and white Americans, too, since 1933.
And now that we know what it is and how it works we can address it together as One People.
It's time for all such obligatory foisted-off "citizenship" masking slavery to end.
Now that we know the Mechanism— back to the rest of the story.
The talk show host went on without exploring the "Mechanism" but asked two more questions that stopped the show:
1. If this had happened to a white man, would we even know about it?
2. Why do colored people continue to elect Democrats who—even though they have had entire decades in which they have controlled both houses of Congress and the Presidency— have never delivered?
Both these questions elicited a long silence. Noticeably long. As if for just a moment, all the assumptions and indoctrination stopped. A ray of truth broke through, and everyone realized— yeah, we are all being victimized, yeah, it's true, we gave the Democrats all that power for years, and....
They did nothing to stop the Mechanism of White Supremacy.....also known as the Mechanism of Corporate Supremacy.
Posted by Paul Stramer at 5:48 PM 10 comments:
Labels: "Mechanism of White Supremacy"?, Anna von Reitz
The Third Decree Over Mandate
Many people don't know what a Decree is, much less a "Mandate" so let's explain. A Decree is issued by sovereign States or Principals (or as in this case, their Lawful Agent) as a direction or order given to secondary parties who are exercising Delegated Powers—- called "Mandates", a word equally applied to the action of issuing a mandate and to those carrying such a mandate forward.
The Federal Constitutions established such mandates and authorized the exercise of our "Delegated Powers" to Third Parties.
There were three groups of Third Parties who received our mandates: the States of America, the Queen/Westminster, and the Pope.
All three have now failed and been divested of power, with the result that the Delegated Powers have, by Operation of Law, returned to the Delegators: The United States of America and the American States and People.
This Third Decree Over Mandate is addressed in effect to the Trustees of those who have been holding and abusing our Delegated Powers, informing them of our position regarding changes that are being made to the Uniform Commercial Code to unjustly enrich the banks, our position with respect to Covid 19 and bringing forward our claims and liens established on our own assets.
Those claims and liens have been brought in the name of the States of America, The United States of America, and The United States, which are all involved at different levels and in different jurisdictions as our Lawful Government.
Most of these claims and liens appear under my name, "Anna Maria Riezinger", in data bases around the world.
This was done to prevent false Claims on Abandonment. The international banks and their co-conspirators have aimed at bankrupting commercial corporations acting "as" governments, and then pretending that our assets being managed by these corporations were "abandoned" by the actual owners.
In the absence of clear evidence otherwise lodged on the public records, they would have gotten away with this bunko, but now the tables are turned.
Our country was used as "Crime Central" — the staging ground for much of the vast underlying crime, by a gang of international pirates.
Via the mismanagement of the Pope and the Queen, the apparatus of our government, and most especially our State of State organizations and our Patent Office and Monetary System, were commandeered and used to profit the perpetrators in Breach of Trust, and to set up this monstrous scheme of Corporate Feudalism promoted by the banks and politicians.
Under this criminal operation American babies were jurisdictionally kidnapped and their political status was deliberately misrepresented, so that they became misidentified as foreigners in their own country.
This is a crime both during war and times of peace, a capital felony requiring the death sentence for those guilty of conspiring to enforce this fraud on innocent people, so the Parties responsible were obligated to provide remedy for their actions , so as to excuse themselves and be able to claim that this vast unlawful conversion was "voluntary"—- all without telling their victims a word about it and without actually providing access to the remedies they published.
All Americans were supposed to be able to discharge all debts simply by signing bills and vouchers . Instead, Americans were impersonated as British Territorial Citizens and prevented from exercising their exemption. Then, next, they were billed as foreigners in their own country and forced to pay the bills of the Perpetrators of this giant con game.
Please read the Third Decree Over Mandate with all the above firmly in mind, and then join your State Assembly.
http://annavonreitz.com/thirddecreeovermandate.pdf
www.TheAmericanStatesAssembly.net.
Posted by Paul Stramer at 5:22 PM 6 comments:
Labels: Anna von Reitz, The Third Decree Over Mandate
Why Kill Colored People?
The simple answer is that the diabolical cads are racists and always have been. They actually think that they are superior in every way, the Master Race, blah, blah, blah.
Logically, if you are going to promote yourself as the Master Race, somebody has to be the Slave Race.
This is part and parcel of their entire "Either / Or" thinking modality. These cretins literally practice "Either / Or" thinking and enforce it on all of us as a means dividing and conquering us— all of us.
There are no actual winners in Satan's Kingdom, other than Satan.
So they divide us into rich and poor, black and white, Catholic and Protestant, and from the time we are babies what do they do?
They teach us—- literally TEACH us—- to look at our differences and not our similarities.
This is so they can manipulate us. Just like they are manipulating emotions and promoting lawlessness using yet another False Flag. It turns out that whoever the unfortunate victim in the video tape may have been, it wasn't Mr. Floyd, who actually died three years ago in another State.
Red flags, anyone?
We've been lied to about the structure of our government. We've been lied about who is in charge. We've had quadrillions of dollars embezzled out of this country. We've been lied to about September 11, the Lusitania, the Maine, the attack on Pearl Harbor, and as I recently demonstrated, lied to about the Atomic Bomb.
And we have certainly been lied to about the safety of vaccines and government oversight of the drug companies and Covid 19.
What more does it take, folks?
We are dealing with Liars. They lie for fun, They lie for profit. Yes, and they lie to control and to excuse their actions and to do hideous things and they aim to come out smelling like roses, too.
If they could lie about the Atomic Bomb and get away with it, obviously, the sky is the limit. Put a phoney veneer of fake science and bogus math over it, and they've already proven they can scare people into building bomb shelters.
Right now, people are rioting over police abuses that have gone on for decades, not just in Minneapolis, but all over this country, especially in Democratic strongholds.
Yes, you heard that right.
Absolutely all the worst police abuses, the racial profiling, the atrocious disrespect and disregard for individual rights and dignity all occur where?
In Democratic strongholds.
Why? Because Democrats have always hated people of color. It was the Southern Democrats in the Rump Congress after the Civil War that re-enslaved the freed plantation slaves as public slaves. It was the Democratic Party that voted Unanimously not to give colored people any voting rights and then turned around and pretended to be BFFs.
They were also the ones that cheated Colored People out of recognition of their Natural and Unalienable Rights and substituted "Equal Civil Rights"—- that could be suspended at the whim of the Congress, just like they are right now.
Liars. Nothing but Big, Fat, Dirty Liars, who talked about freedom and provided enslavement— for everyone, colored and white, alike.
I am told that last night looters destroyed the Treasury Building in New York. I find that highly suspicious. We are left to think that the looters were dumb enough to believe there was money in the Treasury — but they didn't bust open banks and left ATMs standing?
More likely just cover for the destruction of more records that have gone missing or been destroyed.
This is getting monotonous.
I am also told that someone kindly left big piles of bricks for the looters and left truckloads of bricks on every city block just to make the looting easier. Wasn't that thoughtful of someone?
And as always, George Soros and Son are involved.
If this country is such a terrible place how did they become billionaires? Why aren't they in jail for funding sedition— and a whole lot more?
Inquiring minds want to know.
Finally— to get to the question we started with— why kill colored people?
Well, they operate their "government" as a corporation so they want to cut their operating costs. Getting rid of the large inner city ghettos and all the welfare recipients does that very neatly, and once the ghettos are torn down the vermin can take over all that valuable real estate for development of parks and luxury high rises.
But there's more. I already told you about their habit of killing their Priority Creditors? We are all their Priority Creditors, but they owe Colored People more money on average because they have been enslaved as Public Servants ever since 1868.
Most white folk weren't "presumed upon" until 1933.
So, exercise your racial biases, kill the Priority Creditors you owe the most money to, reduce the welfare burden, AND free up some prime real estate for new development, all at the same time.
Colored people of all shades and colors— better think all this rioting and looting over. Better go home and give them no excuse to roll in the tanks and guns.
Don't get mad. Get even. Its hard to spend money you are owed if you're dead.
Join your State Assembly and help make history —and change—that the politicians promise and never, ever deliver.
Posted by Paul Stramer at 8:05 AM 14 comments:
Labels: Anna von Reitz, Why Kill Colored People?
A number of very urgent circumstances are bearing down upon me this morning.
My beloved Labrador Retriever suffered either a stroke or an epileptic seizure last night and so we are waiting for diagnosis. That's just my little world torn apart and an insight into the fact that I and everyone else continues on with the struggles of their private lives on top of all the other work we do and roles we fill.
We have sick dogs and dirty dishes like everyone else.
Thank the True God for all the volunteers and donations and on the ground "boots" coming forward to save this country from itself.
We are sounding a call for unity and clarity of purpose in the midst of the Mayhem and are pleased to see a new video by Mark Emery and the Lighthouse Law Club —I believe it's called "It's Game Time" — calling for unified action and laying out a game plan.
I have always liked Mark, though our approaches have been somewhat different— I slogged on to assemble the actual government owed to this country while he went the "Private Membership Association" route.
Now I think it's time for both ends to meet in the middle, together with several other major patriot groups and efforts, all working together on various levels and at various capacities to solve the same problem.
All of those reading this please pass the message on to Mark Emery that there have been many developments and we need to talk as soon as possible. The contact data I have for him is dated, but mine has remained the same so it's easier for him to call me, but whatever works.
He's right, as usual. It is time to come together, share resources, and deal with the usurpation against our government using all the lawful and legal tools available to us.
Because our vision of people-centered government that respects the rights and property of all people is for all people and the problem of Corporate Feudalism has grown far outside the borders of those countries that first gave the parasite a home, this is not just a call to unite and focus America on the job that needs to be done.
Every day from all around the world, I field calls from people who are waking up and seeing the evils and failures of their own governments and the slow creeping rot of society held captive by corporate robber barons, crooked banks and other institutions gone awry.
It's not just an American problem. The housecleaning and swamp draining is a worldwide necessity.
As Mark so neatly sums it up, we have been standing alone and haven't been able to gain the traction needed to make the needed changes because (1) we've been dumbed down and left ignorant, the better to prey upon us; (2) we've been disorganized; and (3) we haven't had access to our own money and funding needed to do the job.
Well, it's time to change all that. Time to get the education we need, pull together the organizations we need, and put together the funding to make it happen.
We have fifty States and forty-nine State Assemblies coming together. The sole State still Missing is North Dakota, which needs to get back on the map ASAP! If you know people in North Dakota, spread the word.
The Lawful Government of the Land and soil is back and in Session.
The push is now on to "populate" every county in America. Our lawful government has taken our claims into the Lion's Den and lodged everything firmly on the international Public Records.
We will soon be issuing actual State Credentials to replace State of State IDs.
We have websites for all the State Assemblies nearing completion.
And a new block chain Public Notice and Recording System, too.
We have a new Peacekeeping Task Force to bring together the Constitutional Sheriffs, the actual State Militias, and The Continental Marshals as a cohesive network.
We are bringing together a team of both Constitutional Bar Attorneys and non-Bar Counselors of Law to rebuild the lawful Court System and bring justice back into the Admiralty and Maritime Courts that have been used to usurp upon and pillage the people of this country.
It's coming together, folks, and you are making it happen, one telephone call, one Zoom Conference, one donation, and one new lesson learned —-organically, one step are a time.
Your government's main duty is to protect you and your property. The problem is that your government, of, for, and by the people has been Missing in Action for decades.
It's time to change all that.
Posted by Paul Stramer at 7:59 AM 6 comments:
Labels: Anna von Reitz, Unity
The formal Military in this country exists in two subsets— active duty and reserves.
For all practical purposes the "National Guard" and "State Defense Forces" of most States are part of the Active Duty Military and should be considered as "Federal" troops because they take funding from the foreign federal corporations and are "National" with regard to their States in name only.
Similar to the unlawful conversion of our counties resulting from their eagerness to receive federal kickbacks in the form of Federal Block Grants, most "National Guard" units have been unlawfully converted by the same process— which is why they have been deployed "as" federal troops in places like Afghanistan.
Calling them "State National Guards" when they are funded, commanded, and deployed by federal corporations is at best an evasion of these facts and a convenient means of evading constitutional and other prohibitions against foreign troops on state soil.
Bear in mind that all Active Duty U.S. Military are technically foreign troops with respect to the actual States and People whether you call them "National Guard" or "State Defense Forces" or not.
Active Duty Troops domiciled as National Guard forces in each State are commanded by the State of State Governor. Active Duty Troops officially assigned to the U.S. Military are under the authority of the President acting as Commander in Chief.
So the question comes up— what do I do when I finish my tour of duty and want to return home to true civilian status?
The answer for all forms of Active Duty Military personnel is the same. Once you receive your DD214 or equivalent discharge paperwork, you send a registered letter to the head of your branch of service informing them that you are returning to your birthright political status. You keep the letter and mailing receipts as part of your records. You are now officially separated from Federal employment and obligations and are free to join your State Assembly or resume your State National status by recording a simple Declaration.
Officers need to return and resign their Commissions along with the Notice letter, otherwise they remain under obligation to the Federal Government for the rest of their lives as part of the Reserve Forces.
This is, of course, a highly personal choice.
If Officers retain their commissions they cannot act as State Citizens because of their retained Federal service obligations, but they can act as State Nationals and have all their basic rights and guarantees upheld by the Assemblies.
We were having trouble with false claims that retired NCO's and enlisted personnel were similarly obligated to lifetime service and engaged as volunteers serving in "civilian-military" capacities without their knowledge or consent. To put an end to these claims we have had NCO's and Enlisted personnel apply for benefits owed to such personnel and forced the Department of Defense and DOD to admit that they are NOT eligible for benefits and NOT serving in any "civilian-military connection after retiring from Active Duty.
Again, the rule is— if you are maintaining ANY connection other than being fully retired from Federal military service, including any federated 'National Guard' service, you are limited to State National status and cannot serve as a State Citizen until you are actually and factually retired and all volunteer activities including reserve duty has ceased.
Upon your release from Federal U.S. service you are set free to accept a Direct Commission from The United States of America and to serve in your actual State Militia.
The Reserves make up a million man Reserve Force composed of "retired but not returned" U.S. Military and federated National Guard personnel. They have chosen knowingly or unknowingly to remain in Federal jurisdiction after their formal release from active duty.
These unseen defense forces were recently summoned back to work by President Trump.
In addition to these forces we have our own Peacekeeping forces in the form of our Constitutional soil jurisdiction County Sheriffs and Deputies, our actual State Militias, and our Continental Marshals Service.
None of these entities are in competition with each other and ideally work together cooperatively to cover and protect people and property, borders, and assets in all jurisdictions of the law both Public and private.
The actual County, State and International Postal District Forces, that is, peacekeeping forces owed to this country, have been largely defunded in recent years and operate as self-funded organizations supported directly by the people of each State. They operate on a system model similar to that found in Switzerland.
State Citizens between the ages of 21-45 are either direct members of the State Militia or supporting members. Together they help organize Public Safety and Defense Plans for their States and Citizens using the Swiss model and work as civilian peacekeepers. Older and younger members of the community serve a wide range of support activities.
Our Sheriffs can be recognized by their distinctive star badges and State Credentials. Members of our State Militias also have State Credentials issued to them by the State Assembly. The Continental Marshals function as our interface in international jurisdiction and can be recognized by their special Direct Commissions from The United States of America and their distinctive star badges with balls on the points of the stars.
Recently another Direct Commission organization has been authorized to help coordinate our peacekeeping functions at all levels— The Peacekeeping Task Force.
The Peacekeeping Task Force will be visiting local communities and providing education and support for our civilian peacekeeping services, networking local constitutional Sheriffs and actual State Militias and The Continental Marshals Service together to form cohesive protection for all Americans —State Nationals and State Citizens alike.
They may be recognized by their distinctive tan uniforms, their Gadsden Flag and Civil Peacetime Flag patches and Direct Commissions.
In addition to the Active Duty, Reserve Duty, and Civilian Peacekeeping Forces, there are private Law Enforcement Agencies that function as Subcontractors to our Federal Subcontractors and make up a private police force designed to protect the assets of the Territorial United States and the Municipal United States corporations.
These are all private security forces, aka, mercenary forces, under the direction of private and now largely bankrupt governmental services corporations.
These agencies include the DOJ, FBI, FEMA, BATF, IRS, etc. (Municipal) and their Territorial corollaries, Department of Justice, Federal Bureau of Investigations, etc. at the Federal level.
All such Agency Personnel are considered Law Enforcement Agents-for-Hire, otherwise known as Pinkertons and more generally as Mercenaries and they are engaged to enforce the private codes, regulations and Public Policies of the incorporated government services providers.
They are NOT supposed to be speaking to, addressing, arresting, or subjecting average Americans to their private corporate laws and statutes, but they are motivated by profit to do so. They have little or no Public Interest duty or responsibility and their activities presuming upon average Americans who are not employees or dependents of their corporations must be brought under control.
At another level, State Troopers and 'Sheriffs' and local police employed by incorporated entities are all Law Enforcement Officers (LEOs) and if they will not willingly obey and conform to their obligations to obey the Constitutions and the Public Law, they must be recognized as part of the problem.
The situation in Minneapolis this morning is due to the brutal action of a single uniformed corporate Law Enforcement Officer acting in flagrant disrespect of our Constitution and traditions.
Not only should he and the other arresting officers be charged with crimes, fired and not eligible for rehire, but their supervisors and the politicians responsible should be sacked. Finally, the corporation employing these thugs needs to lose its charter. City of Minneapolis and MINNEAPOLIS should both be no more.
And if the State of Minnesota doesn't do its job to discipline its employees, it's charter needs to be revoked, too.
We don't have to put up with this kind of behavior— not from individual men and not from the corporations that hire them.
Get organized and do your part.
Go to: www.TheAmericanStatesAssembly.net.
Labels: Anna von Reitz, For the Military

redpajama_set_name: RedPajamaCommonCrawl


text:
Try the Design Systems ROI Calculator
DesignersDevelopersProduct ManagersUX Writers
BlogYouTubeHelp DocsRoadmapPodcastROI Calculator
PricingBlogHelp
Design Tokens
Vojtech Miksu from Uber: Next-gen tooling for developers
Vojtech Miksu (Software Engineer at Uber) and Evan Lovely (Chief Architect at Knapsack) join Chris to discuss the gap between a frontend developer's code base and what actually gets shipped, the next-gen tool (Ladle) Vojtech created to address this, and ultimately helping developers get closer to what end users experience.
Chris Strahl:
Hi, and welcome to the Design Systems Podcast. This podcast is about the place where design and development overlap. We talk with experts to get their point of view about trends in design, code and how it relates to the world around us. As always, this podcast is brought to you by Knapsack. Check us out at knapsack.cloud. If you want to get in touch with the show, ask some questions, or generally tell us what you think, go ahead and tweet us at the DS pod, we'd love to hear from you.
Hey everybody. This is Chris with the Design Systems Podcast. Today, we're going to do something a little bit different. We have a lot of these conversations that tend to be about how we implement design systems or stories about the design side or stories about collaboration. We wanted to do an episode that was focused on tooling, and we ran across this really interesting article about Ladle, which is this open source project that is very similar to Storybook in how it visualizes components. And it really got us thinking about one particular phrase in it. What is the next gen tooling for front end? And so we looked up Vojtech who happens to work at Uber, and we have him here today on the podcast to talk with Evan Lovely, the chief architect at Knapsack. So, Vojtech, welcome. Really glad you're here. Thanks so much for joining us.
Vojtech Miksu:
Yeah, thanks for inviting me.
And hey, Evan. Glad to see you too.
Evan Lovely:
It's great to be on. Thanks for having us.
Awesome. So we wanted to jump off the conversation today at sort of a question. When we think about what the tooling is right now, like that state of tooling, that understanding of the meaning of that tooling, and you guys said something sort of before the show that I thought was really interesting as an important aspect of modern tooling or next gen tooling, and that is this idea of a focus on realtime feedback for developers. So maybe take me through what you mean by the current state of the tooling and why that realtime feedback really matters.
Yeah. So there's been always a big gap between your code base and what you actually ship into the browser. And this just creates this longer loop and that kind of disconnects you from the experience of developing and debugging. So if you can remove like some of the stuff that happens between your code base and the browser, we can make this loop much faster and that's just better experience because anytime you make a change, you don't have to really wait for the tools to pick it up.
Yeah, it's interesting. Because I think that's also what design systems are about is making it so the feedback cycle is quicker because when you make a component, you'd also traditionally have to implement it in the application before you could actually see it on a website somewhere, which is where somebody would be actually experiencing it.
So is this related to not having to think about like running through a build process? Is this about that time gap between like I wrote this line of code and I can see what this line of code produces visually, where's that real disconnect from real time to async that you guys are talking about?
Applications are getting more complex and just bigger. And usually as they go bigger, they just go slower. Right? So sometimes to spin them up, it just can take minutes. And then to make even incremental changes can take 10 or 20 seconds and it just gets worse. As the application gets bigger and bigger, it usually gets slower. So we need like some different tooling that's able to solve this issue so the development cycle doesn't get slower with the application. It should not matter how big is your application, you should always get similar experience. So I think that's the biggest difference between the older tooling and the new generation tooling.
Gotcha. So in the old model, as the application code base gets bigger and bigger and bigger, the ability to make change to that application slows down. And moreover there's all this tooling that is around that application, like testing comes to mind or any sort of feedback tooling that also summarily has that same sort of slow down effect. And it overall has this big effect on the speed and agility of development.
Yeah. If you want to be a specific, the biggest or the most expensive part is bundling. So it's kind of the process of picking up all your files or your modules and just creating something digestible for the browser. And that just takes more and more time as the code base grows because you need to now look through all these modules and combine them together into these bundles. And that just makes all the tooling slower, including the application and the testing. And there's now a shift to start using tools that don't do this part. They just completely skip the bundling and they just let browser to do what browsers are really good at. And that's just requesting modules and being able to catch them and just speed things up.
And it's kind of really like the browsers have finally gotten good enough and, more specifically, they've got an update cycle that happens automatically. With internet Explorer 11 finally, finally going away all those years ago we ended up with browsers that will self update every six weeks or so. And so, we can feel confident that our users have got a more modern browser, which can handle what the tools used to have to do.
So this is a lot of shifts from tooling that was before you got to the browser, the tooling actually happens in the browser. And so when we think about what a next gen web tool is, you're trying to take advantage of a lot of the capabilities that a web browser offers you that before you had to stuff into the tool. And that overall helps with the bundling you guys talked about and generally makes the application more performant now in a way that isn't as intimately tied to the size of the app.
Yeah, correct. Historically we didn't have a good way how to encapsulate code in JavaScript for browsers and how to load the code into browsers. And then the Node.js came and they had to solve this with CommonJS, which didn't work in browsers. So we still didn't have a good way for browsers how to load JavaScript, so we built all this tooling that's able to take the CommonJS code from Node.js and turn it into something digestible for browsers. But then recently we got ES modules which try to solve this issue and they just offer this mechanism for both browser and node to load and execute code, and we don't need this tooling anymore that does all the bundling and compilation.
So these modern pieces really are about performance. Are they about feedback? What is it that is the core of the value beyond just the speed?
Performance is a big part. But I think it's also just kind of removing some of the obscurity. Because when you take your code base and just turned into one giant file, it's much harder to reason about it. Right? It's like something that you didn't create. It's something that the tool created. If you let browser to download your modules one by one, you can just go to your network tab and you can directly browse all these modules you wrote, you can search through them and it's much easier to understand what's happening in your application. So it's both performance, but also it's, I would say it's easier to debug it. And sure we have tools like source maps, but they are not always great. Sometimes they break, they definitely slow down builds. It's kind of like a workaround for the issue we had with bundling, but now we need to do less and less transformations. So that just improves debugging part of the developer experience.
When you think about that, it lends me to this idea of when I'm making a change and I want to understand how that alters production, it seems like you have a much clearer traceability to that. Right? So I know that I'm making this change over here. I have this idea that there is a scope for that change that is within that particular module or within that particular part of the application I'm working on that no longer affects like this broader system. Is that also correct? And when you think about how I observe real time change and what I'm working on.
Yeah, that's correct. We still do some bundling even with this new generation of tools, especially for production, but in the future we might be able just to skip the bundling, even for production applications. Technologies like HTTP/2 and HTTP/3, it's not as expensive to fire up a lot of HTTP requests so we can get much simpler applications even in the production mode. And that's definitely going to help to debug problems in production as well. Like today, if your production is broken, good luck with debugging, you just get this giant file full of one character variables like heavily optimized and you have no idea what's going inside. Right?
Yeah. I think that it's, what you get is you are a lot closer to what is experienced by the end user, and it's about removing layers of abstraction. You said something about, hey, this is the code that I wrote, and then being able to take a look in the browser and seeing your code being ran. When you're looking at bundled code, it doesn't feel like it's your code. And so being able to be one step closer to what users are actually experiencing in the medium it's destined for in a browser helps a lot.
Yeah. And this is where it kind of starts to relate back to design systems, right. Because if I'm looking at that card or that button or that hero, whatever component is that I'm looking at, and I'm looking at that in a system that is attempting to look as much like my production environment as possible to the point that it is literally the thing that I'm testing or working with should be the exact same thing that is in my production environment. It's tools like this that help us bridge that gap.
Yeah, for sure. And if you think about this, this is how the JavaScript also started, right? You were just able to open an HTML file and type some JavaScript into it and run it and you could see it in the browser. You didn't need any tooling to modify your JavaScript code. You didn't need any bundling. It was very simple and nice for it, and it was very inviting for newcomers to use, but over time it just started developing these very interactive and giant applications and we needed to invent all this tooling to make it work. But now we are kind of going back to the roots and we are just able to let browsers do a lot of this work and to make it work even for these more complicated applications. So we can, again, just start modifying files and see them in the browser without all the obfuscation and bundling and all that stuff.
And having things like that can really help newcomers quite a bit. Many developers have learned by looking at the source code of a site. And I think that can really also help out designers or anybody who wants to kind of dip their toe into things because usually you start out coding by editing somebody else's code as opposed to writing your own from the ground up.
Yeah, for sure. Something special about web, right, and how open it is, I can just go to any website and kind of copy, paste and steal their code and just run it for myself, modify it, play with it. That's not possible with iOS or Android native development where it's much harder. And I remember it was pretty controversial back like 10 years ago when you start using all this bundling and minification, and some people very kind of upset about this, like we are losing this part of the web and it's so open that anyone can just open the source tab and just change things and see how it works. We kind of lost that in the process, but maybe now we can just reclaim part of it back.
That is really interesting because when I was doing more engineering and more web development, I always thought about, I want to be able to understand the impact that the code I'm writing is making on the thing I'm building. And there was a really clear straight line to that. I mean the last time I wrote code professionally, it's like 2011 at this point or something ridiculous. And so when I think about that and that sort of straight line impact of being able to observe that thing, I do think about when I look at modern web applications and the very arcane nature of the code that I look at now.
And so what I think that you guys are alluding to is a future state where maybe that first reality is present again, because all that reason for doing the bundling, the obfuscation, the minification of the stuff that we're putting in our applications, the reasoning for that goes away. And I kind of want to understand a little bit more about that, right? Like what exactly is a browser doing differently now that allows us to not care about those things anymore?
Well, before, a JavaScript file had to be all in one file. I think the first JavaScript tools just took several JavaScript files and then stuck them together one on top of the other to load. And so when you're all kind of in one file you have what's referred to as global scope. And so if you say variable name time, nothing else can use that same variable name. And once you start using libraries, it gets almost impossible to not step on each other's toes.
Yeah, exactly. And now we finally have ES manuals, which solve this issue, and we have much better way how to load code, how to make sure the code is encapsulated, it's in modules, it doesn't conflict with the global scope, just all the good stuff that other languages always had. We finally also have it in the browser. So that's kind of like the new change, the new shift that's happening right now.
So shifting it over to tools and thinking about Ladle and thinking about these ES modules, webpack alternatives type script, et cetera. When we think about this modern tool set, if we're no longer trying to do this bundling, we're no longer trying to put everything in the same space, what are these tools solving that's different than the tools that came before? What makes them really next generation?
Yeah. So for example, with webpack, when you start webpack and try to run your application, it needs to do all this work, it needs to go through every single file in your code base and create this bundle, and then it starts the server and serves you this bundle. And this can take a long time. It depends how big your application is. Vite is like very different. Vite just starts the dev server immediately. It serves you the index HTML page and then it uses browser to download these ES modules on demand as it goes. Right? So now the browser is pretty much discovering your code base and loads only what's needed. And Vite does some compilation, like for example, you need to get to remove type script types or JSX from React. Vite doesn't do any bundling or very little bundling, and it just gives you the webpage, the web application immediately and lets the browser resolve all these imports.
Gotcha. So this is enabling you to be, I guess, a little bit more dynamic about how you think about how the code is enabled or used inside of an application. And that's ultimately what leads to better performance or is it something even more than that?
So the performance is the biggest difference, right? When I just hit my command to start developing, I can see the browser opening the application immediately. With webpack I sometimes have to wait like a minutes before the browser spins up and I can start working. The performance is definitely the central part, but then also in the browser you're not getting any bundles, the browser downloads each module individually. So you can just open your request and you can see how your application looks like. You can see the files you had in your code base. You can see them in the browser. There's no bundling in between.
And also caching is a lot better as well, because let's say there is hundred modules and somebody opens the page and loads them. Then later you ship an update that changes two of those modules with the old build tools, you would have to redownload all 100. And with the new tools, they can cache the other 98 and only download the two that have changed.
Yeah, exactly. And in past we had some very complicated ways on how to split one big bundle into couple small bundles, just trying to decide what should be cached for longer time versus for shorter time. And that's kind of bad. If every application ships its own React and it's inside of this giant bundle, that means you are keep downloading React every single time. There are some proposals to maybe build some global cache inside of browsers for popular libraries, which actually kind of seems as a bad approach as well because it introduces all the problems. But the approach with ES modules is just like, caching is way more granular so you are just caching each individual module instead of trying to create these bundles. So for sure caching is much easier and more efficient this way.
Interesting. So help me understand how this relates to the work that we do in Design Systems, in particular the coding work here. When I think about an engineer working on components or working on assembling an experience based on those components, what does this change about my workflow?
Yeah. So again, it makes it much faster. If you're building a component library, you probably use to do like a storybook. As your library gets bigger and bigger, you just need to keep adding more and more stories. And again, that means more and more work that a tool like webpack has to do before it can spin up, it needs to do more work before it can send you an incremental change. So it just makes your whole developer cycle slower. With Vite or Ladle, this kind of goes away because it doesn't matter how many more components you are adding, it always kind of guarantees the startup time is instant and it only downloads and shows you the component you are currently working with. It doesn't have to really go through the whole code base before it does the thing. It definitely also scales much better.
Specific to your problem at Uber. One of the things that was hard about the system that you had is you guys do a whole bunch of stuff that is external after that component gets built, that is associated with testing, that is associated with all of these other aspects of the engineering cycle that ultimately would require you to rebuild your application over and over and over again. And so that performance hit was multiplied over many different tools. Is that right?
Yeah. Correct. Hundreds of projects. Because the build part is just the first step, right? Once you build your component library or your Ladle instance, only after that, you can run all these tests. So you always wait for the build to finish first. So that just kind of slows down everything down the pipe.
So talk to me about some of the testing that you run.
Yeah. So we run multiple types of testing. One of them is visual snapshot testing. So what we do, we take your Storybook, or now Ladle, and just visit every single page and take a screenshot. And we do this without you, as a developer, you don't need to do anything, we just do it automatically on our servers. So as long as you are developing your components inside of a Storybook or Ladle, you just get this coverage. So that's one important part of our tooling. We also do accessibility testing. We run a X to just check for accessibility issues. And we have additional tooling for interaction testing so you can just write these short snippets for selected stories and you can run tests like click on this button and assert that some value changed to something else. So we try to build additional tooling around Ladle or Storybook, but a lot of it is just automated. So you, as a developer, you don't need to do anything and your components are already covered by visual snapshot testing, which is really nice.
Interesting. So one of the promises of Design Systems is that it represents what users will actually experience. And so that's over in production and another web app, and there's more build tools there. So how do you make sure that when you build out your design system using some tools and then later there is the web application or website that takes those same components and then uses some different build tools that the results are the same and we know what our users are experiencing and testing?
Yeah. So we don't take visual snapshots only for these stories. We also take them for production applications, but that's much harder because, first of all, it can't be automated, because we can't just kind of find every page and every state of your application and take a screenshot. It's something you have to tell us. And also these applications are way more complicated. They do a lot of network requests. They are very flaky. They can just break in so many ways if you try to run them in your CI. So we have these tests as well, but there are always just very few of them and we can automate it as well.
But when it comes to testing, I think visual testing is really the most important one when it comes to the user experience. We had these all other types of tests, like we did just snapshots, which tries to compare the HTML output, the HTML dam, but that doesn't really tell you like if the component looks okay and if it breaks, when it breaks, you don't even know like, is this serious or not. People just always glance over it and they don't even know what's happening. So I think using visual snapshots is really good way how to test your components.
Yeah. That's a lot of what we have experienced as well is that it is a lot easier to test in a design system than it is in a production application. You're able to see a page with just a button on it and can make sure that works as opposed to trying to go and take a picture of your homepage and make sure that not a single pixel has changed because those tests always produce false negative. There's always going to be a pixel off on a homepage. So you learn to not trust them.
Yeah. Also would be, so you say you have like a button and it's easy to test it. We see our developers sometimes create these stories that are essentially full pages. So they're trying to recreate like bigger parts of the app inside of stories because they'll have all this automation and tooling around it. Maybe some developers spend even more time developing in inside of Storybook and Ladle than compared to the production application because they just get all this testing for free. So that's also something that might change. We might have these just two equally important development environments, one that's your application and then another one that's using this concept of stories to split your application into small parts. It's easier to test and automate.
That's been an interesting thing. That's been a really important part of Knapsack that we were thinking of early on is the ability to take a bunch of components and sort of assemble it into a full experience because nobody in user land use a component in isolation, people are always viewing sets of components that ultimately represent an assembled experience. Thinking about that through the lens of testing is an interesting idea where if you had a bunch of sample pages that were created with the design system, you'd be able to test those full experiences instead of just those individual patterns in isolation.
Yeah. And that's what we saw too. People trying to create these bigger parts of application inside of stories instead of just using stories for very atomic pieces of the UI.
So the thing I'm curious about is should Design Systems ship build tools? Because the problem I see is that in a design system, we are building our components and then doing a lot of testing there, which is supposed to give us faith that it's going to be fine in the end. But then in production for the web app, we build things again, which has a possibility of being a little different, especially if those build tools are very different. And so design systems are supposed to be collections of reusable solutions. And I view those not just as like reusable buttons and cards, but also things that help solve problems, like build tools. I'd like to hear some of your thoughts on that.
Yeah. I agree. When I started at Uber, I was working a hundred percent of the component library and design system. And after some time you realize like that's not enough, you also need to provide some tooling and we need to make it easier to use all these components in your application. Over time you actually transition into this role to also build supportive tooling, like Ladle, the tooling for testing, for visual snapshot testing. So we were also just interested to see how developers are using our components. When you take screenshots, you can just kind of directly index all these use cases and see what they do. We also build this tooling that analyzes code base, and we were just searching for a code snippets, how people are using our components, what properties are they customizing. So we were always very interested into like how our components are being used. So I think it's not just enough to create a component library and hope for the best, you also need to closely follow what developers do with your components.
When you were talking about all of the automation that comes along with your design system as well, I was framing in my mind like that's actually a part of the design system that's on top of the components, that's on top of all this other stuff. Right? There's an infrastructure piece to this that ships along with the design system that provides a lot of that powerful automation and a lot of value to your engineering team. I think that's a really cool way of thinking about it is like, it's more than just the component library.
Yeah. And a lot of this tooling we built first for our component library, like visual snapshot testing, we've been using that since the beginning. And then we saw the value of it and we also wanted to bring it to developers so they can use it in their applications, in their stories. So yeah, all of the tooling was built for the component library, but then we also made it more robust so it can be used across all the applications.
If there's an engineer that's listening to this that thinks about like, hey, you're living in that next generation, you're living in that promise land, what do you see as the transition that most people have to go through to get to where you guys are at? When it comes to you all and your modern stack and doing something like building Ladle, where does that transition really happen? Where does that start and what does that feel like?
Yeah. So first of all, we are not there yet. Not even close. We are also in this transition and it's going to be a long transition. I think with ES modules, it's almost like Python 2 versus Python 3 migration. It might never be really fully done. And we talk about a lot of benefits here, but there are also a lot of painful points with ES modules. And I think it's going to take years to actually fully adapt them in the ecosystem. So, that transition needs definitely a lot of changes in terms of tooling. And it's not just bundler, even the tools for testing, they don't always work with ES modules correctly. So you need to kind of change all the tooling. You need to change all the libraries. Everything that's on npm needs to at some point embrace ES modules. So there are a lot of changes we have to make as an ecosystem. And that's going to take a long time.
And when you think about the scope of those changes, we've talked a lot about like the JavaScript side of it. Is there other pieces of this, too, that also represent that next gen tooling?
It's not only about ES modules and the tools that skip bundling. There's also this like a new shift in the way how this tooling is built. People realized JavaScript is not always the fastest language. They start to utilizing languages like Rust or Go. So you have this generation of tools like esbuild or Speedy Web Compiler that can just make your application way faster, even in today's paradigm. So you can still keep using webpack and bundling, but if you can make this underlying compilation like 10 times or a 100 times faster, it can also give you a great performance boost. So I think there are like two different directions and they are complimentary and they're both difficult in different ways, but I think in that future, we might be this ideal promised land when we use ES modules and or outdoing is written in Rust and it's extremely fast. So that might be the future in like five years.
When I think about the vision and I think about you sitting down to construct Ladle, I mean, obviously there was more than just you involved in that conversation, that decision, what was the original thought about why you built that?
Yeah, so it kind of started as a prototype. We saw some of our story books at Uber got really big. Some teams, they just created hundreds of stories and it got very slow. They start complaining like, hey, when I try to start this up it just takes minutes, when I make a change it takes like 50 seconds. Like, can we do something about it? And we kind of start digging into it, like, why is this so slow and like, what's the slowest part of it? And that's when we started looking into different build tools like Vite, and we just saw a big opportunity how to improve this. And we just decided, hey, let's just try these new bundlers and start to prototyping a new solution. So I actually tried a couple different tools, like [inaudible 00:28:58] 2, Snowpack, and then finally we landed on Vite, but it was just kind of a discovery phase, trying to use all these different tools and see like, what are the benefits? What are the drawbacks? Is it something we could use?
Once you settled on the build tool that you wanted kind of at the core of your Storybook replacement, how hard was the lift to be able to implement the pieces of it that you wanted?
I would say it was surprisingly easy because the tool itself, the webpack or Vite, actually does all the hard part, all the heavy lifting. Right? So you don't need to build that much around it because the essential parts that need to be done, like serve your application, go for your code base, all that good stuff, that's already being implemented by Vite or webpacks. So you don't need that much to build around these tools.
That's awesome. I think that it's pretty easy to look at all of the tools out there and think that they are so hard to replace or so perfectly done when really, basically with this big open source world, we just are continuously standing on each other's shoulders and pushing each other to be a little bit better. It's great to be able to not get comfortable with everything being already done.
Yeah. And we are always in the cycle when you create a tool, it gets adoption, people start asking for more features. So the tools grows over time and then it gets bigger and slower and it's much harder to steer it or change it in a bigger way. So somebody else comes and creates another tool that's much smaller, it doesn't have all these features, but it can be much faster. And then again, it grows over the time and kind of like a never ending cycle of open source and the libraries spheres.
Yeah. Yeah. Cue the Lion King music and the circle of life and everything like that.
Yeah. And we can also just help each other to improve. It's much easier just to create a new tool when you try to prototype with ES modules and Vite than trying to change existing tool that's being used already by thousands of developers. It doesn't mean it needs to be a fierce competition. It's more like, hey, this is a prototype of something new, and maybe there are some lessons you could take from this. And you can even see there is now a Vite builder for Storybook. So this might also just kind of help to prove that Vite is something that's viable for Storybook as a concept, and it can bring you all this performance. Maybe you should try it too.
If you could wave a magic wand and add any feature to Ladle, what would you add that would help out your teams?
Specifically for my teams, we are pretty much feature complete in terms of what we wanted to build. One of the things is like interaction testing, make it easier to run tests and see the feedback inside of your browser instead of run it in your terminal and see the output there, because these tests run in browser on real components and they do actions like clicking and typing. So it'd be kind of cool to see it real time and just getting all this feedback in your browser. And maybe even developing these tests in the browser. We used to have these ways with Selenium when you could click around, you could record it, you could replay it. And the premise was like, hey, this is something even like product managers could use to write tests. It never really happened, and it's always up to developers to write these tests. So it's always something I'm thinking about like, is this possible, like, could we do this in the future? So that might be one big thing I would like to see.
Yeah. I definitely see that as an important future. The idea that you can democratize some of that work, right? That idea of like, what does interaction testing look like? Or what is it that I want to see, or my intent in an app.
Yeah. And we also had these natural languages to write these tests. So you could just write like English sentences and it would run these tests based on them, but I've never seen it working. It always came back to developers and writing some JavaScript. Hopefully in the future, it's going to get easier.
Yeah. Bringing in more members of the team. Right? It takes a village to be able to build all these things. And especially in the realm of testing, if the people who were asking for these components to get built, the designers and the product managers, if they could basically say, I want a button that when I click the dropdown menu, I can see menu items below it, then that's going to help the engineer build to that spec. And then also it's going to make sure that it ends up doing what it's supposed to do. And then also, as time marches on and the code continues to change, that the component continues to still function that way. It's the great thing about tests.
Yeah, for sure. And yeah, just in general, always trying to close this gap between product owners, designers and developers is really important.
So what struck me by a part of your story was thinking about some of the parallels of when Evan and I were thinking about Knapsack in the early days. When we were an agency and we were building design systems for large enterprises, fully custom, one of the tools that we reached for pretty frequently was Pattern Lab, which is fairly similar to Storybook in its implementation. And ultimately this sort of same thing played out where we found that Pattern Lab for a variety of reasons wasn't really meeting our needs. And so we looked at different tooling. I think there's an interesting sort of analogous story here.
Yeah. Pattern Lab served purpose for us very well for a long time, but we ended up starting to hit some of the walls. And one reason why we were using Pattern Lab is because we would be building for languages that need to be rendered server-side, and Pattern Lab works well with that. It wasn't about React, basically. And some of our clients needed to be able to have server-side rendered components, but then also React and view. So we ended up having these needs of something has to be able to be rendered server-side, but also they had a couple different template languages and wanted to demonstrate their design system with that all under one roof. And then the other final missing piece, of course, was adding documentation. The only way to really add documentation in Pattern Lab and older versions of Storybook was to just write out the HTML in some component that showed that. And that was really unapproachable by some of the other non-technical contributors.
I love the parallels here between kind of thinking about what old tech or legacy tech looks like relative to modern tools, relative to next gen tools. Vojtech, I just want to say, I really appreciate you telling your story. This has been awesome. Do you have any final thoughts you'd like to leave us with?
Yeah, thanks for bringing me here. Final thoughts. You should look into these new tools like Vite. Read through documentation. They have really good description of how it works, what's changing. Give them a try. If you see your applications are not performing well, maybe this is something you could use. And it's kind of like a paradigm shift, but it's very interesting and I'm just encouraging everyone to read through it.
We'll make sure we link that along with a few of the other projects we talked about in the show notes. But again, just wanted to say thank you. Also, Evan, thanks for co-hosting with me on this one, definitely helped me get a little outside of my own technical depth. I really appreciate y'all.
Thanks so much for your time, Vojtech. It's great being on the show, Chris.
That's all for today. This has been another episode of the Design Systems podcast. Thanks for listening. If you have any questions or a topic you'd like to know more about, find us on Twitter @TheDSPod, we'd love to hear from you with show ideas, recommendations, questions, or comments. As always, this pod is brought to you by Knapsack. You can check us out at knapsack.cloud. Have a great day.
Watch Demo (5 Min)Contact Sales
See how Knapsack helps you reach your design system goals.
See how Knapsack makes design system management easy.
The Design Systems Podcast reaches 100K listens
Evan Lovely, Chris Bloom, Jake Love, and Brittany Smart from Knapsack: Hot Takes on the State of Design Systems
Stephen Gates: What makes a good design leader?
Design once, build once, use everywhere.
Subscribe for design system tips and inspiration
CareersPartnersTerms of ServiceSecurityPrivacy
SolutionsPricingDocsUser Guidesvs Storybookvs Zeroheight
BlogReportsROI CalculatorPodcastHelpContact us
©2023 Knapsack Company. All rights reserved.


HCM CITY — Investors are flocking into the bubble tea market since demand is booming across the country.
In large cities like HCM City and Hà Nội, it is easy to find bubble tea stores belonging to major brands like Alley, Gongcha, Phúc Long, Ten Ren, and Royaltea.
A spokesperson for a famous brand name, Gong Cha, said: "Competition in bubble tea market in Việt Nam is a marathon.
Brand expert Võ Văn Quang was quoted as saying by Người Lao Động (The Labourer) newspaper that the popular drink in Hong Kong and Taiwan has undergone many changes in the Vietnamese market with many toppings to match Vietnamese tastes.
Most of the milk tea brands have come to Việt Nam as franchises, he said.
Dr Đào Duy Khương, a retail expert, said milk tea, unlike coffee and tea, targets youths in big cities, and this demographic's consumption behaviour is trendy meaning investors should change their offerings frequently.


Do you require a minimum amount of days to book for after-school and Holiday Schemes?
Yes a minimum of Two day booking required.
For Events and Holiday Schemes the deposit will be added against your final invoice. However in the event of cancellation the deposit will be non refundable.
Deposits need to be paid as soon as registration form is filled to secure your child's space.
£40 for Homework Dance and Drama Club.
Account name: KidsZone Adventures Sort code: 30-96-26 Account no: 47301968. REF child's name and surname initial.
Do you take Childcare vouchers and Tax Credits ?
If your Childcare voucher provider isn't named on this list please contact us ASAP so we can register with them.
When will I receive my invoice and how do I pay?
KidsZone Adventures invoice parents after each half term via email you will receive an invoice within the first 5 days of the new term. (Please enquire if not received). You will have a 14 day period in which to settle the invoice.
An annual booking fee of £20 for admin fee is charged in September or January (please check club location) for Ofsted Registration and insurance.
KidsZone Adventures accept cheques, bank transfer, direct debit and PayPal which is connected to the invoices.
Do I receive discounts or promotions for using other Kids Zone Adventures Services?
1) We offer a referral fee of £15 off your invoice.
2) During the holiday when promotions are on.
3)10% Sibling discount based on 2 days minimum.


text: {{OUTPUT_REL}} = {{INPUT_REL}}.Distinct();

redpajama_set_name: RedPajamaGithub


We have monthly Clinics at all locations!
Self service dog wash services are available for you and your pet at all Pet Station locations!
Don't worry about forgetting Fido's or Kitty's food this week! Get pet food delivered to you weekly, monthly, or in the time frame of your choice. Set a custom delivery schedule and save a few bucks as well.


text:
One Chance biography - all about One Chance
One Chance pictures
One Chance biography
One Chance songs
One Chance albums
For Courtney, Jon, Michael and Rob, One Chance is the perfect name for a foursome that has invested their heart and soul into their musical dreams and now stands on the verge of savoring the fruits of their labor.
"This name really suits us," says Jon Gordon, 22. "One Chance means we only have one life, this is our one dream and we've only got one chance to do it. We feel like all we need is one chance for people to hear us and they'll love us."
Bound by their love of music and their undeniable talent, these four Chicago natives came together six years ago and overcame all the obstacles that littered their road to success. After a few detours and more than a few roadblocks, the guys found themselves face to face with the biggest R&B superstar in the world and, much to their delight, he liked what he saw. "We got the opportunity to showcase for Usher," Jon recalls. "He could tell that we were already polished. We had been working so hard for so long and it must have shown on stage because we were chosen by Usher over several other acts that showcased for him and his staff that day."
Under Usher's tutelage, the diligent task of developing One Chance as only Usher could, quickly ensued. After countless rehearsals and vocal training, the group presented their more finessed stage show on both the Scream [?] and Up Close & Personal tours, and garnered a legion of fans in the process. The multi-platinum, Grammy-winning artist said he saw reflections of himself in the group. "As an artist, I know what it takes to be successful," Usher says. "I know what it takes to make a mark and have longevity. I had no doubt that these guys have what it takes to not only live up to the great R&B legends of the past, but to have the same kind of respect and longevity that many of those greats still enjoy today."
There's no question that One Chance is next in a long lineage of great R&B male groups. "We got a mean swagger," says 23-year-old Courtney Vantrease, describing the group's uniqueness. "It's a Chicago swagger but it's real and we've got things that you will remember from previous groups, like little things you might remember from Jodeci and Boyz II Men."
Jon adds, "One thing that will set us apart from other groups is that most of them are missing something. Some of them can dance but aren't that strong vocally or maybe they can sing but they're not solid entertainers but with this group we cover the whole spectrum. We're not trying to be something we're not. We can sing. For real! Take away all the music, all the beats, you can even take away the microphones and you will hear natural voices blending in harmony."
Hearing them sing 'for real' is the treat listeners get when they lend an ear to any of the songs featured on the group's debut CD.
The group's introductory single, "Look At Her," featuring D4L's Fabo, served a refreshing new style called Snap & B. "It was something new we were trying," explains Courtney. "I think we were probably the first guy group to do it. The snap movement was really strong so we just decided to incorporate some R&B into it. It's just all about giving people something fresh." Produced by Chocolate Star and Soundz, the song conjured up images of a club scene and a group of men eyeing a special lady who has captivated them with her sexy dance moves.
While the irresistible Snap & B sound resurfaces on the smoothed out single "U Can't," featuring Young Joc and produced by Drummer Boy, it's the beautiful Mr. Bangladesh-produced ballad "Emotional," that showcases the group's vocals. Notes member Rob Brent, 21, "I think it's one of our hottest songs and it shows the versatility of the group." Adds Jon, "The song is about a guy whose girl is about to leave him and he doesn't know what to do so he runs after her and becomes very emotional."
The group's music creates various nuances. The songs are alternately bright and fun and dark and pensive. "We have some really bright voices. We have a couple of dark records but for the most part the album has a young feel. Youthful but not too young and not too old either. It's right down the middle." Adds Jon's brother Mic, 23, "Some of the songs address situations that young people are going through in relationships and in life in general."
Just as their songs run the gamut of styles and emotions, the personalities of the group's members and the talent they possess cover all the bases. "Rob is the young guy with the non-stop dancing, the popping and locking all over the stage," offers Jon. "He has the spunk and a voice that sounds like he's got auto tune on it. He's the guy that likes to riff and run you down the street."
"Jon's the spokesman of the group," says Courtney. "He's the gel that keeps everything together. He keeps our business tight, keeps us practicing and on stage he's the improviser and the one in the group who has the most hip hop flavor."
"Courtney is the quiet, smooth entertainer," chimes in Rob. "He's young but grown and sexy too. Out of all of us he has that in-between look that can go in either direction." "And Mic is that sexy, fly dude," notes Courtney. "Mic is the one that'll take his shirt off on stage and go wild. He's like Jekyll and Hyde."
The mutual love and respect that the members of One Chance have for each other have sustained them through some very trying times over the years, times that often found them chasing down one elusive opportunity after another. "It's been a real rough grind," recalls Courtney. "We left home, sold CDs to rent a van to go to New York and went to different record labels to perform. We all stayed in one hotel room or when we didn't have enough money we all slept in the van." Undaunted, the group packed up the Gordon brothers' not-too-dependable van and hit the road to Atlanta for Usher's showcase. "Even after going through ups and downs we took it upon ourselves to drive down to Atlanta where we slept on the floor in a cold studio, going daily without eating. It's been a struggle but we've gotta say, it's been a blessing and it allows us to appreciate everything that's going to come to us even more."
The rest of the group shares Jon's philosophical perspective: "The struggles that we had before have prepared us for the struggles that are yet to come," says Mic. "Through it all we didn't give up. We stayed together. We used to be sitting up on a couch in a studio, side by side sleeping with our feet propped up on a chair. A lot of people wouldn't have come this far. They would have given up. We have the chance of a lifetime to do what we love to do – to sing and entertain and allow people to hear our story."
And it's a chance that they're more than ready to take.
Similar Biographies
Atozzio biography
Dontae biography
Johnta Austin biography
Claude Kelly biography
Casely biography
Lee Carr biography
Jackie Boyz biography


Co-founder of Energized Work, a consultancy and software development shop, Gus Power has over 10 years experience in software development across a wide range of domains. He brings together systems-level thinking with an uncompromising test-driven approach.
In his spare time Gus can usually be found on a train, working on Grails plugins, doing various linux-y type stuff or putting together some blog entry he'll probably never post. When on terra-firma you'll probably find him enjoying a quiet pint somewhere, immersed in some Wii game or playing a few tunes on his gee-tar.


text:
India Markets open in 8 hrs 6 mins
How young women like Yara Shahidi are helping Barbie stay relevant
Natalie Mayrath
Producer/Reporter
Yahoo Finance 18 March 2019
Since Barbie was "born" in 1959, she's been busting through ceilings, be they glass or plastic. She was created for women by a woman, the legendary Ruth Handler, who ran Mattel when barely a glimpse of women existed in business leadership.
So for Barbie's 60th anniversary, it's no surprise she went big, honoring an unprecedented 20 role models from 18 countries across the globe in an effort to represent and honor diversity, and reinforce the Barbie brand's mission to show young girls that they can actually be anything they imagine.
"Grownish" star and activist Yara Shahidi, whose likeness was tapped in the latest installment of Barbie "Sheroes" (alongside the likes of Naomi Osaka and Adwoa Aboah), saw that possibility in the toys she grew up with, including her own Barbies.
"My parents were really intentional, so a lot of brown Barbies in my life… my toys, my media, my books all reinforced this idea of anything being possible within my world and within my potential," she says.
Shahidi points out that Barbie's significance and staying power go deeper than just a visual reflection. "I think Barbie as a brand has represented our evolution almost as a country," she says. "We've come a long way in that when you look at the history of women's suffrage, especially as you get into the facts of when Native American women were allowed to vote or when black women are allowed to vote, you get into women's rights in the workplace and the rules that are being passed -- these are all things that contribute to us having a freer space as women of this generation."
Mattel, which also sells Fisher-Price toys, Hot Wheels toys and American Girl Dolls, has seen 5 consecutive quarters of growth, which could be riding on the relevancy of Barbie's messaging for women of the world. Lisa McKnight, SVP and Global Head of Barbie for Mattel, says "the secret to the success of Barbie is she's continued to reflect culture and the world girls see around them."
Both Shahidi and Barbie share a passion for the importance of role models and mentors in girls' lives. According to Mentoring.org, young girls who have a mentor starting as early as high school are 130% more likely to take on leadership positions throughout their careers.
Studies show that girls can develop limiting self-beliefs and lack of confidence as early as age 5.
With its Barbie Dream Gap Project Fund Mattel aims to raise awareness around limiting factors that prevent girls from reaching their full potential.
Shahidi, who who counts Michelle Obama as one of her mentors, provides mentorship opportunities to young women in New York City high schools through her non-profit, Yara's Club. She hopes her work will give future generations confidence.
"We have been given messages that say we have to change ourselves to fit in," she says. "Be yourself and let the world catch up."
In addition to its latest installment of role models, Mattel also launched a 60th Anniversary doll collection celebrating six careers that have been in the Barbie line from the beginning, but are still underrepresented by women, including astronaut, pilot, athlete, journalist, politician and firefighter.
• Girls Who Code founder: 'I surround myself with rejection'
• How to stop bias against mothers in the workplace
• The business world still has a female leadership problem


With the right supplier on your side, today's advanced centrifugal casting techniques provide optimal results for a multitude of energy and power generation components.
Spuncast works with companies in conventional coal-fired power, hydroelectric power, concentrated solar power (CSP), wind power and other segments to deliver centrifugally cast parts with high performance characteristics, often at lower costs than forging.
Spuncast centrifugal castings for turbine components meet the Westinghouse casting specification while saving costs.
Tough parts such as wicket gate bushings can help shorten scheduled downtime for routine hydro-turbine maintenance.


text:
Platform work at 16th Street may cause minor delays
Beginning Thursday, September 7, there may be some minor train service delays while BART replaces yellow and black detection tiles on the edge of the platform at the 16th St. Mission Station. The work will take approximately four weeks to complete.
The work will take place Monday through Friday from 8 p.m. to 4 a.m. and weekends from 8 p.m. to 6 a.m. During these hours, there may be train delays of to five minutes. BART recommends that customers adjust their travel plans accordingly. Please watch your step when entering and exiting the trains because the platform edges may be uneven. BART will post directional signs to assist you as you use the station and BART will keep you informed of any changes through passenger bulletins and station announcements.
We regret any inconvenience this necessary work may cause and thank you for your patience.


text:
Quad shows we're not alone in China pushback
Beijing's targeting of Australia for geo-politicised trade punishment is counter-productively encouraging collective pushback from the region.
Mar 14, 2021 – 5.01pm
Scott Morrison says that the historic first heads-of-government meeting of the Quadrilateral security dialogue marks a "new dawn in the Indo-Pacific".
The first iteration of the Quad was read the last rites by the Rudd government in 2008 after traditionally non-aligned India showed no appetite for progressing it.
The second-coming revival of the Quad shows that Australia is not alone in standing up to an increasingly assertive Beijing under President Xi Jinping. It shows that China's targeting of Australia for geo-politicised trade punishment – which is putting this country at the centre of world politics for the first time – is counter-productively encouraging collective pushback from the region.
The Quad helps achieve Australia's goal of engaging our major US security partner in the region under the more ally-friendly Biden administration. AAP
The joint communique issued after Saturday's historic meeting between Mr Morrison, US President Joe Biden, Japanese PM Yoshihide Suga and Indian PM Narendra Modi commits four otherwise historically and racially different liberal democratic powers to an Indo-Pacific "anchored by democratic values, and unconstrained by coercion".
This aligns the strategic goals of the Quad with the Morrison government's commitment to protecting Australia's sovereignty from Beijing's ambition to become the regional hegemon.
The Quad's pledge, led by Australian efforts, to deliver a billion vaccine doses to south-east Asian and Pacific countries is a practical response to China's strings-attached vaccine diplomacy. This will also extend to co-operation to disrupt and provide alternatives to China's hold on critical supply chains, such as rare-earth minerals and telecommunications technology.
The Quad helps achieve Australia's goal of engaging our major US security partner in the region under the more ally-friendly Biden administration. Mr Biden has broken decisively with Donald Trump on climate – hence the inclusion of a climate change working group in the Quad – but not on strategic competition with China.
However, the Quad should not be viewed as Australia loyally cleaving all the way with the US alliance. It represents an important new security framework for pursuing Australia's genuinely independent foreign policy goal of building regional alliances and using multilateral institutions to encourage a rising China – the source of so much of Australia's modern prosperity – back behind the rules-based international system.
Australia's challenge is to continue to bring to the Quad the same maturity and independence of strategic outlook that, in a remarkable triumph for Australian diplomacy, has landed former finance minister Mathias Cormann the secretary generalship of OECD.
It is a remarkable achievement for Mr Cormann, who grew up in Belgium in a family of modest means before settling in Perth as a 25-year-old. Now he has become the first Australian to head a global institution of this prominence since the late James Wolfensohn led the World Bank in the mid-1990s.
The country's most expert opinion and analysis.
Sign up to our weekly newsletter.
The Australian Financial Review's succinct take on the principles at stake in major domestic and global stories - and what policy makers should do about them.
Latest In Economy
Most Viewed In Policy


The Richmond Folk Festival got its start five years ago when the National Folk Festival was hosted here from 2005-2007. The first year I could attend was 2008, but it happens that the RFF coincides with my undergraduate homecoming weekend, and it was a reunion year for my class, so I opted to do that instead. The following year I went to homecoming again, but this year I decided that it was time to check out the festival instead.
The festival starts on Friday evening and runs through Sunday evening. There are seven stages scattered throughout the riverfront area, including two on Browns Island. The terrain is helpful for blocking sound between the stages so that concurrent performances aren't interrupting each other. The performances are scheduled in a slightly staggered manner, and many of the artists have repeat performances on a different stage and time/day, so in that regard the festival organizers are making sure that everyone has a chance to see the performances they want to see, which is pretty handy considering that more than 190,000 people attended this year.
I was particularly thrilled to hear and meet some of the Sacred Harp singers from Sand Mountain, Alabama. They performed on one of the stages on Saturday, and thanks to some friends, I had a seat in the second row. Then on Sunday, as I was walking through the festival, I stumbled upon them holding a somewhat impromptu (not scheduled but sanctioned by festival organizers) open sing, and was able to join them for the last four songs.
The two other stand-out performances I saw were Benedicte Maurseth and Andes Manta. I have heard recordings of the Hardangfele, or Hardanger fiddle, but it wasn't until Maurseth explained the construction that I understood why it sounds like two people playing when it's only one. The fiddle has a set of strings under the ones that are touched by the bow which resonate when the string above them vibrates. She played some trance tunes that were so hauntingly beautiful that I felt a little lost when the music ended. Andes Manta are group of brothers who perform traditional Andean music, including flutes, panpipes, and several stringed instruments. I could have listened to them for hours.
One of the aspects of the folk fest performances that I particularly enjoyed was the educational component. I walked away from most performances with a greater understanding of the context, culture, and technical aspects of the music. Getting some education with my entertainment is a nice bonus.
Unfortunately, because I volunteered about 8 hours of my time at an information booth, I missed quite a bit of the festival (minus what I could hear from one of the nearby stages). While I enjoyed helping out, I think next time I will try to pick a volunteer shift that doesn't overlap with quite so much of the performance times.
The folk fest is admissions-free, but they do suggest a $5 donation per person per day. There are people carrying bright orange five-gallon buckets all over the event, asking for donations from the people attending, but on average, they collected less than $0.40 per person this year. Thankfully, they are able to get sponsorships to cover the rest of the costs of the festival, but there's some concern that the festival may have to scale back or start charging an entry fee if they don't get more donations in the future.
So, if you're in the Richmond area next October and you are looking for something relatively inexpensive and fun to do, please be sure to check out the folk festival!
My review of Carrie Newcomer's The Geography of Light has been published on Blogcritics. The album won't be out for another week and a half, so make sure you save your lunch money between now and then. It's worth it.
With the first pull of the bow across a violin strings and the pluck of an acoustic guitar, I knew immediately that The Geography of Light was going to be everything that I love about Carrie Newcomer's music. Warm, inviting, and as comfortable as an old pair of jeans.


text:
C'era una volta il West/Opinions
From The Spaghetti Western Database
< C'era una volta il West
The best movie ever made? The greatest epic of all times? The most beautiful western ever put to screen? Check, check check! Sergio Leone's magnum opos Once Upon a Time in the West is my absolutely most favorite movie and hands down among the top best movies every fucking made!! Hell yeah! The beauty of the cinematography, the excellent music by Ennio Morricone, the great cast (Claudia Cardinale. what a great ass!! ;-) , and a story so unlike any western before yet so totally typical. It is so great so be able to see this film restored on DVD and just sit back and let the images and the music do its job on your heart. I don't know what else to say, it's just the best thing that ever happened to movies. That's why I won't give a rating, out of fairness to the other movies out there. --Sebastian 22:50, 11 August 2006 (CEST)
Once Upon A Time In The West PAL Region 2 Paramount DVD - Regardless of genre the greatest motion picture ever made. I defy anyone who watches this movie to continue to think of film simply as a form of entertainment, it defines the medium as an art form. As Sergio Leone's incredibly crafted tale slowly unfolds, the different story lines of the main characters gradually intertwine, leading to the most shocking climax in cinema history. Among the revelations in the film are what in "Franks" past began his trail of relentless killing and just how important "Morton's" plans are for the birth of a new West. Follow "Cheyenne's" struggle to clear his name of the terrible slaughter of "Jill McBain's" husband and family, and piece together tantalising clues shown in flashback to "Harmonica's" ultimate purpose. Inspired casting, Henry Fonda as "Frank" the sadistic murderer, Gabriele Ferzetti as "Morton" the all powerful "Mr. Choo Choo". Jason Robards as the charismatic outlaw "Cheyenne", Claudia Cardinale as the not so defenceless widow "Jill" and the utterly mesmerising performance of Charles Bronson as "Harmonica" a man with "something inside, something to do with death!" Stunning cinematography, capturing the sprawling beauty of the West, punctuated with violent action scenes and super tight close ups, all conveying the sense of a time when everything was possible. It must be stated that Ennio Morricone's amazing score is 40% responsible for the films power and success. That's not to say any of the films other elements are in any way lacking, it's that the music is phenomenally good, at times spine-chillingly so. A timeless classic, as fresh today as when it was made and I still find it as enjoyable to watch now as I did the first time I saw it. The picture, sound quality and extras on this double disc dvd set are excellent and it would be a perfect addition to anyones collection.--The Halitosis Kid 10:28, 4 December 2006 (CET)
Retrieved from "https://www.spaghetti-western.net/index.php?title=C%27era_una_volta_il_West/Opinions&oldid=43229"
© 2004-2021 THE SPAGHETTI WESTERN DATABASE. Read about Copyright [DMCA/UrhR] on the SWDb.


Don't mess with the marching band girls. A true story.
The Fairbanks Marching Band will perform in the annual Memorial Day ceremonies at Unionville Center on May 25. Dress is Summer uniform. Music memorization includes The Victors, The Star Spangled Banner, and America the Beautiful. Report time is 9AM and we will warm at 9:15. The performance will be finished by 11AM. You can get all the details by clicking on the image above. This is one of our most important performances of the year honoring those who gave their lives for our freedom.
ONU Honor Band - Congrats!
Congratulations to FHSCB seniors Sara Schrader and Synthia Jester, who have been accepted in to the annual honor band at Ohio Northern University in Ada, Ohio. Synthia and Sara will be rehearsing and performing with the ONU bands, as well as nearly 100 of Ohio's finest musicians in the honor band. Their final concert is on Sunday, May 10, at 4:00 PM on the campus of Ohio Northern.
Congratulations to Melissa Fink for being selected as the field commander for the 2009-10 Fairbanks Marching Band! Thanks to all who auditioned for this upcoming season.
Are you a FMB veteran brass, snare, or tenor player? Do you need something to do in June? Are you interested in working with and learning from a top-12 DCI corps for two days and learn how to be a better player and marcher? Click the link and find out more about The Bluecoats' "The Blue Way" Interactive Educational Experience.
I was just made aware that none of my band or choir grades were showing up on Progress Book. After looking into this, I found that I had entered assignments due at the end of the grading period as 6/2/09 (which is the ACTUAL last day of classes) but Progress Book doesn't know this yet, so all points were hidden from the 4th nine weeks view. I have rectified the problem and now everything should be showing up as normal. Please let me know if you have any further problems viewing your band/choir grades. General music grades were not, and still should not, be affected.
The FMB has been recruited to perform at an important public ceremony on May 15. The village of Unionville Center is dedicating a historical sign from the State of Ohio designating the community as the birthplace of Charles W. Fairbanks. Mr. Humble and Mr. Montgomery have asked that we perform this important civic duty. Band members are to all eat "A" lunch at 10:46 and then change into Summer uniform for the performance. Buses are to load at 11:15 and we depart at 11:30. The brief ceremony will take place at 12 noon. Students will return to FHS and be back in class by 1 PM. FMB members need to get their permission slip signed and returned by May 11. click the pic for more details and permission slip.
Mr. Rebmann shared this video article on NY Times with me yesterday. I had read the article, but not seen the accompanying video. It is wonderful, and powerful, and troubling, and depressing all at the same time. One lesson I hope all you Fairbanks folks take from this is to cherish what you have, and do what is necessary to preserve the arts in our school district for future generations. Be sure to watch the end of the video to see what the future holds for Tiffany, and the Newark High School Symphonic Strings.
Don't forget to see the FHS Drama Club's presentation of "Robin the Hood" on April 17 and 18 at 7pm in Veteran's Auditorium in Marysville!
FHSCB juniors and seniors who received a nomination invitation for the Ohio Northern Honor Band need to RSVP to me by Friday if you want me to include you on my nomination list. I feel badly that it is scheduled on prom weekend and you have to make a choice, but either choice is fine with me. I just need to know your intentions ASAP so I can invite some deserving underclassmen if there are spots available on my nomination list.
conducted by the composer James Curnow.
6th Band: Listen to Your Music!
6th grade band members can listen to their concert music by visiting the "members only" page and clicking on the 6th grade folder. If you need a username or password, simply email me and I'll send it right to you. Use this listening experience to help you prepare for our May 19 performance by listening to learn, and also by playing along with the recording.
Want to see an amazing program of music by a first-rate university wind ensemble? The Capital University Symphonic Band and Symphonic Winds will present a program of music by Grainger, Fillmore, Wagner, Barnes, Reineke, Kopetz, Root, Sousa, and more! The best part is that the concert is FREE! The concert is on Saturday, April 25 at 7:30 P.M. at Mees Hall on the campus of Capital University. For more information, click on the pic to enlarge, call 614.236.6630, or visit www.music.capital.edu.
Candy bars for the FMB sale will be in later today and available for check out. HS members my check them out today (4/14) and JH members can check out starting tomorrow morning (4/15).
Click the pic to see the candy bar check out policy, or click here for more details.
Much research has been done on the effects of music study on the brain, and the latest study reinforces the concept that studying music makes you a better reader. It's worth a read at Science Daily.
Did You Miss The Rookie Parent Meeting?
If you missed the "rookie parent" meeting on Thursday, click on the image or click here to download a .pdf of what you missed. Band camp deposits are due today!
Economy got you down? Need a lift! Need a laugh?
Senior citizens and Young children FREE Pre-sale tickets at Fairbanks High School 4/13,4/14,4/15 during lunch.
Marysville, OH 43040Feel free to forward this message to anyone who might need a break!
You are cordially invited to join us for our 2009 Spring Flute Fest this Saturday April 4th, from 9-5 p.m. located at Bowling Green State University, Moore Musical Arts Center.
Participation is free and open to all ( donations accepted). Participants are also welcome to come throughout the day as their schedule allows.
Our featured masterclass and gala concert guest artists are: Richard Sherman ( Flute Professor at Michigan State University); Alison Sincoff-Brown ( Flute Professor at Ohio University); Nancy Stagnitta ( Flute Professor at Interlochen Arts Academy and Grand Valley University) and Nina Assimakopoulos ( Flute Professor at Bowling Green State University).


text:
declare namespace motion.easing {

	export class IEasing {

		// private function calculate (k:Float):Float;
		// private function ease (t:Float, b:Float, c:Float, d:Float):Float;

	}

}

export default motion.easing.IEasing;


Democratic socialist Alexandria Ocasio-Cortez's stunning primary upset of longtime Rep. Joe Crowley (D., N.Y.) in New York's 14th Congressional District Tuesday invited comparisons to the equally surprising win Rep. Dave Brat (R., Va.) registered over then-House Majority Leader Eric Cantor in 2014.
A look at CNN and MSNBC's coverage of the two wins, however, showed more enthusiasm and excitement over the left-wing Ocasio-Cortez in comparison to handwringing over the right-wing Brat.
Hosts on the networks crowed over her as "badass" (Mika Brzezinski), "super impressive" (Rachel Maddow), showing "tenacity and passion" (Erin Burnett), running "one of the most incredibly impressive campaigns" (Chris Hayes) and "smart" (John Avlon), while those same hosts covered the insurgent Brat rather differently.
Stay tuned to the end for a blast from the past from Al Sharpton, who has since been banished by MSNBC to Sunday mornings.
This entry was posted in Politics and tagged Al Sharpton, Chris Hayes, CNN, Eric Cantor, Erin Burnett, Joe Crowley, Mika Brzezinski, MSNBC, Rachel Maddow. Bookmark the permalink.