wildgift

Ha ha. Ridiculous. The reason why smartphones and some tablets are popular has less to do with touch than with size. It's pleasant to hold a small screen a foot from your face for reading and watching videos.

I beg to differ. They have an awesome rice cooker, and their Panasonic Platinum line of big portable radios was cool in the 80s.

Sure, it's not hard, but there are some things that are challenging, like controlling customer expectations without upsetting them, making deadlines, or moving deadlines.

This is probably because a lot of them lack internet. Our internet penetration is around 75%. Medical insurance is 85%. I suspect there's a lot of overlap between the un-internetted and un-insured.

I'm suspecting that there's a diversity of situations among the people in the individual market that would make this challenging. These are people who are self-employed, or have low wages, or irregular work.

There's some discussion about this above. If the population is 70% white, then the job categories should be 70% white. 90% white isn't random.

There are a fair number of Vietnamese doing residential construction work. Same for Koreans. There are a LOT of Polynesian people doing construction. They aren't numerous in absolute numbers, but something like half the men work in construction.

The main thing that pushes people toward construction work is a lack of education, poverty, and a desire for a middle class life. It's hard work, but generally pays well after you're at it a while. But I think there's limited upward mobility for some people, because I notice lots of Asians in residential, but not in commerical, and definitely not in public works projects.

The reason why public works construction's heavily white is due to construction unions, who have generally seen their numbers declining. The tendency is for fathers to give their jobs to their sons. That fills the apprentice pipeline, and keeps Black and Asian people out. (A lot of Latinos are in construction and get in unions just by force of numbers.) These are the best construction jobs, and can get you an upper middle class lifestyle.

I think the issue of declining jobs or declining union membership tends to cause racist outcomes, even if the people involved aren't racist. Basically, if the overall field is shrinking, the tendency is to avoid hiring. If there are provisions to pass jobs on to their kids, people will do that. The end result is entire fields where the racial composition doesn't change.

As for Asian vets versus physicians: the coursework to become a vet is similar, and vet school is very expensive, but the pay isn't that great compared to a physician's pay. Becoming a vet is really a field for people who come from upper middle class families.

My guess would be that a large fraction of EMTs are in fire departments. Fire departments are notorious for being full of racists. They were pretty segregated until the mid 20th century, too.

As the system was taken over by the government, the pay got good, and it's one of the best jobs someone without college can get. So you can bet that the incumbents would use any weapon, including racism, to discourage competition for these jobs.

I thought this too, but then, due to my lame password management, my mtgox account got owned and they took out around $250. Oh well. Easy come easy go. But what I learned is that bitcoins really are like cash. You lose it, and you won't get it back.

That's what's different with Visa - there's an element of insurance with a credit card, and that is greater than what you get with a bank's checking account.

The insurance of being able to cancel a check is what you get with a regular checking account, and that's greater safety than what you get with bitcoin.

Of course, there's a price to this insurance, and it's the fees, which are much higher than what you pay for bitcoin transactions.

When Adobe buys them up, will funders get shares of Adobe stock?

she's probably getting ripped off in this deal.

That's messed up for the neighbors. Please don't do this.

The killer app is gvim and ctags.

I gave a linux pc to my coworker, for her kids, and they have been using it for a while to do homework. They have some issues now and then, but it works pretty smoothly. The computer is really old - a Sempron with a couple gigs of RAM.

Who is going to bother with a portscanner when there are plenty of targets on port 22. The targets on other ports are more likely to have been set to use keys, or at least have better passwords.

Attacks on port 22 end up consuming CPU.

The tech side is great. The wages side... not so great.

Also, it's not a "sharing economy" when people are selling things.

I wouldn't be surprised if the regulations exist but aren't enforced. What these workers need is power to enforce the laws... and in the absence of adequate laws, to marshal enough popular force to create agreements that are better than what laws might exist.

As first-worlders, it's our moral duty to support people who work to help create that power for the factory workers.

