Exactly the opposite: when things are dark, your pupils dilate and you need less light. Do you turn your smartphone brightness down in bright sunlight?

But brightness isn't the point -- color temperature is. I haven't read the documentation; the software is too simple and easy for that, but the homepage describes what it does. Flux lowers the color temperature at night, which interferes less with sleep. I also find it much more pleasant.

Probably Poe's Law, but you can never be sure.

Yes but what usually happens, is they are "suspended with pay."

That's the problem with "qualified immunity", the cops are above the law in most cases.

According to the EEOC (Equal Employment Opportunity Commission), blanket policies against all felonies are discrimination, under Title VII of the Civil Rights Act of 1964.

EEOC Enforcement Guidance

Blanket policies are racially discriminatory.

That being said, if you're caucasian, you probably won't be able to get anyone to pick up the case. The ACLU won't touch it.

The felony is only supposed to be discriminated against if it affects the job position, i.e., if you rob a bank, you shouldn't be allowed to work in a bank, etc.

They also ban felons from getting professiona licenses (such as a plumber's or electrician's license), getting SNAP food benefits, TANF benefits if they have kids, student loans, etc. Unless the state has passed legislation opting out of the ban, like many have.

It's not right, felonies weren't meant to become life sentences in most cases, but this has the effect of becoming a life sentence. And they wonder why people return to crime... it's because they have no other means of supporting themselves.

Seattle,WA passed a law making it illegal to ask about felonies until you've been given an offer of employment.

> See also #3.

Sorry, you wanted the numbers rendered on your ordered list? Wrong site.

Yeah, I can't imagine why they did that, either.

What is going on here with the lists? Who at Slashdot thought that non-list lists made any kind of sense? How do Slashcode devs not understand the effects of list-style-type: none;? Why does this persist?

Perhaps more salient, why are we, as ostensible tech geeks, not raising more of a fuss about a site that many think represents computer geek-ness, and yet that cannot implement sane (and relatively simple) CSS?

Thank you for that! I haven't laughed like this at an academic paper in, well, a really blooming long time.

And as a bonus, I've given the folks here at the coffee shop something to stare at. :)

Disabling the security check is a bad idea though. It's just better to run all your malware in userspace. :)

You should not have to choose between using 3rd party hardware and having a secure system.

It's nowhere near as hard as you're claiming. Those are bad practices even if you only ever intend to run on Windows. And .NET has had portable ways to do these things since version 1.0, and always encouraged their use.

To me the correct, portable code looks easier to read and write. You don't have to check if directoryname already has a trailing seperator, for example. The Path APIs will also handle .. (and ~/ on linux).

In practice there are only a handful of things you need to know to write portable code in .NET. It was always designed to be cross-platform.

There is no interpreter -- .NET code is never interpreted. The output of the C# compiler is CIL (Common Intermediate Language), which is akin to the output of the front end of the LLVM compilers (called IR "Intermediate Representation"). (note: .NET is older than LLVM)

In both .NET and LLVM, the intermediate language is not suitable for interpretation. It is always translated into native machine instructions before execution. In .NET that can either be at runtime (JITed) or install time (NGENed).

I'm simplifying of course. They don't need to write an interpreter, they need to write a back-end and port the runtime components.

Also, I don't think there's much if any C/C++ left in it, it's C# all the way down.

Give it a little time, you won't like your kids either.

I totally agree. I've conducted dozens of interviews for software engineers. I couldn't hire a black developer if my life depended on it -- I've never had a black candidate. I know the recruiters aren't to blame -- they're desperate for qualified candidates. There were no black people in my university classes either. The dearth of women in IT gets plenty of headlines, but I've known lots of women programmers, including 3 bosses over the years. In my entire career, I've only ever known one black programmer.

It must start long before high school.

That is just categorically wrong, in any industry. It's laughable in the software industry where getting and keeping employees is one of the biggest challenges.

You obviously don't work in the software industry. Employers not only tolerate all kinds of non productive things, they actively encourage them. Software engineers are treated like spoiled, geeky royalty.

OK, now I know you don't work in software engineering. Or any engineering. Trying to convince our employer to do things that are less profitable but more interesting is what we do.

I think it's a myth that people aren't learning C. I interview a lot of devs, many just out of college. Most of them know C/C++. They may be more comfortable with Java/C#/whatever, but they at least know C++ syntax and understand the memory model, etc. It would make no sense for universities to ignore C/C++, if for no other reason than the huge amount of code out there in those languages that you may need to understand. Kids in CS these days are still writing their own compilers, toy OSs and memory managers.

High level languages are more productive, no doubt about that, so it makes sense to learn them. But lower level knowledge is not made obsolete. You're still better off knowing C/C++ and some machine-level things, at least enough to read the code, understand a stack trace, memory dump, single step through compiled code, etc. So learning the high level tools is in addition to the traditional tools, not instead of them.

Yeah, I miss the days when we coders worked closer to the metal, calling getelementid directly instead of using some high level abstraction like jquery.

I'll second that. I've been coding professionally for almost 20 years. Even done some assembly. Yes the tools are much better and more is automated, but the amount you need to know is only growing, and the expectations have never been higher. I don't think the automation is even keeping up actually. Making software is not getting easier.