Rogers offering employees ‘voluntary’ departure, retirement packages
The news comes days after CEO Tony Staffieri told shareholders that Rogers needed to reduce its operating costs and capital investment plans.
#Canada #Economy #Tech #Layoffs
https://globalnews.ca/news/11819272/rogers-employee-departure-packages/
Rogers offering employees ‘voluntary’ departure, retirement packages
The news comes days after CEO Tony Staffieri told shareholders that Rogers needed to reduce its operating costs and capital investment plans.
#Canada #Economy #Tech #Layoffs
https://globalnews.ca/news/11819272/rogers-employee-departure-packages/
Rogers offering employees ‘voluntary’ departure, retirement packages
The news comes days after CEO Tony Staffieri told shareholders that Rogers needed to reduce its operating costs and capital investment plans.
#Canada #Economy #Tech #Layoffs
https://globalnews.ca/news/11819272/rogers-employee-departure-packages/

From lazy.nvim to vim.pack

Background I’ve been using the excellent lazy.nvim package manager for more than three years now, and I’ve been super happy with it. But with Neovim v0.12.0, vim.pack was shipped: a built-in (but still experimental) plugin manager that manages plugins using Git, with no third-party dependencies required, implemented by Evgeni Chasnovski (see neovim/neovim#34009), known for his work on mini.nvim. This piqued my interest, as I’ve found myself creating abstractions and isolations with lazy.nvim that don’t harmonize with my grug brain. So I figured I wanted to see if I could simplify by moving onto vim.pack.

#nvim, #packages, #vim.pack, #lazy.git

From lazy.nvim to vim.pack

Background I’ve been using the excellent lazy.nvim package manager for more than three years now, and I’ve been super happy with it. But with Neovim v0.12.0, vim.pack was shipped: a built-in (but still experimental) plugin manager that manages plugins using Git, with no third-party dependencies required, implemented by Evgeni Chasnovski (see neovim/neovim#34009), known for his work on mini.nvim. This piqued my interest, as I’ve found myself creating abstractions and isolations with lazy.nvim that don’t harmonize with my grug brain. So I figured I wanted to see if I could simplify by moving onto vim.pack.

Fredrik Averpil

Do-it-yourself: Printable Amiga boxes

The British user "amigang" has recreated several classic Amiga bundle packages (as a personal hobby project) and made them available for free download. Included are, among others, recreations of the Amiga 500 Batman Pack and the Amiga 1200 Desktop Dynamite. Individual templates for the Amiga 500, 600, and 1200 are available and can be printed out and assembled.

https://www.amiga-news.de/en/news/AN-2026-04-00093-EN.html

#Amiga #games #retrogaming #packages #boxes

amiga-news.de - Do-it-yourself: Printable Amiga boxes

I have a habbit of making (too) many (small) packages for functionality that might be reused in different context. {box} might be an alternative by making scripts into modlues that can be loaded: https://klmr.me/box/ #RStats #packages #waysofworking
‘box’: Write Reusable, Composable and Modular R Code

A modern module system for R. Organise code into hierarchical, composable, reusable modules, and use it effortlessly across projects via a flexible, declarative dependency loading syntax.

#Mail your #packages early so the post office can lose them in time for Christmas. 📫 -- Johnny Carson #COMEDIANS #LateNightTV
📣 New Package: Django Dependency Map
📄 Understanding the interaction between Django apps as you build
🔗 https://softwarecrafts.co.uk/100-words/day-302
#100_words,#django,#packages,#dependencies,#architecture
New Package: Django Dependency Map - Software Crafts

Understanding the interaction between Django apps as you build