All that stuff costs money. A lot of money, actually. In the US, with such "horrible slavelike labor conditions" (give me a break) benefits make up between 30-50% of the cost to employ someone. The more money an employer has to spend on each employee to get the same productivity the less he can spend on hiring new workers. It doesn't mean he will if he has the cash, but that's usually how companies grow - by adding more people.
The kinds of guarantees described would push every employee's cost up around 50% of their base salary, possibly even higher. Think about that. Without that 50% cost, for every two employees working now there could be an additional employee. That would theoretically cut unemployment down to about 15%. (in practice not as much, for various reasons, but you would definitely see more people being hired)
If you have all these rules then I'm sure you have a minimum wage as well, which further raises the costs of employment. In a highly productive society you can have these nice things, but if half the country is going hungry, don't you think it is more important that they be able to work instead of giving all these plush benefits to the few who can find a job?
40 hours per week, max of 5 hours overtime - it's ILLEGAL to allow more
God, not even the option to work more? That sucks.
I currently work 80 hours a week for two weeks straight, then take two full weeks off. My schedule (which is so freakin nice, I have half the year off) would be illegal in your country. If you were counting, that's 40 hours of over time every week. If I were working a 9-5 job, it would be like getting paid 50% more every other week.
You totally misunderstand what Freedom of Speech is.
You can say whatever you want, but if your words cause harm to others you may be held accountable.
For the government it is a pretty high standard that they have to meet before they can punish someone (serious national security type stuff, that wikileaks bs wasn't quite good enough), among private individuals there is no standard you need to meet before you can terminate your relationship, but if you can show harm (from libel or slander) you can sue successfully. Also if your speech causes immediate harm to the public you will be held accountable. Companies are the same as individuals, with exceptions found in labor laws.
Thus, the story of the NLRB declaring restriction of Facebook usage by companies violates the labor laws.
Some of the instructables are of seriously high quality. Most are not, but there are some absolute gems in there. A lot of it is great just for neat ideas. Like an arduino based RFID door lock or an automated home garden. You aren't going to be building it step by step from their design, but you can use them as a good jumping point, and it's easy to find a very wide range of projects on these sites.
Granted, it's a hell of a lot more than the desktop market, but lets be real here, Linux is still getting crushed. Windows has 75% of that market locked up tight. Linux servers seem to be concentrated on web servers, which make up a small part of the server picture.
You must not understand how land sails and sail boats actually do it then.
They create an air-foil, which generates pull as the craft speeds up. This is basically a force multiplier on the wind pushing behind it. It is entirely dependent on the wind, but it can allow the craft to go faster than the wind itself is moving.
The reason land sails cannot go downwind is because you must have both the force from the wind behind the sail and the correct angle of attack on the leading edge of the airfoil to generate additional pull. Obviously if the top of the airfoil is hitting the headwind instead of the leading edge of the airfoil, there is no way to generate pull.
A propeller relies on the spinning of the blades to cause air to flow over the airfoil at the proper angle, and angle the airfoil hits the oncoming headwind is no longer a problem. Thus it will work in any tailwind situation, downwind, crosswind, whatever. Downwind gives it the most direct force, so it works best downwind.
My experiences with Linux (I've tried many times) have almost always been bad.
In my latest experience, my wireless card was finally recognized by default (I've installed linux on the same laptop several times), and things started off generally well. Wireless networking was still a pain in the ass, but I got it to work reasonably well. I found installing non-repository software generally involves hunting down libraries and editing make scripts, which irked me. In the end it was an audio issue that drove me over the edge. Apparently linux didn't like two applications that use audio at the same time, and between the two of them completely broke my audio settings. I managed to fix it, but it was several days of hell researching what would never have been a problem in Windows. That was the straw that broke this camel's back, and I upgraded to Windows 7 and haven't exactly been able to look back fondly on my linux experience.
You obviously don't know the business very well, since most IEMs run windows and require a thumbdrive to update the firmware, most control systems run windows, and most operator consoles are windows machines.
Assuming your network is safe simply because it is segregated is begging for catastrophy.
Did you miss the recent worm that targeted Siemans SCADA systems? One infected thumbdrive from a careless instrument tech and it's all over.
People in userland need data from the SCADA network to keep the business running. They absolutely must have a way to get it. Saying "no" isn't an option.
If by chance, you wish to do an update at some point, download the update, verify all the signatures with the vendor, burn it to a DVD and walk it over and install it.
Good advice. Try it with 30 plants covering a 1500sq mile area. While you were out all day updating your servers, an instrument tech forgot to clean his thumbdrive before plugging it in to an IEM to update the firmware. Since you didn't have regularly updating anti-virus, your whole network is now down and the company is losing millions of dollars an hour in lost production while you try to clean the 60 servers and 400 consoles on your SCADA network.
It's a full, separate network between the regular userland and SCADA operations.
Because your SCADA network is so wide open, only people who are absolutely integral to the operation of the plant should have access to it. These would be the operators, instrument techs, maintenance personnel, and support engineers.
Everyone who needs to work with data collected during the operation of the plants should be on a completely separate network and have no direct access to the process network. These people generally need internet and intranet access as well, which you want to keep off your process network for hopefully obvious reasons.
So how do you get data from one network to another while keeping them completely separate? That's what the buffer network is for. It's usually much smaller than the other two networks - just a handful of servers for data collection, perhaps a citrix server for indirect remote access between the two systems.
The connections on either end of the buffer network are tightly controlled - only one or two servers for even a very large environment should have access between the two networks (my environment is 20 or so plants sending data through three servers on the buffer network), and measures should be in place to ensure absolutely no direct access between the two larger networks is possible. This is critical to keeping your SCADA network safe.
To sum it all up, basically the buffer network is there to meet the practical needs of a business. The folks in userland need access to data, but it isn't safe to give them access to the SCADA network. So you have the SCADA network send data to the buffer network, and the folks in userland can access that data via highly restricted channels.
Even with that arrangement, you must take a lot of care to do it securely.
There's absolutely no reason industrial control processes should be accessible to the same web browser that can play Facebook games.
What part of "The network your SCADA system runs on should never, ever have direct access to your corporate network or the internet." did you misunderstand?
Firmware updates are usually applied via USB. IEMs and industrial consoles usually run some form of Windows. If you don't have regular Windows and AV updates, you're fucked.
Thanks for commenting when you have absolutely no idea what you're talking about.
Inkscape and it's perfectly fine... it seems to be compatible with illustrator.
There are a lot of things Illustrator can do that Inkscape cannot. I remember doing a 1-off project in Inkscape because I did not want to drop the cash for Illustrator, and then finding all these easy ways to do things in Illustrator that I was struggling with in Inkscape. I think Inkscape is a good program, but like GIMP it just doesn't compare with the real deal.
It's not about using what everyone else uses. If you need to perform a function often enough you are going to find the best tool for the job. It's like the weekend warrior who buys a $20 wrench set compared to the mechanic that has the $2,000 set complete with rolling tool chest. The $20 wrenches work just fine, but they do not compare to the professional kit. I have never seen a high end user application for which the open source version was superior. One may exist, but I've never seen it.
If you're happy to use Microsoft languages and Microsoft APIs and write software that only works on Microsoft Windows, then Visual Studio is for you.
Fortunately you only lose about 10% of the market this way. Not a big negative there.
It seems strange to work on something, or even use something, like this considering that the price of machines, as recently reported here on slashdot, is approaching zero. -- ThwartedEfforts
The more things change, the more they stay the same.
Slashdot Mirror
Exactly.
In my office, if you've got a cold, they don't want you there. Stay home. Don't spread it to everyone else.
One person missing a day is nowhere near as costly as half the office missing a day or more (some people recover more slowly).
All that stuff costs money. A lot of money, actually. In the US, with such "horrible slavelike labor conditions" (give me a break) benefits make up between 30-50% of the cost to employ someone. The more money an employer has to spend on each employee to get the same productivity the less he can spend on hiring new workers. It doesn't mean he will if he has the cash, but that's usually how companies grow - by adding more people.
The kinds of guarantees described would push every employee's cost up around 50% of their base salary, possibly even higher. Think about that. Without that 50% cost, for every two employees working now there could be an additional employee. That would theoretically cut unemployment down to about 15%. (in practice not as much, for various reasons, but you would definitely see more people being hired)
If you have all these rules then I'm sure you have a minimum wage as well, which further raises the costs of employment. In a highly productive society you can have these nice things, but if half the country is going hungry, don't you think it is more important that they be able to work instead of giving all these plush benefits to the few who can find a job?
Seems rather selfish and heartless to me.
40 hours per week, max of 5 hours overtime - it's ILLEGAL to allow more
God, not even the option to work more? That sucks.
I currently work 80 hours a week for two weeks straight, then take two full weeks off. My schedule (which is so freakin nice, I have half the year off) would be illegal in your country. If you were counting, that's 40 hours of over time every week. If I were working a 9-5 job, it would be like getting paid 50% more every other week.
Your country blows.
If you've got skills, you'll get paid regardless of the state of the economy. If you don't, you won't get paid unless the economy is really good.
That's life.
Wow, are you uninformed.
Take your ignorance elsewhere please.
Only if you conform to society.
But actions always have consequences. Denying it doesn't make it untrue.
You totally misunderstand what Freedom of Speech is.
You can say whatever you want, but if your words cause harm to others you may be held accountable.
For the government it is a pretty high standard that they have to meet before they can punish someone (serious national security type stuff, that wikileaks bs wasn't quite good enough), among private individuals there is no standard you need to meet before you can terminate your relationship, but if you can show harm (from libel or slander) you can sue successfully. Also if your speech causes immediate harm to the public you will be held accountable. Companies are the same as individuals, with exceptions found in labor laws.
Thus, the story of the NLRB declaring restriction of Facebook usage by companies violates the labor laws.
Look again.
See the two, red, bubble shaped things? Right in the middle there. Sort of coming off the center in a bubbly sort of way.
Those are the bubbles.
Apparent to whom?
(yuk yuk!)
How to build a freaking pimp kayak.
Some of the instructables are of seriously high quality. Most are not, but there are some absolute gems in there. A lot of it is great just for neat ideas. Like an arduino based RFID door lock or an automated home garden. You aren't going to be building it step by step from their design, but you can use them as a good jumping point, and it's easy to find a very wide range of projects on these sites.
The extra pics are available via the free membership.
I've never seen* pics that were available for pro members only.
Pro just gives you no ads and PDFs. Handy but not exactly necessary.
*Yes, I noticed it. If you didn't, good. Leave me alone.
Since when is 20% of the server market winning?
Granted, it's a hell of a lot more than the desktop market, but lets be real here, Linux is still getting crushed. Windows has 75% of that market locked up tight. Linux servers seem to be concentrated on web servers, which make up a small part of the server picture.
You must not understand how land sails and sail boats actually do it then.
They create an air-foil, which generates pull as the craft speeds up. This is basically a force multiplier on the wind pushing behind it. It is entirely dependent on the wind, but it can allow the craft to go faster than the wind itself is moving.
The reason land sails cannot go downwind is because you must have both the force from the wind behind the sail and the correct angle of attack on the leading edge of the airfoil to generate additional pull. Obviously if the top of the airfoil is hitting the headwind instead of the leading edge of the airfoil, there is no way to generate pull.
A propeller relies on the spinning of the blades to cause air to flow over the airfoil at the proper angle, and angle the airfoil hits the oncoming headwind is no longer a problem. Thus it will work in any tailwind situation, downwind, crosswind, whatever. Downwind gives it the most direct force, so it works best downwind.
In other words: "La la la la la la"
My experiences with Linux (I've tried many times) have almost always been bad.
In my latest experience, my wireless card was finally recognized by default (I've installed linux on the same laptop several times), and things started off generally well. Wireless networking was still a pain in the ass, but I got it to work reasonably well. I found installing non-repository software generally involves hunting down libraries and editing make scripts, which irked me. In the end it was an audio issue that drove me over the edge. Apparently linux didn't like two applications that use audio at the same time, and between the two of them completely broke my audio settings. I managed to fix it, but it was several days of hell researching what would never have been a problem in Windows. That was the straw that broke this camel's back, and I upgraded to Windows 7 and haven't exactly been able to look back fondly on my linux experience.
I gave up Ubuntu (again) about a year - year and a half ago, and I agree with each of his points.
They are largely the same problems that existed 10 years ago, with new faces.
You obviously don't know the business very well, since most IEMs run windows and require a thumbdrive to update the firmware, most control systems run windows, and most operator consoles are windows machines.
Assuming your network is safe simply because it is segregated is begging for catastrophy.
Did you miss the recent worm that targeted Siemans SCADA systems? One infected thumbdrive from a careless instrument tech and it's all over.
That is completely impractical.
People in userland need data from the SCADA network to keep the business running. They absolutely must have a way to get it. Saying "no" isn't an option.
If by chance, you wish to do an update at some point, download the update, verify all the signatures with the vendor, burn it to a DVD and walk it over and install it.
Good advice. Try it with 30 plants covering a 1500sq mile area. While you were out all day updating your servers, an instrument tech forgot to clean his thumbdrive before plugging it in to an IEM to update the firmware. Since you didn't have regularly updating anti-virus, your whole network is now down and the company is losing millions of dollars an hour in lost production while you try to clean the 60 servers and 400 consoles on your SCADA network.
Way to go man.
It's a full, separate network between the regular userland and SCADA operations.
Because your SCADA network is so wide open, only people who are absolutely integral to the operation of the plant should have access to it. These would be the operators, instrument techs, maintenance personnel, and support engineers.
Everyone who needs to work with data collected during the operation of the plants should be on a completely separate network and have no direct access to the process network. These people generally need internet and intranet access as well, which you want to keep off your process network for hopefully obvious reasons.
So how do you get data from one network to another while keeping them completely separate? That's what the buffer network is for. It's usually much smaller than the other two networks - just a handful of servers for data collection, perhaps a citrix server for indirect remote access between the two systems.
The connections on either end of the buffer network are tightly controlled - only one or two servers for even a very large environment should have access between the two networks (my environment is 20 or so plants sending data through three servers on the buffer network), and measures should be in place to ensure absolutely no direct access between the two larger networks is possible. This is critical to keeping your SCADA network safe.
To sum it all up, basically the buffer network is there to meet the practical needs of a business. The folks in userland need access to data, but it isn't safe to give them access to the SCADA network. So you have the SCADA network send data to the buffer network, and the folks in userland can access that data via highly restricted channels.
Even with that arrangement, you must take a lot of care to do it securely.
There's absolutely no reason industrial control processes should be accessible to the same web browser that can play Facebook games.
What part of "The network your SCADA system runs on should never, ever have direct access to your corporate network or the internet." did you misunderstand?
Firmware updates are usually applied via USB. IEMs and industrial consoles usually run some form of Windows. If you don't have regular Windows and AV updates, you're fucked.
Thanks for commenting when you have absolutely no idea what you're talking about.
I don't see why this was modded troll.
If this comment was trollish then so was mine.
A little consistency here mods?
Inkscape and it's perfectly fine ... it seems to be compatible with illustrator.
There are a lot of things Illustrator can do that Inkscape cannot. I remember doing a 1-off project in Inkscape because I did not want to drop the cash for Illustrator, and then finding all these easy ways to do things in Illustrator that I was struggling with in Inkscape. I think Inkscape is a good program, but like GIMP it just doesn't compare with the real deal.
It's not about using what everyone else uses. If you need to perform a function often enough you are going to find the best tool for the job. It's like the weekend warrior who buys a $20 wrench set compared to the mechanic that has the $2,000 set complete with rolling tool chest. The $20 wrenches work just fine, but they do not compare to the professional kit. I have never seen a high end user application for which the open source version was superior. One may exist, but I've never seen it.
If you're happy to use Microsoft languages and Microsoft APIs and write software that only works on Microsoft Windows, then Visual Studio is for you.
Fortunately you only lose about 10% of the market this way. Not a big negative there.
Installing software is a disgrace.
You have a problem double-clicking? Holy shit, how in the world do you get by in Linux?!!
...to do a million and one things windows can't.
Name one.
Dig your sig man.
I found this quote particularly entertaining:
It seems strange to work on something, or even use something, like this considering that the price of machines, as recently reported here on slashdot, is approaching zero. -- ThwartedEfforts
The more things change, the more they stay the same.
You're in the minority on that one bro.