wmu

14 ms·

121.
by wmu 10y ago
It is written from the perspective of amateur. C++ exceptions comes at no cost. RTTI comes at no cost. C printf is unsafe; one can write perfectly safe printf-like formatters in C++ (did it, works well). Why one can use metaprogramming but
122.
by wmu 10y ago
Look at http://algos.inesc-id.pt/~pff/projects/parsat/?Publications It seems Mr Costa has graduated, but the link to his thesis points to an empty pdf.
123.
by wmu 10y ago
#4 is not really language issue, rather a floating point numbers feature.
124.
by wmu 10y ago
Things I'm envy for: 1) documenting changes, 2) compulsory code review, 3) post-failure reports. I wish my company introduced at least one of those.
125.
by wmu 10y ago
Didn't know trash-cli, thanks for sharing.
126.
by wmu 10y ago
All parts, I like how the simple parts were composed to built pretty complicated algorithm.
127.
by wmu 10y ago
1. Lempel-Ziv compression algorithms (both LZ77 and LZ78). They are practical, even if one code their basic versions will get good compression ratio. Moreover, they opened the whole big chapter of data compression (LZW, LZSS and more). 2. T
128.
by wmu 10y ago
Approx 7 years ago I bought a cheap no-name backpack in a supermarket. I needed it for a short journey and thought that I trash it after that trip. It turned to be so good, that now I use it everyday, also during walks and cycling. It'
129.
by wmu 10y ago
It is worth to note that template-related features make compilation time significantly longer. It might seem no-problem unless you face it in a bigger team, then these extra seconds (or minutes) are multiplied.
130.
by wmu 10y ago
A highlighter in Visual Studio is able to distinguish (at least) preprocesor definitions, variables and class names.
131.
by wmu 10y ago
Xeon Phi have got more cores, 50 or 60, and the cores share memory. Unlike GPUs memory space is uniform, there is no need to do explicit transfers to/from GPU's memory.
132.
by wmu 10y ago
On Knights Landing CPU a single core is be able to perform 2 x 16 operations on single-precision numbers, as a core has two AVX512 execution units. Each core can run 4 thread, and KNL has 64 physical cores.
133.
by wmu 10y ago
I've listened to Clif Bar's story, really interesting, inspiring, and... enchanting.
134.
String::find from GCC is 10 times slower than strstr(0x80.pl)
3 points by wmu 10y ago|0 comments
135.
by wmu 10y ago
I like this joke: A junior programmer thinks he knows everything. An intermediate programmer thinks he knows nothing. A senior programmer hates computers. > But I feel like I'm always a step behind the rest. Don't look at thing
136.
by wmu 10y ago
Years ago I saw a WWW server written in PostScript. People were also asking "why?" :)
137.
AVX512F base64 encoding and decoding is 2 times faster than AVX2(0x80.pl)
8 points by wmu 10y ago|0 comments
138.
by wmu 10y ago
Thanks, I've never heard about Hugo, I've seen Sphinx mentioned by mixmastamyk. But... I wish I had enough spare time to do migration. My TODO list is getting longer and longer. :)
139.
by wmu 10y ago
For my website I have a custom python script, and I use RestructuredText for markup. If I started now, I would replace the script with a set of Makefiles... or better use any existing generator.
140.
by wmu 10y ago
I would love to see a comparison to C, C++, Ada, Rust, maybe Cyclone. After reading the page I can't find an answer why Zig is better than any of established languages. (Haven't read comments yet) Speaking of readability... well,
141.
by wmu 10y ago
For me "Figure 6. Performance of various parsers" is unreadable.
142.
by wmu 10y ago
This is so crazy, I like it. :) But if I had a cat, I would stroke it in old-fashion way.
143.
by wmu 10y ago
The solution with a graph object looks nice, but when you allow some graph operations, than subgraphs could be shared among many (new) graphs. So, another level of sharing. I can't find any better solution for this problem.
144.
by wmu 10y ago
> The way the x87 FP stack works is a bit weird, and these days it’s better to do floating-point arithmetic using xmm registers x87 allows to do calculations in extended precision, i.e. word width is 80 bits. SSE is limited to double pre
145.
by wmu 10y ago
Probably no. I think when you reach some level of understanding, you'll use manuals. Then you know what you're looking for. :)
146.
by wmu 10y ago
> The first mistake is using shared_ptr to begin with. Yes, definitively! Using shared pointers can hide bad design. There are some cases when it is hard to choose the owner of data. Two examples come to my mind. The first are directed g
147.
ViZDoom: A Doom-Based AI Research Platform for Visual Reinforcement Learning(arxiv.org)
2 points by wmu 10y ago|0 comments
148.
by wmu 10y ago
Nice question, I had to think for a while. :)
149.
by wmu 10y ago
It's interesting why the ISAs suck or getting rotten over time (for example x86). I mean, designing an ISA is not a job for interns, it have to be developed by experienced engineers. So, are all these guys have no idea what they'r
150.
by wmu 10y ago
Good article. A few years ago I wrote a toy program which demonstrates cost of cache misses (or the power of hardware prefetchers). https://github.com/WojciechMula/toys/tree/master/cache_test

More ›