text:
If you think your jobsite is problematic, wait until you hear what the Building Team for the 380,800-sf Ritz-Carlton Highlands resort in Lake Tahoe, Calif., had to contend with.
The project started off in mid-2006 on the wrong foot. Q&D/Swinerton, the joint venture general contractor, came in with an initial budget that was 10% higher than expected, a result of construction prices being driven up dramatically by a shortage of skilled carpenters and materials shortages, especially for concrete. These issues weighed heavily on the Building Team throughout the project.
To address the issue of the limited availability of concrete supplies and skilled carpentry trades, the general contractor ran estimates comparing the number of carpenters and the amount of material needed to build the project using concrete versus steel frame construction. Steel came out on top in this calculation, and the scales tipped for good in steel's favor when it was determined that the steel framing could be erected in a single season. Concrete construction was used for the four-level underground parking garage and the conference center above it.
Then there were the sheer physical demands of building seven thousand feet up in the Sierra Nevada. Access to the site was so limited that the team had to build a new four-and-a-half-mile access road-at an average grade of 10%-plus six bridges and tunnels before construction could begin on the hotel itself. Water mains and conduit for phones and cable were being laid at the same time, further complicating the roadwork.
In the summer, with the road only partially completed, construction crews found themselves sharing the right-of-way with mountain bikers, outdoor adventurers, trailside workers, and ski-resort repair and safety crews.
Getting 500 trade workers a day to the remote site over a three-year period meant that general contractor Q&D/Swinerton had to rent parking at nearby Truckee Tahoe Airport in the winter and at the Northstar-at-Tahoe resort in the summer and bus everyone up and down the mountain in all kinds of weather. This turned the task of scheduling and coordinating subcontractors into an intricate exercise.
The Building Team found itself working on the sensitive issue of erosion control with a community that's ultra-protective of their lake-these are the same people who bring you the "Keep Tahoe Blue" bumper stickers. The team consulted with local environmentalists and the Lahontan Conservation District on a runoff prevention plan that went well beyond the usual silt fences and waddles: the entire building site perimeter was temporarily paved to prevent soil disruption. Local regulations further stipulated that no soil could be moved from October 15 to April 15, so the team had to work around that restriction as well.
The Lake Tahoe region is blessed with an average 16 feet of snow each season, which can put the freeze on construction projects. To allow crews and materials to move around the site during winter months, snow was trucked away rather than stockpiled on the grounds.
As the building went up, it was encapsulated in plastic and heated so that construction could go on year-round. Unfortunately, this cozy environment also attracted black bears, which occasionally used the space for rent-free accommodation. Construction crews would find beds made of torn-up building insulation when they arrived in the morning.
Serving as inspiration for the five-star resort's architecture were such great historic lodges as the Ahwahnee (Yosemite National Park), the Timberline Lodge (Mt. Hood National Forest), and the Tahoe Tavern (Lake Tahoe). The new Ritz-Carlton has a steeply pitched roof, shallow eaves, shiplap siding, and a rustic base of locally sourced granite.
Inside, a modern take on the traditional lodge fireplace is constructed of weathered granite with a chimney that rises 55 feet above the hotel lobby. The massive four-sided fireplace-with its eight-sided chimney-serves as the focal point of the lobby and head-house. The chimney is not merely decorative: it is the central support column for both the head-house roof and the spiral entry staircase. The fireboxes alone took two months to build due to the intricate herringbone pattern used to lay the 200 tons of stone from which it was fashioned.
A BIM model was used to help coordinate design and construction processes. This cut down the need for frequent visits to the remote site which, along with savings on printing and mail, saved an estimated $285,000. Another $8 million in savings came from the detection of 450 design discrepancies, which the team estimates greatly reduced the number of change orders.
The Building Team of Q&D/Swinerton; East West Partners (owner); Hornberger + Worstell (architect); OZ Architects (architect of record); BraytonHughes Design Studio (interior architect); and S.A. Miro Inc. Consulting Engineers (structural engineers) and many other dedicated professionals surmounted all these challenges to create a 170-room luxury hotel and spa with 23 private residences and a 14,000-sf convention center that earned the project a Silver Award from our judging panel. The project is also awaiting LEED certification from the Green Building Certification Institute.
Although the initial cost estimate came in 10% over budget, the Building Team reworked every facet of the building, shaving almost $22 million from the price tag and bringing the project in at a construction cost of $226 million. The Ritz-Carlton Highlands opened on schedule last December, just in time for the winter ski season.
Silver Award
The Ritz-Carlton Highlands, Lake Tahoe
Truckee, Calif.
Building Team
Submitting firm: Q&D/Swinerton (joint venture GC)
Owner: East West Partners
Architect: Hornberger + Worstell
Architect of record: OZ Architects
Interior architect: BraytonHughes Design Studio
Structural engineer: S.A. Miro Inc. Consulting Engineers
MEP engineer: Beaudin Ganze Consulting Engineers
General Information
Project size: 380,800 sf
Construction cost: $226 million
Construction time: July 2006 to December 2009
Delivery method: CM at risk


text:
Google has just announced that they've launched "Descriptive Terms" to appear with business listings in map search results. According to them, these descriptive terms are some of the most common terms found in user reviews, blogs, web pages and other online references which describe the business. For instance, if you search for "Barbeque Restaurants", you might see a business which lists such items as "banana pudding", "pork chops", "texas style", "baked potato" and "chicken poppers":
So, the cool part of this idea is that the feature will highlight user-generated terms which are frequently used in reference to the business. This is a type of an ontology formed by the vox populi, or common man. More properly, these Descriptive Terms begin forming what's known as a "folksonomy", which started coming into vogue with social media, particularly around the concept of tag clouds.
(It's very slightly ironic that Google Maps has now deployed what are essentially small tag clouds with business listings, since I've heard some Google Engineers mildly disparage tag clouds as being potentially un-userfriendly and potentially bad on sites in some cases!)
But, the really UNCOOL part of the new Descriptive Terms is that Google appears to've launched these willy-nilly without properly safeguarding against sensitive/bad terms that they can end up highlighting.
With very minor testing, I can see numerous instances where the terms selected by the algorithm are inappropriate and unfairly damaging to the businesses.
How would you like to have your restaurant business characterized with the term "terrible food", culled out of the review by a disatisfied customer?
Or, if you're a towing company where you're often despised by those whom are towed, yet liked by property owners, you might have a lot of negative reviews which could get your business attractive labels like "steal" and "complaint":
Or, if you were a doctor, how would you feel about being tagged with phrases like "pretends to care" — and if you're a dry cleaner, how about getting displayed with "stains" and "ruined":
Even more entertaining, if you were a hotel, would you like your listing sporting such amenities as "bed bugs"?!?
It's not particularly surprising that Google Maps has launched this without really caring about how this could negatively impact a lot of businesses. Quite a few of the random things that the algorithms are pulling as sample information to display with listings are potentially bad. For instance, not only are reviews snippets displayed below listings, but the same negative review can get sucked into the tooltip that is displayed when the business's icons are moused-over on the maps (see the example I pulled just a few days ago where penises are featured over a university).
Perhaps I shouldn't call out how bad Google's cleanup of this new feature is, because I've no doubt that it will result in more business for me. Just for example, I've helped out a business recently which had received a negative review from a disgruntled former employee, so the business's tooltip labeled the company location as a "sweatshop".
However, I am very concerned that this sort of casual disregard for what is likely to happen is continuing, and it's going to result in a lot more malicious behavior among competitors as well as small businesses reacting by posting more shill reviews in self-defense.
Since Google apparently deployed this with no mechanism for businesses to be able to modify how their own listing information may appear in search results, companies have no other real choice than to get shill reviews posted on their behalf in order to try to offset negative content.
Google can get up on a high-horse and preach about how companies should not post false reviews, but if your listing in the search results is labeling you as a bad guy, then you must do something fast or lose your business. A major issue with the current arrangement is that it revokes your ability to take negative consumer feedback, improve your customer service, and improve business. If you get labeled as a bad-guy at the outset, you no longer have customers for whom to improve service.
The reviews and ratings arena has already seen more than its fair share of malicious/false reviews posted by unethical competitors, too, and the increased prominence of descriptive terms derived from reviews will result in more offensive behavior as small businesses notice how the system works. As it stands, all they need to do is post a very few false reviews in Google itself, in other reviews sites, or even on blogs they control and they can viciously slice off business from their competitor!
At the moment, it looks to me like all it takes is about two shill reviews of "bed bugs" to totally ruin a hotel. And, it's even easier to damn a business with faint praise — check out the hotels which are now labeled with "small rooms" and "tiny rooms" in Manhattan, NYC (where virtually all the hotel rooms are small).
It's disappointing to see such a feature rolled out without some mechanism in place for handling these situations. It's not all that surprising, considering how Google Maps employees have told us that there is no customer testing performed for these products with business owners.
The sad part about it is that these Descriptive Terms mostly seem completely useless from a consumer point of view. When searching for "theatres" its completely not a surprise that they have "bathrooms". Really, Google? That's the term you wanted to highlight? It's not helpful for "nightclubs" to display the names of bands that previously played there. It's no surprise that "seafood restaurants" might have "new england clam chowder" or "lobster rolls" nor is it surprising to find "dentists" who offer "root canals".
The bizarre random terms that are showing up are not helpful, either. "Front desk", "told me", "conveniently located", and more. It's hard to believe that they performed usability or user-experience testing with these at all before launching them.

subset: commoncrawl


