I don't care what you say about United Airlines they are good people #UAL #United #UnitedAirlines #compassion #widow

#Almeria #UAL Conferencia San Alberto: ¿Por qué me dicen que llego tarde si no existe el tiempo? La física del tiempo? Viernes, 14 nov 12:15. Organizada por la Facultad de Ciencias Experimentales Universidad de Almería. https://agenda.ual.es/eventos/por-que-me-dicen-que-llego-tarde-si-no-existe-e-tiempo-la-fisica-del-tiempo/

#Almeria #UAL Conferencia San Alberto: ¿Por qué me dicen que llego tarde si no existe el tiempo? La física del tiempo? Viernes, 14 nov 12:15. Organizada por la Facultad de Ciencias Experimentales Universidad de Almería. agenda.ual.es/eventos/por-...

¿Por qué me dicen que llego ta...

Meteor or space debris? We will know soon. https://www.wired.com/story/mystery-space-object-strikes-united-airlines-flight-over-utah/ #UnitedAirlines #Aircraft #SpaceDebris #Meteor #NTSB #UAL

Now entertaining the possibility of crafting a minimally working version of ual using zenas.

Not sure how far away from that I am, could still be a year or more away.

#ual #zenas

🏦Curso CRUE en @UIMP | Panel «Programas para fomentar el emprendimiento en las universidades»
Modera: José Luján Alcaraz, Vicepdte. CRUE, Rector #UMU
Ponentes:
➡️José Céspedes Lorente, Pdte. Crue-Asuntos Estudiantiles, Rector #UAL
➡️Alexandra Hernández López, Manager Santander X (Santander Universidades)
➡️Carmen Adán de Manuel, Directora Parque La Salle Technova Barcelona
➡️Esteban Romero Frías, Vicerrector #UGR

Kerem Aktürkoğlu'nun transferinde Galatasaray'ın sözleşmeye eklettiği madde gereği söz hakkı var. Benfica eğer oyuncunun satışına izin verecekse teklif edilen değer karşılığında söz hakkı Galatasaray'a sunuluyor.

Galatasaray, cevap hakkını son güne kadar korursa Fenerbahçe Kerem'i Avrupa listesine yazamıyor. Eğer Benfica bu maddeyi uygulamazsa, Galatasaray'a tazminat ödemek zorunda.

5 günlük cevap hakkının ne zaman kullanılacağına başkan, teknik heyet ve yöneticiler karar verecek.
Kaynak: https://beinsports.com.tr/haber/galatasarayin-soz-hakki-var-kerem-akturkoglunda-carpici-risk

Fenerbahçeli arkadaşlarla yine anlaşamıyoruz. Diyorum ki; bu iş benim için hiçbir öncelik taşımıyor. Yasal olarak bana tanınmış bir süre var, önceliği olmadığından o sürenin sonunda imzamı atarım. Bu durum seni etkiliyorsa randevu iste anlat derdini, elimizden bir şey gelirse yapalım. Ama yok, beyefendiler bizden randevu istemeye yanaşmıyorlar. Gereğini yapmazsak hain olurmuşuz. Peki Fenerbahçe'nin Avrupa'daki kadrosundan Galatasaray kendi kendine niye vazife çıkarsın. Buyrun gelin diyoruz, yok... O zaman ben de en önemsiz işimi en sona atarım kardeşim.
#Galatasaray #fenerbahce #KeremAkturkoglu #UAL

United Airlines 787 about to touch down at San Francisco International , January 2024 #aviationphotography #planespotting #AvGeek #spotter #aviationdaily #photography #aircraft #Nikon #UnitedAirlines #UAL #B787 #ksfo #nikon #nikonphotgraphy

¿Nos vemos esta tarde? Voy a estar por aquí.

📍 Teatro Apolo
⏰ 19:00h
🎟️ Entrada libre hasta completar aforo

En un evento muy chulo, 10 doctorandos de la #UAl contando sus investigaciones de forma desenfada en tan solo 3 minutos

Si vienes, tendrás la oportunidad de votar por tu favorito y otorgar el Premio del Público 🏅

