I've been working on a general repository linter. The idea is to declaratively define a set of rules/conventions for your repo, (for things that language-specific linters don't cover), covering things from directory structure, required files, file staleness/freshness, file size, rules for binary files, rules around use of invisible Unicode, etc. - which can be checked deterministically. Many/most large repos have a set of hand-authored scripts for doing these kinds of checks, the tool I'm building basically packages these in a fast, reusable and extensible tool, with some niceties added.
It would be great if I could integrate this into our existing (and rather extensive) eslint config as as a plugin of some sort rather than integrate yet another new tool to our dev environment. Any plans for that?
Yeppp, I've been seeing this Jacob Coxon [0] guy popping up all over legacy media for the past couple days nonstop...he claims he quit OpenAI and Anthropic because the models are getting 'too smart' and that's dangerous, etc. The typical AI fears mongering drivel, without seemingly any criticism, at all, of the companies he quit supposedly because of these AI fears... and of course the mainstream media appearances prefix the interviews with this guy with 'this is not a marketing stunt'[1]... which, obviously, it is.
Seems just like another case of collusion - continuing the story of VCs pushing all of their companies to use each other and 'stay within the network'. The good news (kinda) for the rest of us, is that many of these VC marketing/product/'strategy' people aren't actually all that competent - this is literally the best they can come up with.
I use alint [0][1] to define and enforce rules about files/globs that should or shouldn't be committed, among other things. You can configure it run as a pre-commit hook or in CI.
I use alint [0][1] to define and enforce rules about files/globs that should or shouldn't be committed, among other things. You can configure it run as a pre-commit hook or in CI.
You can also use something like alint [0][1] to define and enforce rules about files/globs that should or shouldn't be committed, among other things. You can configure it to run as a pre-commit hook or in CI.
I use alint [0][1] to define and enforce rules about files/globs that should or shouldn't be committed, among other things. You can configure it run as a pre-commit hook or in CI.
Kind of sideways rant about tiling window managers on Marcos in general..
I mostly use Linux + dwm as my daily driver, recently added a mac into the mix (mostly for testing personal cross-platform stuff, I use macs for work mostly), and not being a fan of the macos UI in general decided to set up a tiling window manager - googling showed me AeroSpace and Yabai as the most popular options.
The experience with both of these has been quite terrible, and I don't think the problem is with these projects themselves but with macos and how it's UI/desktops work. Full screen windows seemingly break both completely. Doc hiding/showing is completely inconsistent - sometimes it just renders on top of all windows and doesn't hide other times it stays hidden even on mouse hover. Windows just disappear and can't be switched to. Fullscreen tiling seems completely unsupport(ed/able) - you must waste screen space on pointless title/status bars for some reason . After googling it turns out many of these issues exist in a fresh/bare macos and have been know unfixed issues for like 5+ years.
I can't believe there are people claiming macos has a consistent, elegant and high quality UI... it is so terribly shitty and broken
Yeah its a bit painful on mac. You cant have floating windows constantly in front on mac like you have on hyprland. In my implementation I added a super + s shortcut to pull any floating windows I lost to the front again. But its definitly not the nicest solution.
For fullscreen windows I also added a custom implementation with super + f that works in the workspaces setting. Just making videos fullscreen or clicking the green fullscreen button still exits the setup to macos fullscreen. The system is still kinda usable with mac fullscreen in parallel but its not a clean experience.
Just had some time to look at this, it needs SIP disabled which opens up some risk. That was the reason for me to choose AeroSpace as a foundation instead of yabai.
MacOS is so absolutely terrible for programming work. The only coder-favorable unit on Mac that I wish Linux had a similar alternative for is the OSA layer. Nothing else is justifiable there from a software engineering standpoint. Nothing.
Apple keeps insisting on Jony Ive's influence and keeps making "an operating system for florists". Well, I'm a damn programmer - I need the utility, I don't care about stupid animations, widgets, jumping icons in the Dock, etc. If my enterprise overlords didn't push it so hard down my throat, I would be so much happier just using Linux.
Programmers are not a monolith. The minimal tiling keyboard driven thing works great for some, but it drives me up a wall as much as the standard macOS arrangement seems to irritate you.
Actually one of my peeves with Linux is that as of yet, there’s no WM or DE for Linux that gets even 80% of the broad strokes right for people who find a traditional Mac style desktop productive. Most options either lean Windows-style or minimal tiling style, with the only outliers (GNOME, Pantheon, COSMIC) representing the odd niche of a small handful of macOS fundamentals hybridized with conventions from the tiling things and Windows.
I'm not talking only about WMs on Mac - just in general. The restrictions they put around things get to ridiculous level of hassle experience. All those "you're holding it wrong" and "customers don't know what they want" vibes are just super annoying and unproductive. I hate when the software on the hardware you own treats you like a baby. What's the point of calling yourself a "software programmer" when you can't even control the damn software? It feels like making you helpless was the point.
I mean it's all subjective. The relative rigidity of the macOS UI just means that it isn't for people who don't like it.
For those of us who do enjoy it, it's great because a stock install is already 80% of the way to a productive setup. I can have a new Mac ready for work in 15-20m without copying dotfiles or anything like that.
Not that there isn't a place for tinkering and customizing, but it's not the computer(s) that I get work done on. It's for leisure time machines. When I try to work under Linux I end up on side quests trying to fine-tune everything to perfection (which is for practical purposes impossible, unless I write an entire desktop environment for myself) and can't get any work done. On a Mac most things are already configured the way I like and the things I can't I shrug and then focus on my work.
> On a Mac most things are already configured the way I like
Well, I'm not "the defaults" person - there isn't a single piece of software that I ever installed and didn't have to configure later, except maybe some CLI tools. To me, that's the point of "soft" in "software" - it should be malleable. Not everything has to be of the Emacs level of extensibility, but I should be able to change things to extract maximum utility out of it. I don't "tinker" for the sake of it - I make changes for performance and execution.
I squeeze both Linux and Mac environments to their utmost possible scriptability. Bootstraping a Linux box from scratch for me is a matter of minutes. I wish I could say the same thing about Macs - there are tons of things you just can't easily change from the command line, it's a long cycle of - click, open, navigate, click, browse, confirm, click, logoff, reboot, etc. And it's simply annoying. It feels like needless ceremony for the "cybersecurity theater" or whatever. And the 80% of opinionated pre-made things to make you productive is just bullshit - like for example, the very first thing I always do on a new Mac is that I run:
This makes a huge difference in keyboard latency. Why the heck these values are not reachable from the UI is a mystery to me. I'm glad that at least this one is tweakable from the command line, but many other things are not.
I suppose I should be thankful for not having to deal with Windows. Which is way worse.
Ha ha ha. I did settle into using a Mac for development work, but not without a moderate degree of customisation. Reducing keyboard latency was, like you said, one of the changes that made the most difference.
I'm curious what other kinks you have had to iron.
https://alint.org/
https://alint.org/blog/why-alint/
reply