matslina

4 ms·

1.
by matslina 3y ago
Whitespace is ignored in Brainfuck, so just write the compiler in brainfuck and then strip all but 6 newlines.
2.
Save Mars; Quit Twitter(savemarsquittwitter.com)
1 points by matslina 4y ago|0 comments
3.
by matslina 10y ago
This is correct. A players rank will typically differ between both server and go association. Sensei's Library holds more information: http://senseis.xmp.net/?RankWorldwideComparison
4.
by matslina 10y ago
Glibc falls back to quicksort from merge sort (its default algorithm) when there's to little free memory available to accommodate merge sort's O(n) requirement. Quicksort only uses O(log n) additional memory, making it a good opti
5.
by matslina 11y ago
Well, the worst case is still there. You're just going to have a very hard time crafting an input that triggers it.
6.
by matslina 12y ago
Could be. You can have a look at the headline data here: https://gist.github.com/matslina/64601f39ef12bd653be6
7.
by matslina 12y ago
Implementations are available in the repository linked to from the article. Not quite "ready for production", but hopefully a useful starting point. https://github.com/matslina/bfoptimization
8.
by matslina 12y ago
Since bff4lnr is an interpreter, this really becomes apples and oranges. But for fun, dbfi.b on bff4lnr (at -O3) vs all at -O0 and -O3: http://imgur.com/uEEgVr0 Conclusion: if you want speed then compile.
9.
by matslina 12y ago
Here's the no-vs-all optimizations graph for gcc with -O3: http://imgur.com/Q6yycrT
10.
Spotify CEO – $2B and Counting(news.spotify.com)
10 points by matslina 12y ago|0 comments
11.
Compiling Brainfuck to Java, in Brainfuck(hakkalabs.co)
12 points by matslina 12y ago|0 comments
12.
by matslina 12y ago
Mergesort would be a poor choice for qsort() due to the linear space complexity. With N bytes of RAM, you'd only be able to sort (a bit less than) N/2 bytes of data. An in-place algorithm is preferable. Glibc is the only libc I&#x
13.
Algorithmic complexity attacks and libc qsort()(calmerthanyouare.org)
149 points by matslina 12y ago|52 comments
14.
by matslina 13y ago
http://en.wikipedia.org/wiki/Rubber-hose_cryptanalysis
15.
by matslina 13y ago
Spotify's Service Infrastructure (SI) team in New York City is hiring. We, the SI engineers, are on a mission to act as force multipliers for all Spotify engineers. We build and maintain software components that allow our feature teams
16.
A libc qsort(3) shootout of sorts(calmerthanyouare.org)
4 points by matslina 13y ago|0 comments
17.
by matslina 14y ago
Spotify, New York, USA. Software Engineer - Backend Infrastructure Our engineering team is responsible for the infrastructure underlying Spotify's music experience. We work on large scale distributed systems, from handling a billion playlis
18.
Spotify recruiting developers using Minecraft(youtube.com)
1 points by matslina 16y ago|0 comments