Los estudiantes de enfermería de la Universidad de Almería advierten de la preocupante «fuga de talento»

https://fed.brid.gy/r/https://espacioandaluz.com/andalucia/los-estudiantes-de-enfermeria-de-la-universidad-de-almeria-advierten-de-la-preocupante-fuga-de-talento/?utm_source=rss&utm_medium=rss&utm_campaign=los-estudiantes-de-enfermeria-de-la-universidad-de-almeria-advierten-de-la-preocupante-fuga-de-talento

Boeing 777-224/ER
SUnited Airlines
#UA #UAL #UNITED
#Boeing #B777 #N78005
#aviationphotography
#bnw #bnw_aviation #lowkey

April 09, 2025 at 07:19AM

via Instagram https://instagr.am/p/DIM7xW8tFvG/

#ual

Computer-sciencey once more:

The Composition-Oriented ual Way

Part 2: Perspectives - Unified Access Patterns

https://github.com/ha1tch/ual/blob/main/doc/ual-composition/ual-composition-02.md

In ual, traditional data structures like stacks, queues, and dictionaries are seen as different views, implementations, and interfaces which were historically separated into categories that deep down are fundamentally made of the same axiomatic principles. Instead of treating these as separate entities with different operations, ual proposes a unified "perspective system" where these are simply different ways of accessing the same underlying container. This approach offers greater flexibility by allowing programmers to switch between different access patterns without changing the underlying code structure. The system simplifies programming by reducing conceptual overhead and enabling more adaptable algorithms through a more unified approach to data organization and access.

Part 2 of 6, the rest of the series is here:
https://github.com/ha1tch/ual/tree/main/doc/ual-composition

#ual #rustlang #golang #forth #compsci #programming #retrodev #retrofuturism #retrocomputing

ual update:

• ual for Rust devs
  • https://github.com/ha1tch/ual/blob/main/doc/primer/ual-primer-04-rust.md

I added two new intros to the "Primers" collection, one is a general intro, the other a specific one for Rust developers.

ual primer collection

https://github.com/ha1tch/ual/tree/main/doc/primer

• 00 Intro
  • https://github.com/ha1tch/ual/blob/main/doc/primer/ual-primer-00-intro.md

• 01 Mainstream devs

  • https://github.com/ha1tch/ual/blob/main/doc/primer/ual-primer-01-mainstream.md

• 02 Embedded devs

  • https://github.com/ha1tch/ual/blob/main/doc/primer/ual-primer-02-embedded.md

• 03 Retro/minimalist devs

  • https://github.com/ha1tch/ual/blob/main/doc/primer/ual-primer-03-retro-minimalist.md

• 04 Rust devs

  • https://github.com/ha1tch/ual/blob/main/doc/primer/ual-primer-04-rust.md

#ual #forth #rustlang #golang #programming #compsci #foss

ual updates

• new Enhanced Execution Mechanics - Pull and Value Handling
  • Several refinements addressing inconsistencies between ual's way and Forth-like behaviour
  • https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.9-PROPOSAL-enhanced-exec-mechanics.md
• new A renewed effort towards a more cohesive grammar that encompases all/most improvements from the proposals since the 1.3 spec.
  • https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.9-PROPOSAL-consolidated-grammar-spec.md
  • tentative ebnf draft https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-0.1.9-preview.ebnf
  • Rust + Chumsky-based incomplete parser preview based on the preliminary ebnf 1.9 description
    • https://github.com/ha1tch/ual/blob/main/rualc/rualc-1.9-chumsky.rs

This is the ual way:

ual 1.3 spec

• P1:https://github.com/ha1tch/ual/blob/main/spec/current/ual-1.3-spec-P1.md
• P2: https://github.com/ha1tch/ual/blob/main/spec/current/ual-1.3-spec-P2.md

Error Stack Mechanism

• https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.4-PROPOSAL-error-stack.md

Typed Stacks

• P1: https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.4-PROPOSAL-typed-stacks-01.md
• P2: https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.4-PROPOSAL-typed-stacks-02.md

