samth

13 ms·

121.
by samth 6y ago
This analysis has a significant comparability problem because of added features. The core git-repository service is almost never down, but GitHub Actions has had a lot of reliability problems (you can see this clearly on the status page). B
122.
Racket Survey 2020(blog.racket-lang.org)
11 points by samth 6y ago|0 comments
123.
What science can tell us about C and C++'s security(alexgaynor.net)
13 points by samth 6y ago|0 comments
124.
by samth 6y ago
These days, response status messages are automatically inferred: https://docs.racket-lang.org/web-server/http.html?q=response...
125.
by samth 6y ago
You can do that with `syntax/loc` when you're writing macros.
126.
by samth 6y ago
While I can certainly believe that more examples are needed, the second issue I don't understand. If you search for something, it tells you exactly what module it's from: https://docs.racket-lang.org/search/in
127.
by samth 6y ago
It's really just about the initial steps of the project. One talk you might like is https://www.youtube.com/watch?v=wEgaVMOYLEU from 9 years ago.
128.
by samth 6y ago
https://defn.io/2020/01/04/remember-internals/ describes some of this.
129.
by samth 7y ago
Yes, plenty of languages do this. For example, Racket exposes permissions as bitmasks but they work portably across platforms, and Racket handles all the filename encoding issues mentioned here.
130.
by samth 7y ago
Yes, Chez Scheme is mostly written in itself, including most primitives and the entire compiler. Additionally, the way Racket CS is architected, significant parts of the C-implemented Racket runtime are instead written in Racket and compile
131.
Racket 7.6(blog.racket-lang.org)
42 points by samth 7y ago|5 comments
132.
by samth 7y ago
Your notes, while simple, don't cover many of the things the paper does, such as binding or functions or sharing.
133.
Lessons learned from guile, the ancient and spry(wingolog.org)
2 points by samth 7y ago|0 comments
134.
by samth 7y ago
This is correct, however much of the work we've done to make Racket work using the Chez VM could be re-used to build a Guile-backed version of Racket. It's not clear whether that would be of significant value, but it's doable
135.
by samth 7y ago
The position you're taking, roughly that with limited resources you have to aim for achievable goals and while distributed federated networks are the underlying reason Signal works, it can't try to replace them right now, is total
136.
by samth 7y ago
One frustrating thing about Moxie's original post is that Signal derives huge amounts of value by piggybacking on an existing distributed federated network: the phone system. If phone numbers weren't an existing working identifier
137.
by samth 7y ago
I got tenure (last year) after having a kid (two years ago). We do have family in town, which as you say is a big help. We both took leave, and I basically did not do any research during my 12-week leave. I did meet occasionally with my stu
138.
Debuggers Suck(robert.ocallahan.org)
299 points by samth 7y ago|257 comments
139.
Racket 7.5(blog.racket-lang.org)
2 points by samth 7y ago|0 comments
140.
by samth 7y ago
Yes, Racket uses Git. Which things are and aren't a derived work of other things is a complicated question which is, for example, the subject of a big lawsuit between Oracle and Google, and I won't pretend to give a final answer h
141.
by samth 7y ago
I think it's genuinely unclear how something like the LGPL should work in a system with macro expansion and ahead-of-time compilation, where the compiled code will contain copies of the bodies of macros. The FSF discussion of the LGPL
142.
by samth 7y ago
Racket CS works similarly to traditional Racket in this respect -- compiled libraries still contain the results of macro-expansion and inlining from their dependencies, and generated executables still bundle everything together in a way tha
143.
Completing Racket's relicensing effort(blog.racket-lang.org)
169 points by samth 7y ago|56 comments
144.
by samth 7y ago
There are three ways to think about this. 1. R7RS explicitly decided to repudiate R6RS, leading to the disagreement. 2. R6RS made changes that did not have consensus and the resulting vote didn't have a big enough super majority requir
145.
by samth 7y ago
Lincoln's Second Inaugural is good on how insufficient this is.
146.
by samth 7y ago
https://blog.racket-lang.org/2019/01/racket-on-chez-status.h... and the links at the top should provide the explanation. This paper: https://www.cs.utah.edu/plt/publications/icfp19-rddkms
147.
by samth 7y ago
That's about the `thread` construct specifically, which as it says is green threads. Mostly people who are spreading work across multiple cores will have a few places that communicate, each of which has multiple threads to handle inter
148.
by samth 7y ago
Can you say more about the issue with number->string (probably that's the function you used)? Also, I think we'd be happy to take patches to improve the Scribble CSS for mobile.
149.
by samth 7y ago
Yes, Racket support using multiple cores/OS threads. There are two mechanisms -- shared memory parallelism that is limited in what operations the threads can execute in parallel (called futures in Racket) and shared-nothing parallelism
150.
by samth 7y ago
https://github.com/greghendershott/wffi is what you want

More ›