Indeed. A warning is certainly appropriate, but news is news, however horrific it might be.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
As a former H1-B visa holder, current lawful permanent resident, and eligible for U.S. citizenship, you should know that the LAW requirs H1-Bs to be paid at least 90% of the prevailing wage, the employer to handle their INS legal expenses, AND bear the cost of sending them and their family home when they are layed off or their visa expires. H1-Bs generally cost MORE than locals, with all the extra hassles.
Now, where I would likely agree with you is that many companies BREAK those laws to bring in cheap labor, something which I would opose as well.
Yes, it's called "Disorderly Conduct", and is a misdemeanor most places.
HOWEVER, which that might explain a violent response, it does not excuse it: if you assault or kill someone because of what they say to you, even though their actions are criminal, so is your violent response. The proper response is a harassment charge.
Furthermore, that covers speech directed at you, not indirect speech intended for anyone who cares to listen: If I call a black man a nigger, I can certainly expect a punch (or worse). But, at least in the U.S., with it's First Amendment, I can write all the books and cartoons about niggers I want, without breaking any laws. Your recourse, if I offend you is simply to shun me.
Symform, not Synapse.
I once interviewed for a company, Synapse, IIRC, planning to do just that, using error correction to deal with lost/offline shards of data.
The first computer I built used a 6809 and ran either Flex or a homebrew monitor.
I have PLENTY of experience with AMOS on 68k systems. As Caroll Oconnor and Jean Stapleton sang: "Those were the days!"
Some of us might consider that a feature.
Docker is a lot of things, all rolled up into one so it is difficult to describe without leaving out some detail. What is important to one devops person might be unimportant to another. I have been testing docker for the past few months and there are a couple of things about it that I like quite a bit.
I have to explain a couple of things that I like about it before I get to the one that I really like.
1) It has a repository of very bare bones images for ubuntu, redhat, busybox. Super bare bones, because docker only runs the bare minimum to start with and you build from that.
2) You pull down what you want to work with, and then you figuratively jump into that running image and you can set up that container with what you want it to do.
3) (this is what I really like) That working copy becomes a "diff" of the original base image. You can then save out that working image back to the repository. You can then jump on another machine, and pull down that "diff" image (but you don't even really have to think of it as a "diff", you can just think of it as your new container. docker handles all the magic of it behind the scenes. So if you are familiar with git, it provides a git like interface to managing your server images.
It does a lot more than what I describe above, but it is one of the things I was most impressed with.
This is a bad idea.
I lived withing spitting distance of a meth house a couple of years ago, in a nice neighborhood. Wouldn't have known anything were it not for the fact that it got raided. 'Course compared to LSD, Meth is nasty.
Conversely, I didn't dabble much with cassettes. The business for which I coded, very briefly used a cassette deck to load BASIC into the Altair, but switched to 8" hard-sectored floppy drives (being a business, it had "infinite financial resources" compared to my meager means, for some value of "infinite") very quickly: fiddling with the level settings and waiting eight minutes to load BASIC (after enterring the cassette bootloader by hand from the front panel) was not practical.
I DID once write a loader for that same Altair 8800 that used a TI Silent 700 with dual digital cassette heads that recorded at 5120 bps (IIRC) on digital cassettes (or high quality cassettes with a hole punched at the right spot in the leader
I guess the punched card thing was more of a mainframe/mini-computer thing. When I started my undergraduate degree in 1979 most programming at the university was still done on punched cards and run "batch". We did have a row of ten DecWriters, and an express CRT terminal, but there were more punch card machines available. When accounts were issued, they were in the form of orange "control" punched card (80 column) "ACCOUNT command" cards. More mainframe CRT terminals were added over time, and were covetted because they were 1) faster than the DecWriters at 1200 bps over current-loop interfaces, and 2) didn't suffer the inconvenience of having to constantly go get scrap paper (and ensure that someone didn't comandeer your DecWriter!). The downside was that they displayed 24 rows of 80 colums text. So, having got a clean compile, one of the first things one would do was request a printout from the mainframe printers.
What I would do was code on the terminals, and at the end of the term, or when I was running out of my very small disk space allotment, get special permission to have my programs punched on cards for posterity. I got "mag tape" privileges about 1980/81 but realize that the recording density was 1600 bpi (later 6250) and the longest tape real was 2400 feet, so about five megabytes on a long tape (later 22.5 MB, but the 6250 bpi tapes were "finicky"). Only recently did I get rid of about 100 pounds of punched cards.
Actually, to be accurate, I got the Honours degree in 82 and followed it up with a Master of Computer Science degree in 84. Had just a video monitor and 300 BPS Hayes "Smartmodem" at home to connect to the university Cyber 7600 and later 835 mainframes.
HP2000 timesharing computer system with remote access via teletype at 110bps and an accoustic model. I can still remember the smell of teletype ribbons and paper in the high school computer room.
Why? To be able to get the computer to compute stuff for me. Initial programs were to print trig/log tables so i wouldn't have to buy them. I was already a science geek, computing orbital parameters for fun, and adding logs was easier than multiplication.
I was 13 years old. It was 1974.
The next year the high school got a 300 bps DecWriter. OMG! That was "fast". We got a card reader and optical scan 40 column cards, so we could "program" outside of the computer room. At some point we got a 1200 bps portable thermal paper TI terminal.
By 1975 or 76, I was hacking on an Altair at a local business, writing accounting software for them in Basic.
My first computer that I actually owned was a 6809-based system running Flex around 1984. A PC clone came shortly after that. By this time I was well on my way toward an Honours Computer Science degree.
As a former H1-B holder, and current lawful permanent resident ("Green Card"), here long enough to become a citizen (> five years), H1-B DO NOT work cheaper.
At least, it is ILLEGAL to pay them less than 95% of the prevailing wage in the local area (as determined by the State Dept. of Labor). Furthermore, the employer has to bear the brunt of non-immigrant related legal paperwork and the cost of sending them home at the end of their visa. H1-Bs actually cost employers MORE than citizen workers.
While it is true that contracting firms and employers themselves will often lie regarding wages, this is criminal, and strongly opposed by legal H1-B workers as much as it is opposed by citizens.