Ownership Mechanism

• https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.5-PROPOSAL-ownership-system.md

Defer Stack Mechanism

• https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.5-PROPOSAL-defer.md

Stack Perspectives

• https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.5-PROPOSAL-stack-perspectives.md

Concurrency Model

• P1: https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.5-PROPOSAL-concurrency-model-01.md
• P2: https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.5-PROPOSAL-concurrency-model-02.md

Stack Slicing and Segment Borrowing

• https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.6-PROPOSAL-slice-borrowing.md

#ual #forth #rustlang #golang #programming #compsci #foss

Crosstacks are Orthogonal Stack Views

https://github.com/ha1tch/ual/blob/main/spec/incoming/ual-1.8-PROPOSAL-crosstacks.md
Crosstacks are a new ual kind of element that provides orthogonal views across multiple stacks (think: a row of a spreadsheet that traverses several stack columns).
This extension lets you work with data in both vertical (traditional stack) and horizontal (cross-stack) directions with equal efficiency. With crosstacks, you can elegantly express complex operations on multi-dimensional data without specialized syntax. Tailored for matrix operations, image processing, and tensor calculations while maintaining ual's philosophy of explicit, efficient operations.

HA-HT

https://github.com/ha1tch/ual/blob/main/doc/compiler/crosstack-implementation/haht.md
Under the hood, crosstacks use a Hybrid Adaptive Hash-Tree structure that combines direct addressing with specialized data structures. The first two levels provide O(1) access to positions, while the third level adapts between five different implementations based on actual usage patterns. This approach delivers consistent performance for both vertical and horizontal access while efficiently handling sparse data and diverse workloads. At this time this is our best candidate implementation.

#ual #compsci #programming #rustlang #golang #foss #forth #retrocomputing #retrodev

And here I go computer-sciencey again:

The Composition-Oriented ual Way

Part 1: Foundations - Container-Centric Thinking

https://github.com/ha1tch/ual/blob/main/doc/ual-composition/ual-composition-01.md

ual is a programming language that places containers, not values, at the center of its design. Part 1 explores container-centric thinking and how focusing on where values live rather than what they are creates interesting new approaches to code organization and algorithm design.

Part 1 of 6, the rest of the series is here:
https://github.com/ha1tch/ual/tree/main/doc/ual-composition

#ual #rustlang #golang #forth #compsci #programming #retrodev #retrofuturism #retrocomputing

This is nowhere near useful yet, but I thought I'd let you know.
https://github.com/ha1tch/ual/blob/main/rualc/rualc-1.9-chumsky.rs

#ual #compsci #rustlang #forth #programming #retrodev #retrocomputing #retrofuturism #golang

@KingmaYpe

Late follow up on some questions I didn't fully/explicitly address:

First off, thanks again for all the thoughtful input — really appreciate you engaging with this.

• You're absolutely right about ual's potential as a learning and onboarding tool for embedded developers who may not want to dive into the full depth of Rust right away. That's very much in line with my thinking. Part of what motivates ual is exactly that: creating a way to teach ownership, borrowing, and safety concepts explicitly and visibly, without needing to wrestle with lifetimes, traits, or complex generics right out of the gate. So, yes, I think it could be a stepping stone for people who want Rust-like safety but in a smaller, simpler package. Many projects might benefit from rapid prototyping at worst.

• Also, I think your idea about implementing ual as a front end to the Rust compiler is really interesting — and I hadn’t fully considered it in those exact terms before! Right now, my Rust proof-of-concept (iual) is more of a "manual mapping" to see how the concepts translate, but the idea of a more integrated approach — like a proper front end — is something I'd definitely like to explore further. Especially if it means getting the benefits of Rust's mature backend (like LLVM integration, tooling, etc., although we are already getting some of that through TinyGo, a Go compiler for embedded systems) while keeping ual’s stack-oriented, explicit model.

So thanks for putting that thought on the table.

#ual #rustlang #programming #compsci #foss

