Actually, both lawing that workers must be paid and outlawing theft are banning the same little liberty: to enjoy other people's work for free.
However - of course this liberty goes against lots of other bigger liberties, so if we aim for maximum liberty, we need to stop this one.
I don't really know if management supposes the people are honest or dishonest, but this is the Moral way. Isn't simpler just do the Science way? Check the things, asks politely for work done, efficiency, things like that.
It's trivial to reach a compromise: make crystal clear what's employee's personal things and what is job-related things, and apply this to e-mail accounts. Allow companies to check employee's job-related mail, but not the personal one. Ta-da! Problem solved.
About your 2nd paragraph: labour unions are just making their job, to defend the worker's interests. It's not their fault, but legal - Brazil's Legislative power isn't known for effective law-making...
Con artists already know by centuries that there's a somewhat "attention optimum": less than this, you'll lose profit; more than this, the cops arrive.
They should learn this little piece of popular wisdom...
The empty set doesn't exist because no set exist in the physical sense of the word. Sets are just abstractions, made as a way to deal with things that do exist.
And this can be said about the math as a whole - numbers don't exist because they aren't things, they represent them.
And this bring us on the topic again: are wavefunctions "just math" or, as the study wants to prove, real things? Their properties can be, actually, just particles' properties that are easier to describe as a wave.
I'll wait for experimental data to say something definitive, but IMHO until now wave as physical is still plain bullshit.
It's interesting to Microsoft to kill tracking, since it's what their biggest rival - Google - uses for generate revenue, and MS's income comes from their [dubious quality] OS and office suite.
The attacks are being directed at the routers, not the ISPs.
Most Brazilian ISPs use a "borrow my router" (we call it comodato) system, where the client uses ISP's router instead of his own.
The thing is... these routers are configured with a default password and most users don't know/want to change it.
So, no, no peace in MMOs... and as a side note, even being Brazilian, I must agree with you: Brazilian MMO players are fcking annoying, worse if you do know Portuguese.
The ISPs were GVT and Oi (source).
Actually, for me, this is kinda funny - I use Oi, but I only saw about this DNS poisoning here in Slashdot... no changes, no malware warning, nothing.
Just a noob [me] saying - note the 'IMO' [in my opinion]. I may be wrong, I know, but I see multiple executable and lib pathes as against KISS principle
Sadly, this way will be throwing away useful software that should come pre-installed and almost everyone uses until the ISO fits in a regular CD. But the Canonical stuff we never use will still be there.
They need to call it "light" because politicians are stupid enough to ban if they call it "radiation" - although a powerful enough laser won't be visible light, but UV radiation...
Well, if you're going to be serious about this, then I'd guess that the "/bin" versus "/usr/bin" distinction might not mean much these days for a system with terabytes of disk space but maybe on small embedded systems it's valuable; e.g., a "standalone" boot using only the root filesystem. If so, then I think that maintaining the separation for all "*NIX" systems can be useful in a "I know where that is" type of way.
I disagree in three points:
1. Even these embadded systems have nowadays enough capacity for both / and/usr;
2. Symlinks, symlinks everywhere if one needs so badly that kilobytes, and
3. initramfs reading/etc/fstab and mounting/usr before the real init - that is the way Fedora is trying to do it, source: https://fedoraproject.org/wiki/Features/UsrMove
And for a class of commands that a typical "user" neither cares about nor would know what to do with,
There is no such thing as a typical user, different users need different things. And confusers will always find a way to mess everything, with or without bin vs. sbin distinction - "oops, I intended to write rm -f./*, NOT rm -f/* !". Privileges stop them making the system unusable.
Finally, I definitely make use of "/usr/local/bin" and "/usr/local/sbin" as a very handy separation between "stuff that's part of the OS" and "stuff I put there myself". Usually via symlinks to stuff in/opt which I generally arrange via package-name directories.
If it's part of OS, why it's in/usr/local in first place? And users needing this distinction can always do a/random/custom/directory/bin and set syslinks in/usr/bin, or even set the path.
But really, for mindless stuff like this, I prefer to just leave a snarky comment:-)
There is - a small one, but (your milleage may vary) an annoying one.
Simplifying the hierarchy would ease the things both for users and for devs - you don't need to "guess" or search anymore where is the executable and the libraries.
I know that "if it's working, don't fix it" is a good rule of thumb, but it's just this - a rule of thumb. When misused, it becomes "if it's working BADLY, don't fix it".
Actually, I think Fedora's issue is not about "making it easy to understand", but about making it easy to maintain.
Once, these distinctions were useful and meaningful. Today, they're pretty much arbitrary - it's not only/sbin and/bin, but: /bin /usr/bin /usr/local/bin /sbin /usr/sbin /usr/local/sbin /usr/games
etc. The same applies to libraries.
Do we really need SEVEN directories making the same thing?
Fedora got +1 respect from me because of this - FHS is deprecated IMO, and simplifying the directory hierarchy was needed for a long, long time.
If they go a step further and adopt the same reasonable hierarchy from GoboLinux, even allowing installing software one-user-only, I'll switch immediately, even being a RPM distro (I work better with.deb).
Now, let me do a wishlist...
* Compressed directories;
* Xfce and Mate fusing into one highly configurable DE, with as much features as the user WANTS, but allowing a small RAM footprint if the user doesn't use them;
* A K3B GTK+ port;
* Ubuntu's and Debian's.deb packages being fully compatible again;
* An optimized, bug- and crash-free Firefox fork;
* Ballmer dying in a fire [not really].
...after the KDE's crazy drop of functionality in KDE4, and GNOME trolling us with 'we want to make it so simple you cannot do real work in GNOME 3', now Microsoft is following the pioneers of interface hell! What a wonderful way to go!
Now, let us imagine the future...
[Random user] "Will Mac OS X v10.9 "Lazy Kitty" have a dock?"
[Apple dev] "No, it's too boring and like, yesterday. But it'll have so much eye candy that your eyes will develop diabetes!"
[Random user 2] "Where are my icons in Xfce5?"
[Xfce dev] "They're too resource-heavy, we let them out. You ain't gonna need them!"
Actually, both lawing that workers must be paid and outlawing theft are banning the same little liberty: to enjoy other people's work for free.
However - of course this liberty goes against lots of other bigger liberties, so if we aim for maximum liberty, we need to stop this one.
I don't really know if management supposes the people are honest or dishonest, but this is the Moral way. Isn't simpler just do the Science way? Check the things, asks politely for work done, efficiency, things like that.
It's trivial to reach a compromise: make crystal clear what's employee's personal things and what is job-related things, and apply this to e-mail accounts. Allow companies to check employee's job-related mail, but not the personal one. Ta-da! Problem solved.
About your 2nd paragraph: labour unions are just making their job, to defend the worker's interests. It's not their fault, but legal - Brazil's Legislative power isn't known for effective law-making...
Con artists already know by centuries that there's a somewhat "attention optimum": less than this, you'll lose profit; more than this, the cops arrive.
They should learn this little piece of popular wisdom...
Burzynski is what you get when you breed a troll and a scammer.
The empty set doesn't exist because no set exist in the physical sense of the word. Sets are just abstractions, made as a way to deal with things that do exist.
And this can be said about the math as a whole - numbers don't exist because they aren't things, they represent them.
And this bring us on the topic again: are wavefunctions "just math" or, as the study wants to prove, real things? Their properties can be, actually, just particles' properties that are easier to describe as a wave.
I'll wait for experimental data to say something definitive, but IMHO until now wave as physical is still plain bullshit.
It's interesting to Microsoft to kill tracking, since it's what their biggest rival - Google - uses for generate revenue, and MS's income comes from their [dubious quality] OS and office suite.
Protip: land kittens must be harvested 3-month old to ensure a tasty meat.
One that has no bash. I don't know if that fork bomb works on Windows without editing...
The attacks are being directed at the routers, not the ISPs.
Most Brazilian ISPs use a "borrow my router" (we call it comodato) system, where the client uses ISP's router instead of his own.
The thing is... these routers are configured with a default password and most users don't know/want to change it.
So, no, no peace in MMOs... and as a side note, even being Brazilian, I must agree with you: Brazilian MMO players are fcking annoying, worse if you do know Portuguese.
When you know that Slashdot has better news for geeks than Terra and UOL.
Oi's DNS default poisoning (an unwanted "custom search" instead of 404 error page) is sadly working as usual.
The ISPs were GVT and Oi (source).
Actually, for me, this is kinda funny - I use Oi, but I only saw about this DNS poisoning here in Slashdot... no changes, no malware warning, nothing.
Says who?
Just a noob [me] saying - note the 'IMO' [in my opinion]. I may be wrong, I know, but I see multiple executable and lib pathes as against KISS principle
Sadly, this way will be throwing away useful software that should come pre-installed and almost everyone uses until the ISO fits in a regular CD.
But the Canonical stuff we never use will still be there.
I'll just say that you can tweak a GNOME 2 enough to look like Aqua [OS X interface], but the inverse is not true.
Say hello to Xfce. And dream as many of us that old GNOME 2 code will make its way to Xfce as xfce-goodies-2.
They need to call it "light" because politicians are stupid enough to ban if they call it "radiation" - although a powerful enough laser won't be visible light, but UV radiation...
Well, if you're going to be serious about this, then I'd guess that the "/bin" versus "/usr/bin" distinction might not mean much these days for a system with terabytes of disk space but maybe on small embedded systems it's valuable; e.g., a "standalone" boot using only the root filesystem. If so, then I think that maintaining the separation for all "*NIX" systems can be useful in a "I know where that is" type of way.
I disagree in three points: /usr; /etc/fstab and mounting /usr before the real init - that is the way Fedora is trying to do it, source: https://fedoraproject.org/wiki/Features/UsrMove
1. Even these embadded systems have nowadays enough capacity for both / and
2. Symlinks, symlinks everywhere if one needs so badly that kilobytes, and
3. initramfs reading
And for a class of commands that a typical "user" neither cares about nor would know what to do with,
There is no such thing as a typical user, different users need different things. And confusers will always find a way to mess everything, with or without bin vs. sbin distinction - "oops, I intended to write rm -f ./*, NOT rm -f /* !". Privileges stop them making the system unusable.
Finally, I definitely make use of "/usr/local/bin" and "/usr/local/sbin" as a very handy separation between "stuff that's part of the OS" and "stuff I put there myself". Usually via symlinks to stuff in /opt which I generally arrange via package-name directories.
If it's part of OS, why it's in /usr/local in first place? And users needing this distinction can always do a /random/custom/directory/bin and set syslinks in /usr/bin, or even set the path.
But really, for mindless stuff like this, I prefer to just leave a snarky comment :-)
It was not snarky. Its chromatic index was 3. :-D
There is - a small one, but (your milleage may vary) an annoying one.
Simplifying the hierarchy would ease the things both for users and for devs - you don't need to "guess" or search anymore where is the executable and the libraries.
I know that "if it's working, don't fix it" is a good rule of thumb, but it's just this - a rule of thumb. When misused, it becomes "if it's working BADLY, don't fix it".
Actually, I think Fedora's issue is not about "making it easy to understand", but about making it easy to maintain. /sbin and /bin, but:
/bin
/usr/bin
/usr/local/bin
/sbin
/usr/sbin
/usr/local/sbin
/usr/games
Once, these distinctions were useful and meaningful. Today, they're pretty much arbitrary - it's not only
etc. The same applies to libraries.
Do we really need SEVEN directories making the same thing?
QWERTY is horrible - it's tautological - we use it because we use it. The same applies to LHS.
Fedora got +1 respect from me because of this - FHS is deprecated IMO, and simplifying the directory hierarchy was needed for a long, long time. If they go a step further and adopt the same reasonable hierarchy from GoboLinux, even allowing installing software one-user-only, I'll switch immediately, even being a RPM distro (I work better with .deb).
.deb packages being fully compatible again;
Now, let me do a wishlist...
* Compressed directories;
* Xfce and Mate fusing into one highly configurable DE, with as much features as the user WANTS, but allowing a small RAM footprint if the user doesn't use them;
* A K3B GTK+ port;
* Ubuntu's and Debian's
* An optimized, bug- and crash-free Firefox fork;
* Ballmer dying in a fire [not really].
Agreed. Figure 4 revelas that 85% of Windows users don't know how customize their desktop.
...after the KDE's crazy drop of functionality in KDE4, and GNOME trolling us with 'we want to make it so simple you cannot do real work in GNOME 3', now Microsoft is following the pioneers of interface hell! What a wonderful way to go!
Now, let us imagine the future...
[Random user] "Will Mac OS X v10.9 "Lazy Kitty" have a dock?"
[Apple dev] "No, it's too boring and like, yesterday. But it'll have so much eye candy that your eyes will develop diabetes!"
[Random user 2] "Where are my icons in Xfce5?"
[Xfce dev] "They're too resource-heavy, we let them out. You ain't gonna need them!"