tincholio

Well, way back in the day, dev tools weren't free, either, for the most part.

It's excciting, but I saw a review of a pre-release c2 on youtube [0] the other day, and it seemed extremely slow in the interactions. Otherwise, it seems like a cool device.

[0] https://youtu.be/5titW5dclwg

He looks like Dracula on LinkedIn

My take on this is that when outsourcing the code writing, you miss out on building a mental model of how it works that you do develop when doing it yourself. The degree to which that is a problem is probably variable, I suppose.

Most of those are not really "frameworks" as such (with some exceptions, like Biff or Fulcro), but rather libraries, or curated collections of libraries. Most Clojure people tend to roll their own set of libraries, rather than use actual frameworks.

I've been experimenting with this (it's in Babashka, which is for scripting Clojure, but you can do it with just bash, if your bash-fu is stronger than mine :D ):

    #!/bin/env bb
    
    (ns switch
      (:require [clojure.java.shell :as sh]
                [babashka.process :refer [pipeline pb shell process]]
                [clojure.string :as str]))
    
    (def workspace-ids
      (-> (pipeline (pb "hyprctl workspaces")
                    (pb "grep 'workspace ID'")
                    (pb "awk '{print $3}'"))
          last
          :out
          slurp
          (str/split #"\n")
          (->> (reduce (fn[acc e]
                         (try (let [ee (Integer/parseInt e)]
                                (conj acc ee))
                              (catch Exception e acc))) [])
               (filter #(and (pos? %)
                             (not= 10 %))))))
    
    
    
    (doseq [w workspace-ids]
      (-> (process (str "hyprctl dispatch moveworkspacetomonitor " w " 1"))
          deref
          :exit
          println))
    
    (process "hyprctl dispatch workspace 8")

It basically just moves all workspaces with positive IDs (so not the special workspace) to the external monitor, which seems to have a consistent ID of 1.

Indeed!

I have been having some issues with X/i3 (using i3 as a WM for Plasma), mostly with multiple screen setups (windows getting all screwy when connecting/disconnecting, lots of flickering, etc.), and also with my trackpoint's middle button scrolling randomly going away, and needing to use xinput incantations to fix it. I tried Hyprland with QuickShell, and after some QS-related pains, I just dropped to plain Hyprland. It's been working quite nicely so far. There was a lot of trial and error, and there's still some bits that could use improvement, but overall things just work nicely. The main sticking point for me now is that the screen-sharing and using Flameshot is a bit convoluted, and that the workspaces configuration does not support multiple external monitors (as in, the one in my office, and the one home, it needs some resetting each time I change those, or at least I haven't found the way to configure it properly as I had on i3).

So far, it has been a moderately positive change.

> the ones that like to think everything up-front before doing anything.

I don't think that's the case. If they were really thinking up-front, they'd be doing proper req analysis and design work, rather than interactively growing a ball of mud that "does the minimal thing to pass a test". To me, it seems like TDD is sold as this "foolproof" design / dev approach, which is anything but.

Not the parent poster, but I suspect he's thinking of stuff like Lighttable, or Liquid. Editors that were written in Clojure, or specifically for Clojure, and had cool features that were not available elsewhere at the time. (I'm boring myself, and pretty much only ever used Emacs with Cider)

I think it's because the playing sounds mechanical, there's very little articulation and dynamics.

It's pretty impressive engineering, yet it sounds like crappy MIDI... Doubt many people will go dropping 40K on this.

And the cost of parking... Parking your car in Hki is eye-watering

I had to specifically block those from being shown, they were all over for me. I don't have any issue with them, but my kids use my steam deck, and game on my pc, and I didn't want them seeing those.

It's the standard in most hard science fields. Also common in some humanities, too.

?

Seems like he honored his surname with his attitude :)

Mixing can work pretty well. I'm using Plasma with i3 as a WM, and it hits the perfect spot for me. Not sure if the same thing can be done on Wayland, though?

Congrats man! Just as a side note, "paras" means best, in Finnish, so that'd make you the Best Chopra!

Friends' posts are a tiny fraction of what you see on FB nowadays.

The Slack blocks format is horrendous, and not very powerful.

?

It's been a common problem with HN. I remember when NodeJS came out, it was exactly the same, and then with all the crypto-craze.

Nil punning in Clojure gives you that kind of experience, for example. Things that would break in other languages, just "work as you'd expect them" in Clojure (except when you drop down to host primitives, and then nils don't behave nicely anymore). In general, it makes for a really pleasant dev experience, I find.

I actually wrote a (not so polished) clone of that in Ruby, way back when...

Finland, for one

That only works if the workspace is on an actual screen, because it's otherwise not rendered. Maybe the virtual monitor solution via xrandr would work for that, but I haven't yet tried that.

See Babashka.

I've also used it fairly extensively, both in academia and in industry jobs (using Emacs org-mode, with several target languages, often combined). I found it very useful when thinking through a problem, and as documentation for myself later on. At some point it starts to become a bit unwieldy. Nowadays, most of my work is in Clojure, and I find that the literate workflow gets in the way of REPL-driven development, so I haven't been using it as much lately.

Overall, I'd highly recommend it.

NPS is utter bullshit, and has been thoroughly debunked, yet it's so widespread...