IMF: Imperialist Monetary Fund
monovergent
If you want to avoid this judgement, get an Apple silicon Macbook Air or something...
Damn, me over here trying to flex my Chicago95-ass X201T to my classmates
Storytime!
As a physics major, daily driving Linux worked out pretty smoothly. The thing that saved me from trouble the most was making a weekly full system backup (I used Clonezilla and my file server). If anything was truly incompatible, I took care of it on the school's computers.
In my second semester, I began dual-booting on my X201 Tablet and desktop, eventually booting into Windows infrequently enough that I made my X201T Linux-only by the end of my second year.
Around that point, I began using LUKS full-disk encryption on my machines and USB drives. I highly recommend if you don't already, even if just for peace of mind. I have strong ideas about the way things ought to look and work, so being able to customize Linux to my heart's content (with Chicago95 ofc) made doing work on my computer a bit more enjoyable.
Documents
- MS Office: Libreoffice worked 95% of the time. For the other 5%, I used the school computers or my Windows VM.
- Google Docs and GMail: accessed through Chromium, which I only used to access Google and sites linked to my school's SSO system.
- We did a lot of writing in Latex, though it might be a physics thing
- A lot of other small stuff I'm starting to forget, but if I don't mention it, I probably did it through the browser.
Lab
- MATLAB: GNU Octave sufficed 75% of the time, often needing just slight changes to the code. Otherwise I used the lab computers or my desktop with actual MATLAB.
- Proprietary dana analysis software: One had a .deb package for oldoldoldstable so I set up a VM just for that. Otherwise, lab computers it was.
- Lab computers running old and new versions of Windows were available to us, so if there was anything computationally intensive or requiring proprietary software, I would just take care of it in the lab.
Social
- Slack, Discord, Facebook, Instagram, Whatsapp: browser client, which I would check on a schedule
Tools
- VPN: NetworkManager, though it was a bit janky. I think it's a lot better nowadays.
- Printing: We had a web print portal to upload docs and pdfs to a printer of our choice.
Graphics
- Mostly prepared my posters, etc in a mix of Libreoffice Draw, GIMP, and Inkscape
- Adobe: Had to use it on one occasion. Used the library computers where it was installed for everyone to use.
- Digital notes: I would use Xournal on my X201 Tablet whenever I forgot to bring my notebook or refill my fountain pen. Managed to impress a few of my iPad-toting classmates when I whipped out the pen and the display around on what they believed to be an ancient clunker.
As for the desktop, I had purchased it with gaming in mind, but it eventually became my SMB file share, media server, and RDP session host so I could make any library desktop like my own. Each thing in its own VM, of course. By the end of it, I was one of about 3 students running a server over the campus LAN. Even in the comp sci department, surprisingly few students used Linux.
Linux also met all of my computing needs while studying abroad in Germany. For five whole months, I had not used Windows once. Though my SSD did give out on me once, a backup saved the day.
A friend once did need to use a rather invasive remote proctoring tool. Highly recommend a separate laptop or at least a fresh SSD for this case.
Mobile privacy, if it's relevant
- I was in the fortunate position where none of my classes or jobs required proprietary mobile apps
- Friends used Venmo or whatever else, I paid back in cash
- SMS and emails sufficed for regular communication
Overall, it was smooth sailing using Linux throughout my college years and no incompatibilities that couldn't be solved in the library or a computer lab.
edit: i used debian btw
Middle mouse click is indispensable but it seems to be first to fail on my mice
Wayland, but I'm patiently waiting for xfce to support it
yt-dlp. Too many options to remember and look up every time, but all useful and missing from GUIs when you just want to dowload audio or 'good enough' quality video in batches without re-encoding.
While nmtui is perfectly fine for the CLI-uninitiated, I sometimes wonder why the nm-connection-editor window doesn't provide the same level of functionality.
A metal 128 GB USB on my keychain next to the U2F key
16 GB Ventoy partition with:
- Clonezilla ('deploying' my system image and backups)
- Mint Debian Edition (everything needed to test and recover my Debian systems)
- Debian netinstall
- Various manuals and reference documents
- Portable CrystalDiskInfo and VeraCrypt for Windows
- Dumping grounds for files that I intended to transfer between machines, particularly the XP retro gaming rig
- An optimistic IF-FOUND.TXT
- KeePass
- Previously Windows, until once upon a time, I booted into WinRE via Ventoy, got confused between X:, C:, and whatever else, and proceeded to nuke my USB instead of another disk. The Windows installer lived on its own USB happily ever after.
And a LUKS encrypted partition in the remaining space with more documents and a backup of almost all of my photos.
To make it clear, I would still use Linux with GNOME/libadwaita over Windows any day. Yes, some themes are ridiculous and will be a nightmare for any developer to work around. That said, I can't help but be concerned about the coming demise of theming with the way GTK is going.
What first pushed me to start exploring Linux was when Windows 8 forced the Metro theme down our throats. My time with Linux would have started three years later if M$ had kept Windows 7 theming options - that's how important a customizable, sensible theme is to me.
I'm glad that I don't have to do that again since there are DE options that do insist on keeping theming alive.
Is DivestOS any better in this respect?
On a file share, a notes directory with each category as a subdirectory, and plain text files for each note. Accessible from my computers and phone.
On my laptop, the launcher for my text editor (Pluma) points to a bash script that creates a blank text file YYYYMMDD_text in ~/.drafts and opens that file with Pluma. If it already exists, YYYYMMDD_text_1, or whatever increment is created. That's mostly to take advantage of Pluma's autosave feature, which only works with already saved documents. Then I save the document to the file share if it's worth keeping.
ThinkPad X230 with 9 cell, 16 GB RAM, total 1TB storage, and an Atheros NIC. A bit limiting at times, but I 'outsource' heavier tasks to my much more powerful desktop. I'm quite uncompromising with laptop design and 'ergonomics', so I'm trying to piece together a custom laptop based around the Framework mainboard before the X230 no longer meets my demands.
For testing stuff on Windows and work stuff that requires it, an X1 Carbon Gen 7 with 16GB RAM and 256 GB storage.
TIL what happens when the thermometer maxes out