You can add Aerith/Aeris back into the party manually, sure -- that doesn't mean she'll be in the STORY at all. She won't have any dialogue (aside from generic lines that EVERY character says exactly the same) and sometimes the game will crash with her in your party.
In other words you just swapped character data into your party, she's not actually "there" story-wise.
Ancestors of the Amiga you mean. Yes, Jay Miner did a fantastic job on the Atari 800XL's chipset. =)...but the best they could muster without temporal or spatial dithering or scan-line interrupt tricks was 80x192 in 16 colors. The Plus/4 could display all 121 colors onscreen at once (albeit with restrictions on how close different colors could be to eachother) without any sort of trickery.
That said, the 800XL's color palette was way better than the Plus/4's....and I'm surprised nobody smacked me for my bad math in my earlier post. The luminence register is 3-bits, not 4. =) 8 shades of luminence for a total of 121 colors. xD
Oddly, the Plus/4 had BETTER graphics in some ways, and worse than others.
Its bitmap graphics capabilities were quite superior. In fact it had 8-bit color of sorts! Colors on it were selectable from the C-64's normal complement of 16 colors (4-bits), and in addition there was a 4-bit brightness register (16 levels of brightness)you could set when picking a color. The end result was each color became 16 possible colors, giving you 121 total available colors! (Why 121 and not 128? Well, one of the 16 colors was black... and black is still black no matter how bright you make it. =P) This gave it by far the most colorful graphics of any home computer in 1984. Sadly, most programmers didn't have the first clue how to use this graphics mode effectively, and the small amount of software released for the platform mostly used 16 colors.
The big complaint about the Plus/4's graphics was the removal of hardware sprites, something which greatly hurt its gaming potential....but then Commodore was pushing it as a home-productivity solution.
The president says we should ban cloning in *all its forms*! Let's start by banning the oldest form of cloning -- identical twins!
Because obviously a human with the same genetic makeup has the same soul, thus leading to one clone never knowing if they're "real" or not! (Or is it a soulless evil, husk? I'm never quite sure what the Luddites believe.)
No, the threat of a nuclear reactor going meltdown and melting down through the mantle, coming into contact with supercold water...
That would be *VERY* impressive. Melting through the crust all the way to the mantle would be an incredible feat that has so far not been accomplished. Finding supercold water in the mantle mixed in with all the red-to-white-hot molten magma would be an incredible discovery as well!
Specifically I live not very far from the Twin Falls, Idaho Dell facility mentioned in TFA (I even know some folks who work there.)
The huge problem with this is that socially, rural America sucks. It's cheap to live here, but aside from skiing/snowboarding/whitewater (thank goodness this is Idaho and not Nebraska) there's really nothing to do for youngish geek-oriented people. It's simply not fun to be here unless you are religious and/or enjoy cowboy-type stuff. ESPECIALLY if you're single.
The social scene in a city is far better suited to IT workers. That's why they want to live there -- not just for the jobs.
As has been noticed by another poster, typical slow-response LCDs have HUGE problems with high-contrast scrolling text.
Try this. Open up a textmode display (just black and white text) and open up your favorite console text editor. Make a file that has a solid line of big letters (capital Ms work well) every other line. Then scroll so that you're alternating between odd and even rows having the line of characters.
If you want, write a program to do this for you.
What you wind up with is a STROBE effect.
Theoretically the screen should only be putting out the same amount of light per frame. The number of white pixels onscreen is exactly the same every frame....but what's happening is that for a split second when the screen is updating, the pixels are turning a dull shade of gray, and the total light output of the monitor is lower. You can test this by not even looking at the screen, and just aiming the monitor at the floor or something and looking at the total reflected light. It will strobe. The faster the response time of your monitor, the shorter the "dark" periods will be, and the strobing effect will lessen.
CRTs do this too, but the phosphors continue to glow during the refresh, and this glow time is carefully tuned to match typical refresh rates. This is why televisions seem to flicker less at 60Hz interlaced compared to monitors -- the phosphors are tuned for slower response.
Anyway, that's an example of where a faster response time helps on an LCD display. It's not just gaming, folks. It's any case where you have to read a lot of scrolling text. I get headaches from scrolling text on slow-response LCDs.
Given that the median wage in the U.S. is $11.87, and that huge numbers of people (particularly out of work tech people) make $5.15 an hour or have no income at all, that $20 represents at the very LEAST more than an hour of work in all probability.
...is that the age of consent in New York is seventeen, not eighteen. Seventeen-year-olds are perfectly free to go bang anyone they want -- keeping them out of internet chat rooms isn't going to stop anything.
Given that the majority of the planet (and the majority of U.S. states for that matter) sets the age of consent somewhere below eighteen, it's sort of funny that the internet is treated as somehow different....and if the argument is that they have to adhere to the MAXIMUM age of consent to just be safe, they'll need to set it to 21 (Trinidad and Tobago, which has the highest age of consent in the world).
(Sorry for late response, I do follow up on replies eventually)
11.975 the old version has ended. The author now makes a new one with actual dialogue. ^^; I think it's lost some of its charm. On the other hand, it's still random and goofy. xD
Hm and I think Pokey makes a bit more sly commentary under its randomness... Pokey also appears to be rather mean-spirited sometimes. xD Finally, the author of Pokey spends way less time on his art. These are all reasons to love Pokey of course. =3
Crispin's a great guy, a good actor, and genuinely cares about the works he's dubbing....and even he will badmouth some of the stuff he's worked on. There's a HUGE problem with the whole process of making dubs in the U.S. that simply hasn't been fixed by the companies, and probably never will be (see earlier posts that enumerate some of these flaws). A good actor can't save it.
Hell, even a good director can't save it if the system is flawed.
If we fix the system with ensemble recording, more time to fix problems, better Japanese cultural and pronunciation education for the actors (it helps for a character to know why they're reacting the way they are and to even pronounce their own name correctly), and better environmental-awareness of voices (limit the fidelity of the voices so they sound like they're really in the kind of environment that they're supposed to be -- real people don't sound like a hifi reproduction from a microphone that's a foot from their face) then even inexperienced actors with enough takes and enough coaching can release a good product, and good, experienced actors like Crispin could REALLY shine!
The publishers just aren't going to allow that though.
My problem may be solved SOMEDAY because someone is putting in blood, sweat, and tears to independently develop a driver with no support from the manufacturers.
Strongarming didn't work, it failed. If it had worked, they'd have released code instead of the community having to reverse-engineer stuff.
That's all well and good that an open-source driver is being developed. I cheer it on -- it will certainly make the hardware useful on other platforms....but I really wish I could just load a driver now and use it -- and the lack of a stable ABI prevents this. I wish I could recompile the wrapper so it will at least work with my specific kernel -- and the lack of a stable API prevents this.
Yes, and it's very dogmatic. It presents good reasons for the internal API to change, but IMHO the reasons against not offering a stable ABI for external driver support amount more to calling the developers of these "leeches".
Guess what? Tons of products now offer "linux support" by ugly wrappers or, worse yet, per-distro builds, or even WORSE no drivers at all.
Hell yeah I want open source drivers in the kernel. It's nice when the drivers come built-in! Lots of companies agree with this concept in the Win32 environment as well and various builds of the NT kernel ship with drivers for all sorts of hardware built-in.
The problem is not everyone is going to do this......and as a result I'm stuck sitting here porting Highpoint's stupid wrapper to 2.6.13. They're NOT going to give me open-source drivers, and there was no other card in its price range that did what we needed it to do here.
To whoever modded me flamebait -- it wasn't flamebait! I'm not trying to piss anyone off. I'm just saying that while it's Highpoint's fault somewhat for not updating their driver, it's also the fault of Linux for not having a better-structured way for deprecating and removing old code. (i.e. don't remove deprecated code in minor revisions!)
Fortunately the needed changes aren't that big (I had to familiarize myself with the APIs, both old and new, which is why I'm taking so long), but I shouldn't have to be doing this at all. That's why I'm grumpy.
So right now, with a server that needs to be deployed, would I benefit from a stable ABI (or at least a stable API!) for device drivers? Hell yeah! I would be doing other, more productive things with my time.
THANKFULLY drivers for the chipset family that the 1820A uses are finally starting to trickle into patches to the kernel, but they're in a very very very alpha state at the moment. Maybe in half a year this won't be an issue anymore. =/
Trying to strongarm companies into releasing open source drivers by making closed-source ones a bitch to make work will NOT convince them to open their code (witness ATI and nVidia). We have to show them other merits to opening their code (being installed by default being a good one to start with -- assistance from the community in bugfixes being another).
In order to accomodate stuff that is still closed, we need solid ABIs for things like drivers, for things like standard libraries. Right now the only one we can count on is the basic executable environment ABI. The only way you can count on THAT working is to have everything statically linked into the executeable......and for device drivers you're just screwed. =/
If we had these my job would have a lot fewer headaches and I could focus on more important tasks.
This really can't go on, with developers releasing binaries for every distribution under the sun that people badger them enough to support. There needs to be a common, intelligent interface to shared libraries that works regardless of when or how the library was compiled!
There also needs to be a stable driver ABI so that we don't have to recompile the kernel module wrapper for every kernel we build -- assuming the manufacturer even gives you wrapper code. Linux on the desktop simply is not going to succeed with issues like these!:: frustrated and right now trying to port drivers for the Highpoint 1820A to kernel 2.6.13 since some deprecated code got removed IN A STABLE KERNEL SERIES and now the compile breaks::
Er, the 8088 and the 8086 were both 16-bit CPUs that took 16-bit instructions. The 8088 was only "8-bit" in that it had an 8-bit data bus, internally it was 16 bits wide.
The 8-bit progenitor of these was the 8080. The 8086/8088 were designed to be assembly-compatible with the 8080, but not binary-compatible. (i.e. you took your 8080 assembly and ran it in an 8086 assembler that was 8080-aware and it would produce working code with little-to-no tweaking).
There's presently functioning two orbiters (Mars Global Surveyor, Mars Odyssey), two rovers (MER A a.k.a. Spirit, MER B a.k.a. Opportunity), and Mars Reconnaissance Orbiter is on the way.
I realize TFA has the info but it sort of belongs in the headline. "The mars probe" just sounds silly and uninformed.
If I could get paid for the rest of my life for work I did this year!
I'm a sysadmin/network guy. That cluster I set up? I think I should get paid royalties on it forever! Every person who builds or uses a cluster like mine should pay me royalties for the next century! They won't have a choice, because the government will enforce it!
Oh wait, for some reason only music and movies (and books and paintings... though that's becoming less important in a McEntertainment society) get that protection.
Even if I somehow created an incredible invention -- say a food replicator or something that could feed the entire planet... I'd only get a patent on it for 20 years. Although then I'd probably be sued under the DMCA for enabling the duplication of valuable edible intellectual property.
Why are movies and music so goddamn special? Inventions get patent protection for far less time......and no other kind of labor gets any protection at all! Hauling lumber gets you a paycheck for a day -- not a lifetime!
Copyrights are corporate welfare. Welfare is sometimes a good thing! Government intervention in capitalism is a good thing sometimes!...but copyrights today are such an incredible intrusion on the free market that they can only have a negative effect. I have no idea how otherwise hardcore capitalists will mouth-frothingly support government handouts in the form of 90 year copyrights.
Why does everyone seem so hellbent on the notion that the ONLY way the war could end was with Japan's surrender? (Unconditional or conditional)
Yes, I know about the Potsdam Declaration......but even the people who call into question the need for an unconditional surrender often seem to assume that surrender was important at all?
The other solution... is JUST STOP FIGHTING. Let the Japanese "save face". They don't get their country occupied. They don't have to capitulate. Hell, they might even get to keep a colony or two!
The point is that their rampant expansion would've been stopped, and they'd be kicked out of just about everywhere they'd invaded over the past decade or so.
There's an end to the war where nobody has to get bombed. Nobody dies in invasions......and everyone gets to go home.
Copyrights are governed internationally by the terms of the Berne Convention, which the European Union member states have signed (the vast majority of them, anyway).
(I'm writing from a U.S.ian point of view)
In other words, they're bound by a treaty.
Our illustrious president has shown no qualms about withdrawing from important international treaties... both signed ones and signed AND ratified ones... Can we expect any other country to care more now?
Slashdot Mirror
You can add Aerith/Aeris back into the party manually, sure -- that doesn't mean she'll be in the STORY at all. She won't have any dialogue (aside from generic lines that EVERY character says exactly the same) and sometimes the game will crash with her in your party.
In other words you just swapped character data into your party, she's not actually "there" story-wise.
Ancestors of the Amiga you mean. Yes, Jay Miner did a fantastic job on the Atari 800XL's chipset. =) ...but the best they could muster without temporal or spatial dithering or scan-line interrupt tricks was 80x192 in 16 colors. The Plus/4 could display all 121 colors onscreen at once (albeit with restrictions on how close different colors could be to eachother) without any sort of trickery.
...and I'm surprised nobody smacked me for my bad math in my earlier post. The luminence register is 3-bits, not 4. =) 8 shades of luminence for a total of 121 colors. xD
That said, the 800XL's color palette was way better than the Plus/4's.
Since you don't have to mess with lenses at all... ...just vary the sweep length of each scanline. =)
Oddly, the Plus/4 had BETTER graphics in some ways, and worse than others.
...but then Commodore was pushing it as a home-productivity solution.
Its bitmap graphics capabilities were quite superior. In fact it had 8-bit color of sorts! Colors on it were selectable from the C-64's normal complement of 16 colors (4-bits), and in addition there was a 4-bit brightness register (16 levels of brightness)you could set when picking a color. The end result was each color became 16 possible colors, giving you 121 total available colors! (Why 121 and not 128? Well, one of the 16 colors was black... and black is still black no matter how bright you make it. =P) This gave it by far the most colorful graphics of any home computer in 1984. Sadly, most programmers didn't have the first clue how to use this graphics mode effectively, and the small amount of software released for the platform mostly used 16 colors.
The big complaint about the Plus/4's graphics was the removal of hardware sprites, something which greatly hurt its gaming potential.
...what they're seeing aren't the last stages of "maturity", but rather the earlier signs of old age?
Drawing sweeping conclusions from only two groups and making all these blanket assumptions makes for a completely worthless study.
The president says we should ban cloning in *all its forms*! Let's start by banning the oldest form of cloning -- identical twins!
Because obviously a human with the same genetic makeup has the same soul, thus leading to one clone never knowing if they're "real" or not! (Or is it a soulless evil, husk? I'm never quite sure what the Luddites believe.)
No, the threat of a nuclear reactor going meltdown and melting down through the mantle, coming into contact with supercold water...
That would be *VERY* impressive. Melting through the crust all the way to the mantle would be an incredible feat that has so far not been accomplished. Finding supercold water in the mantle mixed in with all the red-to-white-hot molten magma would be an incredible discovery as well!
Of course, because everyone knows compilers are destructive!
Specifically I live not very far from the Twin Falls, Idaho Dell facility mentioned in TFA (I even know some folks who work there.)
The huge problem with this is that socially, rural America sucks. It's cheap to live here, but aside from skiing/snowboarding/whitewater (thank goodness this is Idaho and not Nebraska) there's really nothing to do for youngish geek-oriented people. It's simply not fun to be here unless you are religious and/or enjoy cowboy-type stuff. ESPECIALLY if you're single.
The social scene in a city is far better suited to IT workers. That's why they want to live there -- not just for the jobs.
As has been noticed by another poster, typical slow-response LCDs have HUGE problems with high-contrast scrolling text.
...but what's happening is that for a split second when the screen is updating, the pixels are turning a dull shade of gray, and the total light output of the monitor is lower. You can test this by not even looking at the screen, and just aiming the monitor at the floor or something and looking at the total reflected light. It will strobe. The faster the response time of your monitor, the shorter the "dark" periods will be, and the strobing effect will lessen.
Try this. Open up a textmode display (just black and white text) and open up your favorite console text editor. Make a file that has a solid line of big letters (capital Ms work well) every other line. Then scroll so that you're alternating between odd and even rows having the line of characters.
If you want, write a program to do this for you.
What you wind up with is a STROBE effect.
Theoretically the screen should only be putting out the same amount of light per frame. The number of white pixels onscreen is exactly the same every frame.
CRTs do this too, but the phosphors continue to glow during the refresh, and this glow time is carefully tuned to match typical refresh rates. This is why televisions seem to flicker less at 60Hz interlaced compared to monitors -- the phosphors are tuned for slower response.
Anyway, that's an example of where a faster response time helps on an LCD display. It's not just gaming, folks. It's any case where you have to read a lot of scrolling text. I get headaches from scrolling text on slow-response LCDs.
Given that the median wage in the U.S. is $11.87, and that huge numbers of people (particularly out of work tech people) make $5.15 an hour or have no income at all, that $20 represents at the very LEAST more than an hour of work in all probability.
...is that the age of consent in New York is seventeen, not eighteen. Seventeen-year-olds are perfectly free to go bang anyone they want -- keeping them out of internet chat rooms isn't going to stop anything.
...and if the argument is that they have to adhere to the MAXIMUM age of consent to just be safe, they'll need to set it to 21 (Trinidad and Tobago, which has the highest age of consent in the world).
Given that the majority of the planet (and the majority of U.S. states for that matter) sets the age of consent somewhere below eighteen, it's sort of funny that the internet is treated as somehow different.
:: laughs ::
(Sorry for late response, I do follow up on replies eventually)
11.975 the old version has ended. The author now makes a new one with actual dialogue. ^^; I think it's lost some of its charm. On the other hand, it's still random and goofy. xD
Hm and I think Pokey makes a bit more sly commentary under its randomness... Pokey also appears to be rather mean-spirited sometimes. xD Finally, the author of Pokey spends way less time on his art. These are all reasons to love Pokey of course. =3
Hooray for Pokey!
I've been a longtime fan of Pokey as well. I need to get a Mr. Nutty Warmth Sheath.
My SECOND favorite dadaist webcomic though has to be Listening to 11.975Mhz. I love the Crumb-esque elements combined with the cute girls. XD
Crispin's a great guy, a good actor, and genuinely cares about the works he's dubbing. ...and even he will badmouth some of the stuff he's worked on. There's a HUGE problem with the whole process of making dubs in the U.S. that simply hasn't been fixed by the companies, and probably never will be (see earlier posts that enumerate some of these flaws). A good actor can't save it.
Hell, even a good director can't save it if the system is flawed.
If we fix the system with ensemble recording, more time to fix problems, better Japanese cultural and pronunciation education for the actors (it helps for a character to know why they're reacting the way they are and to even pronounce their own name correctly), and better environmental-awareness of voices (limit the fidelity of the voices so they sound like they're really in the kind of environment that they're supposed to be -- real people don't sound like a hifi reproduction from a microphone that's a foot from their face) then even inexperienced actors with enough takes and enough coaching can release a good product, and good, experienced actors like Crispin could REALLY shine!
The publishers just aren't going to allow that though.
My problem may be solved SOMEDAY because someone is putting in blood, sweat, and tears to independently develop a driver with no support from the manufacturers.
...but I really wish I could just load a driver now and use it -- and the lack of a stable ABI prevents this. I wish I could recompile the wrapper so it will at least work with my specific kernel -- and the lack of a stable API prevents this.
Strongarming didn't work, it failed. If it had worked, they'd have released code instead of the community having to reverse-engineer stuff.
That's all well and good that an open-source driver is being developed. I cheer it on -- it will certainly make the hardware useful on other platforms.
=( It's really frustrating.
I can get free gold, wheat and salt over the network?! Sign me up!!
Yes, and it's very dogmatic. It presents good reasons for the internal API to change, but IMHO the reasons against not offering a stable ABI for external driver support amount more to calling the developers of these "leeches".
...and as a result I'm stuck sitting here porting Highpoint's stupid wrapper to 2.6.13. They're NOT going to give me open-source drivers, and there was no other card in its price range that did what we needed it to do here.
...and for device drivers you're just screwed. =/
Guess what? Tons of products now offer "linux support" by ugly wrappers or, worse yet, per-distro builds, or even WORSE no drivers at all.
Hell yeah I want open source drivers in the kernel. It's nice when the drivers come built-in! Lots of companies agree with this concept in the Win32 environment as well and various builds of the NT kernel ship with drivers for all sorts of hardware built-in.
The problem is not everyone is going to do this...
To whoever modded me flamebait -- it wasn't flamebait! I'm not trying to piss anyone off. I'm just saying that while it's Highpoint's fault somewhat for not updating their driver, it's also the fault of Linux for not having a better-structured way for deprecating and removing old code. (i.e. don't remove deprecated code in minor revisions!)
Fortunately the needed changes aren't that big (I had to familiarize myself with the APIs, both old and new, which is why I'm taking so long), but I shouldn't have to be doing this at all. That's why I'm grumpy.
So right now, with a server that needs to be deployed, would I benefit from a stable ABI (or at least a stable API!) for device drivers? Hell yeah! I would be doing other, more productive things with my time.
THANKFULLY drivers for the chipset family that the 1820A uses are finally starting to trickle into patches to the kernel, but they're in a very very very alpha state at the moment. Maybe in half a year this won't be an issue anymore. =/
Trying to strongarm companies into releasing open source drivers by making closed-source ones a bitch to make work will NOT convince them to open their code (witness ATI and nVidia). We have to show them other merits to opening their code (being installed by default being a good one to start with -- assistance from the community in bugfixes being another).
In order to accomodate stuff that is still closed, we need solid ABIs for things like drivers, for things like standard libraries. Right now the only one we can count on is the basic executable environment ABI. The only way you can count on THAT working is to have everything statically linked into the executeable...
If we had these my job would have a lot fewer headaches and I could focus on more important tasks.
This really can't go on, with developers releasing binaries for every distribution under the sun that people badger them enough to support. There needs to be a common, intelligent interface to shared libraries that works regardless of when or how the library was compiled!
:: frustrated and right now trying to port drivers for the Highpoint 1820A to kernel 2.6.13 since some deprecated code got removed IN A STABLE KERNEL SERIES and now the compile breaks ::
There also needs to be a stable driver ABI so that we don't have to recompile the kernel module wrapper for every kernel we build -- assuming the manufacturer even gives you wrapper code. Linux on the desktop simply is not going to succeed with issues like these!
Er, the 8088 and the 8086 were both 16-bit CPUs that took 16-bit instructions. The 8088 was only "8-bit" in that it had an 8-bit data bus, internally it was 16 bits wide.
The 8-bit progenitor of these was the 8080. The 8086/8088 were designed to be assembly-compatible with the 8080, but not binary-compatible. (i.e. you took your 8080 assembly and ran it in an 8086 assembler that was 8080-aware and it would produce working code with little-to-no tweaking).
Ah yes, mod me "moron". I was shamelessly only counting U.S. craft. :: cringes :: On checking the original submission it doesn't specify that. ^^;
Mars Express has been returning some fantastic data!
Too bad the telecommunications probe has been cancelled. =( It would really improve the data return of MSL when it gets there.
...which probe?
There's presently functioning two orbiters (Mars Global Surveyor, Mars Odyssey), two rovers (MER A a.k.a. Spirit, MER B a.k.a. Opportunity), and Mars Reconnaissance Orbiter is on the way.
I realize TFA has the info but it sort of belongs in the headline. "The mars probe" just sounds silly and uninformed.
If I could get paid for the rest of my life for work I did this year!
...and no other kind of labor gets any protection at all! Hauling lumber gets you a paycheck for a day -- not a lifetime!
...but copyrights today are such an incredible intrusion on the free market that they can only have a negative effect. I have no idea how otherwise hardcore capitalists will mouth-frothingly support government handouts in the form of 90 year copyrights.
I'm a sysadmin/network guy. That cluster I set up? I think I should get paid royalties on it forever! Every person who builds or uses a cluster like mine should pay me royalties for the next century! They won't have a choice, because the government will enforce it!
Oh wait, for some reason only music and movies (and books and paintings... though that's becoming less important in a McEntertainment society) get that protection.
Even if I somehow created an incredible invention -- say a food replicator or something that could feed the entire planet... I'd only get a patent on it for 20 years. Although then I'd probably be sued under the DMCA for enabling the duplication of valuable edible intellectual property.
Why are movies and music so goddamn special? Inventions get patent protection for far less time...
Copyrights are corporate welfare. Welfare is sometimes a good thing! Government intervention in capitalism is a good thing sometimes!
Why does everyone seem so hellbent on the notion that the ONLY way the war could end was with Japan's surrender? (Unconditional or conditional)
...but even the people who call into question the need for an unconditional surrender often seem to assume that surrender was important at all?
...and everyone gets to go home.
Yes, I know about the Potsdam Declaration...
The other solution... is JUST STOP FIGHTING. Let the Japanese "save face". They don't get their country occupied. They don't have to capitulate. Hell, they might even get to keep a colony or two!
The point is that their rampant expansion would've been stopped, and they'd be kicked out of just about everywhere they'd invaded over the past decade or so.
There's an end to the war where nobody has to get bombed. Nobody dies in invasions...
Copyrights are governed internationally by the terms of the Berne Convention, which the European Union member states have signed (the vast majority of them, anyway).
(I'm writing from a U.S.ian point of view)
In other words, they're bound by a treaty.
Our illustrious president has shown no qualms about withdrawing from important international treaties... both signed ones and signed AND ratified ones... Can we expect any other country to care more now?