text:
#RSL Tweets of the Day (@RealSaltLake)
About 36 hours to another fireworks show at #RioT ... #RSL v PDX leg one 7p MT Sunday #BELIEVE http://instagram.com/p/gfosCpsFVo/
#RSL fans- don't say I should, wish or could have. Support the kings of #MLS & #RioTStrong on #PDX. No excuses-SELLOUT #RioT. @RealSaltLake
Retweeted by Real Salt Lak
With Schuler and Velasquez #rsl now has 18 diff players with goals. Team is the star! How do you defend that?
#RSL rookie Benji Lopez called in for US U-20 camp http://sbn.to/16Ne97W
SeBasTian VeLasQueZ @TiaN_Futbol
Amazed By Mike J Work! He Came Up With This Amazing Tattoo On My Arm! The South Goal Of Rio Tinto With… http://instagram.com/p/geqWJOpKrR/
RealSaltLake.com: RSL vs LA Galaxy, Postgame reactions: Kyle Beckerman
RealSaltLake.com: RSL vs LA Galaxy, Postgame Reactions: Nat Borchers
ESPN 700: Sebastian Velasquez on The Bill & Hans Show
MLSsoccer.com: Real Salt Lake vs Portland Timbers: The Scouting Report
MLSsoccer.com: Houston Dynamo vs. Sporting Kansas City: The Scouting Report
Real Salt Lake News & Notes
RealSaltLake.com: Kreis lauds RSL's performance after eliminating LA Galaxy in extra time
RealSaltLake.com: #MLS4RSL - Part III
RealSaltLake.com: Kresi: Bring it on Sunday, RSL fans
The Salt Lake Tribune: Real Salt Lake eager for matchup with Timbers
The Salt Lake Tribune: Thoughts on RSL advancing to Western Conference final
MLSsoccer.com: Jason Kreis says quick turnaround while staying home will benefit Real Salt Lake
MLSsoccer.com: Portland attempts to figure out Real Salt Lake after going winless in 2013 series
koin.com: Playoff Preview: Timbers-Real Salt Lake
Soccer by Ives: MLS Playoff Preview: Timbers vs RSL
For the Fans, By the Fans
RSL Soapbox: Taking a look back at RSL and Portland through 2013: Goals galore before midfield locks down
RSL Soapbox: Player Ratings: Goalkeeping, defensive contributions highlight series win over Galaxy
RSL Soapbox: RSL rookie Benji Lopez called in for US U-20 camp
RSL Perspective: Real Salt Lake find victory over the LA Galaxy and something more
MLS, Other News & Notes
MLSsoccer.com: The Throw-In: For New York, Seattle, LA Galaxy & New England, this one hurts
MLSsoccer.com: Sporting Kansas City hoping to flip the postseason script this time around against the Houston Dynamo
MLSsoccer.com: Familiar foes: Houston Dynamo happy to play role that has made Sporting Kansas City "sick of us"
MLSsoccer.com: Three-peat dream done in early, but do LA Galaxy consider their 2013 season a failure?
MLSsoccer.com: Houston Dynamo vs. Sporting KC | MLS Cup Playoffs Eastern Conference Championship Preview
Pro Soccer Talk: MLS Playoff Preview: Sporting Kansas City meets Houston in first leg of MLS conference final
Pro Soccer Talk: The Clint Dempsey gambit in Seattle? Mark it under "big failure" so far
Pro Soccer Talk: Colorado Rapids say Oscar Pareja going nowhere
Pro Soccer Talk: Where will MLS Cup be held? Down to three candidates
Pro Soccer Talk: Western or Eastern Conference final: Which series will showcase MLS best?
ESPN FC: Sporting's chance to dent the Dynamo
ESPN FC: Galaxy come down to earth with a bump


text:
Friends of F1@1F
One of the most gratifying parts of this project has been meeting all sorts of people in the early morning line. And as it turns out, I'm not the only person who goes home and writes about the experience.
I offer anyone who has stood in line with me–or in line without me–who has written about his or her experience at the Court to send me a link, and I will post it here.
The first blogger in my Friends of F1@1F feature is Brandon Forbes. Forbes was twenty-sixth in line for Tuesday morning's arguments and blogs at Good Gov, Y'all. He recapped his experience outside and inside the Court with an entry titled, "Sitting Courtside, Breyer & Scalia Give Me Hi-Fives," in which, among other things, he posited his own thoughts on a conversation we had while shivering on First Street:
In our pre-dawn discussion, Mike voiced his love of The Brethren, an Armstrong and Woodward SCOTUS tell-all that caused much controversy when it was published in the 'late 70s with its inside look at the Burger Court and which I tried to read in high school and now need to re-read. Anyway, he made an interesting case for Potter Stewart as being the last "pure judge" on the Court, meaning, I think, that he was appointed outside of the ideological box that has been present in judicial discourse since the late '70s. One could make the case that Stevens also fits this bill, at least at his appointment, though he has drifted further and further to the left in reaction to the Rehnquist/Scalia conservatism that emerged in the late '80s, a conservatism which now generally wins if the current Court splits 5-4 (see Citizens United). I'd like to look into this more, but my initial thought is that Roe might be responsible for this divide, much in the same way as West Coast Hotel v. Parrish could be seen as the dividing line for the modern interpretation of the Commerce Clause. In other words, judges appointed after Roe have the ideological boxes of the culture wars to deal with before they get on the Court just as judges after West Coast Hotel had the necessity of having a robust interpretation of the Commerce Clause as requisite for getting on the Court. But maybe that's a bit of a convoluted analogy. A way to say it simpler might be: Roe v. Wade has been the benchmark case since 1973 for determining who gets on the Supreme Court (either supportive or against), and Stewart didn't have to deal with that hanging over his confirmation. Interesting discussion, anyway.
I do, in fact, believe that Justice Stevens does fit the Stewart mold, but Brandon makes a good point that this has been obscured by the Court's post-Roe politicization, in which the Court, as Jeffrey Toobin recently noted, "has become a partisan battlefield."
Indeed, Stevens has consciously strived for the survival of Stewart's legacy despite the rise of rigid ideology on the Court. As Jeffrey Rosen wrote in 2007,
Stevens, however, is an improbable liberal icon. "I don't think of myself as a liberal at all," he told me during a recent interview in his chambers, laughing and shaking his head. "I think as part of my general politics, I'm pretty darn conservative." Stevens said that his views haven't changed since 1975, when as a moderate Republican he was appointed by President Gerald Ford to the Supreme Court. Stevens's judicial hero is Potter Stewart, the Republican centrist, whom Stevens has said he admires more than all of the other justices with whom he has served. He considers himself a "judicial conservative," he said, and only appears liberal today because he has been surrounded by increasingly conservative colleagues. "Including myself," he said, "every judge who's been appointed to the court since Lewis Powell" — nominated by Richard Nixon in 1971 — "has been more conservative than his or her predecessor. Except maybe Justice Ginsburg. That's bound to have an effect on the court."
In his one of his final written opinions, Justice Souter, another judge in the Stewart–if not Harlan II–mold of judicial conservatism, planted a seed of wisdom for future justices who follow in his and Stevens's footsteps once today's age of politically-aligned ideology subsides:
Changes in societal understanding of the fundamental reasonableness of government actions work out in much the same way that individuals reconsider issues of fundamental belief. We can change our own inherited views just so fast, and a person is not labeled a stick-in-the-mud for refusing to endorse a new moral claim without having some time to work through it intellectually and emotionally. Just as attachment to the familiar and the limits of experience affect the capacity of an individual to see the potential legitimacy of a moral position, the broader society needs the chance to take part in the dialectic of public and political back and forth about a new liberty claim before it makes sense to declare unsympathetic state or national laws arbitrary to the point of being unconstitutional. The time required is a matter for judgment depending on the issue involved, but the need for some time to pass before a court entertains a substantive due process claim on the subject is not merely the requirement of judicial restraint as a general approach, but a doctrinal demand to be satisfied before an allegedly lagging legal regime can be held to lie beyond the discretion of reasonable political judgment.
The whole dissent is worth reading. I am convinced that a generation from now, Souter's parting words will steer a Court that reflects a society confident enough to allow a judge to judge, rather than force a justice to fit facts into predetermined ideological frameworks. Just as Harlan and Stewart, both Eisenhower nominees, entered the Warren Court comparatively conservative to their stridently liberal brethren but now appear to be sober moderates, so too will Stevens and Souter be remembered as moderate despite their reputation as liberals from serving in a politically distorted age on the Court.
In other words, the principled judging qua judging of Harlan, Stewart, Stevens, and Souter has been an enduring casualty of the Warren and early Burger Courts' politically liberal overreach and the subsequent politically conservative overcorrection of the Rehnquist and early Roberts Courts.
But I don't think it is too offensive for this Jew to say on this Easter day that the moderates' jurisprudence will be resurrected by a confident public that trusts judges' judgment and votes for Presidents and Senators that reflect America's transcending the current culture wars.
If this vision of the late Roberts Court looks more like the apocalypse scenes in the Book of Revelations than the Gospel, then you should check out Josh Blackman's blog. Blackman and I got to know each other as we liveblogged the McDonald line. In addition to his libertarian-originalist blogging and his FantasySCOTUS league, Blackman has beatified, through non-profit incorporation, the first Justice Harlan as the Court's proto-originalist. Through his Harlan Institute, Blackman seeks to deepen schoolchildrens' understanding of the Constitution–an honorable goal, even if in pursuing it, he hopes to perpetuate a particular ideology into the next generation that gets in the way of my own vision for how we view the Court and politics.
But I come not to quibble the future with Josh, but rather to praise his prankster skills. Yesterday, he posted a story titled, "FantasySCOTUS.net to receive 30 min advance notice before opinions issued to curb cheating":
When I mentioned this unfortunate fact [of FantasySCOTUS cheating] to friends at the Supreme Court, they clued me into a little known SCOTUS secret. Certain reporters, news agencies, and blogs, receive 30 minute advance notice before opinions are issued. While the Court does not release the holding of the opinion, the Clerk of the Court sends a brief e-mail, listing the opinions that will be issued.
At first I was incredulous, and didn't believe this was possible. But at some point during the Rehnquist Court, Nina Totenberg, the doyenne of One First Street, used her enormous clout to push for this privilege. She was tired of hiking to the Court on days when lousy opinions were issued. Once she asked for it, the Court could not say no. Apparently, Lyle Denniston at SCOTUSBlog has been receiving these tips for years. No wonder he is always able to get post such thorough summaries so quickly.
Like any cert grant, in order to qualify for this special privilege, the Rule of 4 applies. Justice Sotomayor came through, and joined the Chief Justice, Justice Alito, and Justice Thomas. Apparently the Junior Justice is a serious Fantasy Sports fan, and fell in love with the league, and was appalled that people would cheat. Sadly, Justice Scalia decided to recuse, due to some of my recent publications criticizing his views in McDonald.
Justice Breyer, joined by Justice Stevens and Justice Ginsburg, dissented from the issuance of our petition. He does not seem to be a fan of FantasySCOTUS.net. In a verbose opinion, he wrote that while liberty must be active, fantasy court leagues must be passive, and we were not worthy of this privilege. Paraphrasing Chief Justice Roberts famous admonition from Parents Involved, Justice Breyer wrote "the way to end lame fantasy sports leagues is to end lame fantasy sports leagues."
That's a hell of a clever April Fools' joke. Seems credible at first, but steadily slides into farce and, ultimately, self-deprecation. Very good stuff.
If you have written about your SCOTUS experience, please do send me the link. If I get a few more stories, I will also add an F1@1F Friends link to my blogroll.
UPDATE: Josh Blackman writes in,
"Nice dig at Harlan [Institute] ;). It really isn't ideological. [Harlan Institute's] not about institutionalizing originalism. Its about teaching about the history of the constitution to influence decisionmaking. There is a difference. If I do my job right w harlan, kids will learn enough about history to make themselves informed and need not reach the results I wish."
I quibble no longer: that's an absolutely honorable goal.
UPDATE II: Brandon Forbes, Duke Divinity School '03, writes,
Easter is actually on Sunday. Jesus is still technically "dead" right now. The Christians will be unhappy if you resurrect him too soon.
Point taken. I'll be sticking to my matzoh from now on. At least Brandon and I will be on the same page for who to root for in the Final Four tomorrow.
UPDATE III: One day after this post, the NYT has published an interview with Justice Stevens by Adam Liptak. Along with getting even closer to Justice Stevens's internal deliberations upon his perhaps-imminent retirement, the interview also gets to Justice Stevens's self-conception as a judicial conservative by touching upon his majority opinion in Kelo and the final paragraph of his Baze v. Rees concurrence:
His views have generally remained stable, he said, while the court has drifted to the right over time. "To the extent I look back at earlier situations," he said, "I really don't think I've changed all that much."
Often, he added, the law requires a certain result, as in the court's 2005 decision in Kelo v. City of New London, which allowed local governments to use the power of eminent domain to take private property for business development.
"The Kelo case was one of my most unpopular opinions, and that was one where I thought the law really was pretty well settled on the particular point," he said.
Asked if he would have answered the question presented in the case differently had he instead been a legislator, Justice Stevens said probably yes.
In the area of capital punishment, though, he said his views had shifted.
"I certainly would not have expected during my first years on the court to have written an opinion like I did in Baze," he said, referring to Baze v. Rees, the 2008 decision that rejected a challenge to lethal injections. Though Justice Stevens voted with the majority, he wrote that he had come to the conclusion that the death penalty violates the Eighth Amendment. He went on to say that his conclusion did not justify "a refusal to respect precedents that remain a part of our law."
He explained Friday why he did not follow the approach of Justices William J. Brennan Jr. and Thurgood Marshall, who adopted a practice of dissenting in every death penalty case.
"I'm still a member of the court, and I still have to work," Justice Stevens said. "I never really agreed with Justice Brennan and Justice Marshall that your own personal view on the issue should prevent you from participating. You're still a member of the team, and the team has to confront the problem."
But that did not mean Justice Stevens, who in 1976 voted to reinstate the death penalty, was satisfied with the court's capital jurisprudence.
"There are a number of death cases that troubled me," he said. The Baze opinion, he added, "was really my reaction to the developing jurisprudence, which I think moved in a direction that I didn't expect and is not correct."


