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).
Another incentive might be to route all (say) netflix traffic to a VPN so that it doesn't get throttled by your ISP.
Or routes out through a country that doesn't have shit for selection.
find . -maxdepth 1 -name -f -delete
python -c "import os; os.remove('-f')"
after swearing at my terminal for a while before resorting to reading the rm man page.
I find that half the time the swearing comes after trying to read the man page. Then it's time to fire up the old Google...
... which more often than not returns a link to the online copy of the man page
80 columns is fine if you are only working with a single file. Being able to have long vertical views of code with documentation, design work, other code, compiler outputs, etc beside the code without having to switch between virtual displays is a huge productivity booster.
Call me spoiled if you like, but without people pushing for bigger and better ways of doing things, we'd still be stuck punching holes in pieces of cardstock and hoping we stacked them in order.
Then you need better eyes.
What? I'm saying that even on standard desktop-sized displays, I can see the characters become blocky when reduced because there are not enough pixels. Someone with poor eyesight wouldn't notice a difference between a pixel display and a printout at the same physical size.
Why is there no mention of Display Port? Current 4K LCD all accept this, and with the right GPU, you can most certainly drive at 60Hz, full resolution.
This is more about HDMI being a broken standard to me. I just don't like DisplayPort because it's sort of Apple's thing.
I regularly use a 1080p monitor in the 24" range and I can tell you I would *definitely* like the resolution to be higher. I do a lot of text-based work and I can see the letters start to get blocky if I reduce the text size while I know for a fact I could easily read text even smaller when printed on a decent laser printer.
Try it one day. Use a word processor to print "the quick brown fox jumped over the lazy dog" in steadily reduced font size down the page. Print that page and hold it next to the computer screen at a comfortable viewing distance and find the smallest font size you can read on the printed version and the on-screen version. If picked the same paper and monitor sizes (as measured by a real-life ruler), you may want to see an optometrist.
Yes, resolution DOES matter. A line of text requires a certain number of vertical pixels to be legible. Whether that line is an inch high or a quarter-inch high makes no difference. For people that need to see more at once, they absolutely do need more pixels. The image from a 1080p projector may look fine from across the room, but you can still only see a small amount of text at a time.
You are making the fundamental error that people just want their displays to look nice instead of actually being able to see either fine detail or large quantities of information at the same time. Some of us DO need (or want very, very much) more pixels on our displays.
That's just it. The summary says "Had the keys been leaked..." when in reality it is very obvious that they were leaked, Nokia just paid somebody and hoped they wouldn't use it. Encryption keys aren't something you can just give back, and a giant certificate revocation would have been noticed by a lot of security researchers.
Basically, this story boils down to the fact that Nokia is out millions of dollars and their infrastructure is STILL compromised. Pinky swear indeed...