#proglang — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #proglang, aggregated by home.social.
-
Nikita Lisitsa posted his experience with designing and implementing his own programming language, a game scripting language that's "[...] a weird blend of C++, Rust, Python, Zig, and maybe a few other languages".
https://lisyarus.github.io/blog/posts/making-your-own-programming-language.html
-
Nikita Lisitsa posted his experience with designing and implementing his own programming language, a game scripting language that's "[...] a weird blend of C++, Rust, Python, Zig, and maybe a few other languages".
https://lisyarus.github.io/blog/posts/making-your-own-programming-language.html
-
Nikita Lisitsa posted his experience with designing and implementing his own programming language, a game scripting language that's "[...] a weird blend of C++, Rust, Python, Zig, and maybe a few other languages".
https://lisyarus.github.io/blog/posts/making-your-own-programming-language.html
-
Nikita Lisitsa posted his experience with designing and implementing his own programming language, a game scripting language that's "[...] a weird blend of C++, Rust, Python, Zig, and maybe a few other languages".
https://lisyarus.github.io/blog/posts/making-your-own-programming-language.html
-
Nikita Lisitsa posted his experience with designing and implementing his own programming language, a game scripting language that's "[...] a weird blend of C++, Rust, Python, Zig, and maybe a few other languages".
https://lisyarus.github.io/blog/posts/making-your-own-programming-language.html
-
I've added some light "automated proving" capbilities to my geometric predicate generator.
(Context is still high performance mesh booleans, but this is applicable to so much more geometric computation)
With enough symbolic perturbation I was able to prove that the perturbed query point cannot lie on the plane.
This is not done via proof search but via rewriting / optimization.
Basically, "prove <expr>" is definitely true if we can simply "<expr>" to "true".
-
I've added some light "automated proving" capbilities to my geometric predicate generator.
(Context is still high performance mesh booleans, but this is applicable to so much more geometric computation)
With enough symbolic perturbation I was able to prove that the perturbed query point cannot lie on the plane.
This is not done via proof search but via rewriting / optimization.
Basically, "prove <expr>" is definitely true if we can simply "<expr>" to "true".
-
I've added some light "automated proving" capbilities to my geometric predicate generator.
(Context is still high performance mesh booleans, but this is applicable to so much more geometric computation)
With enough symbolic perturbation I was able to prove that the perturbed query point cannot lie on the plane.
This is not done via proof search but via rewriting / optimization.
Basically, "prove <expr>" is definitely true if we can simply "<expr>" to "true".
-
I've added some light "automated proving" capbilities to my geometric predicate generator.
(Context is still high performance mesh booleans, but this is applicable to so much more geometric computation)
With enough symbolic perturbation I was able to prove that the perturbed query point cannot lie on the plane.
This is not done via proof search but via rewriting / optimization.
Basically, "prove <expr>" is definitely true if we can simply "<expr>" to "true".
-
I've added some light "automated proving" capbilities to my geometric predicate generator.
(Context is still high performance mesh booleans, but this is applicable to so much more geometric computation)
With enough symbolic perturbation I was able to prove that the perturbed query point cannot lie on the plane.
This is not done via proof search but via rewriting / optimization.
Basically, "prove <expr>" is definitely true if we can simply "<expr>" to "true".
-
Currently on a side quest to dig deeper into error handling in parsers. Any parser whose diagnostic messages impress you especially (and why)?
-
Currently on a side quest to dig deeper into error handling in parsers. Any parser whose diagnostic messages impress you especially (and why)?
-
Currently on a side quest to dig deeper into error handling in parsers. Any parser whose diagnostic messages impress you especially (and why)?
-
Currently on a side quest to dig deeper into error handling in parsers. Any parser whose diagnostic messages impress you especially (and why)?
-
Currently on a side quest to dig deeper into error handling in parsers. Any parser whose diagnostic messages impress you especially (and why)?
-
Just submitted my latest Swedish Science Council grant proposal: "Navigating the Incomparable"!
We want to build correct-by-construction software for multi-objective optimization—helping safely navigate complex trade-offs like economic costs vs. global temperature rise (see the attached idealised Pareto front).
To do this, we're proposing three connected work packages (see diagram) moving from formal specification, to state-space reduction, and finally scalable execution. We aim to combine #FunctionalProgramming, #DependentTypes, and dimensional analysis to build algebraically accountable tools for climate policy and fusion energy.
If funded, this opens a new PhD position in 2027!
📖 Read the full abstract: https://patrikja.owlstown.net/posts/5441
#Haskell #Agda #TypeTheory #ClimateScience #FusionEnergy #ProgLang
-
Just submitted my latest Swedish Science Council grant proposal: "Navigating the Incomparable"!
We want to build correct-by-construction software for multi-objective optimization—helping safely navigate complex trade-offs like economic costs vs. global temperature rise (see the attached idealised Pareto front).
To do this, we're proposing three connected work packages (see diagram) moving from formal specification, to state-space reduction, and finally scalable execution. We aim to combine #FunctionalProgramming, #DependentTypes, and dimensional analysis to build algebraically accountable tools for climate policy and fusion energy.
If funded, this opens a new PhD position in 2027!
📖 Read the full abstract: https://patrikja.owlstown.net/posts/5441
#Haskell #Agda #TypeTheory #ClimateScience #FusionEnergy #ProgLang
-
Just submitted my latest Swedish Science Council grant proposal: "Navigating the Incomparable"!
We want to build correct-by-construction software for multi-objective optimization—helping safely navigate complex trade-offs like economic costs vs. global temperature rise (see the attached idealised Pareto front).
To do this, we're proposing three connected work packages (see diagram) moving from formal specification, to state-space reduction, and finally scalable execution. We aim to combine #FunctionalProgramming, #DependentTypes, and dimensional analysis to build algebraically accountable tools for climate policy and fusion energy.
If funded, this opens a new PhD position in 2027!
📖 Read the full abstract: https://patrikja.owlstown.net/posts/5441
#Haskell #Agda #TypeTheory #ClimateScience #FusionEnergy #ProgLang
-
Just submitted my latest Swedish Science Council grant proposal: "Navigating the Incomparable"!
We want to build correct-by-construction software for multi-objective optimization—helping safely navigate complex trade-offs like economic costs vs. global temperature rise (see the attached idealised Pareto front).
To do this, we're proposing three connected work packages (see diagram) moving from formal specification, to state-space reduction, and finally scalable execution. We aim to combine #FunctionalProgramming, #DependentTypes, and dimensional analysis to build algebraically accountable tools for climate policy and fusion energy.
If funded, this opens a new PhD position in 2027!
📖 Read the full abstract: https://patrikja.owlstown.net/posts/5441
#Haskell #Agda #TypeTheory #ClimateScience #FusionEnergy #ProgLang
-
Just submitted my latest Swedish Science Council grant proposal: "Navigating the Incomparable"!
We want to build correct-by-construction software for multi-objective optimization—helping safely navigate complex trade-offs like economic costs vs. global temperature rise (see the attached idealised Pareto front).
To do this, we're proposing three connected work packages (see diagram) moving from formal specification, to state-space reduction, and finally scalable execution. We aim to combine #FunctionalProgramming, #DependentTypes, and dimensional analysis to build algebraically accountable tools for climate policy and fusion energy.
If funded, this opens a new PhD position in 2027!
📖 Read the full abstract: https://patrikja.owlstown.net/posts/5441
#Haskell #Agda #TypeTheory #ClimateScience #FusionEnergy #ProgLang
-
Question for #PL folks:
Is there any usable work taking the typed assembly languages work and layering it on top of #LLVM ? Been quite a while since I read that work, but from what I remember, TAL two had the intersection / union types you'd need for SSA form.
Reason: I will (eventually) need a low-overhead, direct-to-native, and safe way to distribute executable code in a distributed system.
-
Question for #PL folks:
Is there any usable work taking the typed assembly languages work and layering it on top of #LLVM ? Been quite a while since I read that work, but from what I remember, TAL two had the intersection / union types you'd need for SSA form.
Reason: I will (eventually) need a low-overhead, direct-to-native, and safe way to distribute executable code in a distributed system.
-
Question for #PL folks:
Is there any usable work taking the typed assembly languages work and layering it on top of #LLVM ? Been quite a while since I read that work, but from what I remember, TAL two had the intersection / union types you'd need for SSA form.
Reason: I will (eventually) need a low-overhead, direct-to-native, and safe way to distribute executable code in a distributed system.
-
Question for #PL folks:
Is there any usable work taking the typed assembly languages work and layering it on top of #LLVM ? Been quite a while since I read that work, but from what I remember, TAL two had the intersection / union types you'd need for SSA form.
Reason: I will (eventually) need a low-overhead, direct-to-native, and safe way to distribute executable code in a distributed system.
-
Question for #PL folks:
Is there any usable work taking the typed assembly languages work and layering it on top of #LLVM ? Been quite a while since I read that work, but from what I remember, TAL two had the intersection / union types you'd need for SSA form.
Reason: I will (eventually) need a low-overhead, direct-to-native, and safe way to distribute executable code in a distributed system.
-
Yorick Phoenix comments on the programming languages he used or was exposed to over his long career in computing. Lots of interesting anecdotes and historical tidbits.
This series of over 30 posts has no table of contents but the posts are arranged in a doubly linked list.
-
Yorick Phoenix comments on the programming languages he used or was exposed to over his long career in computing. Lots of interesting anecdotes and historical tidbits.
This series of over 30 posts has no table of contents but the posts are arranged in a doubly linked list.
-
Yorick Phoenix comments on the programming languages he used or was exposed to over his long career in computing. Lots of interesting anecdotes and historical tidbits.
This series of over 30 posts has no table of contents but the posts are arranged in a doubly linked list.
-
Yorick Phoenix comments on the programming languages he used or was exposed to over his long career in computing. Lots of interesting anecdotes and historical tidbits.
This series of over 30 posts has no table of contents but the posts are arranged in a doubly linked list.
-
Yorick Phoenix comments on the programming languages he used or was exposed to over his long career in computing. Lots of interesting anecdotes and historical tidbits.
This series of over 30 posts has no table of contents but the posts are arranged in a doubly linked list.
-
https://www.kindness.city/blog/2026-03-22-care.html
A bit of a ranty blog today.
I really want to write software that's actually good.
Increasingly, I believe the trick to doing this isn't #types, or #proglang , or formal methods, or #agile, or #XP, or #TDD, or any other fancy technique, process, or technology. It's Care.
And the reason most software still sucks? It's not stupidity, and it's not because everyone else has been duped by the "wrong" development ideology (waterfall, formal methods, agile, etc). It's the Market.
Here's what #openbsd , #slackware, and #emacs are teaching me about taking the time to work on what matters.
-
https://www.kindness.city/blog/2026-03-22-care.html
A bit of a ranty blog today.
I really want to write software that's actually good.
Increasingly, I believe the trick to doing this isn't #types, or #proglang , or formal methods, or #agile, or #XP, or #TDD, or any other fancy technique, process, or technology. It's Care.
And the reason most software still sucks? It's not stupidity, and it's not because everyone else has been duped by the "wrong" development ideology (waterfall, formal methods, agile, etc). It's the Market.
Here's what #openbsd , #slackware, and #emacs are teaching me about taking the time to work on what matters.
-
https://www.kindness.city/blog/2026-03-22-care.html
A bit of a ranty blog today.
I really want to write software that's actually good.
Increasingly, I believe the trick to doing this isn't #types, or #proglang , or formal methods, or #agile, or #XP, or #TDD, or any other fancy technique, process, or technology. It's Care.
And the reason most software still sucks? It's not stupidity, and it's not because everyone else has been duped by the "wrong" development ideology (waterfall, formal methods, agile, etc). It's the Market.
Here's what #openbsd , #slackware, and #emacs are teaching me about taking the time to work on what matters.
-
https://www.kindness.city/blog/2026-03-22-care.html
A bit of a ranty blog today.
I really want to write software that's actually good.
Increasingly, I believe the trick to doing this isn't #types, or #proglang , or formal methods, or #agile, or #XP, or #TDD, or any other fancy technique, process, or technology. It's Care.
And the reason most software still sucks? It's not stupidity, and it's not because everyone else has been duped by the "wrong" development ideology (waterfall, formal methods, agile, etc). It's the Market.
Here's what #openbsd , #slackware, and #emacs are teaching me about taking the time to work on what matters.
-
https://www.kindness.city/blog/2026-03-22-care.html
A bit of a ranty blog today.
I really want to write software that's actually good.
Increasingly, I believe the trick to doing this isn't #types, or #proglang , or formal methods, or #agile, or #XP, or #TDD, or any other fancy technique, process, or technology. It's Care.
And the reason most software still sucks? It's not stupidity, and it's not because everyone else has been duped by the "wrong" development ideology (waterfall, formal methods, agile, etc). It's the Market.
Here's what #openbsd , #slackware, and #emacs are teaching me about taking the time to work on what matters.
-
Rupert Lane reconstructed the code of Joseph Weizenbaum's Online Programming Language (OPL).
Based on a printout of source code found among Weizenbaum's papers archived by MIT Libraries, I have reconstructed the language so it can live again for the first time in nearly sixty years on a IBM 7094 emulator running CTSS.
https://timereshared.com/reconstructing-joseph-weizenbaums-opl
-
Rupert Lane reconstructed the code of Joseph Weizenbaum's Online Programming Language (OPL).
Based on a printout of source code found among Weizenbaum's papers archived by MIT Libraries, I have reconstructed the language so it can live again for the first time in nearly sixty years on a IBM 7094 emulator running CTSS.
https://timereshared.com/reconstructing-joseph-weizenbaums-opl
-
Rupert Lane reconstructed the code of Joseph Weizenbaum's Online Programming Language (OPL).
Based on a printout of source code found among Weizenbaum's papers archived by MIT Libraries, I have reconstructed the language so it can live again for the first time in nearly sixty years on a IBM 7094 emulator running CTSS.
https://timereshared.com/reconstructing-joseph-weizenbaums-opl
-
Rupert Lane reconstructed the code of Joseph Weizenbaum's Online Programming Language (OPL).
Based on a printout of source code found among Weizenbaum's papers archived by MIT Libraries, I have reconstructed the language so it can live again for the first time in nearly sixty years on a IBM 7094 emulator running CTSS.
https://timereshared.com/reconstructing-joseph-weizenbaums-opl
-
Rupert Lane reconstructed the code of Joseph Weizenbaum's Online Programming Language (OPL).
Based on a printout of source code found among Weizenbaum's papers archived by MIT Libraries, I have reconstructed the language so it can live again for the first time in nearly sixty years on a IBM 7094 emulator running CTSS.
https://timereshared.com/reconstructing-joseph-weizenbaums-opl
-
This draft paper dated 1979, apparently never published, gave an historical overview of early programming languages for AI.
The document helps make sense of names like POPLER and QLISP. What's interesting is high level languages such as PLANNER and CONNIVER saw initial interest but little actual use.
https://stacks.stanford.edu/file/druid:vg077ps3762/vg077ps3762.pdf
-
This draft paper dated 1979, apparently never published, gave an historical overview of early programming languages for AI.
The document helps make sense of names like POPLER and QLISP. What's interesting is high level languages such as PLANNER and CONNIVER saw initial interest but little actual use.
https://stacks.stanford.edu/file/druid:vg077ps3762/vg077ps3762.pdf
-
This draft paper dated 1979, apparently never published, gave an historical overview of early programming languages for AI.
The document helps make sense of names like POPLER and QLISP. What's interesting is high level languages such as PLANNER and CONNIVER saw initial interest but little actual use.
https://stacks.stanford.edu/file/druid:vg077ps3762/vg077ps3762.pdf
-
This draft paper dated 1979, apparently never published, gave an historical overview of early programming languages for AI.
The document helps make sense of names like POPLER and QLISP. What's interesting is high level languages such as PLANNER and CONNIVER saw initial interest but little actual use.
https://stacks.stanford.edu/file/druid:vg077ps3762/vg077ps3762.pdf
-
This draft paper dated 1979, apparently never published, gave an historical overview of early programming languages for AI.
The document helps make sense of names like POPLER and QLISP. What's interesting is high level languages such as PLANNER and CONNIVER saw initial interest but little actual use.
https://stacks.stanford.edu/file/druid:vg077ps3762/vg077ps3762.pdf
-
X-mas comes early this year: the ICFP 2025 talks are now on YouTube.
You can catch my talk on "Domain-specific tensor languages" below. We explore implementing tensor calculus in #Haskell, supporting both Einstein notation and Penrose diagrams to model things like General Relativity and black holes. 🕳️🚀
My talk: https://www.youtube.com/watch?v=04cxfddDwuI
Full Playlists:
🔗 ICFP papers: https://www.youtube.com/watch?v=COD4tnVtHoQ&list=PLyrlk8Xaylp4WyLpPH40RBw-kZSdkpkVs
🔗 JFP First papers: https://www.youtube.com/watch?v=oZLSDFfpHp0&list=PLyrlk8Xaylp68qJ-kEeXEPne0ePPwNGFihttps://mastodon.acm.org/@sigplanav/115667300324636252
cc @sigplanav (https://sigplan.org)
#icfpsplash25 #ProgLang #TensorCalculus #Physics #FunctionalProgramming
-
X-mas comes early this year: the ICFP 2025 talks are now on YouTube.
You can catch my talk on "Domain-specific tensor languages" below. We explore implementing tensor calculus in #Haskell, supporting both Einstein notation and Penrose diagrams to model things like General Relativity and black holes. 🕳️🚀
My talk: https://www.youtube.com/watch?v=04cxfddDwuI
Full Playlists:
🔗 ICFP papers: https://www.youtube.com/watch?v=COD4tnVtHoQ&list=PLyrlk8Xaylp4WyLpPH40RBw-kZSdkpkVs
🔗 JFP First papers: https://www.youtube.com/watch?v=oZLSDFfpHp0&list=PLyrlk8Xaylp68qJ-kEeXEPne0ePPwNGFihttps://mastodon.acm.org/@sigplanav/115667300324636252
cc @sigplanav (https://sigplan.org)
#icfpsplash25 #ProgLang #TensorCalculus #Physics #FunctionalProgramming
-
X-mas comes early this year: the ICFP 2025 talks are now on YouTube.
You can catch my talk on "Domain-specific tensor languages" below. We explore implementing tensor calculus in #Haskell, supporting both Einstein notation and Penrose diagrams to model things like General Relativity and black holes. 🕳️🚀
My talk: https://www.youtube.com/watch?v=04cxfddDwuI
Full Playlists:
🔗 ICFP papers: https://www.youtube.com/watch?v=COD4tnVtHoQ&list=PLyrlk8Xaylp4WyLpPH40RBw-kZSdkpkVs
🔗 JFP First papers: https://www.youtube.com/watch?v=oZLSDFfpHp0&list=PLyrlk8Xaylp68qJ-kEeXEPne0ePPwNGFihttps://mastodon.acm.org/@sigplanav/115667300324636252
cc @sigplanav (https://sigplan.org)
#icfpsplash25 #ProgLang #TensorCalculus #Physics #FunctionalProgramming
-
X-mas comes early this year: the ICFP 2025 talks are now on YouTube.
You can catch my talk on "Domain-specific tensor languages" below. We explore implementing tensor calculus in #Haskell, supporting both Einstein notation and Penrose diagrams to model things like General Relativity and black holes. 🕳️🚀
My talk: https://www.youtube.com/watch?v=04cxfddDwuI
Full Playlists:
🔗 ICFP papers: https://www.youtube.com/watch?v=COD4tnVtHoQ&list=PLyrlk8Xaylp4WyLpPH40RBw-kZSdkpkVs
🔗 JFP First papers: https://www.youtube.com/watch?v=oZLSDFfpHp0&list=PLyrlk8Xaylp68qJ-kEeXEPne0ePPwNGFihttps://mastodon.acm.org/@sigplanav/115667300324636252
cc @sigplanav (https://sigplan.org)
#icfpsplash25 #ProgLang #TensorCalculus #Physics #FunctionalProgramming
-
X-mas comes early this year: the ICFP 2025 talks are now on YouTube.
You can catch my talk on "Domain-specific tensor languages" below. We explore implementing tensor calculus in #Haskell, supporting both Einstein notation and Penrose diagrams to model things like General Relativity and black holes. 🕳️🚀
My talk: https://www.youtube.com/watch?v=04cxfddDwuI
Full Playlists:
🔗 ICFP papers: https://www.youtube.com/watch?v=COD4tnVtHoQ&list=PLyrlk8Xaylp4WyLpPH40RBw-kZSdkpkVs
🔗 JFP First papers: https://www.youtube.com/watch?v=oZLSDFfpHp0&list=PLyrlk8Xaylp68qJ-kEeXEPne0ePPwNGFihttps://mastodon.acm.org/@sigplanav/115667300324636252
cc @sigplanav (https://sigplan.org)
#icfpsplash25 #ProgLang #TensorCalculus #Physics #FunctionalProgramming