EuAndreh

5 ms·

1.
by EuAndreh 10d ago
Just checking, are they print magazines? Or are you referring to the online articles instead?
2.
by EuAndreh 10mo ago
As free advertisement to rsync.net, I also like the service and support. I have not deleted any of my daily borg backups for many years, covering my laptop and some servers. Borg has an equivalent `borg serve` feature as detailed in the ar
3.
by EuAndreh 1y ago
Despite its flaws and issues, email is federated and has been working at scale for decades.
4.
by EuAndreh 1y ago
Besides being the stardand, it also has a standard: https://pubs.opengroup.org/onlinepubs/9799919799/utilities/e...
5.
by EuAndreh 1y ago
Come on, these three phrases aren't equivalent or comparable. They "can arguably be construed as the violence" from a discriminatory argument. An honest argument wouldn't provide us this false equivalence.
6.
by EuAndreh 2y ago
There are many other factors that influence language popularity besides technical quality, like: - marketing; - big companies using it; - familiarity; - history of the creators; - history of the influencing languages; - timing
7.
by EuAndreh 2y ago
> That's fine for a primitive compiler built for a school project, but not much else. Not true. On the one hand, just see how many non-compiled languages are used outside of primitive school projects. On the other hand, this simpler
8.
by EuAndreh 2y ago
I have the impression you're mixing single-pass compilation and O(1) memory use of the compiler. As is, C already is single-pass compilable, modulo some unnecessary syntax ambiguities. As the compiler reads the text, it marks some char
9.
by EuAndreh 2y ago
Thanks, but no thanks.
10.
by EuAndreh 2y ago
> The parser being stand-alone means it is much simpler to understand and unittest. Stand-aloneness and single-passness are orthogonal. > I found no advantage to a single pass compiler. It isn't any faster. A gigantic advantage:
11.
by EuAndreh 2y ago
I have my own list of things that could "easily" be added to C, but I'd rather them not to be.
12.
by EuAndreh 2y ago
Good suggestions, but also meh, e.g.: forward declaration requirement enables a single-pass compiler to emit code on-the-fly. I have a much better list for things to add to C: Nothing. C isn't perfect, or nearly as good as it could be
13.
by EuAndreh 2y ago
LISP doesn't really read well the bigger the codebase [citation needed]
14.
by EuAndreh 2y ago
There is nothing wrong with using PEGs for SQL parsing, but this article (I didn't read the paper) presents flawed arguments: - tech $X is from the 60s, therefore it is bad and/or outdated: one doesn't need to "disrupt&q
15.
by EuAndreh 2y ago
Not key value dictionaries, just pointers are needed. A closure with no behaviour is just a pointer to the enclosed variable. A closure with 2 pointers is a pair, which you can get the car and cdr. The runtime needs to make the pointee ava
16.
by EuAndreh 2y ago
Zero accessibility =/ As great as it may be, this isn't something I'd pick as it'd be unusable in this cases.
17.
by EuAndreh 2y ago
From the same article: > Brazil’s Supreme Court has drastically expanded its power to counter the antidemocratic stances of Mr. Bolsonaro and his supporters. The title is a leading question. I can come up with different titles for the s
18.
by EuAndreh 2y ago
Yep, that says not to include generated files in VCS. I've also seen the bison and flex output included in VCS, and the same guidelines apply.
19.
by EuAndreh 2y ago
Oh god why. I thought (and hoped) that GP didn't actually mean this. I see how a team or an organization can eventually get to this point. It just saddens me that they got there.
20.
by EuAndreh 2y ago
s/generated/generate/
21.
by EuAndreh 2y ago
> Nowadays it's not that big a deal. The same can be said about autotools itself :/ Historical and current use indeed vary, and many times even using autotools itself isn't as appropriate.
22.
by EuAndreh 2y ago
That's not the case for autotools output, or flex and bison output. If the generated files are what you say? Well, just embed the generation step into the build system. A simple approach like that is easily made reproducible, and we
23.
by EuAndreh 2y ago
IIRC Debian has a policy on preferring to generated files themselves. I couldn't find the link to it right now, though.
24.
by EuAndreh 2y ago
yacc and lex, their description and some implementations are simple. Flex and certainly Bison are not.
25.
by EuAndreh 2y ago
In this case, I can say autotools's advice is outdated at best, and one shouldn't follow it. It adds unneeded complexity.
26.
by EuAndreh 2y ago
No unauditable generated code for me, either manually or automatically, thanks.
27.
by EuAndreh 2y ago
I disagree based on the existence of a standartized but diverse ecosystem. The languages listed above all have: - a language specification; - more than one competing implementation. Erlang doesn't have a specification, so you're a
28.
by EuAndreh 2y ago
Any complaints or criticism on the lack of some widget on Motif? Also, I'm curious: is the app accessible? AFAICT, Motif doesn't even mention accessibility, and is where Sun made real progress in the past.
29.
by EuAndreh 2y ago
Not that big of a deal. Lisp has a drastically simpler syntax, but can behave is the same way. This thing that is different from other languages is having a static lexer and parser, versus having a fynamic one. In Perl you modify it indir
30.
by EuAndreh 2y ago
From the fact that the LoC count of the implementation is beyond "millions". How about this equivalence: I appreciate how extremely sophisticated GCC is, and the very well optimized output it generates. It is still is 100x more c

More ›