- Reduces personal catastrophic financial risk in starting a new small business or non-profit. - Supports people obtaining an education. - Supports people who are not able to work (invalid, disabled, etc.) - Provides a "floor" of survivability for people who *are* employed but at sub-living-wage. - Encourages finding a job, because it doesn't go away when you do obtain a job. Said another way, it benefits everyone, not just those who have a job. - Puts more power in employees' hands when it comes to bargaining for wages, health and safety, etc. The old-school way of handling this is unionizing, which can still work as well, but a UBI improves the employees' negotiating position without the need for collective contracts or mass strikes. - Done properly, could replace *dozens* of complex, expensive government assistance programs (unemployment, welfare, social security, etc.), improving government efficiency and effectiveness. - Would encourage legal migration, as only citizens would enjoy the benefits. - Would support families where one partner wants to leave the workforce (fully or partially) to care for children or elderly relatives. - A UBI *could* be scaled based on age (making it a better possible replacement for Social Security) or past income history (making it more viable as a replacement for unemployment insurance).
Yes, there *are* people who would never lift a finger again to be useful to society in any way if they could instead survive on a UBI. But I believe the vast majority would use that spare time to improve themselves (education, job skills, etc.), to improve their communities (volunteering, activism), and to hold their ground for the *right* job.
Also, while I don't think it should be means-tested (for the above reasons), a UBI could provide extra financial incentive for people who *are* showing that they are claiming other income during the same month. Or those who are in school and making good grades. Or those who can show time volunteered at a non profit. Or simply based on age.
Three other points:
- Even if someone sat on their butt and collected their UBI for the rest of their life, they would be spending their UBI, which does much more to increase economic activity then a rich guy sticking those same dollars into stock market speculation.
- A "guaranteed job" would be far too expensive to manage for whatever useful output the recipients give in labor. This isn't the 1930s, we don't need a bunch of unskilled government workers building railroads and dams by hand. So we would have them doing something fairly useless, while we would have to also provide all of the oversight to manage the workforce, enforce participation/eligibility, handle health and safety risks, provide training, etc.
- Neither form of assistance makes sense unless it is paired with universal healthcare.
As someone who has been involved in fashion, art, and glamour photography for some time, I find the article's dismissal of cosmetology licensing to be careless and poorly researched.
Applying makeup is a licensed activity because of significant health and safety issues related to hygiene and proper use of certain products (such as latex, for example, as used in the movie and theater industries). You could very literally lose an eye, go into anaphylactic shock, or get a nasty rash because some village idiot decided to play makeup artist and didn't know what they were doing. People doing this really DO need to know what they are doing.
Likewise, bartender licenses are less about memorizing obscure drink recipes and more about properly working within the law around alcoholic drinks and potentially inebriated customers. These licenses are not a burden to obtain (working with a non-profit art gallery, we obtained them for some of our board members so we could legally serve wine at our shows), and they are a serious intervention to help cut down on drunk driving, alcohol poisoning, and underage drinking.
Here in Texas, the licensing agency recently got rid of mandatory licensing of interior designers (my wife is one) and talent/modeling agencies (which, again, I'm familiar with through photography). The result is a total disaster in both fields. To do an effective job, interior designers need to understand building codes, proper construction techniques, when to call in a structural engineer, permitting, blueprints and drawings, special laws around commercial furniture, etc. But without a license, anyone who watches a bunch of HGTV and thinks they are the next Joanna Gaines can go represent themselves as a designer, and homeowners and businesses *don't know what they don't know*. And in the talent agency world, particularly in modeling, there is a HUGE problem of outright scams, not to mention sketchy guys claiming to "manage" models or singers, who act more like wannabe pimps.
So yeah, maybe licensing can be a bit of a protection racket in some industries, but it's way too easy to deride someone else's education from a place of ignorance about the service they are performing and the risks involved in the decisions they make.
(Also, make no mistake, this article isn't about makeup or pints of lager, it's about an ongoing, long-term, well-funded dispute about what the differences should be between a doctor and a nurse practitioner. The arguments about other industries are merely window-dressing.)
I started using Vue this year. I evaluated React but I just couldn't enjoy the JSX syntax. Angular 2 had just come out and I found it to be far too obtuse, too far from "the metal." I briefly experimented with Riot, but it was losing IE11 compatibility too fast.
Vue hit the sweet spot for me -- the ramp-up was easy, the code and API have a small but powerful footprint, it works well either interpreted in-browser or compiled via webpack, the Chrome dev tools are great, and I didn't have to learn the entire ecosystem (Vue, Vuex, Axios, etc.) to become productive. Coding single-file components reminds me of the good old days of writing server-side ASP.NET controls -- markup and script are separate, the lifestyle is simple to grok. The framework just does one thing--it handles the DOM update/manipulation details, allowing me to focus on behavior and state. I also like that the vast majority of my Vue code isn't really "vue," it's just plain HTML and JavaScript, so whatever comes next (web components, etc.), the transition will be much less painful than if I were using a more opinionated framework.
I read the bill. Disclosure of security threats is completely VOLUNTARY for individuals, private companies, local/state governments, utilities, etc. ("non-Federal entities"). There is no mandate. There are no demands for back doors. There is no provision for unfettered sharing of network traffic, only a mechanism for voluntary sharing of information about detected threats. Even then, they must be careful to strip away any unrelated personal information.
I'm a BIG believer in personal privacy and 4th Amendment protections, but I'm a little disappointed by the "Chicken Little" rhetoric about this bill compared to what is actually contains.
Tax breaks by local or state governments to win construction projects NEVER make sense, and should be outlawed as a form of unfair treatment under the law.
Small businesses hire FAR more employees and put FAR more back into the local economy than large companies who have the political clout to win abatements. Every tax abatement won by a company deciding to do business somewhere is an effective tax INCREASE on every other business and resident of that jurisdiction.
When a company moves into town, they are taking advantage of the roads, sewers, fire and police protection, schools, and other appurtenance of civilization, and they should pay their fair share for that infrastructure.
Speaking specifically about data centers -- they hire relatively few people, take up a large land mass, add stress to the local electrical grid, create buildings that drive down surrounding land values (who wants to live next to a windowless building with huge air conditioners?), etc. etc.
I'm not saying they are "bad" neighbors, but they certainly don't deserve a ticker tape parade, and they should pay their fair taxes like anyone else.
Well said. And while I agree it shouldn't have been done, I'm significantly LESS concerned with the *government* looking at *government* computers used by *government* employees than I am with the government spying on people without probable cause who are *not* their employees and on computers that they do *not* own.
One corollary of Metcalfe's Law is that, since most people are cheap, it is difficult to create suitable network effects based solely on users who are willing to pay a fee to participate.
I would pay for an ad-free, censorship-free Facebook-style service, but most of my friends and family wouldn't.
The one job interview I went on where I could put that skill to use showed me why I *wouldn't* want such a job.
The issue wasn't the language per se, it was the fact that most companies still using COBOL are also trapped in chronically underfunded and undervalued IT departments, holding old machines and apps together with bailing wire and duct tape.
Congresscritters and the bureaucrats who make the decisions are completely incapable of understanding transmission rates and why 4 vs. 10 matters in the real world.
Instead, we should just tell them that any definition of "broadband" should at *least* pass the smell test of meeting the recommendations for Netflix's service, which is 5Mbps for HD and 25Mbps for Ultra HD.
A Netflix stream of course isn't a standard unit of measure, but it's at least an analogy they might understand.
This is one of the most comfy chairs I own, reproductions are affordable, and they are gorgeous. The recline is comfortable while still allowing non-desk work (the Eames is *too* reclined for my taste), the arms are wide enough to curl up in, and the back is high enough to support your head. Many reproductions allow adjusting the recline tension.
You'll need to supply your own power and a stand for the laptop.
1. Integrate the documentation with the application. Treat it like code rather than as a separate document.
2. When new features are proposed, plan them by FIRST forking and changing the documentation, THEN implement the change based on the change in the story. This not only guarantees good documentation, it ensures the developers are all on the same page about what the changes should/shouldn't do.
3. Focus documentation on the common tasks, software limitations, and side-effects. Far too much documentation wastes reams of paper telling people "to create a new widget, click the New button." If the "New button" is hard to find, difficult to click, or does something other than creating a new widget, that is a failure of the UI, not the documentation.
In my experience, the word "Enterprise" usually means a shitty piece of uselessly generic and hopelessly complex software combined with an expensive consultant team who spend 5% of their time configuring/using the software as intended and 95% of their time hacking around its limitations by glomming on little "tumor" systems to shoehorn it into your business.
I love C#. I program in it every day. It's plenty fast, and it's a great language.
However, there are two reasons I would suggest looking to another language.
First, the hottest market for gaming right now is mobile. While it's possible to compile C# for iPhone or Android using Xamarin (along with Windows and OS X), it's not exactly a native experience.
Second, C# (like O-C, C++, etc.) is a general programming language -- it's not in any way specific to the domain of game programming. So, while it's *possible* to design complex games in any modern language, you're probably going to spend *way* too much time dealing with silly stuff like tracking graphics resources and animation loops and simulated physics. You'll have a higher chance of success if you use a language and platform that is more game-specific out of the box.
I would suggest looking into Swift -- it'll give you access to the lucrative iOS market, it's C-like, and it has features that are game-specific. Sure, it's a new language it doesn't compile to Android, but by all accounts it looks like a great language with first-class support for gaming, so you can focus less on infrastructure code and more on the game.
Another option would be HTML5. Depending what sort of game you're looking to build, Javascript and HTML5 may be just the ticket, and there are a number of libraries that can abstract away browser differences and assist with the plumbing needed to make a game run.
An Samsung Galaxy S3 is almost $600 unlocked as well.
Instead, Apple should SQUASH the black market by making it easy for customers to report a device stolen. Once reported stolen, Apple should brick the phone remotely and contact the service provider to have the IMEI blacklisted.
AT&T and TMobile just started blocking blacklisted IMEIs last month. As other carriers follow suit and companies like Apple make it easier for the average consumer to make the report, thieves will eventually learn that the devices are worthless.
People actually do go to school to learn how to wrangle with international corporations, torts, contracts, etc., and the vast, vast majority of the good ones don't program on the side, or if they did, would give legal advice on an Internet forum.
This makes as little sense in the modern age as those "virtual reality" helmets we're all supposed to be using by now.
Companies like Leap are making much more advanced technology that requires nothing attached to your hand and uses motion sensors to track your hand movements with incredible precision. Comparatively, this guy's mouse-finger contraption looks as silly as Doc's brain-wave reader in BttF.
(I don't represent Leap, I just remember hearing about their tech awhile back.)
ReplayTV had a DVR many years ago with this exact feature, and they got their asses sued off by Hollywood for it (http://en.wikipedia.org/wiki/ReplayTV). The suit was never decided. It even had a feature that did the reverse, playing *only* the commercials (aka "Superbowl Mode").
But even *that* was based on earlier technology patented back in 1993 (http://www.google.com/patents/US5333091) and used in VHS machines dating about 10 years ago, maybe longer.
As a DISH subscriber, I'm happy they are finally implementing this, but they ARE going to have a fight on their hands.
Now, if only someone can invent technology to get rid of those awful graphic overlays advertising other shows/movies. And the ridiculous "OMG IT'S TOTALLY RAINING OR SOMEONE GOT ELECTED DOGCATCHER" crawls from the local news.
It's a newer camera, great mix of features (including 1080P video and GPS geo-tagging). As a professional photographer, I'm a Canon fan-boy. (Nikon is good too.)
DP Review is a great geek-compatible site for camera reviews, here's their take:
A tracking device will only help aid in recovery *after* theft, it won't prevent the theft in the first place.
Since you already likely have to carry some sort of insurance, it's cheaper to just ensure you have coverage for theft, ensure that the front wheel is locked, and keep the make / model / VIN / photo / insurance info handy in case you ever have to make a police report.
I'm speaking from experience, my scooter was stolen a few years ago -- Vespa LX-150. The insurance company cut a check, I bought a new one.
So, the juicy tax break goes to the big corporation who will bring in a few thousand jobs and treat the politicians to steak dinners. As for the thousands of small businesses who employ many times more Tennesseans than Amazon ever will, they are screwed when it comes to trying to compete with the retail giant.
This is the sort of corporate giveaway that should outright be unconstitutional.
Slashdot Mirror
In light of recent events, I am now limiting my MoviePass subscription to $0 / month.
Sad to see it go, I never expected their business model to last long term, but it was a good run... :(
A universal income has a few advantages:
- Reduces personal catastrophic financial risk in starting a new small business or non-profit.
- Supports people obtaining an education.
- Supports people who are not able to work (invalid, disabled, etc.)
- Provides a "floor" of survivability for people who *are* employed but at sub-living-wage.
- Encourages finding a job, because it doesn't go away when you do obtain a job. Said another way, it benefits everyone, not just those who have a job.
- Puts more power in employees' hands when it comes to bargaining for wages, health and safety, etc. The old-school way of handling this is unionizing, which can still work as well, but a UBI improves the employees' negotiating position without the need for collective contracts or mass strikes.
- Done properly, could replace *dozens* of complex, expensive government assistance programs (unemployment, welfare, social security, etc.), improving government efficiency and effectiveness.
- Would encourage legal migration, as only citizens would enjoy the benefits.
- Would support families where one partner wants to leave the workforce (fully or partially) to care for children or elderly relatives.
- A UBI *could* be scaled based on age (making it a better possible replacement for Social Security) or past income history (making it more viable as a replacement for unemployment insurance).
Yes, there *are* people who would never lift a finger again to be useful to society in any way if they could instead survive on a UBI. But I believe the vast majority would use that spare time to improve themselves (education, job skills, etc.), to improve their communities (volunteering, activism), and to hold their ground for the *right* job.
Also, while I don't think it should be means-tested (for the above reasons), a UBI could provide extra financial incentive for people who *are* showing that they are claiming other income during the same month. Or those who are in school and making good grades. Or those who can show time volunteered at a non profit. Or simply based on age.
Three other points:
- Even if someone sat on their butt and collected their UBI for the rest of their life, they would be spending their UBI, which does much more to increase economic activity then a rich guy sticking those same dollars into stock market speculation.
- A "guaranteed job" would be far too expensive to manage for whatever useful output the recipients give in labor. This isn't the 1930s, we don't need a bunch of unskilled government workers building railroads and dams by hand. So we would have them doing something fairly useless, while we would have to also provide all of the oversight to manage the workforce, enforce participation/eligibility, handle health and safety risks, provide training, etc.
- Neither form of assistance makes sense unless it is paired with universal healthcare.
As someone who has been involved in fashion, art, and glamour photography for some time, I find the article's dismissal of cosmetology licensing to be careless and poorly researched.
Applying makeup is a licensed activity because of significant health and safety issues related to hygiene and proper use of certain products (such as latex, for example, as used in the movie and theater industries). You could very literally lose an eye, go into anaphylactic shock, or get a nasty rash because some village idiot decided to play makeup artist and didn't know what they were doing. People doing this really DO need to know what they are doing.
Likewise, bartender licenses are less about memorizing obscure drink recipes and more about properly working within the law around alcoholic drinks and potentially inebriated customers. These licenses are not a burden to obtain (working with a non-profit art gallery, we obtained them for some of our board members so we could legally serve wine at our shows), and they are a serious intervention to help cut down on drunk driving, alcohol poisoning, and underage drinking.
Here in Texas, the licensing agency recently got rid of mandatory licensing of interior designers (my wife is one) and talent/modeling agencies (which, again, I'm familiar with through photography). The result is a total disaster in both fields. To do an effective job, interior designers need to understand building codes, proper construction techniques, when to call in a structural engineer, permitting, blueprints and drawings, special laws around commercial furniture, etc. But without a license, anyone who watches a bunch of HGTV and thinks they are the next Joanna Gaines can go represent themselves as a designer, and homeowners and businesses *don't know what they don't know*. And in the talent agency world, particularly in modeling, there is a HUGE problem of outright scams, not to mention sketchy guys claiming to "manage" models or singers, who act more like wannabe pimps.
So yeah, maybe licensing can be a bit of a protection racket in some industries, but it's way too easy to deride someone else's education from a place of ignorance about the service they are performing and the risks involved in the decisions they make.
(Also, make no mistake, this article isn't about makeup or pints of lager, it's about an ongoing, long-term, well-funded dispute about what the differences should be between a doctor and a nurse practitioner. The arguments about other industries are merely window-dressing.)
Dammit, I'm still trying to get used to Swatch "beat time"...
I started using Vue this year. I evaluated React but I just couldn't enjoy the JSX syntax. Angular 2 had just come out and I found it to be far too obtuse, too far from "the metal." I briefly experimented with Riot, but it was losing IE11 compatibility too fast.
Vue hit the sweet spot for me -- the ramp-up was easy, the code and API have a small but powerful footprint, it works well either interpreted in-browser or compiled via webpack, the Chrome dev tools are great, and I didn't have to learn the entire ecosystem (Vue, Vuex, Axios, etc.) to become productive. Coding single-file components reminds me of the good old days of writing server-side ASP.NET controls -- markup and script are separate, the lifestyle is simple to grok. The framework just does one thing--it handles the DOM update/manipulation details, allowing me to focus on behavior and state. I also like that the vast majority of my Vue code isn't really "vue," it's just plain HTML and JavaScript, so whatever comes next (web components, etc.), the transition will be much less painful than if I were using a more opinionated framework.
beer. Back to my beer.
Why do /. comments strip emoticons, especially important ones like beer?
*sigh*
$ git --version
git version 2.6.3
$ brew update
$ brew upgrade git
$ git --version
git version 2.8.1
Back to my
I read the bill. Disclosure of security threats is completely VOLUNTARY for individuals, private companies, local/state governments, utilities, etc. ("non-Federal entities"). There is no mandate. There are no demands for back doors. There is no provision for unfettered sharing of network traffic, only a mechanism for voluntary sharing of information about detected threats. Even then, they must be careful to strip away any unrelated personal information.
I'm a BIG believer in personal privacy and 4th Amendment protections, but I'm a little disappointed by the "Chicken Little" rhetoric about this bill compared to what is actually contains.
Tax breaks by local or state governments to win construction projects NEVER make sense, and should be outlawed as a form of unfair treatment under the law.
Small businesses hire FAR more employees and put FAR more back into the local economy than large companies who have the political clout to win abatements. Every tax abatement won by a company deciding to do business somewhere is an effective tax INCREASE on every other business and resident of that jurisdiction.
When a company moves into town, they are taking advantage of the roads, sewers, fire and police protection, schools, and other appurtenance of civilization, and they should pay their fair share for that infrastructure.
Speaking specifically about data centers -- they hire relatively few people, take up a large land mass, add stress to the local electrical grid, create buildings that drive down surrounding land values (who wants to live next to a windowless building with huge air conditioners?), etc. etc.
I'm not saying they are "bad" neighbors, but they certainly don't deserve a ticker tape parade, and they should pay their fair taxes like anyone else.
Well said. And while I agree it shouldn't have been done, I'm significantly LESS concerned with the *government* looking at *government* computers used by *government* employees than I am with the government spying on people without probable cause who are *not* their employees and on computers that they do *not* own.
One corollary of Metcalfe's Law is that, since most people are cheap, it is difficult to create suitable network effects based solely on users who are willing to pay a fee to participate.
I would pay for an ad-free, censorship-free Facebook-style service, but most of my friends and family wouldn't.
I took COBOL -- late 90's.
The one job interview I went on where I could put that skill to use showed me why I *wouldn't* want such a job.
The issue wasn't the language per se, it was the fact that most companies still using COBOL are also trapped in chronically underfunded and undervalued IT departments, holding old machines and apps together with bailing wire and duct tape.
Congresscritters and the bureaucrats who make the decisions are completely incapable of understanding transmission rates and why 4 vs. 10 matters in the real world.
Instead, we should just tell them that any definition of "broadband" should at *least* pass the smell test of meeting the recommendations for Netflix's service, which is 5Mbps for HD and 25Mbps for Ultra HD.
A Netflix stream of course isn't a standard unit of measure, but it's at least an analogy they might understand.
This is one of the most comfy chairs I own, reproductions are affordable, and they are gorgeous. The recline is comfortable while still allowing non-desk work (the Eames is *too* reclined for my taste), the arms are wide enough to curl up in, and the back is high enough to support your head. Many reproductions allow adjusting the recline tension.
You'll need to supply your own power and a stand for the laptop.
1. Integrate the documentation with the application. Treat it like code rather than as a separate document.
2. When new features are proposed, plan them by FIRST forking and changing the documentation, THEN implement the change based on the change in the story. This not only guarantees good documentation, it ensures the developers are all on the same page about what the changes should/shouldn't do.
3. Focus documentation on the common tasks, software limitations, and side-effects. Far too much documentation wastes reams of paper telling people "to create a new widget, click the New button." If the "New button" is hard to find, difficult to click, or does something other than creating a new widget, that is a failure of the UI, not the documentation.
In my experience, the word "Enterprise" usually means a shitty piece of uselessly generic and hopelessly complex software combined with an expensive consultant team who spend 5% of their time configuring/using the software as intended and 95% of their time hacking around its limitations by glomming on little "tumor" systems to shoehorn it into your business.
But I admit I'm a little jaded.
I love C#. I program in it every day. It's plenty fast, and it's a great language.
However, there are two reasons I would suggest looking to another language.
First, the hottest market for gaming right now is mobile. While it's possible to compile C# for iPhone or Android using Xamarin (along with Windows and OS X), it's not exactly a native experience.
Second, C# (like O-C, C++, etc.) is a general programming language -- it's not in any way specific to the domain of game programming. So, while it's *possible* to design complex games in any modern language, you're probably going to spend *way* too much time dealing with silly stuff like tracking graphics resources and animation loops and simulated physics. You'll have a higher chance of success if you use a language and platform that is more game-specific out of the box.
I would suggest looking into Swift -- it'll give you access to the lucrative iOS market, it's C-like, and it has features that are game-specific. Sure, it's a new language it doesn't compile to Android, but by all accounts it looks like a great language with first-class support for gaming, so you can focus less on infrastructure code and more on the game.
Another option would be HTML5. Depending what sort of game you're looking to build, Javascript and HTML5 may be just the ticket, and there are a number of libraries that can abstract away browser differences and assist with the plumbing needed to make a game run.
An Samsung Galaxy S3 is almost $600 unlocked as well.
Instead, Apple should SQUASH the black market by making it easy for customers to report a device stolen. Once reported stolen, Apple should brick the phone remotely and contact the service provider to have the IMEI blacklisted.
AT&T and TMobile just started blocking blacklisted IMEIs last month. As other carriers follow suit and companies like Apple make it easier for the average consumer to make the report, thieves will eventually learn that the devices are worthless.
If you don't have a lawyer, get one.
People actually do go to school to learn how to wrangle with international corporations, torts, contracts, etc., and the vast, vast majority of the good ones don't program on the side, or if they did, would give legal advice on an Internet forum.
This makes as little sense in the modern age as those "virtual reality" helmets we're all supposed to be using by now.
Companies like Leap are making much more advanced technology that requires nothing attached to your hand and uses motion sensors to track your hand movements with incredible precision. Comparatively, this guy's mouse-finger contraption looks as silly as Doc's brain-wave reader in BttF.
(I don't represent Leap, I just remember hearing about their tech awhile back.)
ReplayTV had a DVR many years ago with this exact feature, and they got their asses sued off by Hollywood for it (http://en.wikipedia.org/wiki/ReplayTV). The suit was never decided. It even had a feature that did the reverse, playing *only* the commercials (aka "Superbowl Mode").
But even *that* was based on earlier technology patented back in 1993 (http://www.google.com/patents/US5333091) and used in VHS machines dating about 10 years ago, maybe longer.
As a DISH subscriber, I'm happy they are finally implementing this, but they ARE going to have a fight on their hands.
Now, if only someone can invent technology to get rid of those awful graphic overlays advertising other shows/movies. And the ridiculous "OMG IT'S TOTALLY RAINING OR SOMEONE GOT ELECTED DOGCATCHER" crawls from the local news.
It's a newer camera, great mix of features (including 1080P video and GPS geo-tagging). As a professional photographer, I'm a Canon fan-boy. (Nikon is good too.)
DP Review is a great geek-compatible site for camera reviews, here's their take:
http://www.dpreview.com/previews/canons100/
A tracking device will only help aid in recovery *after* theft, it won't prevent the theft in the first place.
Since you already likely have to carry some sort of insurance, it's cheaper to just ensure you have coverage for theft, ensure that the front wheel is locked, and keep the make / model / VIN / photo / insurance info handy in case you ever have to make a police report.
I'm speaking from experience, my scooter was stolen a few years ago -- Vespa LX-150. The insurance company cut a check, I bought a new one.
- Facebook
- FaceTime
- NetFlix
- iBooks
- Zinio / Newsstand
- Angry Birds
Done.
So, the juicy tax break goes to the big corporation who will bring in a few thousand jobs and treat the politicians to steak dinners. As for the thousands of small businesses who employ many times more Tennesseans than Amazon ever will, they are screwed when it comes to trying to compete with the retail giant.
This is the sort of corporate giveaway that should outright be unconstitutional.