mrkmarron

6 ms·

1.
by mrkmarron 8mo ago
What is your take on usability of these systems? In practice they seem to be rather un-ergonomic and usage devolves into require everything. As agentic systems seem to mainly interoperate with REST style systems I suspect that using URIs fo
2.
by mrkmarron 1y ago
The key capability that Bosque has for API specs is the ability to provide pre/post conditions with arbitrary expressions. This is particularly useful once you can do temporal conditions involving other API calls (as discussed in the b
3.
Bosque Programming Language Blog – Strings(bosquelanguage.github.io)
2 points by mrkmarron 2y ago|0 comments
4.
by mrkmarron 2y ago
Just saw the edit. I have 2 answers: 1) Fuzzing is under-utilized even for simple code. AFL is dead easy to use and, even so, most projects don't have it in CI runs. So, despite how much I like it, in general it seems people do not see
5.
by mrkmarron 2y ago
At the end of the day you have 2 problems (1) how to make execution deterministic within some boundary be it a process, hypervisor, or distributed system and (2) how you handle non-determinism when data crosses this boundary. You can move t
6.
by mrkmarron 2y ago
I just rewatched the end of the video to make sure I didn't miss anything. Deterministic execution and replay is very-very well-known and understood. It is possible that your packaging and market fit is right on. Lots of cottage indust
7.
by mrkmarron 2y ago
Thanks for sharing, I felt like there were earlier but the x,y trick jumped out at me and that was the one I remembered off the top of my head.
8.
by mrkmarron 2y ago
I think you underestimate the level to which this area has been studied. And I wish you would talk about these new results then instead of announcing 5+ year old results then. It would be great to see progress in this area (not my primary a
9.
by mrkmarron 2y ago
FYI playing Super Mario with fuzzing (AFL) was done in a fun 2020 S&P paper. Also finds bugs and security issues. "IJON: Exploring Deep State Spaces via Fuzzing" https://casa.rub.de/fileadmin/img/Publ
10.
Bosque programming language at 3 – starting next phase(github.com)
2 points by mrkmarron 4y ago|0 comments
11.
by mrkmarron 6y ago
The design of the language is done in a manner that allows us to translate the code (and all conditions) into very friendly SMTLib code -- that we don't need to add a lot of additional checks like frame rules or havocs and where the se
12.
by mrkmarron 6y ago
Hi and thanks for the questions: 1. By design the language provides some novel memory invariants including, no cycles in the object graph, no old-to-new pointers, and no pointer updates. Thus, we don't need to worry about cycle collect
13.
by mrkmarron 6y ago
You are right, allof is inconsistent with the language naming conventions. I was updating some other collections support and made that fix as well. Thanks!
14.
by mrkmarron 6y ago
Hi, project owner here, great to see this on HN and always happy to hear from folks here and on the GitHub repo. We also have a webinar with Q&A scheduled for Thursday morning ( https://note.microsoft.com/MSR-Webinar-Prog
15.
by mrkmarron 7y ago
There were some discussions for a more general system -- e.g. Int[Seconds] would be a typed int indicating the contents represented seconds. We needed to think more about all of these usecases and how things worked so we decided to start wi
16.
by mrkmarron 7y ago
My understanding it Elm checks for signature changes such as adding a parameter to a function. We would like to do more and actually compare the actual behavior of the code before/after the change as well.
17.
by mrkmarron 7y ago
Great question. We take a very maximalist stance here and do not provide any environmental API’s in the Bosque language. Instead all IO, data-time, IP address operations must be part of a host platform – similar to how JavaScript does not p
18.
by mrkmarron 7y ago
The current purpose is explore language design choices and their impact on their general utility for programmers and enabling automated developer tools (like verifiers and compilers). The hope is to use Bosque as a proof of concept for vari
19.
by mrkmarron 7y ago
It is a Spanish word used in the SouthWest US for forest along a river. No particular reason behind the name, just a unique and easily searchable choice.
20.
by mrkmarron 7y ago
I would say accidental complexity comes from mostly historical reasons. Two sources discussed in the report are reference equality and looping. These make a ton of sense if you are implementing a language with a compiler that targets an x86
21.
by mrkmarron 7y ago
Hi project owner (Mark) here. It is a bit late in the evening for me but I will try to answer any questions when I can. The Bosque language is currently in a very early state with lots of work to do and not ready for practical use. However,