Lecture: Idris – Reviving an Early Unix Clone
by Michael Engel @me_
https://wiki.dfupdate.se/projekt:updateringar#upcoming

When: 2026-04-11, 19:00 CEST
Where: Svartbäcksgatan 65, 75333 Uppsala
Stream: https://bbb.cryptoparty.se/rooms/upd-0mo-m2u-aq8/join

The ideas behind #Unix have significant impact on the design of a large number of #operatingsystems. In addition to more recent systems modelled after Unix, such as Minix or Linux, early operating systems inspired by Unix, such as Coherent, Venix, and also the #Idris OS developed by the company Whitesmiths, existed already in the 1970s. For many years, almost the only information available about Idris was a short Wikipedia page. This has changed in 2025 when a #PD68 computer, an Idris-based Motorola 68000 system developed as a project of computer hobbyists in Sweden and Norway, was donated to the computer museum in Dalby. Subsequently, an international cooperation also managed to get hold of and run the #Atari ST port of Idris, which extends the regular Idris system by providing a version of the X10 window system. In this talk, we give details about the recovery of Idris using emulation on different abstraction layers. In addition, we give an introduction to the structure of Idris for Motorola 68k-based systems with a focus on enabling Unix to run on computers lacking virtual memory management.

See you there!

projekt:updateringar [Update Wiki]

Idrisでビジネスロジックを書く場合どのように証明を書けるのか気になった
https://qiita.com/ssc-dninomiya/items/b47ae268846675dc3f4f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Idris

Idrisでビジネスロジックを書く場合どのように証明を書けるのか気になった - Qiita

背景 最近、輪読会でIdrisの勉強をしました。 教材はプログラング言語Idrisに入門させたい(v0.9)を使ったのですが、ド・モルガンの法則等の証明はとても興味深かったです。 証明を書くことで、単体テスト等で確認していたことがコンパイラで賄える点は非常に便利だと感じま...

Qiita

In #Birkenhead on Monday? Join us from 6pm every Monday at our new event!

Monday :: Programming -> Fun -> IO () is a close-knit group of programmers looking to improve their skills alongside others. Each session, we decide what language or concepts we're going to focus on as a group, returning at the end to discuss what we've built or learned.

Focus on improving your programming skills in good company!

#programming #rust #python #perl #c #cpp #rust #zig #go #assembly #fortran #haskell #idris

RE: https://hachyderm.io/@BoydStephenSmithJr/116298200584577447

Anyone out there with some opinions on both @codeberg and @gitlab particularly for developing #Haskell, #Idris, #Lean, or #Agda ? If you can,, please address my concerns in the quoted toot.

Thanks to Sirius-beta Labs who are once again sponsoring lunch for #BFPG Hack Day. UQ St Lucia, Saturday 28 March. Be there or be a lambda cube!

#FP #Haskell #OCaml #Idris #Gleam #Lean #Scala #Erlang #Elixir #FSharp #Clojure #Lisp #Agda #Rocq #Rust #Scheme #Racket

https://luma.com/uu28az9h

BFPG Hack Day - March 2026 · Luma

Come to BFPG Hack Day for some wholesome fun hacking on side projects, tackling tutorials, grinding axes and shaving yaks! Work together or independently.…

Okay, I'm declaring my #idris library https://gitlab.com/bss03/type-aligned done. I don't have any issues/tasks remaining. `pack-db` should automatically pick up the latest commit during the next update, within 24 hours.

I'm still open for all kinds of feedback, but until I get some, I think I'm going to switch to a PureScript project for a bit. I need to update to spago 1.x and figure out how to publish packages in that ecosystem. I need left Kan extensions to do the nseted (non-uniform) folds I was working on.

Plus, I feel like working with Halogen might make me more comfortable with React, or at least make me more interested in polishing those skills for a potential employer.

Boyd Stephen Smith Jr. / type-aligned · GitLab

GitLab.com

GitLab

Worked through the first round of issues for #idris type-aligned, but I came up with a couple more today: https://gitlab.com/bss03/type-aligned/-/issues

As usual, any feedback is appreciated.

Issues · Boyd Stephen Smith Jr. / type-aligned · GitLab

GitLab.com

GitLab

Ugh. I just SUCKED in a online 80 minute coding assessment for a new job.

I tried to do part of it in Haskell, which was a bad idea because they really wanted you to use an *array* algorithm, so the *list* solution I put forth just did not scale. (I needed a bit of a sliding window; the list approach was recalculating way too much.)

The other two parts were in React and Spring Boot and while I have used those, it's been a few years. The React problems was particularly difficult; I only got the smallest bit done. The Spring Boot I think I almost had, but I was missing something basic, so the tests weren't finding my perfectly good service.

The "employer" nodes said use whatever resources you want just don't copy in code. But, the proctor tried to lock their tab to fullscreen all the time, which made looking things up harder than it should have been. And, with frameworks that large, I think there are few developers that don't look things up (or consult an "AI") every damn day. Or maybe I just suck.

I doubt I'll hear any more from that employer. Anyone hiring for #Idris work? ;)