I don't think they're quite competing with directly with Walmart, but only due to the targeted demographic.
Walmart targets everyone, which usually results in more of a sway towards the lowest common denominator. Target's marketing (Target's target marketing?) is seemingly always geared towards upper middle class, or whatever makes up that income level now. It even shows in their branding. Take a look at how Target specific brands are expressed (Archer Farms, Market Pantry, etc) and compare them to their counterparts over at wally world.
Here's an excellent example of this: Starbucks embedded cafes in Target stores under the Starbucks brand. They did the exact same thing in Walmart, but ran under the Seattle's Best marquee in order to provide the lower priced option.
I actually think an entire repo of libraries is the wrong way to go. With the git model, we have however many repos acting as the source for these libraries. This repository that contains all of these submodules can then be the arbiter of which version should be included in the release.
> Yes, some will say - but this is good - centralization is bad... Well, it depends. If you can spend time to figure out who is who, then it will work for you.
And this problem doesn't exist with SVN? Sure, maybe if you are the sole publisher of all these libraries it might be ok, but with most real world examples, there exists multiple contributors. Now they need to go through you when there needs to be a specific update to that library. With git, the maintainer of the repo of libraries(submodules) just updates the specific submodule to whatever release works for their tastes.
Most of these complaints sound like an SVN user having some pain when trying to think in git.
PHP Full Stack developer. I really don't want to write a full resume out here. I'll do/ learn anything. Currently working (salary, full benefits) for a large state university where I develop their Drupal CMS, manage the codebase, interface with clients, etc. I also do work for a private company that does affiliate marketing.
I need a job that will better my career, as I fear stagnation in my current environment.
I'm familiar with API's, third party service integration, cloud setup, data migration. Is there a general catch all term for "I do web stuff"? I haven't encountered anything in my wheel house that takes more than 3-4 days to figure out. Most recent was working on an HMAC API in Symfony2 for an Angular frontend.
My last 2 months have been on 4 hours of sleep per night.
Yeah it works, but God does it suck. This has occurred out of a need to get work done, so I wonder how many others found themselves conditioned in the same way.
> I even know people who deliberately did "out and back" jumps to leap-frog over others at the same original company.
This is commonly known as a valid strategy at the place I work. It's very difficult to come in giving a shit about my code when the future of my position is a dead end.
> Doesn't this method of including dynamic data in the index.html page prevent it being served from a CDN?
if your cdn is serving static html pages then yeah probably. If it's just serving assets like images/js/css/fonts, it shouldn't be an issue since those would all be extra reqs anyway, and not "compiled" into the html.
I serve up all my angular view templates as static files (ui-router), use ng-include for dumb stuff like footer text that never changes, and rely on the API (hmac) for populating content.
Perhaps this is over opinionated, but angular seems to me to be designed so that you don't have to do ANY view templating bullshit on the server. I don't have a single angular app that hits the app server for an html template compiled by code. In fact the only thing I do serverside templating in now is drupal.
Depends on how you're using angular to inject views.
Vanilla angular views are requested, parsed, bindings added, and then presented. It's one request for the html, all the rest happens in browser.
angular ui views may be different, but according to my network panel on chrome its still one request for the template and whatever assets it brings with it.
I'm going to guess the guys meant they will preload the first view based on page state, which does indeed save a single round trip, but means nothing for any state changes that would occur after the fact. I would argue that an app which needs to micro optimize like this might not be built correctly from the get go, as you're really only saving 1 request and whatever small byte size of the content.
Please don't mess with my ability to scroll through content. Additionally, having content in between the nav breaks is infuriating, and my scroll bar is gone.
We'll pretty much take care of whatever a company needs as long as it isn't .net. We're predominately a PHP shop that deals with Magento and Drupal dev, but we also do full app development from scratch on Symfony2 or Yii, whatever fits the task the best.
We get requests for doing maint on clients old sites, migrations to new setups, and sometimes just build off little glue apps that makes peoples' lives easier around their respective offices. It's small but getting there.