If someone is considering offing themselves, it might be simpler to take their gun and blow their head off instead of trying to hang themselves, jump off a building/bridge, slice their wrists, etc.

To the person doing the act, shooting themselves in the head is probably going to seem less painful and more convenient then most other options.

If that's the case, then removing the gun might reduce the chances of actually carrying through on a suicide attempt.

How would you propose to decide who is responsible enough to own a firearm? Can crazy people own them? What about clinically depressed people? What about people under psychological treatment generally? At what age should someone be able to carry a firearm? Should they be allowed in all buildings? Should businesses be allowed to deny entrance to people carrying weapons? What about on a plane/train/bus/etc.?

Assuming current OS behaviour, I'd be happier with a ~42-46" 4K screen. Just a bit higher pixel density than my current 24" 1920x1200 monitor, but almost 4x the number of pixels.

With current OS behaviour, a 32" 4K screen would have teeny-tiny text in some places.

The only advantage I can see would be that you could "fullscreen" the app within the virtual monitor area.

Some apps (media players, for example) behave differently when run fullscreen vs within a window. The "virtual monitor" window manager would let you trick the app into thinking it was running fullscreen.

It's just the ubiquitous crappy ones that don't.

Presumably it would be just a hollow shell, and thus vastly lighter in weight than the pyramid of giza.

I don't see that in the Sears catalogue anymore...

Personally I'd love to have a 48" ultrawide 4K computer monitor, with a substantial curve. As it stands, people with multimonitor setups already curve them, so this would be no different.

By writing it in macros the code is moderately human-readable, while giving the performance benefits of actually being written in assembly. By doing it that way the compiler also has the opportunity to optimize the assembly somewhat.

And the legal opinion there was that to switch licenses would require the approval of every copyright holder.

By contributing to the codebase they did not actually assign you copyright...so each contributor holds copyright in the portion that they actually wrote.

Even now it's possible to just make a good product, treat your employees right, and sell it for a fair price.

Some personal examples in the woodworking tools category: Lie-Nielsen Toolworks, Veritas Tools.

The problem is that the physical DVD netflix service has a selection that is different from the streaming netflix service. If you want the increased selection, you have to forego the ability to download it.

There is no technical barrier preventing netflix from allowing you to download a DRM'd exact copy of a DVD. You could then play it, or transfer it to another device, or maybe even transcode it for smaller screens and transfer it to another device, all within their app. The only barrier is copyright. And by allowing in-advance downloads you could preload devices for use where there is no data connection.

The OP is suggesting that this copyright barrier doesn't make sense.

The streaming library is currently different from the physical DVD library. Not everything is in both.

I would support a model that actually reflects the real costs involved...that is a fixed monthly cost for the physical connection, and a variable per-GB charge.

The reason why most people don't like bandwidth metering is that the ISPs charge way too much per GB at the retail level. And if you lump the connection costs in with the bandwidth costs then the high-usage people end up subsidizing the low-usage people. It's much more fair to break out the fees separately (the way my gas/electrical/etc bills do it).

I think if end-users were charged a per-GB rate that was more in line with the wholesale rate plus a reasonable amount of profit then there would be minimal complaints.

If it was only about equal traffic in both directions netflix could just have all their clients send random data back to their servers and then just drop all the data. That would increase the overall network load, but it would be "balanced".

Seriously, it makes no sense that increasing the overall network load would reduce the fees being paid. That's ridiculous.