smoove
smoove on Hacker News
Robin Dunbar disagrees with this huge monkeysphere
#11: dinmamma == your mom.
go sweden!
Musician.
Soometimes, while playing guitar, i wish i would not own a computer, because i'm sure my guitarplaying would be so much better... then i snap back to the real world and am happy as fuck that the computer pays my food.
benchmarking with a "hello world" program... seriously?!
How many hello world services do you guys run in production?
I for one exclusively use GNU wget for my surfing needs! Through GNU Emacs of course.
Uhh, a custom cursor! Whoops, i left your site...
"5. Keep passwords as encrypted for security. Decrypt them in application when required." stopped reading there
This is from 2005, love this line: "2009 developers will face cpus with 20+ cores".
btw. where is my jetpack goddamnit...
Oh. my. god. there is a guy on the internet making comics about my life. oO
I've got the exact same function (also php) but mine is called print_arr() as in array.
Normal German layout, with some keys (braces and other programming stuff) mapped to the home row with caps lock as the modifier key. So <caps lock>+h = $ for example -> sucks to program on computers not owned by me ;)
I also consider to switch the y and z keys like in the us layout, because i need the y key way more often (copy selection in vim) and find it very uncomfortable to reach.
That's just playing a video of a location in the same location?! There is no augmented reality whatsoever, just watching videos...
>>Would it really? I'd like to see some hard data on that.
The process would be this:
-> User submits Regex
-> Google fetches all documents in it's database (46 billion documents according to mryan) - If we assume 1kb of data per document (wich is probably way to small), google just fetched 43869 GigaByte of data
-> now google somehow iterates over said 43869Gb (we assume we have a lot of RAM btw.) and check if the regex matches any of them
-> Search results are delivered to user (days later?)
I can not give you any "hard facts", but the problem is that if you can not build an index, you have to look at each individual document. And in google's case the amount of documents is just way too high.
I guess the main problem is that you really can't build an index for regexes, you would need to apply the search regex "live" to all the documents the searchengine knows - this will not scale at all.
Also, if you let a user search for any regex, it would be really easy to overload the server, by entering very complex regexes.
Genius: Body restricts reach to arm length...
Maybe he is too young to remember the pre-google search experience ;)
I don't have anything running on that port :/
Welcome to the wonderful world of youtube comments, where kids and inbreeds meet to discuss their thoughts.
"We'll do a rewrite later on ...", nope!