Flemming Quist Møller (70).
Andita dwi Meirna (35).
Riot in Copenhagen; Police shoots directly at people; 11 wounded (19).
Stig Pedersen (47).
Per Rossing (50).
Walther Frederiksen (92).
Recently it has become all the rage to use AJAX/HTML5 for navigation: instead of letting the browser fetch a page from scratch, a part (or all the content - I am looking at you, pjax) is fetched via AJAX and the URL is manipulated via the new pushState functionality introduced in HTML5.
While it is a very cute trick, it also demands a lot of the website developer to make it work right. Browsers have been through roughly two decades of evolution by now - do you think you can re-implement core browser behaviour in a couple of lines of Javascript?
If github can't, chances are you can't either. So checkout out why you should not do it.
I would love to be proven wrong. Leave a comment.
Update: Oh my gawd, even the new bobdylan.com uses this horrible abomination of a bad idea!
⊗ (0 comments)
"That said, exactly because they are so important, it does frustrate me when I hit things that I perceive to be steps backwards. [...]
The same thing is what frustrated me about many of the changes in Gnome 3. The whole “let’s make it clutter-free” was taken to the point where it was actually hard to get things done, and it wasn’t even obvious *how* to do things when you could do them. That kind of minimalist approach is not forward progress, it’s just UI people telling people “we know better”, even if it makes things harder to do. That kind of “things that used to be easy are suddenly hard or impossible” just drives me up the wall, and frustrates me."
- TechCrunch interview with Linus Torvalds, 2012 nominee for the Millenium Technology Price.
⊗ (0 comments)
I just noticed that the current crop of consumer motherboards now support 8GB memory modules, making a switch from 16GB to 32GB in my desktop computer feasible.
So I spent a while looking at CPUs and motherboards.
Man, what a jungle.
What I'd like is a CPU with low power consumption and a motherboard with firewire and room for 32GB ram.
That should be pretty straight forward, right?
I have been using AMD processors since I retired ye olde Intel Pentium 4(?) 800 MHz, so I went looking at AMD.
It seems that there are no 45W CPUs in AMDs current line up (not considering processors "below" the Phenom II line (I have an AMD Athlon II X2 245e currently)).
65W AMD CPUs are the prohibitively expensive AMD Phenom II X4 910e and the slightly pricey (compared to similarly numbered CPUs with higher power consumption) A8-3800.
Hm.
Then I looked at Intels offerings. The Intel Core i5-2500T is a 45W solution, but ... a motherboard with firewire for Intel CPUs is a bit more expensive than the AMD alternatives, and do I really want to buy an Intel CPU?
Maybe I should just wait. Or do you have some good advice?
⊗ (0 comments)
I have made two files to test the problem I alluded to earlier:
Both files are just a 440 Hz sine wave for 5 minutes.
Here is the experiment: transfer both files to your phone. Start playing the 44.1 kHz one, turn off the screen. It sounds the same with the screen off and on, right?
Now try with the 48 kHz file. As soon as I turn off my screen, the sound starts to crackle and pop!
As some podcast-producers distribute 48 kHz-files, this is quite annoying; and it took me a while to find, because it only starts when the screen is turned off.
I wonder where the correct place to report this bug is?
It seems to have been reported before.
A comment in the first report notes that if you turn on the equalizer (in the "Play Music" app, choose "Sound Effects" in the top menu), the problem disappears. This work around works on my phone, but...
⊗ (0 comments)
Hacker News has two polls:
Here are plots of the votes:
Enjoy!
Update: I got some feedback on my graphs, and have added a scatter plot as well! And the scatter plot with log scales.
⊗ (0 comments)
Email-client:
Calendar:
Come on, phone folks, adding a tea timer can't really be that off putting to your sense of clock design!
Music:
MarketPlay:
Sync:
Really. I mean: Really.
⊗ (0 comments)
I have resisted creating a Google account on my Samsung Galaxy Nexus until today.
Maybe my tinfoil hat has been pressing too hard on my skull, but I thought it would be an interesting experiment to see how long I could use my new phone without signing up and potentially giving Google access to all my data.
Today I created a new account, so I could download the ~10 apps I wanted to installed from the Android Market^WGoogle Play Store.
After installing the apps, I went into Settings to remove the account. A window popped up warning me: "Removing this account will delete all of its messages, contacts and other data from the phone!"
Uh oh. That didn't sound nice.
It sounds like removing the Google account might mean that the contacts I had in the phone before I created the account would be deleted?!
I really didn't feel like recreating them all from scratch. So, before clicking the "OK" button, I went to my contact list and exported it to a file, which I then email'ed to my desktop computer.
Which turned out to be a good idea, because after removing the account, the only contact left on the phone was myself!
That is not only stupid but also rude!
Following the logic that my data from before the account was created now belonged to the Google account, I went to my desktop computer and logged into Google Dashboard with the account I just removed from my phone.
The phone had been granted full access - makes sense. Revoked.
There was a calendar. Which cannot be deleted. The interface says it is deleting it, but it keeps appearing in the list.
There were three welcome emails in Gmail. Never mind.
There were two bookmarks in Chrome Sync. Deleted.
But here is the kicker: The 51 contacts that was deleted from my phone a couple of minutes ago was automatically uploaded to the google account without my consent. (Didn't Path just get into trouble for doing something like this?) Deleted.
My tinfoil hat and I feel vindicated. You may snicker as much as you want.
⊗ (0 comments)