This isn't about that kind of sexism. It's about a softer sexism that's really about familiarity.

It's real, and it's a problem. Look at how Hilary Clinton was dealt with by critics and her handlers during her run for the presidential nomination. They were worried if she was feminine enough. I thought it was totally absurd, pointless, and even stupid, but I suspect it made sense to people in their late 50s and 60s.

In the same way, I'm kinda comfortable with the way Michelle Obama is treated by her supporters in the media - but if I stand back and really analyze it, it's patently sexist and offensive. Who cares about her domesticity? She was a CEO. What she brings to the table is being able to potentially work on policy or be a political operative. To people in their 40s (and maybe even 30s), though, this sexist treatment in the media makes us comfortable.

Even Laura Bush could have been an operative - but her party is old, and that just wouldn't fly. We're in the age of the power couple, and that's reality, but our biases and sexism will prevent this from being accepted for a decade or more.

There's still plenty of room for anger and protests. Maybe not in this particular situation, because it's basically an elite situation where you're trying to effect a cultural change, but in other situations rage is necessary.

Because it's true. Older men don't like to report to younger people in general, but are more okay with younger men than younger women.

There's sexist and there's sexist. Even the nicest person can be biased, and the bias can be basically invisible to everyone involved. Sexism isn't just about male chauvanists.

When you're leading, it doesn't necessarily matter who is at fault. Hiring someone who screws up reflects on the leader. Likewise, being unable to pull in the talent was a problem.

Why didn't he hint that during negotiations then?

My guess is that he just didn't feel comfortable reporting to a younger woman. Maybe he couldn't really figure it out, but he wasn't put into his comfort zone and backed off.

Dealing with a male, even a younger one, was probably easier. A bump in the title probably helped, too.

Oh yeah, DOS sucked. I remember Xenix and MKS and some other unixy toolkit. Oh yeah also Coherent. I ran a shell called Gulam on an Atari, and it was nice. Fake pipes were better than no pipes :)

Did all the processes run in the same address space on the Amiga??

Really? I though OS/2 was on the 386. I thought that the 286 had some limit on the size of a process, but you could execute multiple processes. I don't know why, but I think it was 64k per process. Also, the other thing I recall was thinking that it was a nice idea.

I was only familiar with 68k so I'm probably wrong here.

Ah, yes he did, except he was obstinate about using anything more fancy than email. As I remember it, though, there were a lot of ports of the GNU tools to all the unices, and the PC was still not as good as the Unix workstations. So where's the motivation to make Hurd, you know?

People weren't really clamoring for Hurd or a kernel for GNU, because they got an OS with their computer, and got the GNU tools and libc. The really major geeks would buy old, used workstations, which were built like tanks and were plenty fast for running single-user unix.

Calendars work when other people are depending on your decisions, and it's basically more important to make a decision than anything else. Everything is driven by the need to make that decision. The decision may be imperfect, but the overall system can tolerate that most of the time - and when it cannot, it appears as a schedule problem.

Calendars fail when you need to perform labor to complete a piece of work, and you don't know how long it'll take. A to-do list is a detailed list of tasks to complete, generally in a specific order, to complete a piece of work. That work is probably part of a larger piece of work. There are dependencies between pieces of work. Times, if they exist in the to-do list, are generally estimates.

The only way to put tasks into a calendar, if you want the calendar to reflect reality, is to pad out each task with extra time. That way, the schedule doesn't fail.

However, if you padded out your to-do list with enough extra time so you could fit it into a calendar that could remain largely unchanged for the next year... your productivity would be pretty low. It would be a pretty relaxing job, however.

There are problems when these two different ways to organize work aren't reconciled correctly. You have work crunches, where people are forced to work late, or you have calendar failures where your obligations to outside parties aren't met, or both.

Both are intolerable, and a sign of bad management.

Linus also had the internet. Look at rms' signature - UUCP, ARPAnet. The internet, usenet and the patch program made collaboration much easier.