PeCaN

95 ms·

841.
by PeCaN 11y ago
From watching it I'm almost inclined to say it maximizes its chances of not losing over necessarily winning.
842.
by PeCaN 11y ago
Maybe it's a regional thing? My understanding of how people use it is still ‘spirit of the time’.
843.
by PeCaN 11y ago
Just for the record, I didn't consider the parent's tone to be abrasive at all.
844.
by PeCaN 11y ago
Well... they wrote their own PHP-to-C++ compiler (which is both insane and incredibly impressive), then their own PHP tracing JIT compiler, and their own PHP type checker.... At what point does it become their own language? Also a good amou
845.
by PeCaN 11y ago
SQLServer is super Win32 specific, even to the extent of using undocumented Windows APIs (I think the canonical example is NtReadFileScatter and NtWriteFileScatter, which are more flexible than the documented ReadFileScatter and WriteFile
846.
by PeCaN 11y ago
I think D is closer to Scala than Rust is. D's metaprogramming is quite a bit more advanced than Rust and it has opt-in garbage collection. The type system isn't advanced like Rust, let alone Scala, but it mostly gets the job done
847.
by PeCaN 11y ago
Or Idris, which is (IMO) more practically useful than Agda.
848.
by PeCaN 11y ago
This may have the highest quality-of-implementation/quality-of-idea ratio of anything I've seen.
849.
by PeCaN 11y ago
Derp, how'd I miss that. Yeah, I bet that was what the parent meant.
850.
by PeCaN 11y ago
Modern C++ isn't really that fun on Windows either... (no Valgrind, GCC and Clang are ported later, many fewer libraries) D on Windows is surprisingly pleasant though.
851.
by PeCaN 11y ago
While modern C++ is pretty nice, I still think D and Rust have completely eaten its lunch. At this point I think the only thing C++17 does better than D or Rust is brand recognition. :P
852.
by PeCaN 11y ago
And there's the fact that its rendering of 1px vector rectangle borders depends on their location. Yup, sometimes they render a little bit thicker[1], which can be fixed by moving it up or down a couple pixels. I kind of hate Photoshop
853.
by PeCaN 11y ago
OK, wait, what? Of course two implementations will implement line breaking the same way, it's _specified_ how they should do it. That's the whole point of a spec . ICU and libutf8proc will both break lines for you. They exist spe
854.
by PeCaN 11y ago
Sigh, thank you for ranting for me. I just want to add to what you said: > > There is not much choice how to split a string into words (split on 0x20? yes. split on 0x0a? mostly. split on 0x09? maybe. allow carriage return? maybe.). &
855.
by PeCaN 11y ago
DWARF 3 and 4 can contain information about macros, and GDB can expand them (macro exp foo(bar,...)). Compile with the somewhat under-mentioned flags -gdwarf-4 -g3 to retain macro definitions. This lets you debug expansions easily, but does
856.
by PeCaN 11y ago
The X-macro pattern comes to mind: #define LIST_ERROR_TYPES(X) \ X(OK, "") \ X(ERR_OOM, "out of memory") \ X(ERR_BAD_STRING_ENCODING, "string was invalid utf-8") \ ... #define DEF_ENUM(id
857.
by PeCaN 11y ago
Not just "basically", that actually is the so-called ‘Zen of Lisp’. With something like paredit, your editing isn't text editing so much as manipulating the AST in a very literal sense. Then you can write macros to do that fo
858.
by PeCaN 11y ago
There's always M4, which will preprocess just about anything you throw at it. The syntax starts off pretty godawful, but eventually you learn to love it. C# and Java are much nicer with a little M4. Everybody loves to hate on text-subs
859.
by PeCaN 11y ago
Which is a enabled by default with -Wall. I'm a fan of compiling with -Wall -Wextra and manually disabling any irrelevant warnings (which is rare, and preferable to do on a per-file basis in the Makefile).
860.
by PeCaN 11y ago
If you want to debug preprocessor-generated code, -gdwarf-4 -g3 usually does the trick with GCC and Clang. If it doesn't, you can just gcc -E it and run it through clang-format or something, and compile and debug the expanded version.
861.
by PeCaN 11y ago
The canonical use of which being safe min/max: #define min(a, b) ({ \ __typeof__(a) _a = (a); \ __typeof__(b) _b = (b); \ _a > _b ? _b : _a; \ }) #define max(a, b) ({ \ __typeof__(a) _a = (a);
862.
by PeCaN 11y ago
What do you think of alternative, non-neural-network approaches to deep learning such as Bayesian networks[1] or Support Vector Machines (which as I understand it are largely dead, but the theory behind them is interesting and could lead to
863.
by PeCaN 11y ago
Has elinks development stopped? I vastly preferred it to lynx, but it seems unmaintained now.
864.
by PeCaN 11y ago
It's IDE-ish for some languages. I would call it a full-featured TypeScript IDE (with IntelliSense, syntax-checking, a decent debugger, etc) but not much else.
865.
by PeCaN 11y ago
Doing something that you _know_ is wrong, then complaining when the compiler happens to break it, is entitled if I've ever seen it. I don't think I would trust code that relies on undefined behavior to be secure . That doesn&#x27
866.
by PeCaN 11y ago
I use it for a living, and I cannot recommend that piece of shit. The IDE is alright, except the IntelliSense, if you can even call it that, becomes unusably slow in sufficiently large (really, just non-trivial) projects. The 32-bit compile
867.
by PeCaN 11y ago
http://www.getlazarus.org/ They just had a release recently actually (which made it to HN front page!). It's basically cross-platform open-source Delphi (FreePascal, technically). As someone who works in Embarcadero De
868.
by PeCaN 11y ago
What does one even use that much FPGA for? Any organization that could afford that could probably afford making an ASIC of comparable or better performance. ...That said, that's crazy impressive.
869.
by PeCaN 11y ago
Not just "relatively small"—positively tiny. You could fit hundreds of these on a single FPGA.
870.
by PeCaN 11y ago
It would be really interesting to see if Apple picks up, say, RISC-V or does their own ISA once their ARM license expires. (Does it expire?)

More ›