xkarga00

31 ms·

271.
by xkarga00 13y ago
They wouldn't sell many more in any case... unfortunately.. ps. huge Ghostface fan right here
272.
Running Raspberry Pi natively in a Honda Civic(technologytell.com)
27 points by xkarga00 13y ago|17 comments
273.
by xkarga00 13y ago
"I am reminded of Dijkstra's remark that the teaching of BASIC should be rated as a criminal offense. Seeing the hapless candidate get bowled over by a question that should be a mere formality makes me wonder if the same might be
274.
The foundation for an open source city(theopensourcecity.com)
1 points by xkarga00 13y ago|0 comments
275.
Ten reasons not to use a statically typed functional programming language(fsharpforfunandprofit.com)
2 points by xkarga00 13y ago|0 comments
276.
Let Zorin OS pick up where Windows XP left off(techrepublic.com)
1 points by xkarga00 13y ago|0 comments
277.
by xkarga00 13y ago
There are no implications here, it's stated pretty explicitly: "Reference counts MAY be best done by putting a mutex around an integer variable, for instance. BUT as a high-level approach, using channels to control access makes it
278.
by xkarga00 13y ago
Probably by making the mistake to read the Effective Go. http://golang.org/doc/effective_go.html#concurrency "Do not communicate by sharing memory; instead, share memory by communicating. This approach can be take
279.
by xkarga00 13y ago
Using mutexes isn't considered as idiomatic Go code
280.
by xkarga00 13y ago
http://tuxradar.com/content/take-linux-filesystem-tour/
281.
by xkarga00 13y ago
Just downloaded and tried the app. Simple and elegant, very good work!
282.
Parallel garbage collection(research.microsoft.com)
2 points by xkarga00 13y ago|0 comments
283.
Why i switched from Python to Go(slideshare.net)
3 points by xkarga00 13y ago|0 comments
284.
Dr. Dobbs Journal – February 2014(dc.ubm-us.com)
2 points by xkarga00 13y ago|0 comments
285.
Famous Forks(geek-and-poke.com)
2 points by xkarga00 13y ago|0 comments
286.
Test-Driven Development for Embedded C [book review](agilesoc.com)
2 points by xkarga00 13y ago|0 comments
287.
Dwarf planet Ceres is spewing water into space(theverge.com)
1 points by xkarga00 13y ago|0 comments
288.
Computer Programming using GNU Smalltalk (canol.info)
2 points by xkarga00 13y ago|0 comments
289.
Where the world’s biggest coffee drinkers live(qz.com)
1 points by xkarga00 13y ago|0 comments
290.
Sacramento Kings Accept Bitcoin Now(gizmodo.com)
1 points by xkarga00 13y ago|0 comments
291.
USS Rancocas: The Cornfield Cruiser(lockheedmartin.com)
21 points by xkarga00 13y ago|7 comments
292.
Take the Evernote Coding Challenge(evernote.com)
1 points by xkarga00 13y ago|0 comments
293.
Why Tablets Won't Replace PCs Anytime Soon(mashable.com)
4 points by xkarga00 13y ago|1 comments
294.
My Android phone opens my garage door when I approach my house on my motorcycle.(github.com)
2 points by xkarga00 13y ago|0 comments
295.
by xkarga00 13y ago
Kanye West Demands Coinye Programmers Shut Down the Digital Currency http://newsfeed.time.com/2014/01/07/bound-2-happen-kanye-wes...
296.
New cryptocurrency inspired by Kanye West(coinyeco.in)
3 points by xkarga00 13y ago|1 comments
297.
by xkarga00 13y ago
"They expect continued support and upgrades not a dead forgotten project 3 years down the road." Go is open sourced for like the last 4 years and has its own separate community. There isn't such a possibility either down or u
298.
by xkarga00 13y ago
"Does Google pay full time salaries and lets primary Go creators work on Go during the day?" Have you ever read any interview or watched any presentation about Go by Rob Pike, Andrew Gerrand, or any other Go/Google engineer?
299.
by xkarga00 13y ago
Of course it is implied that there is future support for Go since there are serious people behind Go who are Google developers but its current popularity comes from various implementations of the language and "rewritings" which ar
300.
by xkarga00 13y ago
"Our engineers were comfortable with Git and we preferred to stay with a familiar tool, so we took a long, hard look at improving it to work at scale. After much deliberation, we concluded that Git's internals would be difficult t

More ›