text:
QuarryGirl -- a fabulous vegan blogger who we on VegSource follow regularly -- has broken an important story. The story...
News Tagged As:
Entries tagged with: photoshop
1 result(s) displayed (1 - 1 of 1):
Want to convince your friends to go vegan? Show them photos of meat and pretend it's vegan -- like VegNews does!
Jeff Nelson, Founder VegSource | April 14, 11 at 06:06 PM


text:
A 7-year-old boy has come to the aid of San Francisco 49er Kyle Williams, whose two miscues in last week's playoff game against the Giants likely cost his team a trip to the Super Bowl and generated death threats.
Sick fans tweeted that Williams should "jump off the Golden Gate Bridge," that he and his family "deserve" to die and other awful sentiments.
Owen Shure, a diehard 49ers fan from Los Angeles, was as inconsolable as any San Francisco fan after Williams fumbled a punt late in the game. But when his father pointed out that no one felt worse than Williams, the boy showed compassion adults could learn from, according to Owen's godfather, film critic Ben Mankiewicz.
U.S. & World
"Can I write him a letter to make him feel better?" Owen asked his dad. His father said "sure," and here's what the kid wrote:
Dear Mr. Williams:
We just watched the Playoff game. I feel really bad for you but I wanted to tell you that you had a great season. you sould be very proud, so I wanted to say thank you.
I am your #1 FAN!
Owen Shure
Los Angeles, CA
p.s. your awsome
Mankiewicz, writing in The Huffington Post, said he was moved by his godson's actions.
Next season I'll have a new favorite player. It's Kyle Williams. I'll also have an old favorite little boy. It's Owen Shure.


text:
Search This Blog
I LOVE MOVIES! Old movies. New movies. With the need to share my love of film with you in these purposely short reviews. I hope this will increase your interest into going back into the theatre to watch a movie. Nowadays, most people have their heads buried in a cell phone, missing all of cinematic life in front of them. Not me baby! Now go watch a movie!!
Showing posts from July, 2016
FILM: Batman v Superman: Dawn of Justice (2016, Sci-Fi, Action, Adventure)
- Get link
- Other Apps


text:
Richard Scudamore, the head of the Premier League, supports women's football, good on him, but – he talks the drearily familiar way about them when he lets his hair down.
Premier League chief Richard Scudamore's sexist views are today exposed by his former PA.
She reveals how the boss who publicly backs women's football exchanged sleazy emails with senior colleagues in which females were referred to as "gash".
Yeah that's no good. Talking about them as if the hole between the legs were all there is to them – that's no good.
Scudamore – who will be at Manchester City's Etihad Stadium today for their expected crowning as Premier League champions – likes to be seen as a champion of equality in the game.
He has joined forces with the FA and Sports England to promote a new FA Women and Girls programme with a £2.4million investment over two years.
The soccer boss has publicly claimed the league strives to be at "the leading edge" of the "whole equality agenda".
But his former PA saw another side to 54-year-old Scudamore who earns more than £1million a year. She told the Sunday Mirror his emails were sent to her automatically while she was working for him at the Premier League last October so she could arrange his diary.
"I can tell you he has no respect for women," she said. "I don't think anyone should have to be exposed to such language and opinions at work.
"It was highly offensive. The emails portrayed women in a very derogatory manner. I have worked for very professional organisations and never seen anything like it. That's why it shocked me."
But it's the hip new thing.


text:
All Of The Lights Rmx ft. Lil Wayne,Big Sean & Drake
This remix has been talked about for the past couple of days, and I don't think it's quite done yet. One thing is done though . . . any questions about Big Sean's lyrical ability! Listen to him and Drake kill it!


