Ben Ramsey
boosted
All about the new pipe operator in PHP 8.5:
https://thephp.foundation/blog/2025/07/11/php-85-adds-pipe-operator/
Today I realized #Go and #Rust both have panics instead of exceptions and both originate from the second half of the 2000s.
These facts are now mentioned in https://gato-lang.dev/
If you have experience with Go or Rust, I'm interested in your thoughts on the lack of exceptions in these languages. It looks to me like an attempt to simplify things that eventually backfired, as evidenced for example by https://www.crowdstrike.com/en-us/blog/dealing-with-out-of-memory-conditions-in-rust/
An interesting remark in Josep Bigorra's post on why Scheme can be used for production work:
There鈥檚 only one truly universal ecosystem: the C ecosystem. Dynamic language modules are often just bindings to existing C libraries.
<"/>
There鈥檚 only one truly universal ecosystem: the C ecosystem.
Here is my quick and dirty interpretation.
The actual ecosystem of computer programs is the machine language of the architecture they are running on.
Programming in machine language is done in assembly language.
C is (still) the dominant machine-independent assembly language.
NB: this universality excludes the bytecode languages of the JVM etc.
For my next #compiler project, I want to write the optimization passes myself, but I don't want to deal with generating machine code for multiple platforms. So tell me #programminglanguages #plt #pldev #compilers fedi, what is an IR that I can target that has a non-optimizing compiler to machine code and supports multiple platforms? This rules out most popular IR like LLVM, C, QBE, Cranelift etc.
In short, I want something that does only instruction selection, register allocation and codegen for multiple platforms. I don't need optimization, so I expect this thing to be really small and lightweight, unlike LLVM, GCC etc.