stmw

11 ms·

1. 181.▲
   Non-English-based programming languages(en.wikipedia.org)

   2 points by stmw 11mo ago|1 comments
2. 182.▲
   by stmw 11mo ago

   Good upvote-worthy points, I'd just say that this is exactly the issue - eventually you end up with a Java++ implementation of exceptions. As you say, the more limited implementation can be done more efficiently than the post post cl
3. 183.▲
   by stmw 11mo ago

   This is a good direction - many ABI's provide for this kind of thing at the top of the stack for interrupts (meaning x-bytes below the downward-growing stack are reserved by the OS).
4. 184.▲
   by stmw 11mo ago

   And that was really my (unpopular) opinion above - that exceptions and garbage collectors are two examples of runtime/compiler/language features that after some iteration around the corner cases tend to end up in roughly the same
5. 185.▲
   by stmw 11mo ago

   You're completely right, I was wrong - thank you for the correction. Adding ref to the SEH part of Microsoft C extensions https://learn.microsoft.com/en-us/cpp/cpp/structured-excepti...
6. 186.▲
   by stmw 11mo ago

   For clarification, this is not just a Rust, or a Zig thing. [removed incorrect info re: Linux]
7. 187.▲
   by stmw 11mo ago

   I am talking about the wider category that includes stack unwinding as an error handling pattern for errors outside of catastrophic. T My opinion (which one need not approve of) is that it asymptotically approaches the language-level contro
8. 188.▲
   by stmw 11mo ago

   But it's not really encouraged as it is in C++ or Java. Quoting Rustonomicon: "There is an API called catch_unwind that enables catching a panic without spawning a thread. Still, we would encourage you to only do this sparingly.
9. 189.▲
   by stmw 11mo ago

   I would argue that is largely true because we got the ABIs and the hardware to support them to be highly optimized. Thing slow down very quickly if one gets off that hard-won autobahn of ABI efficiency.
10. 190.▲
    by stmw 11mo ago

    Fair point re: Zig vs Rust, but my larger point was about exceptions by any other name, in the linked article: "Instead, when returning an error, rather than jumping to the return address, we look it up in the side table to find a corr
11. 191.▲
    by stmw 11mo ago

    I'm simultaneously amused and concerned by the recurring proposals for Rust to add 1. exceptions 2. garbage collection Sometimes in slightly modified forms or names, and often with very well-articulated, technically competent justific
12. 192.▲
    The Truth About Memory Supply, Pricing and What Comes Next(eetimes.com)

    3 points by stmw 11mo ago|0 comments
13. 193.▲
    MIT Prof Barbara Liskov, on Data Abstraction and Object-Oriented Programming [video](youtube.com)

    7 points by stmw 11mo ago|1 comments
14. 194.▲
    by stmw 11mo ago

    https://en.wikipedia.org/wiki/Barbara_Liskov
15. 195.▲
    by stmw 11mo ago

    Very cool!
16. 196.▲
    Magnetic Core Memory(computerhistory.org)

    9 points by stmw 11mo ago|2 comments
17. 197.▲
    Digital Apollo: Human and Machine in Spaceflight(web.mit.edu)

    1 points by stmw 11mo ago|0 comments
18. 198.▲
    SampCert: Verified Foundations for Differential Privacy (PLDI 2025)(dl.acm.org)

    1 points by stmw 11mo ago|0 comments
19. 199.▲
    by stmw 11mo ago

    "...adversaries are no longer leveraging artificial intelligence (AI) just for productivity gains, they are deploying novel AI-enabled malware in active operations. This marks a new operational phase of AI abuse, involving tools that d
20. 200.▲
    GTIG AI Threat Tracker: Advances in Threat Actor Usage of AI Tools(cloud.google.com)

    1 points by stmw 11mo ago|1 comments
21. 201.▲
    Intellectual Ventures: Mosquito Laser Shootdown Sequence (2010) [video](youtube.com)

    3 points by stmw 11mo ago|0 comments
22. 202.▲
    by stmw 11mo ago

    For those interested, the start of much of this was Federico Fagin with the 4-bit 4004 and its immediate successors https://en.wikipedia.org/wiki/Federico_Faggin
23. 203.▲
    by stmw 11mo ago

    Indeed, this aspect of early x86 is something more people need to know about... It still has its remnants in low-level code. Of course, 6502 and other 8-bit processors had similar issues tryign to go beyond the 64K addressing limit, but onl
24. 204.▲
    Fyrox Game Engine 1.0 Release Candidate(fyrox.rs)

    3 points by stmw 1y ago|0 comments
25. 205.▲
    by stmw 1y ago

    It appears there are two schema compatibility modes and no guarantee of minor version binary compatibility.
26. 206.▲
    by stmw 1y ago

    I am not sure if W3C EXI, or ASN.1 BER or something else is better, but agree that using DOP (rather than OOP) design principles is the right answer -- which means focusing on the encoding first, and working backwards towards the languages
27. 207.▲
    by stmw 1y ago

    I am skeptical that it's possible to make this work in the long run.
28. 208.▲
    by stmw 1y ago

    Regarding design tradeoffs: I am very skeptical that this can be made to work for the long run in a cross-language way without formalizing the on-the-wire contract via IDL or similar. In my experience, while starting from a language to arri
29. 209.▲
    Architecture and Platform Information for Compiler Writers(llvm.org)

    3 points by stmw 1y ago|0 comments
30. 210.▲
    Chip Hall of Fame: Intel 8088 Microprocessor (2017)(spectrum.ieee.org)

    42 points by stmw 1y ago|9 comments