text:
- Modern sites often combine all of their JavaScript into a single, large bundle. When JavaScript is served this way, loading performance suffers. Large amounts of JavaScript can also tie up the main thread, delaying interactivity. This is especially true of devices with less memory and processing power.
- Do you need code-splitting? Check Lighthouse's JavaScript Bootup Time is Too High audit and the code coverage panel in DevTools to measure the impact of your app's scripts on performance and how many scripts are unused.
- Code-splitting can be done in the following ways:
- Vendor splitting separates vendor code (e.g., React, lodash, etc.) away from your app's code. This allows you to keep application and vendor code separate. This isolates the negative performance impacts of cache invalidation for returning users when either your vendor or app code changes. This should be done in every app.
- Entry point splitting separates code by entry point(s) in your app, which are the scripts where tools like webpack and Parcel start when they build a dependency tree of your app. This is best for pages or apps where client side routing is not used, or a blended app where some parts use server side routing and others are part of a single page application.
- Dynamic splitting separates code where dynamic
import()statements are used. This type of splitting is often best for single page applications.
- Choose tools that split code for you (Preact CLI, PWA Starter Kit, etc.) where possible. React, Vue, and Angular support manual code-splitting.
Maybe you've heard this before, but there's a lot of JavaScript on web pages now, and on median mobile hardware, that can be a Bad Thing™. Yet, setting arbitrary limits on what's too much JavaScript is not the best approach. Every application is different. What's not much JavaScript in one app is far too much in another. Users and their devices vary!
That's why it's important to consider how you serve JavaScript. Do you bundle all of your scripts into one big file and serve it on all pages? If so, you'll want to reconsider this approach, and consider code splitting!
Too much too soon
Many apps place all their scripts into one file and deliver a large bundle at initial load. This file contains not just support for the initial route, but support for every interaction in every route — regardless of whether those routes are ever visited!
This all-or-nothing approach can be inefficient. Every second spent loading, parsing, and executing bytes of unused code prolongs your app's time to interactivity (TTI), which means users are forced to wait unnecessarily before they can use it. This problem is felt more by users on mobile devices where slower processors or network connections can impose further delays. The figure below shows how much longer parsing and compiling can take on a mobile device versus a desktop or laptop with a more powerful processor:
We know that faster apps are better apps. People enjoy using them more, and there are numerous case studies for how they improve various business metrics. Compared to the all-or-nothing approach, code splitting emphasizes bundling the minimum of code that can be delivered and parsed as needed for the current route, rather than all at once.
Do I need to code split?
"Do I even need to split code in my app?" is a valid question, and as is the case with many web development questions. If your app has many routes rich with functionality and makes heavy use of frameworks and libraries, the answer is almost certainly "yes". However, only you can answer that question for yourself, as you'll need to rely on your own understanding of your app's architecture and the scripts it loads, as well as a mixture of tools such as Lighthouse, DevTools, real devices, and WebPagetest.
Fortunately, you can use the information gleaned from this audit in concert with the code coverage tool found in the drawer in DevTools (which you can open with the esc key when DevTools is focused) to find out what scripts contain unused code for the current route.
While Lighthouse is great for assessing performance, you should remember that it does so synthetically. The capabilities and processing power of devices run along a massive gradient, ranging from blazingly fast all the way to excruciatingly slow, with many users on devices somewhere in between. It's crucial that you test on real devices, specifically those that are not the on the bleeding edge. Just because your site doesn't struggle to load on an iPhone X doesn't mean that someone's older (but still serviceable) Galaxy S5 will perform similarly. If you're unable to procure a real device for testing, you can always fall back on WebPagetest, which allows you to assess performance across a variety of platforms.
Set a budget and stick to it
If you treat performance as a one-off task, your performance improvements will eventually go by the wayside, as the addition of new features and tech debt will erase the gains you've made. Performance budgets help you to to cement gains, and prevent the addition of new features from killing your app's performance.
Performance budgets enable shared enthusiasm for keeping a site's user experience within the constraints needed to keep it fast. They usher in a culture of accountability that enable business stakeholders to weigh the impact to user-centric metrics of each change to a site.
Embracing performance budgets encourage teams to think seriously about the consequences of any decisions they make from early on in the design phases right through to the end of a milestone.
Performance Budgets are aided by having internal processes for operationalizing a performance culture within a business. Organizational performance budgets ensure that a budget is owned by everyone rather than just being defined by one group (e.g engineering). Ensuring fast page loads are one of the most common performance budgets teams set.
When budgets have been set and the entire organization is aware early on what the budget parameters are, you're able to say performance isn't just an engineering issue, but a critical piece of the whole package as a site is constructed. It provides a guideline for design and engineering when considering performance and should be checked with each decision that could impact performance.
When teams are crafting their performance budgets, they need to review their research and be aware of the metrics that matter most to their users. If you're trying to get interactive quickly on a low-mid end device, you can't ship 5MB of JavaScript.
Walking back from Alex Russell's performance budgeting goals outlined in "Can You Afford It?", this may be:
- Time-To-Interactive < 5s on 3G over an emulated (or real) Moto G4
- JavaScript budget of < 200 KB if targeting mobile. If you're just starting out, align with a budget that's less than the HTTP Archive medians for desktop.
- Budgets for other resources can be drawn from a total page weight target. If a page cannot be larger than 600 KB, your budget for images, JS, CSS, etc will need to fit in. It's important we remind developers more resources can be lazy loaded as needed, but the initial costs should be clearly budgeted.
A range of options are available for sites looking for inspiration on how to set budgets: you can check your competitor's sites or consult industry medians derived from case studies in your vertical.
Getting hands on with code splitting
Simply talking about code splitting without having concrete examples to point to may only leave readers with more questions. To improve clarity, this guide will show you the different ways you can split code by way of an example app, which you can use as a reference.
The app has three routes:
- The search page, (also the default route) where users can search for guitar effect pedals.
- The pedal detail page, which is shown when the user clicks on a pedal in the search results. Users can also add a pedal to their favorites list from here.
- The favorite pedals page, which lists the user's favorite pedals.
Most examples will show you how to split code along these routes using webpack, but the dynamic code splitting section will also show you how to split code using Parcel as well. Let's start by showing how you can split your app JavaScript by entry point in webpack.
Spitting code by multiple entry points
If you're not familiar with the term, an entry point is a file where webpack starts to analyze your app's dependencies. To use the tree analogy, it's the trunk of your app where assets, routes, and functionality branch from. Some apps have a single entry point but others may have multiple entry points.
When this approach makes sense: You're developing an app that's not a single page application (SPA). Or perhaps even a blended application where some pages don't use client side routing, but other pages might. In cases like these, it makes sense to split code across multiple entry points.
What to look out for: If your entry points share vendor libraries or modules, duplicate code can occur across your scripts. We'll address this in a bit.
There are three entry points in the example app that correspond to each of the routes described earlier, which are index.js, detail.js, and favorites.js. These scripts contain Preact components which render pages for those routes.
Configuring webpack to split code across multiple entry points
In webpack, we can split code by entry points by specifying them in the
config like so:
module.exports = {
// ...
entry: {
main: path.join(__dirname, "src", "index.js"),
detail: path.join(__dirname, "src", "detail.js"),
favorites: path.join(__dirname, "src", "favorites.js")
// ...
Conveniently, when there are multiple entry points, webpack treats them all as separate dependency trees, meaning that code is automatically split into named chunks like so:
Asset Size Chunks Chunk Names
js/favorites.15793084.js 37.1 KiB 0 [emitted] favorites
js/detail.47980e29.js 44.8 KiB 1 [emitted] detail
js/main.7ce05625.js 49.4 KiB 2 [emitted] main
index.html 955 bytes [emitted]
detail.html 957 bytes [emitted]
favorites.html 960 bytes [emitted]
As you may guess, chunk names come from the object keys in the entry config, which makes identifying which chunk contains code for which page a snap. The app also uses html-webpack-plugin to generate HTML files that include the corresponding chunks for each page.
Removing duplicate code
Though we've created nicely split chunks for each page, there's still a problem: There's a lot of duplicate code in each chunk. This is because webpack treats each entry point as its own dependency tree without assessing what code is shared between them. If we turn on source maps in webpack and analyze our code with a tool like Bundle Buddy or webpack-bundle-analyzer, we can see how much duplicate code is in each chunk.
Here, the duplicate code comes from vendor scripts. To remedy this, we'll tell
webpack to create a separate chunk for those scripts. To do this, we'll use the
optimization.splitChunks configuration
module.exports = {
// ...
optimization: {
splitChunks: {
cacheGroups: {
// Split vendor code to its own chunk(s)
vendors: {
test: /[\\/]node_modules[\\/]/i,
chunks: "all"
// The runtime should be in its own chunk
runtimeChunk: {
name: "runtime"
// ...
This configuration says "I want to output separate chunks for vendor scripts"
(those loaded from the _nodemodules folder). This works because all vendor
scripts are installed by npm to _nodemodules, which we check for with the
is also specified to move webpack's
runtime into its own chunk
to avoid duplication of it in our app code. When we add these options to the
config and rebuild the app, the output shows that our app's vendor scripts have
been moved to a separate file:
Asset Size Chunks Chunk Names
js/vendors~detail~favorites~main.29eb30bb.js 30.1 KiB 0 [emitted] vendors~detail~favorites~main
js/main.06d0afde.js 16.5 KiB 2 [emitted] main
js/detail.1acdbb27.js 13.4 KiB 3 [emitted] detail
js/favorites.230214a7.js 5.52 KiB 4 [emitted] favorites vendors~detail~favorites~main
js/runtime.2642dc2d.js 1.46 KiB 1 [emitted] runtime
index.html 1.1 KiB [emitted]
detail.html 1.1 KiB [emitted]
favorites.html 1.1 KiB [emitted]
Because the vendor scripts, the runtime, and shared code are now split to dedicated chunks, we've reduced the size of the entry point scripts, as well. Thanks to our efforts, Bundle Buddy gives us a better result:
Before we split the vendor code, a few thousand lines of code were shared between bundles. Now it's significantly less than that. While separating vendor code into separate chunks can incur additional HTTP request(s), that may only be an issue if your app is still on HTTP/1. Additionally, serving your scripts like this is way better for caching. If you have one giant bundle, but either your app or vendor code changes, the entire bundle would need to be downloaded again.
If you really want to go for the gold, though, you can eliminate most or all
shared code between bundles and employ a type of splitting called "commons
splitting". In the example app, this can be achieved by creating another entry
cacheGroups like so:
module.exports = {
// ...
optimization: {
splitChunks: {
cacheGroups: {
// Split vendor code to its own chunk(s)
vendors: {
test: /[\\/]node_modules[\\/]/i,
chunks: "all"
// Split code common to all chunks to its own chunk
commons: {
name: "commons", // The name of the chunk containing all common code
chunks: "initial", // TODO: Document
minChunks: 2 // This is the number of modules
// The runtime should be in its own chunk
runtimeChunk: {
name: "runtime"
// ...
When we employ commons splitting, code common amongst chunks will be split to a
new chunk named
commons, which is reflected in the output:
Asset Size Chunks Chunk Names
js/commons.e039cc73.js 40 KiB 0 [emitted] commons
js/main.5b71b65c.js 7.82 KiB 2 [emitted] main
js/detail.b3ac6f73.js 5.17 KiB 3 [emitted] detail
js/favorites.8da9eb04.js 2.18 KiB 4 [emitted] favorites
js/runtime.2642dc2d.js 1.46 KiB 1 [emitted] runtime
index.html 1.08 KiB [emitted]
detail.html 1.08 KiB [emitted]
favorites.html 1.08 KiB [emitted]
When we re-run Bundle Buddy, we should receive a notice that our bundles no longer have duplicate code across chunks.
While removing all duplicate code is a worthwhile goal, it's important to also be pragmatic. Seek to dedupe as much code as possible, but understand that doing so with this configuration may enlarge initial bundles by pulling in code that may not be used on the current page. Which can be mitigated by lazy loading scripts, which we'll cover next!
Splitting code dynamically
Splitting code by multiple entry points as demonstrated above is logical and
intuitive, but it may not be practical for your app. Another method is to lazy
load scripts with the dynamic
import("./myFancyModule.js").then(module => {
module.default(); // Call a module's default export
module.andAnotherThing(); // Call a module's named export
import() returns a
you can also use
let module = await import("./myFancyModule.js");
module.default(); // Access a module's default export
module.andAnotherThing(); // Access a module's named export
Whichever method you prefer, both Parcel and webpack can detect
import()s and
split code imported by them accordingly.
When this approach makes sense: You're developing a single page application with many discrete pieces of functionality that not all users may, well, use. Lazy loading this functionality can reduce JS parse/compile activity as well as bytes sent over the network.
What to look out for: Dynamically importing a script kicks off a network request, which means user actions could be delayed as a result. There are ways to mitigate this, though, which we'll cover soon.
Let's start by covering how dynamic code splitting works in Parcel.
Dynamic code splitting with Parcel
The most intuitive tool to use for dynamic code splitting is Parcel. Without any configuration, Parcel builds a dependency tree accounting for both static and dynamic modules, and outputs scripts with names that nicely align with your inputs.
In this version of the example app, client side routing is provided by preact-router and preact-async-route. Without dynamically imported modules, all components needed by all routes would need to be imported (and thus downloaded by the client) up front:
import Router from "preact-router";
import { h, render, Component } from "preact";
import Search from "./components/Search/Search";
import PedalDetail from "./components/PedalDetail/PedalDetail";
import Favorites from "./components/Favorites/Favorites";
<Search path="/" default/>
<PedalDetail path="/pedal/:id"/>
<Favorites path="/favorites"/>
</Router>, document.getElementById("app"));
Here, we're loading every component for every route whether or not the user ever
visits them. When we architect apps this way, we're missing out on a potential
opportunity to improve loading performance by lazy loading JavaScript. In the
case of this example app, we can defer the components needed for the
/pedal/:id and
/favorites routes by using dynamic
import() and
preact-async-route like so:
import Router from "preact-router";
import AsyncRoute from "preact-async-route";
import { h, render, Component } from "preact";
import Search from "./components/Search/Search";
<Search path="/" default/>
<AsyncRoute path="/pedal/:id" getComponent={() => import("./components/PedalDetail/PedalDetail").then(module => module.default)}/>
<AsyncRoute path="/favorites" getComponent={() => import("./components/Favorites/Favorites").then(module => module.default)}/>
</Router>, document.getElementById("app"));
You'll notice a few things that are different from the previous example:
- We're statically importing only the
Searchcomponent. This is because the default route uses this component, so it's reasonable to load it up front.
- preact-async-route handles asynchronous routing via the
- The
Favoritescomponents are lazy loaded when the user navigates to the routes using them by the
AsyncRoutecomponent via
When we build the app, Parcel outputs the following:
dist/src.e54c18ce.js 65.56 KB 2.87s
dist/PedalDetail.7f417dfd.js 7.66 KB 1.52s
dist/Favorites.02c87dad.js 3.06 KB 1.17s
dist/index.html 964 B 882ms
With zero configuration, Parcel automatically splits dynamically imported scripts into lazy-loadable chunks that can be loaded on demand.
When we land on the default route, only the scripts needed are loaded to support it. When the user navigates to either the pedal detail or favorites routes, the scripts for those routes will be loaded on demand.
Dynamic code splitting with webpack
Like Parcel, webpack can split dynamic imports to separate files. It does so
with little guidance, in fact. It's just that when webpack encounters
calls, it doesn't name the output files like Parcel does:
Asset Size Chunks Chunk Names
js/main.2c418923.js 10.2 KiB 0 [emitted] main
js/2.6b340cb3.js 3.32 KiB 2 [emitted]
js/3.a52088da.js 349 bytes 3 [emitted]
js/4.232e6590.js 521 bytes 4 [emitted]
js/vendors~main.526c9b0c.js 42.9 KiB 5 [emitted] vendors~main
js/runtime.8b59d0ff.js 2.26 KiB 6 [emitted] runtime
js/1.175d2b19.js 6.11 KiB 1 [emitted]
index.html 1.08 KiB [emitted]
Here, you can see that webpack assigns IDs to
import()s rather than names.
This doesn't matter so much for your app's users, but it can problematic for
development reasons. To get around this, we'll need to use a special kind of
comment known as an inline directive to tell webpack what the output file
names should be:
<Search path="/" default/>
<AsyncRoute path="/pedal/:id" getComponent={() => import(/* webpackChunkName: "PedalDetail" */ "./components/PedalDetail/PedalDetail").then(module => module.default)}/>
<AsyncRoute path="/favorites" getComponent={() => import(/* webpackChunkName: "Favorites" */ "./components/Favorites/Favorites").then(module => module.default)}/>
</Router>, document.getElementById("app"));
In the above snippet, an inline directive called
webpackChunkName tells
webpack what the name of a chunk should be. When used within
import() calls,
webpack gives proper names to chunks like so:
Asset Size Chunks Chunk Names
js/main.b72863fc.js 10.2 KiB 0 [emitted] main
js/Favorites.0ce4835e.js 3.33 KiB 2 [emitted] Favorites
js/simpleSort.ef5256f9.js 358 bytes 3 [emitted] simpleSort
js/toggleFavorite.fc4ea97d.js 534 bytes 4 [emitted] toggleFavorite
js/vendors~main.526c9b0c.js 42.9 KiB 5 [emitted] vendors~main
js/runtime.a735e0fe.js 2.32 KiB 6 [emitted] runtime
js/PedalDetail.ba7a0692.js 6.12 KiB 1 [emitted] PedalDetail
index.html 1.08 KiB [emitted]
This syntax is a bit unwieldy in my opinion, but it works. If you want to how the example app does dynamic code splitting with webpack, check out the app repo's webpack-dynamic-splitting branch.
Loading performance considerations
A potential pain point with code splitting is it increases the amount of requests for scripts which, even in HTTP/2 environments, presents challenges. Let's cover some ways you can improve loading performance in apps where code splitting is used.
There's that "budget" word again
At the start of this guide, we talked at a high level about performance budgets,
which can be difficult to enforce if the practice isn't followed in your
organization. If you use webpack in your project, you can configure your app to
throw an error for builds emitting assets that are too large by way of the
performance configuration
object. With this config
object, we can effectively enforce budgets for asset sizes like so:
module.exports = {
// ...
performance: {
hints: "error",
maxAssetSize: 102400
This configuration effectively tells Webpack "if any asset larger than 100 KB is
emitted during build, throw an error". This is certainly a draconian
configuration (and is one you probably can't put into an existing app without
running into some trouble), but if you're serious about sticking to a budget,
performance object can help you do just that. Be sure to check out other
options available in this object, such as
Precache scripts with a service worker
One of the Ps of the PRPL pattern stands for precache, which involves precaching remaining routes and functionality with a service worker when it initializes. Precaching is great for performance in the following ways:
- It doesn't impact loading performance of the app's initial load, because service worker registration and subsequent precaching occurs later on in the page loading process.
- Precaching remaining routes and functionality with a service worker ensures they're available immediately when they're requested later.
Of course, adding a service worker to an app with code generated by modern tooling can be challenging, owing to a number of reasons (such as output filenames with hashes in them). Thankfully, Workbox has a webpack plugin that can generate a service worker for your app with little effort. At a minimum, you can install workbox-webpack-plugin and bring it into your webpack config like so:
const { GenerateSW } = require("workbox-webpack-plugin");
From there, you can add an instance of
GenerateSW to the
plugins config:
module.exports = {
// ...
plugins: [
// ... other plugins omitted
new GenerateSW()
// ...
With this configuration, Workbox generates a service worker that precaches all
JavaScript in your app. This is probably fine for small apps, but for large ones
you'll may want to limit what's precached. This can be done via the plugin's
chunks option to whitelist chunks:
module.exports = {
// ...
plugins: [
new GenerateSW({
chunks: ["main", "Favorites", "PedalDetail", "vendors"]
// ...
Using the whitelist approach, we can ensure the service worker precaches only the scripts we want. To see how Workbox is used in the example app, check out the repo's webpack-dynamic-splitting-precache branch!
Prefetching and preloading scripts
Precaching scripts with a service worker is one way to improve loading performance for your app, but they should be treated as a progressive enhancement. In the absence of (or even in addition to) them, you may want to consider prefetching or preloading chunks.
rel=prefetch and
rel=preload are resource hints that fetch a specified
resource before the browser otherwise would, which can improve loading
performance by masking latency. Though they're both very similar at first
glance, they behave quite differently:
rel=prefetchis a low priority fetch for non-critical resources to be used later. Requests kicked off by
rel=prefetchoccur when the browser is idle.
rel=preloadis a high priority fetch for critical resources used by the current route. Requests for resources kicked off by
rel=preloadmay occur sooner than when the browser would otherwise discover them. Preloading is super nuanced, though, so you'll want to check out this guide (and potentially the spec) for guidance.
If you want an in-depth explainer on these resource hints, read this article. For the sake of this guide, though, I'll limit guidance in this area as it applies to webpack.
It may be reasonable to prefetch scripts for routes or functionality you're
reasonably certain users will visit or use, but have not yet done so. A good use
case for prefetching in this guide's example app occurs where we mount the app's
Router component in the index.js entry point:
<Search path="/" default/>
<AsyncRoute path="/pedal/:id" getComponent={() => import(/* webpackChunkName: "PedalDetail" */ "./components/PedalDetail/PedalDetail").then(module => module.default)}/>
<AsyncRoute path="/favorites" getComponent={() => import(/* webpackPrefetch: true, webpackChunkName: "Favorites" */ "./components/Favorites/Favorites").then(module => module.default)}/>
</Router>, document.getElementById("app"));
Here, we've added the
webpackPrefetch inline directive (in addition to
webpackChunkName) to the
AsyncRoute for the favorites page. If no
prefetching was done for the scripts on this route, a user requesting them could
experience latency like this:
On a slow connection, the user may have to wait for a few seconds before the
scripts for the favorites route finally arrives. Using
though, we can make this less painful and idly prefetch that JavaScript when the
user first lands on the app:
Prefetches are generally low risk, as they don't significantly contend for bandwidth since the resource is fetched during idle time with low priority. That said, the potential to waste bandwidth is there, so you'll want to make sure whatever you're prefetching has a reasonable chance of being used.
Preloading is similar to, but ultimately different than prefetching. The
webpackPreload inline directive can invoke a preload much the same way
webpackPrefetch does for a prefetch. In my admittedly anecdotal experience,
however, using
webpackPreload to preload dynamic imports is roughly as
beneficial as simply bundling all functionality for a given route into one large
Preloading, in my opinion, makes the most sense for scripts critical to rendering the initial route. Twitter does this to speed up loading of the Twitter Lite app:
webpackPreload only works with dynamic
import() calls, so in
order to preload chunks critical to the initial route in the example app, we
need to rely on another method involving a plugin called
Once this plugin is installed, we bring it into the webpack config like so:
const PreloadWebpackPlugin = require("preload-webpack-plugin");
Then we configure the plugin to preload the
main and
vendors chunks by
adding an instance of the plugin to the
plugins array:
plugins: [
// Other plugins omitted...
new PreloadWebpackPlugin({
rel: "preload",
include: ["main", "vendors"]
This configuration will place preload hints via
<link> elements in the
<head> for both the
vendors and
main chunks.
While this doesn't confer much of a performance boost in the example app, it can boost loading performance in apps where there are many chunks of JavaScript and other resources that would otherwise contend for bandwidth. To see preloading in action in the example app, check out the webpack-dynamic-splitting-preload branch.
Conclusion and resources
There's no doubt that code splitting is tough. What's more, how you'll split code in your specific app will take time for you to figure out. If you want to know more, or just want different takes on the subject, check out this list of resources:
- Official webpack code splitting docs.
- Official Parcel.js code splitting docs.
- Official React code splitting docs.
- Official Vue code splitting docs.
- Official Angular code splitting docs.
- Dynamic import() guidance here on Web Fundamentals.
Rest assured, though, that code splitting will improve performance for your app, which will reap rewards as users will find your app more engaging and easier to use. Good luck!
Special thanks to Patrick Meenan, Jason Miller, Jeff Posnick, Sam Saccone, Philip Walton, for their valuable feedback, which significantly improved the quality of this article.


text:
Djarum has come a long way since its humble beginnings in the 1950s. Growing from strength to strength, today our high-tech mass production lines produce cigarettes for both the domestic and international market
With over half a century of history behind it, Djarum has come a long way from its quiet beginnings on the streets of Kudus. Today Djarum has become a familiar icon in Indonesia thanks to our popular clove-and-tobacco cigarette products, which are familiar all over the archipelago. We are one of the largest cigarette manufacturers in Indonesia and have also established a strong international presence, providing satisfaction to customers daily.
Despite our success, Djarum remains firmly rooted in its hometown of Kudus. These roots help us to remember where we came from, and to keep in mind our obligations to society. As we have grown, so have our abilities to contribute: where once we helped the community of Kudus, today our corporate social initiatives programs have a national focus and a global outlook.


text:
LITTLE ROCK — A Republican legislator who mocked "Boston liberals" in a tweet sent Friday in the midst of a deadly manhunt for suspects in the Boston Marathon bombings apologized for his remarks amid a shower of criticism from colleagues on both sides of the aisle.
Rep. Nate Bell, a gun rights advocate from Mena, tweeted early Friday: "I wonder how many Boston liberals spent the night cowering in their homes wishing they had an AR-15 with a high capacity magazine?"
Bell, who apparently was mocking recent failed efforts in Congress to impose stricter gun safety measures in the wake of the Newtown, Conn., school massacre, initially avoided reporters after the House recessed an early session Friday. Later in a Facebook post, a link to which he posted on Twitter, he said he regretted his poor choice of timing.
"As a staunch and unwavering supporter of the individual right to self-defense, I expressed my point of view without thinking of the effect on those still in time of crisis. Please know that my thoughts and prayers were with the people of Boston overnight and will continue as they recover from this tragedy."
In an interview on Little Rock television station KARK, Bell said he "in no way at all intended to be insensitive to anyone" and said he was "very sad that it hurt people's feelings, that it hurt already raw emotions, that it further added to their pain."
Overnight, one of two suspects in the Boston marathon bombings was killed in a shootout with police, and Boston and surrounding communities were on virtual lockdown Friday as authorities hunted for the second suspect. Authorities believe the suspects were responsible for the death of a Massachusetts Institute of Technology police officer found shot on campus.
In a Facebook post early Friday afternoon, Bell said his earlier comments were ill-timed, "given the ongoing tragedy that is still unfolding."
House Speaker Davy Carter and the House leaders of both major parties all issued statements critical of Bell's early tweet.
"I want to extend my deepest apologies to the people of the City of Boston and the state of Massachusetts for the inappropriate and insensitive comment made this morning by an Arkansas House member," said Carter, R-Cabot. "I can assure the people of Boston and the people of Massachusetts that Arkansans have them in their thoughts and prayers during this tragic time."
House Minority Leader Greg Leding, D-Fayetteville, said Bell's tweet was "tasteless and uncaring."
"I can't speak for them, but I would imagine every other member of the Arkansas House of Representatives, the Arkansas Senate and Arkansans everywhere find Rep. Bell's comments to be as reprehensible as I do. Boston is a city of patriots, and all Arkansans should stand with them today," Leding said in a statement.
House Majority Leader Bruce Westerman, R-Hot Springs, said Bell's remarks did not reflect the position of the GOP caucus.
"There is a time to debate the Second Amendment rights guaranteed to our citizens. Now is not the time … Politics and posturing about Boston have no place inside the Arkansas House of Representatives," Westerman said in a statement released through the Republican Party of Arkansas.
Asked if Bell could be sanctioned over the incident, Carter said he was not going to consider that "in the heat of the moment."
"We'll talk about that kind of stuff later," he said.


text:
Q. A lot of your teams have shown the kind of resilience the Red Sox showed tonight. In that context can you appreciate what they have pulled off here?
JOE TORRE: Oh, no question. We always respected their ballclub. We knew they had a ton of ability. The fact that when they get on a roll they can do things like they do to us. You watched it when they ran off those 20 out of 22 or whatever it was in August, and they are very capable. You know, we had a couple of games, if you go back in the series, where we had situations the way we wanted it, leads late in the game and we just could not close the deal. We certainly never took them for granted, even up 3-0 because we know how explosive they can be.
Q. You had said before the game it was important for the pitching to set a tone for your club early, it must be disappointing.
JOE TORRE: Well, disappointment, it's just too bad it happened. You go out there and all of a sudden you give up a two-spot and a four-spot and that's a hell of a hill to climb. Fact is, even if you try to fight your way back, Derek Lowe did another great job for them. We just, you know, kept, if we scored a run, they scored two, we scored two, they scored one, so we could never really mount anything to get back into it. You know, we just didn't pitch well enough.
Q. Looking back on the last week, does it cross your mind that the 19 runs was like a home-run hitting contest with a lot of batting strokes, in that one game, might have been like batting practice?
JOE TORRE: No, I don't think so. We've had games that go both ways in that way. I think we were pretty grown up enough to know where we were and that was still only one game. We had got beaten. We were beaten 22-0 in one game and we certainly know that good teams bounce back from that stuff. But I don't think it changed anything. First off, my batting coach, his first year as a coach did an outstanding job and the kind of player he was, he certainly is aware of how his players are, how his hitters are.
Q. Have you had a chance yet to speak with George Steinbrenner and knowing him now as well as you do, how do you expect him to react to what happened?
JOE TORRE: Well, he's going to be disappointed. I saw him before the game. He was offering all of the support he possibly could. I mean, none of us want this to happen. We went out there, busted our tails. I think everybody was a little surprised that we were up 3-0, and, you know, you thought going in it was going to be a seven-game series. However, you didn't think it was going to be three straight and three straight and then of course they finished us off tonight. I mean, George knows that we do the best we can. Unfortunately the results are not always what you want them to be.
Q. You've had some classically-constructed teams in the past and this year maybe not the balance that the Red Sox had. Did they have a better-constructed team with the left-handed bullpen, Roberts to come in and pinch-run, little things?
JOE TORRE: We never got in that position really to utilize our -- who you wanted to take out for a pinch-runner for us. They had a little better balance. They picked up Myers which gave them that extra left-hander. They are a thunder. As I say, they can put winning streaks together before you blink your eye and we knew that, we knew that. That's why we were wanting to close the deal. That's why I brought Mariano in in Game 4 with two innings to go, even though we had a 3-0 lead. I thought this was the time to do it because we had the opportunity to do it. Certainly, after playing them as often as we did, we are very much aware of what their capabilities were.
Q. After you got to 3-0, was there anything that collectively happened that you could cite or was it just a game-by-game thing?
JOE TORRE: I wish I could. To be perfectly honest with you, which I always try to be, after that game, you know, we spent as much time talking about tomorrow than we did about what we just did after Game 3. I don't know anything that happened. Nothing consciously happened. We certainly, as I said, never took anybody for granted. But, you know, the Red Sox, Derek Lowe came in in Game 4 and just basically got us down. But even that being said, just because what did we have -- we had four runs which is fine, and we had a one-run lead going into the ninth inning. So we were where we wanted to be in Game 4 with Mariano on the mound. And then Game 5, we had a two-run lead in the eighth inning with Gordon in the game. So those two times, I don't think anything happened after Game 3 because we were in good position in Game 4 and Game 5, positions that we would take any single day of the week.
End of FastScripts...


text:
Decorative Show Caps
Decorative Show Caps - These bolt and fastener
covers are a great way to hide ugly screw heads. They have a cap and washer that snaps together
for a corrosion proof seal. Shipped 10 per package. Available in Show Chrome or Gold Electroplate.
Loads of Kool Cover Bolt Cover Kits in Stock!
Kool Cover kit sample. These are packed for each specific bike.
Large Covers for 17mm Bolt Heads.
Chrome Press-in Allen Bolt Hole Plugs.
You can also buy them based on the bolt sizes you need, to beautify that custom project!
Some Kits have as many as 81 caps to fully dress a specific bike.
Kool Cover Bolt Cover Kits - Cover those unsightly
bolt heads on your bike with these complete cover kits. The covers are easy to install, and are
designed to cover every exposed hex bolt on your motorcycle. Manufactured from a synthetic material and
beautifully chromed, these covers are resistant to rust and oxidation. Less expensive and much easier
then replacing your bolts with chrome fasteners, these Kool Covers are the choice of the day to dress
up your bike and add that 'extra detail'!
19mm Riser Bolt Covers
#8126 19mm Riser Bolt Covers - Perfection lies in
the details. Often ignored, but glaringly obvious, your stock zinc plated riser bolts peer out
from under your top triple tree. Our chrome Riser Bolt Covers go on in seconds and right this
wrong. These covers fit 19mm bolt heads, and add a beautiful chrome touch to an otherwise dull
Chrome Star Washers
Chrome Star Washers - These chrome star washers
are a great way to dress up stud mounted accessories, like rear trunk racks, grab handles, etc. They
distribute the load across a much larger area, minimizing the possibility of fiberglass or plastic
body panel cracks where accessories are installed. They have a 1/4" diameter hole in the
center, and are 1 1/4" in outside diameter. Shipped in packs of 10, this is a whale of a deal!
Universal Eagle Lights
Universal Eagle Lights - Here's the original. A
Küryakyn exclusive! Style, function and added visibility, all in the same light. Eagle lights
can be mounted on any motorcycle, trailer, mirror, caliper or frame cover, light bar, etc.
This 12-volt light draws very little juice and has a super-long life. Approximately 2"W x
1-7/8"H. 3-year warranty. Warning: The use of blue, green or purple lights is prohibited
in some states. Be sure to check your state's laws before ordering.
Lighted Condors with 1500 Emblem
Lighted Condors with 1500 Emblem - Available only
by Küryakyn, these awesome lighting additions come in chrome or gold. They measure
approximately 7" W x 2-1/4" H and come with a three-year limited warranty. All gold condors are
double lacquer coated for long life.
OEM Plastic Rivets used in Body panels
Reusable Plastic Rivets - These OEM Plastic Rivets
are used in body panels all over the Gold Wing. Now, you can replace your broken or missing
body rivets with these inexpensive beauties!
Replacement Grommets for Body Panels & Covers
Replacement Grommets - These OEM rubber grommets
are used by Honda to hold body panels & covers securely in place. Set of five contains two
ovals, two rounds, and one slotted grommet.
Flame Accents- Chrome plated laser cut steel FLAME
accents. Easily attached with 'gorilla' adhesive tape, and WILL NOT fall off!
Chrome Flame Accents -
3-1/4" flame (pair) $17.96
Chrome Flame Accents -
6" flame (pair) $35.96
Chrome Flame Accents -
8" flame (pair) $44.96
Applications for Universal Trim Kits
Universal Trim Chart
Universal Trim Kits - This product line of 'Cruis Wing'
decorative chrome plated steel accents are available in 6 lengths to allow installation in a
multitude of locations. They can be used on cruisers, touring bikes, trikes, etc. Installation is
a snap using the supplied heavy-duty adhesive strips. Can be easily formed to misc contours and
non-flat surfaces.


text:
I accidentally deleted the Unread Article folder. I would like to recover that folder and when an article is deleted reflect it is in the trash.
I tried doing an new folder named Unread Articles and it did read the unread files ok.
However, when I delete the articles a I read them they do not appear in the trash folder like they did in the past. I think the article may actually in the trash.
I removed Vienna and reinstalled. The Unread Article folder and files reappeared and the missing articles in the trash.
Deleting Vienna apparently is retains information because it showed my existing feeds which I thought would be gone and I'd have to start totally feed with a new Vienna.
I'm a Mac OS 10.12 Sierra, Was using Vienna 3.
Deleted Folder
An RSS/Atom newsreader with features comparable to commercial newsreaders.
1 post • Page 1 of 1
1 post • Page 1 of 1
Who is online
Users browsing this forum: Google Feedfetcher


text:
swynne brauchte ein neues Briefpapier Design und hat einen Wettbewerb auf 99designs gestartet.
Aus 20 Designs von 6 Designern wurde eine Gewinner gewählt.
See "reubenhauser" winning entry. http://contests.sitepoint.com/contests/4205 Start-up business needs to look solid, sharp, credible, approachable but not your "average Joe" kind of home inspection service. Owner is smart, guys guy from Wisconsin and used to own construction business. Need business suite that is not that complicated to get printed up. Colors are black, white and Texas Longhorn orange. Need to have on the card the PO Box in Austin and also TREC License #9857 (I have a .gif of the logo that can be revised that I can email).
Spahn Superior - see logo
Desired Color Scheme:
White, Black, Gray and Texas Longhorns Orange
Desired Style:
Clean, simple, professional, sharp, solid, see logo
Accepted File Formats:
Standard Web Formats (.jpg, .gif or .png); Vector Formats (.eps, .pdf or .ai)
Just picked winning logo for Need Gift Logo for Boyfriend's new Business contest I ran for gift logo for my boyfriends business on sitepoint. http://contests.sitepoint.com/contests/4205. If you send me your email address I can also forward to you the email in other files. First time using site and I did not realize I could or should run mulitple items in same contest. So now I need the following business suite - business card, stationary, envelope and label to affix to presentation folders. Needs to be professional, sharp with a unique flair but not too fancy. Also need a design that will transfer to TREC Home Inspection Reports located http://www.trec.state.tx.us/formsla…ction.aspÂ. (Promulgated by the Texas Real Estate Commission(TREC) P.O. Box 12188, Austin, TX 78711-2188, 1-800-250-8732 or (512) 459-6544 (http:\\www.trec.state.tx.us). REI 7A-0). Cannot change report just add header and design element.


text:
Local Fresh necesitaba un nuevo diseño de logotipo y lanzó un concurso de diseño en 99designs.
Un ganador ha sido elegido entre 128 diseños de 31 diseñadores freelance.
Oregon City Dentistry
We are developing a new brand identity for a dentist in Oregon City, OR. Although it has been a thriving practice for the past ~15 years, it has always operated under the doctor's name, Brett L. Johnson, DMD. We are looking to anchor this dental practice to that location via a brand name to leverage 'search marketing', as well as to associate the doctor to the city. Services at that location include cosmetic, restorative, preventative and general dentistry for individuals and families alike.
We are looking for a word mark and logo treatment that is clean, simple and professional. No color palette or specific visual aesthetic has been chosen so we are open to a variety of design concepts and colors. As caveat, using pure 'earth tones' may not be the best choice since brown has an association to dirt, which does not promote a sense of freshness / cleanliness for a dental practice. Any brand logo for the project can be a simple word mark or incorporate many of the stronger landmarks of the area. Additional information and ideas can be drawn from:
http://www.orcity.org/photogallery ; or
Individuals interested in general dentistry from the southwest Portland, OR metro area.
Please submit each concept 2-up, with one version against pure white background and a second version reversed against a pure black background; no gradient backgrounds; we want the winning design to display well in a variety of applications (print, online, etc.)
Format: The winning design must be delivered as an Adobe .ai vector format file. All artwork must be original (no stock art elements) and full copyright ownership must be conveyed to Brett L. Johnson, DMD.
If you need any further clarification on this brief, we will be happy to address your questions. Thank you in advance for your time and interest in this project. We look forward to receiving your ideas!
Descubre cómo funciona un concurso de diseño u obtén más información sobre nuestros servicios de diseño de logo.


text:
The University of Washington defines diversity broadly to include "race, sex, gender identity, socioeconomic status, ethnicity, sexual orientation, age, disability, nationality, religion, and military status." Diversity at UW
Diversity is a fundamental value of the Libraries and is identified among the core values of our strategic plan. Our staff create an environment that appreciates, acknowledges, encourages and celebrates differences by functioning and communicating effectively and respectfully within the context of varying beliefs, behaviors, orientations, identities and cultural backgrounds. We seek and provide opportunities to gain experience working and collaborating in diverse, multicultural, and inclusive settings with a willingness to change for continual improvement. Our appreciation for diversity allows us to serve our increasingly diverse communities more effectively and with more sensitivity.
Equity at UW
Libraries support YOU!
During times of political division and unrest, libraries continue to provide tools for advancing and creating knowledge, fostering critical thinking and evidence-based arguments, and promoting reasoned dialog. In the words of UW Libraries Dean Betsy Wilson,
"We are at a place where freedom of speech and open exchange of ideas are celebrated. At the same time, we do not and will not let hate speech or other actions that threaten the well-being of any member of our community go unchecked or unchallenged."
The UW Libraries is committed to and working on providing support to individuals directly affected by changes in national policy, including undocumented students, immigrants, Muslims, LGBTQ folks and those with visas or green cards. We stand against racism, prejudice, stereotyping, and discrimination. Thanks for visiting the UW Libraries. You belong.
Featured Guides & Resources
These guides are meant to collect resources from across the campus. Have a suggestion for more resources? Let us know and we'll consider adding it!
Report Bias on Campus
Reports received through this form will be reviewed by the Bias Incident Advisory Committee who will offer support, ensure investigation, coordinate healing, and take actions to minimize future incidents. Bias may involve, but is not limited to, bullying, harassment, destruction of property, targeted hateful graffiti, discrimination based on one's identity, intimidation, or physical, verbal or written assault. If you see or experience bias on campus or through a UW online service, report it!
Libraries Diversity Advisory Committee
Libraries personnel at all levels of the organization are responsible for developing and maintaining a culture supportive of and committed to diversity and inclusion. A Diversity Committee and Diversity Officer implement and maintain the Libraries' Diversity plan and provide support and guidance. Both the Committee and Diversity Officer report directly to the Dean of University Libraries.
Four Areas of Ongoing Focus
- Services to constituents
To enrich the quality of life and advance intellectual discovery by connecting people of diverse backgrounds and ethnicities with knowledge.
- Recruitment of staff from diverse backgrounds
To increase the diversity of the Libraries' workforce at all levels of the organization.
- Retention of staff from diverse backgrounds
To promote an inclusive and supportive workplace culture as an important element in retaining a diverse staff.
- Organizational culture
To incorporate awareness of the value and importance of diversity at all levels of the Libraries so that staff recognize their responsibility in maintaining a culture supportive of and committed to diversity; provide a supportive and safe working and learning environment.


text:
Train Amsterdam → Bourg St Maurice
Duration 13h22 - From NZ$295
- Departure station : Amsterdam cs (Stationsplein 15 1012 AB Amsterdam)
Amsterdam, capital city of the Netherlands
Amsterdam, capital city of the Netherlands Amsterdam, the capital city of the Netherlands, is located in the province of North Holland. The city got its name from a dam in the river Amstel and was a small fishing village at its creation. Nowadays Amsterdam is a busy seaport and one of the top European financial centres as well as a major cultural hub. The canals, world-famous museums and historical sights makes Amsterdam one of the most romantic and beautiful cities in Europe. It has all the advantages of a big city: culture, nightlife, restaurants with international cuisine, good transport system. However, the city has also a quiet and relaxed atmosphere largely thanks to its extensive canals, low road traffic, small green parks and flower fields. In Amsterdam, places of interest are never far away, get a bike or hop on a tram for an authentic local experience. Amsterdam can be reached easily by train from other European capitals - Paris, London or Brussels. Learn more about Amsterdam
Bourg Saint Maurice, "the mountain in the city" At an altitude of 840 meters, Bourg Saint Maurice merits its slogan: "the mountain in the city". Holiday-makers can make the most of its famous ski resort, "les Arcs", which offers an incredible view onto the Tarentaise Valley and the Mont Blanc. Learn more about Bourg St Maurice
Book your journey from Amsterdam to Bourg St Maurice From NZ$295 NZ$295
Practical information
Reviews & ratings
Overall appreciation
No reviews for this product yet


text:
Amy Adams, Jennifer Lawrence and Matthew McConaughey picked up the top awards at the Golden Globes 2014.
'American Hustle', 'Breaking Bad' and 'Dallas Buyer's Club' won the most awards at the 71st annual event in Los Angeles, hosted by Tina Fey and Amy Poehler at the Beverley Hilton Hotel.
'American Hustle' won three awards out of seven nominations, including Best Supporting Actress (Musical or Comedy), which was handed to Jennifer Lawrence for her role as Rosalyn Rosenfeld in the film.
In her acceptance speech, she said: "I don't know why it's so terrifying it's obviously a good thing. Thank you to my family and my team, thank you so much!"
The film, directed by David O Russell, also took home the award for Best Motion Picture (Comedy) and Best Actress in a Musical or Comedy for Amy Adams.
'Dallas Buyer's Club' also picked up two awards, which went to Matthew McConaughy, who played an AIDS victim, and Jared Leto in the Best Actor (Drama) and Best Supporting Actor categories.
Jared said his role was very "transformative" and joked: "I did not ever use any prostethics in this film. That tiny little Brazilian bubble butt was all mine."
'12 Years a Slave' lost out on six nominations but won the top award for Best Motion Picture (Drama).
'Breaking Bad' was among the winners in the TV categories, with two wins and other winners included Leonardo DiCaprio as Best Actor (Musical or Comedy) for his role in 'The Wolf of Wall Street' and Cate Blanchett for Best Actress (Drama) in Blue Jasmine.
Full list of winners at the Golden Globes 2014..
Best Actor in a motion picture (drama)
Matthew McConaughey - Dallas Buyers Club
Best Actress in a motion picture (drama)
Cate Blanchett - Blue Jasmine
Best Director - motion picture
Alfonso Cuarón - Gravity
Best motion picture (musical or comedy)
American Hustle
Best Actress in a motion picture, musical or comedy
Amy Adams - American Hustle
Best Actor in a motion picture, musical or comedy
Leonardo Dicaprio - Wolf of Wall Street
Best Animated Feature film
Best Foreign Language Film
The Great Beauty (Italy)
Best Actor in a TV series, drama
Bryan Cranston - Breaking Bad
Best Actor in a mini-series or TV movie
Michael Douglas, Behind the Candelabra
Best Actress in a mini-series or TV movie
Elisabeth Moss - Top of the Lake
Best Supporting Actress in a motion picture
Jennifer Lawrence - American Hustle
Best Actress in a TV series (drama)
Robin Wright - House of Cards
Best TV Series (comedy)
Brooklyn Nine-Nine
Best TV Miniseries or Movie
Behind the Candelabra
Best Original Song - Motion Picture
Ordinary Love - Mandela: Long Walk to Freedom
Best Actor in a TV Series (comedy)
Andy Samberg - Brooklyn Nine-Nine.
Best Actress in a TV Series (comedy)
Amy Poehler - Parks and Recreation
Best Original Score - Motion Picture
All Is Lost - Alex Ebert
Best Screenplay - Motion Picture
Spike Jonze - Her
Best Supporting Actress in a series, mini-series, or TV movie
Jacqueline Bisset - Dancing on the Edge
Best Supporting Actor in a series, mini-series or TV movie
Jon Voight - Ray Donovan
tagged in Amy Adams Golden Globes


text:
You don't have any saved vehicles!
Look for this link on your favorites:
Once you've saved some vehicles, you can view them here at any time.
Porsche Certified, ONLY 31,005 Miles! Leather Interior, Bluetooth, iPod/MP3 Input, CD Player, Brake Actuated Limited Slip Differential, Dual Zone A/C, Aluminum Wheels, JET BLACK METALLIC, Turbo Charged, Power Liftgate, All Wheel Drive.
Leather Seats, Power Liftgate, Turbocharged, iPod/MP3 Input, Bluetooth, CD Player, Dual Zone A/C, Brake Actuated Limited Slip Differential Rear Spoiler, MP3 Player, All Wheel Drive, Aluminum Wheels, Remote Trunk Release.
Edmunds.com explains Grip is plentiful, and the Macan changes direction with confidence and poise. The all-wheel drive also lets you put down the power easily..
Vehicles must pass an extensive 111-point checklist and inspection, 24/7 Roadside Assistance is included during the Certified Warranty period, Trip-Interruption Services, Balance of original 4-year/50,000-mile new car warranty, 2 Year/Unlimited Mile Warranty from the date of sale, when/if New vehicle warranty has expired, All coverage expires at 8 years/100,000 total miles, $0 Deductible for warranty repairs, transferable to subsequent owners, All work done by Porsche-trained technicians, only genuine Porsche parts are used in reconditioning
Welcome to Reeves Import Motorcars, a family owned and operated business since 1971. On behalf of our staff
While every reasonable effort is made to ensure the accuracy of this information, we are not responsible for any errors or omissions contained on these pages. All offers are mutually exclusive. All vehicles subject to prior sale. Please verify any informa Please confirm the accuracy of the included equipment by calling us prior to purchase.
Manufacturer's Suggested Retail Price. Excludes options; Dealer sets actual selling price. Tax, Title and Tags not included in vehicle prices shown and must be paid by the purchaser. While great effort is made to ensure the accuracy of the information on this site, errors do occur so please verify information with a customer service rep. This is easily done by calling us at (813) 337-6616 or by visiting us at the dealership.
**With approved credit. Terms may vary. Monthly payments are only estimates derived from the vehicle price with a 72 month term, 5.9% interest and 20% downpayment.
*Number of views in last 30 days
† Based on 2015 EPA mileage ratings. Use for comparison purposes only. Your actual mileage will vary depending on how you drive and maintain your vehicle.
You don't have any saved vehicles!
Look for this link on your favorites:
Once you've saved some vehicles, you can view them here at any time.
(813) 337-6616Call Now
103 E. Fowler Ave • Tampa, FL 33612Get Directions
Open Today! Sales: 9am-6pm
Service: Closed
Parts: Closed


text:
Hi Everyone. It's me, Kevin Monahan. I'm the new Content and Community Lead for Premiere Pro and After Effects. I do all the documentation and related community content, like Help, tutorials, and articles, for these products. I also manage the After Effects and Premiere Pro communities, so you should see me out on the forums helping out. Stay tuned to this space for more information about Premiere Pro, After Effects and the community which surrounds them.
If you have a topic that you'd like to see me blog about, or if you see some outstanding tutorials or other related info, please let me know. My e-mail is kmonahan – AT – adobe.com.


text:
Questions about debt? Post them in our Ask the Community Forum to hear how others like you are managing their plans, sticking to their budgets, and working toward becoming debt free.
Have a financial question and want CareOne's advice? Our experts are available to answer your questions and offer support and advice as you work your way to a debt free life.


text:
In real life im mixing, and composing music. You can look me up in google or on myspace, just search for Zoxfeld. Modding stalker is my hobby, I wanted something different, so I formed a team and we are working on a stalker which pleases our expectations. Check our homepage (dezowave.com) to find more information about us, and our work, also don't forget to check on us on youtube :) (youtube.com/dez0wave)
The member you are trying to view has set their account to private. Only friends of this member are able to view their details.
Continue browsing the member list, to find the profile you are after.


text:
|System: X360, PS3, PC
|Review Rating Legend
|Dev: EA DICE
|1.0 - 1.9 = Avoid
|4.0 - 4.4 = Great
|Pub: Electronic Arts
|2.0 - 2.4 = Poor
|4.5 - 4.9 = Must Buy
|Release: July 9, 2009
|2.5 - 2.9 = Average
|5.0 = The Best
|Players: 2-24 (Online)
|3.0 - 3.4 = Fair
|ESRB Rating: Teen
|3.5 - 3.9 = Good
Because Battlefield 1943 is made by DICE, it implements the Frostbite engine used in Battlefield: Bad Company. That means persistent destructibility of environments is an important tactic. Blowing out building walls to remove cover, laying vegetation low for a better view, and destroying fuel dumps to take out squads of enemies are important aspects to winning the game. Unfortunately, it is painfully apparent and strange that many objects are unable to be destroyed.
Many times, player tactics will be frustrated by structures that simply won't collapse and weapon types that can't cut into objects they probably should be able to. That being said, if everything was made to be destructible, eventually the maps would break down to such a point mid-battle that they wouldn't be fun. As such, I respect the decision by DICE to limit destructibility. Still, the inconsistencies are apparent and often maddening.
A few more problems I encountered are also worth mentioning. For starters, forming squads of friends to head online and connecting to servers is often impossible; getting frequently kicked from games seems to be part of the experience. A ticker at the bottom of the title screen addresses these issues, claiming that new servers are being added and that daily maintenance at 2 AM PST are fixing the problems. Still, since there is no single-player component, not being able to play due to bad coding is a real bone of contention. Also, there seems to be a glitch with the auto-save feature. Every time I exit out of the game, all of my ranks accrued during play are lost. While this has no bearing on gameplay, it does frustrate my ability to collect certain in-game accolades. It should be noted that this issue has not cropped up for other players I know (I'll try re-downloading the title to see if that solves the issue).
It is also difficult to kill players. I would like to see more one-shot kills implemented. Too often, it takes three to four shots to bring down a player even with a high-powered rifle. This takes out some of the core appeal, but it by no means breaks the game. In fact, novice players will probably enjoy the "Juggernaut"-like ability to withstand damage. Finally, while vehicles are awesome, ghost-riding jeeps into buildings is an exploit that bucks the balanced trend. Players are charging enemy positions with these vehicles only to abandon them at the last second. This allows them to send an explosive, high-speed weapon at entrenched players, while keeping them on their feet unscathed, ready to mop up any survivors. I would like to see some kind of penalty for diving off a speeding vehicle introduced. If players were knocked prone and dazed for employing such a tactic, it might help balance out the exploit.
Despite a lack of depth found in other full-fledged FPS offerings (even from what's found in the Battlefield franchise itself) and a number of initial coding missteps, Battlefield 1943 is an arcade offering you really shouldn't miss. The $15 price tag and the overall quality make this a great purchase for anyone interested in shooters.
Jonathan Marx
CCC Editor / News Director
Game Features:


text:
Refine results
Keyword search
- Accessible by public transport (24)
- Bicycle rack (11)
- Bus parking (8)
- Car parking (32)
- Children's quiz available (22)
- Disabled toilets (8)
- Display on history (25)
- No dogs allowed except assistance dogs (9)
- Guided tours – ask on site for details (3)
- May close for lunch in winter, please call in advance (2)
- May close for lunch, please call in advance (6)
- Picnic area (13)
- Restaurant/café (3)
- Self service tea/coffee (8)
- Shop (21)
- Strong footwear recommended (37)
- Toilets (20)
- Visitor centre (5)
- Water bottle refill (13)
Search results
The search has returned 73 placesRefine results
Aberdour Castle and Gardens
Admire views of the Forth from what's possibly Scotland's oldest standing castle.
Antonine Wall: Bar Hill Fort
Observe the spectacular views from the highest fort on the Antonine Wall.
Antonine Wall: Bearsden Bath House
Get an insight into the everyday lives of Roman soldiers stationed on the Antonine Wall.
Antonine Wall: Croy Hill
See where Romans cut a ditch through solid rock at this Antonine Wall fort.
Antonine Wall: Dullatur
Stroll along the frontier of the Roman Empire at the site of two Antonine Wall camps.
Antonine Wall: Westerwood to Castlecary
Roam a section of the north-west frontier of the Roman Empire.
Auchagallon Cairn
Roam an ancient burial place overlooking a bay on one of Scotland's most beautiful islands.
Barochan Cross
Admire the stonework of a rare surviving cross from an early medieval kingdom.
Biggar Gasworks Museum
Enter what was one of the first small-town gasworks to open in Scotland – and among the last to close.
Blackfriars Chapel, St Andrews
Encounter a tranquil ruin amid the bustle of a busy street in this rare remnant of St Andrews' monastic past.
Blackness Castle
See for yourself why this mighty fortress is known as 'the ship that never sailed' – with its pointed stem, square stern and tall mast.
Bothwell Castle
Delve into a site that saw a great deal of action during the Wars of Independence with England. Bothwell Castle, built on a grand scale in the late 1200s, was hotly fought over.