Recently getting a new Mac for work, coming from Hyprland has been tough, but I feel like I’m getting there. Aerospace and Karabiner-Elements have gotten me most of the way there. Have had to write a few scripts to get the workspaces working the way I’m used to, but overall I got a significant part of my workflow to mirror my Linux setup, but would still love to get the super+right click to resize working somehow (there is a native way to move windows with ctrl+cmd+left click which was nice).
Not OP but it's the best auto tiling WM I've found for MacOS so far. Yabai requires SIP disabled for what I would consider core features which is a no go on a work laptop. Aerospace sides steps this and MacOS's horrible window management by just not using the built in spaces. I've only had to restart it a couple times over the last 4 months due to bugs.
Recently got a mix board and have been learning on mixxx. If anyone has any general guides for learning to dj in mixxx I’d love to know. Honestly, I feel a little lacking in the fundamentals of digital audio so I’m probably going to focus on that before going too deep, but so far mixxx has been great! It was pretty hard for me to navigate, but that’s 100% because I have no idea what I’m doing. Curious to seeing if the update will help with discoverability.
80% of DJing is the generalized skill of picking music that fits the vibe, that you can practice with any software. 10% is doing transparent and/or engaging transitions and the rest of the 10% is technical chops, being fluid and being able to recover when you inevitably fuck up. Approach your learning accordingly :)
As a DJ since age 16 who earned a living from it once:
The number one most important skill is to pick the right music in the right moment. Period. Online many people will tell you about beatmatching, transitions, the best gear and all that, and sure, it is good if you can do that or buy that. But better a DJ who picks good music with crude transitions than one who picks boring music with stellar transitions. My digital sets I do with my laptop, Mixxx and an audio interface, no controller, just keyboard shortcuts.
Even if you just crudly made hard cut-transitions and don't match beats you can still give people a great evening if your music selection and the order in which you present it is good. I once had people partying till early morning with my phone (android/poweramp) as a source, as it wasn't a planned gig.
That means you (should) invest significant time in listening and sorting your music and have an clear idea which types of DJ set you like. A lot of this will depend on the style(s) of music as well. Putting on dub is very different from straight techno which is very different from let's say playing an 80s post punk set or something entirely eclectic. And a lot of that depends on the venue, the crowd etc. A good DJ will react to the circumstances around them.
As for Mixxx, most of the metaphors and parts of the UI in DJ software is derived from vinyl DJing. A crate would be a literal crate filled with vinyls. Since vinyl is heavy as shit, bringing all your music was/is not an option and DJs packed literal crates, for a specific gig, etc. The two Decks on Mixxx are refering to the record players (typically two "Decks") you would have with vinyl. In the middle you have a mixer section, just like the mixer between the two record players.
Your task is (a bit simplified): selecting a song, playing it, selecting another song and then transitioning to that song ad infinitum. So you load up a song in the left deck hit play and have it play and you move the crossfader to the left so only the left deck can be heard. You then search for the next track while the song is playing and load it up on the right deck. Mixers typically have a PFL button (pre fader listen) that allow you to "privately" listen to channels even if their volume fader (or the crossfader) is turned down (this is why DJs have headphones). You basically listen with one ear to the the thing the audience hears and with the other to the next song.
Now the song on the left deck is nearing its end and you have another song on the right deck, you try to make the two align in time, tempo, frequency, pitch in such a way that the transition sounds good and then you use the crossfader to blend over. Or you could just wait for song A to finish and then hit play on song B if you don't care too much about the transition. Or you could mix only the bass from song A with the hihats from song B, add effects, shout something into the mic and then play a song from a third deck, while all while listening to song requests.
For the tempo matching Mixxx has a button that does that for you on each deck, not like if you DJ with vinyl where you have to do that by ear. The mixer has an EQ (changing the level of Bass/Mids/Highs at fixed frequencies) and a Filter (cutting away high and low frequencies with variable frequency, allowing you to avoid situations where two basslines/hihats are playing at once during a transition.
You can go arbitrarily complex, but as mentioned at the beginning, music selection and situational awareness is king, everything else is just details as long as you don't make jarring mistakes with jumps in level or prolonged gaps of silence etc.
Would love to know how they went about implementing these. I always find custom elements interesting. I know the guys over at data-star.dev used one to implement their inspector element, but unfortunately that is also behind pro.
I know Lit is used a lot but I’m always looking for new approaches.
Since you are asking about other approaches, I've been doing some interesting and simple custom elements with my Knockout-inspired view engine [0]. I built an open source MPA application with a bunch of them [1]. I even gave a brief presentation on it [2] (each PR starting with #2 is a "slide"; I presented it in a "Presentation" profile for VS Code opening the numbered files in order, with the Live Preview extension side-by-side with a simple git alias to jump to "slide" merge commit based on PR number; I thought it went well to show off Developer Experience).
My biggest advice appears to be: remember that the Shadow DOM is optional.
I mean they mention the built in browser features they use, but make no mention of the actual authoring of the components unless I’m missing something. I’m curious if they’re leaning on existing frameworks for authoring web components or if they’re implementing them from scratch.
- pages are saved as text-files-written-to-disk with git autocommits (similar to mycorrhiza[0])
- "blocks" that process parts of pages differently - similar to edna[1]
- pages editable via web interface (rudimentary phone support)
- autolinks between pages
- simple picture upload interface (^V with a pic in clipboard will upload the pic + paste appropriate markup)
- single user system, intended as a personal knowledge base
this system will replace https://j3s.sh and https://abyss.j3s.sh eventually -- all old links will redirect to the new wiki. it's been quite an undertaking, but i think the end result will be worth it :3
Something to keep an eye out for is Lux: https://github.com/nvim-neorocks/lux. Looks like a promising replacement to Luarocks, but is still pretty early in development.
I believe it’s finally enabled by default in nightly builds, so it should be standard soon. I may be wrong and it may have been scoped css enabled, but both are available by feature flags on nightly and plan to be enabled by default by the end of the year.
Most interesting part of this imo was using a separate modfile for tools to avoid version conflicts. This was a concern I saw brought up with regards to `go tool`, but this seems to address them.
I only started using "Desktop" linux about 2 years ago when I got my new Laptop. When I first started, I had no idea what the whole Xorg/Wayland story was up until that point. After a bit of research, I tried starting with i3, but could never get it configured correctly to use my laptop monitor and my desktop ultrawide monitor at the same time. After about a month of this, I swapped over to Hyprland and haven't looked back since.
While I never encountered any serious issues that prevented me from using my laptop when I first started, a few things didn't work properly all the time. In the past, I used to have a few issues getting screen sharing working, sometimes I couldn't launch a steam game. Since then, the experience has gotten to the point where I really don't notice any issues. Screen sharing works fine now, I can't remember the last time I couldn't get a steam game to launch. I don't even have issues with electron apps anymore. This is all while running on an Nvidia GPU.
I know there are still issues on things like accessibility, but from someone who doesn't have the time investment into Xorg, Wayland felt pretty good a few years ago, and now I really can't find anything to personally complain about with regards to it.
I started using sway seven years ago, and even then I had very few issues. Granted I use integrated Intel graphics and I mostly just want to arrange terminal emulators, but still, on that happy path, it hasn’t been a problem.
What software did you use? I have to use Google Meet, Microsoft Teams, Anydesk, and an onscreen keyboard. When I checked a couple of months ago, Anydesk wouldn't even launch. I have been dabbling with Wayland ever since it was made available on Arch Linux, but invariably have to go back to X.org after just a few hours on Wayland.
Looking forward to this! Had been lurking in the discord for a while but never talked much so I never was able to get a beta key. The Terminal Inspector seems super cool and is what I'm most excited to try out. Seems like it'd be really useful for Bubble Tea [0] apps which I've been having run writing.
