Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
User Journal

Journal: Two minutes of euuugh 2

Journal by Qzukk

Chrome's new bookmark manager is definitely a poster child for "half-ass it then push it to the masses". It seems to be working hard to almost replicate the Windows 8.0 Metro interface that everyone loved down to the "checkmark a tile to open the menu".

Tips:

If you want to make a new folder, go to the folder you want it to be in and press the NEW button on the left outside of the folders, there's no button for it on the right inside the folder (but there is a button to delete the entire folder from inside the folder).

If you want to drag items into your new folder, drop them quick. If you hesitate Chrome decides that you are re-ordering the items and you want the bookmark to go before the folder even though your mouse is directly over the tile.

If you have nested folders, opening a subfolder seems to randomly display all the elements in the center of the screen where you can't click on anything because its all on top of each other. Sometimes. There's no tree view of nested folders. Top level folders are on the left, after that you have to drill down individually.

No right clicking. Haven't you heard that there's no way to right click on a tablet?

When you checkmark a folder you don't get the option to edit its name or description. You have to open the folder then rename it from the inside.

User Journal

Journal: nettin_pure: Gone?

Journal by johndiii
nettin_pure seems to have stopped updating his journal. Sad; it was a constant in a changing Slashdot. It will be missed.

In any case: Happy birthday, nettin_pure. I hope the day has been a very good one. LÃ breithe sona duit!
User Journal

Journal: I logged in. 2

Journal by rdewald

I was doing some research for a project and happened back here. Hello slashdot.

Find me on Twitter, or put dot com after my user name.

User Journal

Journal: 0.38 Seconds of Hate 2

Journal by Qzukk

For the love of all that is holy, please do NOT automatically select shit from a dropdown list if I'm typing and a dropdown opens up underneath where the mouse pointer just happens to be idling on the screen.

Chrome: This. Means. YOU.

User Journal

Journal: Chances of being killed by police in the USA

Journal by Space cowboy

So 104 people were killed by police in the USA during August, 2014. To my eyes, that's an absolutely enormous figure. As a Brit, I compare it to the 1 person killed over 3 years by the UK police. Yes, they're two different countries, yes there's a lot more people in the US, yes they have different cultures, yadda yadda yadda; people are dying here.

Let's do some maths:

  • Population of the USA: 319 million (source: http://tinyurl.com/bpotuf9)
  • Percentage chance for a person to be shot in August is then: (104 x 100%) / 319,000,000 = 0.000033%

That's a scarily huge percentage, given that it's normalised by population. Bear in mind that police in the USA are not ... shy ... at shooting at suspects, and neither are they 100% accurate. Some of the casualties are in fact bystanders.

Now let's consider extrapolating for the period of time that most shootings occur (i.e.: suspect between the ages of 15 and 40), and see how that changes things:

  • Chance to be shot over 25 year period = (104 x 12 x 25 x 100%) / 319,000,000 = 0.0097%
  • Rounding that, since this is an extrapolation, we get 0.01%

Now that's an amazingly large percentage chance of being shot dead by a policeman. Let's do the same thing for the UK:

  • Population of the UK: 65 million (source: http://tinyurl.com/kzsalbe)
  • Percentage chance for a person to be shot over last 3 years is then: (1 x 100%) / 65,000,000 = 0.0000015%
  • Therefore percentage chance for a person to be shot in August 2014 is 0.0000015 / 12 / 3 = 0.0000000427%
  • Therefore percentage chance to be shot over 25 year period is 0.0000000427 x 12 x 25 = 0.0000128%

Compare 0.01% and 0.00001% and remember these are normalised by population. Yeah.

User Journal

Journal: [Beloved] It Is Not a Word 2

Journal by johndiii
It is not a word spoken,
Few words are said;
Nor even a look of the eyes
Nor a bend of the head,

But only a hush of the heart
That has too much to keep,
Only memories waking
That sleep so light a sleep.

-- Sara Teasdale

I remember.
User Journal

Journal: Holy shitballs, slashdot. Malicious ads being served up.

Journal by Qzukk

Love is over.

I was redirected to http://java-update-us.com/index.html?sid=42&aff_sub=wb-playanma-us&aff_sub2=am1&aff_sub3= which dropped a java_installer.exe into my Downloads folder from some ad playing on http://science.slashdot.org/story/14/07/24/1357256/empathy-for-virtual-characters-studied-with-fmri-brain-imaging around 2:30PM central time 7/24

User Journal

Journal: Serious proposals to replace obamacare begin 49

Journal by Qzukk

The WSJ has floated an opinion piece offering what it calls a conservative alternative to Obamacare, that I think is the first time I've seen any conservative alternative except "Nuh-Uh!" Google news popped it up with a link to http://stream.wsj.com/story/latest-headlines/SS-2-63399/SS-2-381425/ which seems to be some sort of glorified rss feed with an HTML skin, so I have no idea if the link will be good for anyone else in the future.

It is, in my opinion, a beginning. In the past, I've called obamacare the wrong answer to the wrong question. This article suggests extending the current employer tax writeoff so that everyone, not just the employers, can buy insurance with tax-free money. Then it goes a step further by means-testing a tax credit for the poor so they can buy privately operated insurance with their tax credit instead of getting Medicaid. I think this is a good start to answering the question of how to make it possible for everyone to get at least minimal health insurance (if they want it. This is the conservative version, remember).

It is still the wrong question, though.

User Journal

Journal: 2.8 seconds of hate - bash-completion 1

Journal by Qzukk

In an effort to be fancy and helpful, bash now has context aware tab completion (in the bash-completion package on Debian). Based on where you are and what command you're typing, pressing tab will Do (what the completion script writer thought was) The Right Thing.

Unless what you think is the right thing was was the behavior of older versions of bash where you could do

**/*.c<Tab><Tab>

and (eventually, ** is damn slow) get a list of all of the matching files. It also worked with [...] {...} ? or any of the other bash wildcards. You know, just in case you wanted to see what your command is going to do before you hit enter.

Now I have to ^U, ls ^Y, then ^Y, which takes about 2.8 seconds (including the realization that bash is just going to keep beeping at me if I keep hitting tab). Or disable fancy and helpful completion with complete -r

User Journal

Journal: Two minutes of WTF 1

Journal by Qzukk

So I right clicked in an explorer window in windows 7 and went to "New >" on the menu and the submenu didn't open. I clicked it a few more times and nothing happened. I clicked it a few more times and the entire explorer shell crashed and restarted.

Wish I knew why the hell it sometimes takes 30+ seconds to get to "New Word Document" on my work computer.

User Journal

Journal: 2 mins of hate: What can make me switch to a new RCS again 1

Journal by Qzukk

Three words: Four. Way. Diff.

Show me where my patch (before and after) conflicted with the last patch (via blame) before and after. Bonus points if you can show both complete commit messages. Extra bonus points if you look at the branch, figure out where it went wrong (at what point did my patch last apply cleanly?) and show me all the commits since.

Telling me shit's fucked up doesn't help anyone (that's what I got with cvs).

Telling me what I was trying to do tells me what I was trying to do, not what Bob was doing when he checked in before me, but at least I know what the hell I was doing when I did it months/years ago (this is where I am now with git rebase).

Telling me what the hell I was trying to do and what the hell Bob was trying to do, now that's what I need, because now I know what it's supposed to be doing when I'm done merging the code and can do so with a reasonable degree of confidence that both Bob and I will be happy with the result.

For my company's workflow, this would be the holy grail of revision control. I'd even be tempted to use a graphical tool to do it.

fortune: cannot execute. Out of cookies.

Working...