Since some have asked why I'd bring up Rust when talking about ual, I want to clarify why I think this is relevant — especially for Rust developers interested in ownership, borrowing, generics, embedded systems, and language design.

Here are the key reasons why ual should probably be of interest to the Rust community, or at the very least to Rust leaders and Rust designers, even if that's not immediately obvious to new Rust developers:

1. An Explicit Alternative to Ownership and Borrowing (No Lifetimes Needed)

• ual proposes an ownership and borrowing system that is fully explicit and doesn't rely on lifetimes.
  
• Ownership is treated as a relationship between containers and values, not something inferred by the compiler.
  
• Borrowing is explicit and scoped in code, so there’s no hidden inference or guessing what the borrow checker wants.
  
• You can see exactly when a value moves, is borrowed, or is returned, instead of it being deduced from subtle rules.
  
• For Rust developers who are used to working around lifetime issues or fighting the borrow checker, ual offers a visible, container-based model that may be simpler in some contexts.
  

2. Container-Centric Genericity as a Lightweight Alternative to Traits

• Rust’s trait system is powerful but can be complex and heavy, especially for embedded systems or low-overhead code.
  
• ual focuses on generic algorithms operating on containers (stacks) rather than individual type parameters.
  
• It uses explicit type-switching and bring operations instead of abstract trait bounds and impls.
  
• This allows reusable, type-safe algorithms without needing to engage with the full machinery of Rust's generics.
  
• For embedded and systems developers who often find traits overkill for simple cases, this is a fresh alternative to achieve reuse safely and explicitly.
  

3. Borrowing Slices, Made Explicit and Visual

• Rust slices (&[T], &mut [T]) are powerful but frequently cause borrowing and lifetime headaches in complex code.
  
• ual introduces borrowed stack segments, which are fully explicit in code and scope:
  
  • You clearly mark and control what part of a container is borrowed.
    
  • You explicitly see what’s borrowed and for how long — no guesswork, no inference.
    
  • Mutability and read-only access are controlled through syntax and scopes, avoiding subtle conflicts.
    
• This is directly relevant to Rust devs frustrated by slice-related borrow checker issues, offering a more visual and controlled borrowing model.
  

4. A Philosophical Cousin to Rust — Explicitness, Safety, and Responsibility

• Like Rust, ual is concerned with memory safety, resource correctness, and predictable control of side effects.
  
• ual emphasizes making everything explicit — no hidden drops, no implicit borrowing, no magic.
  
• Safety is treated as an ethical responsibility, not just a technical constraint, which aligns with Rust’s philosophy but makes the mechanics visible and teachable.
  
• If you care about Rust’s focus on preventing errors by design and explicit resource handling, ual explores similar goals through a different lens.
  

5. Embedded Systems Focus — Shared Goals, Different Answers

• Rust has a strong embedded systems community focused on safe, low-level control and resource-constrained environments.
  
• ual is designed from the start for embedded and resource-conscious systems, with:
  
  • Explicit stack management for predictable resource use.
    
  • Minimal runtime, aligned with no_std-like constraints.
    
  • Safety guarantees without introducing heavy compile-time machinery that can be difficult in embedded contexts.
    

- For embedded Rust developers pushing against compile-time limits or seeking alternatives for resource handling, ual may offer new ways of thinking about ownership and control.

B... But... What the $%·$% does ual have to do with Rust?

Because ual aims to address some of the same fundamental problems Rust does — ownership, borrowing, generics, resource safety, embedded programming — but through a model based on explicit containers and stack flows.

For Rust developers who:

• Care about ownership and borrowing but are curious about alternatives to lifetimes.
  
• Have struggled with complex traits and generics, especially in embedded contexts.
  
• Want to explore explicit slice/borrowing models that avoid hidden inference.
  
• Value explicitness, responsibility, and safety in system design.
  
• Work in embedded systems and care about resource efficiency and control.
  

— ual is highly relevant, even if its design is very different.

If any Rustaceans are interested in discussing these ideas — how they compare, where they overlap, and where they differ — I’m happy to talk!

I am: h (AT) ual.fi

#ual #rustlang