While it might not change the nature of your arguement...
int foo (int a, int b, int c)
and int foo (int a, int b, int c, int d)
Can actually both be function prototypes in C++ code (at the same type). Which one is called depends on how many arguements are supposed (and of which type).
Copy protection blocks both legal and illegal copies. There is nothing wrong with copying a DVD, especially for backup (or active use in the case of backing up or archiving the original).
Really, it's the distribution of the copied DVDs which is illegal, something which the movie companies (and music companies in regards to CDs) generally leave out when mentioning the "terrible hackers" and their circumvention of copy-protection.
It can strike both ways, in that it's not fair to the employees to be off without pay, and not fair to an employer to pay an entire staff that isn't present. While I can understand the anger at larger companies for disregarding employees' safety, the fact is that some smaller companies could be hit extremely hard by being unstaffed but still paying wages over a prolonged (say a week) period.
Requiring your employees to show up and threatening them with firing is a different matter, however. You work the days to get the pay, but you shouldn't be required to work in the event that it's endangering your safety.
I would say that this should fall under the same categories as "unsafe working conditions" and other forms of dangerous disregard for employee safety.
Who would you call if your employer had live wires open on a wall, dangerous chemicals out in the open, possible fumes dangers? I would say that requiring the employees to go to work in hurricane situations is the same as putting them in an unsafe environment at work. I don't know about the USA, but here in Canada there are definately laws/organizations to protect workers against this, so check them out.
Furthermore, in the event that somebody is injured, I'd say that the company would be in extreme danger of having their asses sued off. This is regardless of whether you're at work, or on the way to. Requiring that employees come to work during possibly life-endangering disasters is a good way to be sued. In this case, I'd say that a court would very likely go with the plaintiff, as it's very hard to explain off this type of endangerment to anyone.
Yes, but how long should they carry the logs. In good circumstances a DDOS attack or heavy spammage would be detected by a weekly log. I'm getting that they (the feds) wanted logs kept around a fair bit longer though.
Beware of heating them or causing them to burn though. In a small room (i.e. apartment, dorm, etc) they can possibly release enough CO2 if combusted to be dangerous.
Just a thought... the battery is probably a good thing to remove but if the caps still have any juice in them, wouldn't the most likely thing for them to short either be themselves, or the connected path (which won't overvolt as the cap won't be any more than any connected circuitry can take anyhow).
Unless you're really unlucky it should be ok. I just cleaned up a computer lab which had a heavy roof leak overnight. We had some dead CD-ROMs, and 4 keyboards which didn't work quite right. The computers themselves were fine after drying for several weeks, and even the monitors (some of which the leak was right over and thus soaked nicel) were OK - and they've got much nicer sized capacitors than your standard mobo.
I might leave off the PSU though, they're fairly cheap to replace and I wouldn't want to soak down one of them...
Which is why it's probably a good thing that I don't have to actually chart my hours, as well as spending enough time moving between locations that few people wonder at my lunch being slightly extended - or working in the building late.
Of course, the best lunch extensions are when the boss takes myself and fellow techs out. It's one of the few times we all get together to discuss/argue stuff... lunch is paid for, and tends to go a little longer than my usual alloted breaktime as well.
With most bosses I've had, what counts is results, and maybe it's just here (I'm Canadian) but most are fairly aware of an employees' work too.
For me, it's dependant. I'm not uncommon (in fact lately it's been quite common) for me to burn a lunch-hour still working on something, or end up working late.
When a time comes that I need a break for some reason or other though, I don't feel too bad about letting my lunch hour go an extra 10-15, or reading slashdot in my spare compile moments. As long as my unpaid overtime is in excess of my paid slack-time... no guilt here.
Well, for me it's always depended on the type of stress/pressure. An important piece of software that needs to work, a deadline, coding or decoding some obscure language idiosyncrasies - no problem.
Having somebody walk up to me and immediately grill me on something (say a blonde hair on my shoulder)... temporary freeze-up.
As far as life goes though, I've tended to be a "prepare for the worst, hope for the best" type of guy. I expect that things probably won't go my way, and prepare the following:
a) How I would react under certain bad situations
b) How the other persons involved might react (and my reaction to their reaction)
c) Countermeasures and contingency plans
So really, one of the more unpleasant types of stress is the "oh my crap it's just happened right now" variety. The good thing is that these are very trying but usually short-lived
Stress works well with goals as well. I can definately stress on something knowing that I have a given problem that I can solve, or it will be over by a certain amount of time. Having no known end to a problem (relationship, unemployment, etc) is probably the worst type of stress.
Learned this the first time I had a disk array fail and had to restore from backup. I don't remember where I found it, probably in the LILO documentation somewhere.
Indeed, you would likely be on the right track with this and find what you need... but for those that don't know, check/etc/lilo.conf
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda2
# Specific LILO OS options
image=/path/to/kernel #usually/vmlinuz
label=Linux
read-only
So Mr. High-and-mighty parent before you seems a bit off himself. You see, the kernel doesn't really need to know where the root partition is (it should be mounted when you compile the kernel, as per/etc/fstab). However, the boot loader (generally lilo/grub) does need to know, and just by knowing lilo and seeing the comments or samples in lilo.conf your average admin could figure *that* one out...
Now, it seems to me that I've forgotten a bit about quotas. I'll have to go read up on that, I'd expect to have it down again in about, oh... 30-50 minutes.
For any linux admin, if you stopped learning when you finished your course (or started a job), then you're probably not a great admin.
Nobody "knows it all." You might know enough to get the job done, but there are almost endless avenues which one can explore to enhance that knowledge (get the job down better, faster, or in a more automated fashion). If anything, I've learned more/faster since I took up my primary SysAdmin-style job.
Also, if you can handle stress... the fastest way to learn how something works is to have it not work. I've speed-learned any number of things when an odd problem came up (and there have been some very unusual ones).
So really, a quick course will get you quickly started, and fill in some of the basics that might require some personal stumbling. There's enough new to learn and enough personal habits to develop that for most people, as long as you're willing to realize that there is more to learn and go for it.
Once you've got your basic CLI args, config files, etc... you can always move into learning more about BASH scripts, PERL, new applications, and various other avenues (and let us not forget, cool new games, of course).
You wouldn't want to be screwing around and experimenting with dual booting the home Windows box and risking the wife's Christmas card list and the kids' term papers.
Which is why I used a spare PC, and others I know picked up cheap used ones. You don't need superduper hardware to run 'nix as a server, and in fact the most expensive part is often the monitor. In fact, starting a new PC from scratch is a bit easier and has its own benefits - mainly that once your down, you have a spare machine to use as a personal NAT/FTP/webserver, etc etc.
I got started in 'nix when I built my own cheapee webserver on a P200 I had laying around. You can pick one up in the buy-and-sell for peanuts, or if you want a desktop a P2/400/w 128MB+ (256 recommended) will do just fine.
I used to work in a company branch which repackaged software (with a custom packager) after testing it against existing base apps. For example, if a new PeopleSoft application was coming in, we had images of the 4-5 most common desktops/hardware, and the app would be installed on all. Any existing apps breaking or errors in the new app were to be noted and hopefully fixed. This would be back in the win9x days, so DLL-hell was still common.
Of all the culprits for incompatability or causing problems, PeopleSoft apps were the worst. In fact, I used to dread a new PeopleSoft app since often enough if it wasn't killing an existing application, it was just not behaving as expected. Win2k/WinXP have likely solved any DLL conflict issues, but I'd still hate to be the one QA testing a PeopleSoft app in general...
Indeedy. Back in the days when I was but a measly VB coder (yes, I know I know, this was many years ago) - I actually had a fairly decent 3d program working using.... D3D. Now the D3D stuff wasn't actually supported for VB back then, there was a 3rd-party module which made interfaces with the API rather easy though (I believe it was made by some french dude, though the name long escapes me now). In the latter stages, I also incorporated some amount of OpenGL support into my renderer.
Now, even with a rather undocumented API and a non-supported module, the D3D stuff was just plain easier. In fact, it was too easy, given that I could code a 3d app in VB without truly understanding some of the more intrinsic details of how the APIs/D3D worked
Of course, the more people using it and putting up samples, etc... the more other people can pick it up.
Nowadays I've been getting more into OpenGL, though recently I've been sidetracked. Documentation is still a bit sketchy at times, but I've coded some basic GL C++ apps. Obviously, there's no D3D or DirectX in general for Linux. After I understand some more about Mesa and GL though, I'll probably move to SDL which is supposed to be similar.
The true strength that I see is that there are a lot of people willing to contribute, a lot of existing games/etc that are open-source for me to pick apart, and of course GL runs on 'nix and windows (as well as I'd assume Mac).
Perhaps privacy... although truly with the current state of wireless security for the average person the concept may be mutually exclusive to running a wireless net.
I do not doubt that the Uni blocks or monitors connections. Some things that come to mind are p2p, pr0n, and other materials that the uni might deem "objectionable." If they're regulating their airwaves (in an unregulated spectrum at that) then sure as tootin they're probably regulating their internet...
Perhaps we need some sort of dummy moderation message that doesn't affect score, but does allow people to register their agreement/disagreement with the opinions of the statement
Why moderate though? If you agree or disagree, wouldn't it be better to reply and state your reasons. If you worried about personal karma burn, post AC.
I have a few points and a fairly decent position to do so from. In college, we had some good teachers, some bad ones, and some average ones. One of the best, a former IT Admin from a large company with a passion for both teaching and computing (but much less teaching credentials than computing, I believe). One of the worst, a prof who majored in English and non-IT courses and couldn't understand the course well enough to teach it. The guy actually was sitting in on our C++ courses in order to learn for teaching it in following semesters.
Not all people in a given profession can teach it, but not everyone with a teaching degree can teach all courses.
Now, I work (and incidentally am posting from) in schools. I'm a tech not a teacher, but obviously interact a fair bit with the staff and see how things go.
We actually have a lot of good teachers here, but one of the problems I see is that they are overworked and misplaced. You get a guy who is great at teaching subject X also having to teach subject Y (which he isn't great at teaching), because budget limitations don't allow another teacher for Y.
The other thing that astounds me is teachers with poor grammatical and/or spelling skills. Yes, they're not teaching english, but doesn't it set a poor example for students when the teachers can't spell? Support requests have some abominable spelling errors, many which are common (and I believe should be well known to teachers) and others which are just.. well... kinda dumb.
I'm hoping that when I have children ready for school... the teachers will be able to spell, and the "system" will exist to teach rather than sell books and promote cola brands...
I installed Cedaga via dpkg (Debian) without problems. Using "Cedega/path/to/some.exe" works just fine, getting all my apps/games to work doesn't of course but actually running Cedega hasn't been a problem.
Check ~/.transgaming/config or something similar. Email me if you need help, but right now I haven't yet installed wineX again (probably by tomorrow)
And even if the game is supported, your hardware might not be. Two machines off the same build, one is an Epia-M and the other an Athlon. Epia works quite nicely with linux games and GL acceleration. Will *not* run windows games at all. Some works very nicely for menus etc but anything rendered does not show up.
Athlon with the NVidia card, everything works fine for some games that just don't work on the Epia.
I used an image from the Epia to setup the Athlon, so except for the kernel modules and XF86Config for the different video cards all is virtually the same. I could expect games to behave like crap, but the difference in running at all seems suspect with Cedega.
I do still have a TG subscription for the main machine, but I really with I could get my portable to run the windows stuff as well (I am not dual-booting it)
It's not about where he criminally infringed so much as from whom the "piracy" took place though. I seriously doubt that the US would have intervened if it were a company without vested US interested that had been "infringed" upon.
There aren't really any "magical" powers in this one, at least in the sense of your traditional fantasy spells etc. The "evil government" "unlikely heroes", "earth nearing destruction" "main bad guy" themes are all basic to many other movies as well.
The problem with FFTSW was not that it wasn't established, it was that it was a sci-fi futuristic "alien menace" type movie rather than a Fantasy type one. Your typical FF tends to have elements such as:
A mix of high/low technology. For some reason swords tend to go alongside nuclear reactors.
Magic. Not special superhuman ability, but magic. Summons are a big thing too in latter FFs.
Main characters generally seem to have some form of identity crisis and go off at some point.
Of course, there are many others. But really FFTSW was an animated sci-fi movie with some FF named characters, guards that looked Shinra-like, and a FF tag. If you changed the guards, the title, and perhaps renamed Cid nobody would likely associate with the FF game series.
As a happy fan of FF games since the original (US) SNES release... I've a strong attachment to them and squaresoft (barring FFX2 which was a fanboy tribute).
Yes, but unless the patent laws are fixed, then somehow I think innovation is going to suffer. It's quite hard to come up with something new and incredible when either a concept patent or a component patent makes the idea completely unsalable/unprofitable before it even gets off the ground.
I hate to say it, but it might end back home. Basically once the local economy has been so badly undercut, either minimum wage will drop terribly or the resulting depression will mean that your average IT worker will hire off for some Doritos and Udon as a salary...
I'm not entirely joking either... the economy does have a stress point. When reached things will either cycle back to square one or explode....
Slashdot Mirror
While it might not change the nature of your arguement...
int foo (int a, int b, int c)
and
int foo (int a, int b, int c, int d)
Can actually both be function prototypes in C++ code (at the same type). Which one is called depends on how many arguements are supposed (and of which type).
Copy protection blocks both legal and illegal copies. There is nothing wrong with copying a DVD, especially for backup (or active use in the case of backing up or archiving the original).
Really, it's the distribution of the copied DVDs which is illegal, something which the movie companies (and music companies in regards to CDs) generally leave out when mentioning the "terrible hackers" and their circumvention of copy-protection.
It can strike both ways, in that it's not fair to the employees to be off without pay, and not fair to an employer to pay an entire staff that isn't present. While I can understand the anger at larger companies for disregarding employees' safety, the fact is that some smaller companies could be hit extremely hard by being unstaffed but still paying wages over a prolonged (say a week) period.
Requiring your employees to show up and threatening them with firing is a different matter, however. You work the days to get the pay, but you shouldn't be required to work in the event that it's endangering your safety.
I would say that this should fall under the same categories as "unsafe working conditions" and other forms of dangerous disregard for employee safety.
Who would you call if your employer had live wires open on a wall, dangerous chemicals out in the open, possible fumes dangers? I would say that requiring the employees to go to work in hurricane situations is the same as putting them in an unsafe environment at work. I don't know about the USA, but here in Canada there are definately laws/organizations to protect workers against this, so check them out.
Furthermore, in the event that somebody is injured, I'd say that the company would be in extreme danger of having their asses sued off. This is regardless of whether you're at work, or on the way to. Requiring that employees come to work during possibly life-endangering disasters is a good way to be sued. In this case, I'd say that a court would very likely go with the plaintiff, as it's very hard to explain off this type of endangerment to anyone.
Yes, but how long should they carry the logs. In good circumstances a DDOS attack or heavy spammage would be detected by a weekly log. I'm getting that they (the feds) wanted logs kept around a fair bit longer though.
Beware of heating them or causing them to burn though. In a small room (i.e. apartment, dorm, etc) they can possibly release enough CO2 if combusted to be dangerous.
Just a thought... the battery is probably a good thing to remove but if the caps still have any juice in them, wouldn't the most likely thing for them to short either be themselves, or the connected path (which won't overvolt as the cap won't be any more than any connected circuitry can take anyhow).
Unless you're really unlucky it should be ok. I just cleaned up a computer lab which had a heavy roof leak overnight. We had some dead CD-ROMs, and 4 keyboards which didn't work quite right. The computers themselves were fine after drying for several weeks, and even the monitors (some of which the leak was right over and thus soaked nicel) were OK - and they've got much nicer sized capacitors than your standard mobo.
I might leave off the PSU though, they're fairly cheap to replace and I wouldn't want to soak down one of them...
Which is why it's probably a good thing that I don't have to actually chart my hours, as well as spending enough time moving between locations that few people wonder at my lunch being slightly extended - or working in the building late.
Of course, the best lunch extensions are when the boss takes myself and fellow techs out. It's one of the few times we all get together to discuss/argue stuff... lunch is paid for, and tends to go a little longer than my usual alloted breaktime as well.
With most bosses I've had, what counts is results, and maybe it's just here (I'm Canadian) but most are fairly aware of an employees' work too.
For me, it's dependant. I'm not uncommon (in fact lately it's been quite common) for me to burn a lunch-hour still working on something, or end up working late.
When a time comes that I need a break for some reason or other though, I don't feel too bad about letting my lunch hour go an extra 10-15, or reading slashdot in my spare compile moments. As long as my unpaid overtime is in excess of my paid slack-time... no guilt here.
Well, for me it's always depended on the type of stress/pressure. An important piece of software that needs to work, a deadline, coding or decoding some obscure language idiosyncrasies - no problem.
Having somebody walk up to me and immediately grill me on something (say a blonde hair on my shoulder)... temporary freeze-up.
As far as life goes though, I've tended to be a "prepare for the worst, hope for the best" type of guy. I expect that things probably won't go my way, and prepare the following:
a) How I would react under certain bad situations
b) How the other persons involved might react (and my reaction to their reaction)
c) Countermeasures and contingency plans
So really, one of the more unpleasant types of stress is the "oh my crap it's just happened right now" variety. The good thing is that these are very trying but usually short-lived
Stress works well with goals as well. I can definately stress on something knowing that I have a given problem that I can solve, or it will be over by a certain amount of time. Having no known end to a problem (relationship, unemployment, etc) is probably the worst type of stress.
How the kernel knows where the root partition is.
/etc/lilo.conf
/vmlinuz
/etc/fstab). However, the boot loader (generally lilo/grub) does need to know, and just by knowing lilo and seeing the comments or samples in lilo.conf your average admin could figure *that* one out...
Learned this the first time I had a disk array fail and had to restore from backup. I don't remember where I found it, probably in the LILO documentation somewhere.
Indeed, you would likely be on the right track with this and find what you need... but for those that don't know, check
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda2
# Specific LILO OS options
image=/path/to/kernel #usually
label=Linux
read-only
So Mr. High-and-mighty parent before you seems a bit off himself. You see, the kernel doesn't really need to know where the root partition is (it should be mounted when you compile the kernel, as per
Now, it seems to me that I've forgotten a bit about quotas. I'll have to go read up on that, I'd expect to have it down again in about, oh... 30-50 minutes.
For any linux admin, if you stopped learning when you finished your course (or started a job), then you're probably not a great admin.
Nobody "knows it all." You might know enough to get the job done, but there are almost endless avenues which one can explore to enhance that knowledge (get the job down better, faster, or in a more automated fashion). If anything, I've learned more/faster since I took up my primary SysAdmin-style job.
Also, if you can handle stress... the fastest way to learn how something works is to have it not work. I've speed-learned any number of things when an odd problem came up (and there have been some very unusual ones).
So really, a quick course will get you quickly started, and fill in some of the basics that might require some personal stumbling. There's enough new to learn and enough personal habits to develop that for most people, as long as you're willing to realize that there is more to learn and go for it.
Once you've got your basic CLI args, config files, etc... you can always move into learning more about BASH scripts, PERL, new applications, and various other avenues (and let us not forget, cool new games, of course).
You wouldn't want to be screwing around and experimenting with dual booting the home Windows box and risking the wife's Christmas card list and the kids' term papers.
/w 128MB+ (256 recommended) will do just fine.
Which is why I used a spare PC, and others I know picked up cheap used ones. You don't need superduper hardware to run 'nix as a server, and in fact the most expensive part is often the monitor. In fact, starting a new PC from scratch is a bit easier and has its own benefits - mainly that once your down, you have a spare machine to use as a personal NAT/FTP/webserver, etc etc.
I got started in 'nix when I built my own cheapee webserver on a P200 I had laying around. You can pick one up in the buy-and-sell for peanuts, or if you want a desktop a P2/400
I used to work in a company branch which repackaged software (with a custom packager) after testing it against existing base apps. For example, if a new PeopleSoft application was coming in, we had images of the 4-5 most common desktops/hardware, and the app would be installed on all. Any existing apps breaking or errors in the new app were to be noted and hopefully fixed. This would be back in the win9x days, so DLL-hell was still common.
Of all the culprits for incompatability or causing problems, PeopleSoft apps were the worst. In fact, I used to dread a new PeopleSoft app since often enough if it wasn't killing an existing application, it was just not behaving as expected. Win2k/WinXP have likely solved any DLL conflict issues, but I'd still hate to be the one QA testing a PeopleSoft app in general...
Indeedy. Back in the days when I was but a measly VB coder (yes, I know I know, this was many years ago) - I actually had a fairly decent 3d program working using.... D3D. Now the D3D stuff wasn't actually supported for VB back then, there was a 3rd-party module which made interfaces with the API rather easy though (I believe it was made by some french dude, though the name long escapes me now). In the latter stages, I also incorporated some amount of OpenGL support into my renderer.
Now, even with a rather undocumented API and a non-supported module, the D3D stuff was just plain easier. In fact, it was too easy, given that I could code a 3d app in VB without truly understanding some of the more intrinsic details of how the APIs/D3D worked
Of course, the more people using it and putting up samples, etc... the more other people can pick it up.
Nowadays I've been getting more into OpenGL, though recently I've been sidetracked. Documentation is still a bit sketchy at times, but I've coded some basic GL C++ apps. Obviously, there's no D3D or DirectX in general for Linux. After I understand some more about Mesa and GL though, I'll probably move to SDL which is supposed to be similar.
The true strength that I see is that there are a lot of people willing to contribute, a lot of existing games/etc that are open-source for me to pick apart, and of course GL runs on 'nix and windows (as well as I'd assume Mac).
The rooms aren't really big enough to need wireless anyway, though.
Yeah, but if you run wired to the bathroom then the door doesn't close properly...
Too much money to burn?
Perhaps privacy... although truly with the current state of wireless security for the average person the concept may be mutually exclusive to running a wireless net.
I do not doubt that the Uni blocks or monitors connections. Some things that come to mind are p2p, pr0n, and other materials that the uni might deem "objectionable." If they're regulating their airwaves (in an unregulated spectrum at that) then sure as tootin they're probably regulating their internet...
Perhaps we need some sort of dummy moderation message that doesn't affect score, but does allow people to register their agreement/disagreement with the opinions of the statement
Why moderate though? If you agree or disagree, wouldn't it be better to reply and state your reasons. If you worried about personal karma burn, post AC.
They might as well start up religion.slashdot.org and flame on.
:-)
Would the icon then be a burning bush? How appropriate would that be?
I have a few points and a fairly decent position to do so from. In college, we had some good teachers, some bad ones, and some average ones. One of the best, a former IT Admin from a large company with a passion for both teaching and computing (but much less teaching credentials than computing, I believe). One of the worst, a prof who majored in English and non-IT courses and couldn't understand the course well enough to teach it. The guy actually was sitting in on our C++ courses in order to learn for teaching it in following semesters.
Not all people in a given profession can teach it, but not everyone with a teaching degree can teach all courses.
Now, I work (and incidentally am posting from) in schools. I'm a tech not a teacher, but obviously interact a fair bit with the staff and see how things go.
We actually have a lot of good teachers here, but one of the problems I see is that they are overworked and misplaced. You get a guy who is great at teaching subject X also having to teach subject Y (which he isn't great at teaching), because budget limitations don't allow another teacher for Y.
The other thing that astounds me is teachers with poor grammatical and/or spelling skills. Yes, they're not teaching english, but doesn't it set a poor example for students when the teachers can't spell? Support requests have some abominable spelling errors, many which are common (and I believe should be well known to teachers) and others which are just.. well... kinda dumb.
I'm hoping that when I have children ready for school... the teachers will be able to spell, and the "system" will exist to teach rather than sell books and promote cola brands...
I installed Cedaga via dpkg (Debian) without problems. Using "Cedega /path/to/some.exe" works just fine, getting all my apps/games to work doesn't of course but actually running Cedega hasn't been a problem.
Check ~/.transgaming/config or something similar. Email me if you need help, but right now I haven't yet installed wineX again (probably by tomorrow)
And even if the game is supported, your hardware might not be. Two machines off the same build, one is an Epia-M and the other an Athlon. Epia works quite nicely with linux games and GL acceleration. Will *not* run windows games at all. Some works very nicely for menus etc but anything rendered does not show up.
Athlon with the NVidia card, everything works fine for some games that just don't work on the Epia.
I used an image from the Epia to setup the Athlon, so except for the kernel modules and XF86Config for the different video cards all is virtually the same. I could expect games to behave like crap, but the difference in running at all seems suspect with Cedega.
I do still have a TG subscription for the main machine, but I really with I could get my portable to run the windows stuff as well (I am not dual-booting it)
It's not about where he criminally infringed so much as from whom the "piracy" took place though. I seriously doubt that the US would have intervened if it were a company without vested US interested that had been "infringed" upon.
The problem with FFTSW was not that it wasn't established, it was that it was a sci-fi futuristic "alien menace" type movie rather than a Fantasy type one. Your typical FF tends to have elements such as:
- A mix of high/low technology. For some reason swords tend to go alongside nuclear reactors.
- Magic. Not special superhuman ability, but magic. Summons are a big thing too in latter FFs.
- Main characters generally seem to have some form of identity crisis and go off at some point.
Of course, there are many others. But really FFTSW was an animated sci-fi movie with some FF named characters, guards that looked Shinra-like, and a FF tag. If you changed the guards, the title, and perhaps renamed Cid nobody would likely associate with the FF game series.As a happy fan of FF games since the original (US) SNES release... I've a strong attachment to them and squaresoft (barring FFX2 which was a fanboy tribute).
Yes, but unless the patent laws are fixed, then somehow I think innovation is going to suffer. It's quite hard to come up with something new and incredible when either a concept patent or a component patent makes the idea completely unsalable/unprofitable before it even gets off the ground.
I hate to say it, but it might end back home. Basically once the local economy has been so badly undercut, either minimum wage will drop terribly or the resulting depression will mean that your average IT worker will hire off for some Doritos and Udon as a salary...
I'm not entirely joking either... the economy does have a stress point. When reached things will either cycle back to square one or explode....