anti-idpol action @ pkill @programming.dev

I am working on fedi software that is hoping to allow Kodi, Plex and Popcor

---

Read more

Posts

5

Comments

360

Joined

2 yr. ago

wake me up when Rust fixes its' supply chain attacks susceptibility (solid stdlib and rejecting external crates, including transitive deps

ah great, another glowie thread

The party was meant to just be the organizer of the workers, not the ruler. The degeneration took off only after Lenin's death and the 4th Congress of the Comintern, which was dominated by Troika. that's why Mayakovsky was a devout Bolshevik until Stalinzation advanced and started scrapping several progressive conquests of October, leading to his suicide at the refusal to prop up the Stalinist degeneracy.

Also Lenin was, for instance, not a big fan of the many experimental artistic movements that flourished after the Revolution, but did not suppress them, unlike Stalin.

He also regretted banning other parties (but which was necessitated by every single one of them taking up arms against Sovnarkom) and before his death wanted to offer Trotsky a post of Commisar of Internal Affairs in a desperate bid to curtail the bureaucracy, but Trotsky, unfortunately, refused.

implying that corrupt scumbag Brezhnev was a proper communist

Notesnook ftw

https://altcha.org is nice plus a crowdsec bouncer

In Clojure, -> is used for inserting the piped argument at the head position in the arguments of whatever it is passed to, while ->> is used for inserting it at the tail. This approach is great for working with immutable data in a series of approachable transformations, which I believe is one reason why so many Domain-Specific Languages for generative programming are written in that language, aside from its interactive REPL. Additionally, there is no need to worry about excessive copying, as this is generally well optimized.

This can be particularly useful with HoneySQL, which is more of a DSL for SQL rather than a typical ORM tool. For example:

 clojure

    
(defn apply-filters [query filters]
"applies WHERE clauses to a query"
  (reduce (fn [q [column value]]
            (helpers/where q [:= column value]))
          query
          filters))

(defn build-dynamic-query [{:keys [table columns filters sort-by limit]}]
  (-> {}
      (helpers/select columns)
      (helpers/from table)
      (apply-filters filters)
      (helpers/order-by sort-by)
      (helpers/limit limit)
      sql/format))

;; Result - a super readable function call that resembles a natural language 
(build-dynamic-query 
  {:table :products 
   :columns [:id :name :price] 
   :filters {:category "electronics" :in-stock true}
   :sort-by [:price :desc]
   :limit 20})

  

Lenin was 47 in 1917

(\r (frequencies "strawberry"))

the 'I' in LLM stands for intelligence

lots of onions cut in rings as they resemble parentheses the most

death by specificity is a thing...
HTTPServletRequest has a fuckton of methods but 90% of them could be eliminated if one treated the data as a simple fucking map instead of creating 4 methods for each key in every record of your schemas.

personally I'd sum it up this way: it is usually enough to abstract two parts of your code: the repetitive stuff and the stuff that can be separated from external dependencies like db or network. That should be enough to ensure readability and that you can test it properly and not have to deal with rewriting half your codebase when you decide to change an external dependency.

Funny how he is actually now a fan of Clojure yet the examples in his book are actually full of mutating data and side effects. And Rich Hickey also stressed that tests are no silver bullet.

we had a plenty of more deterministic tools for parsing human readable text to machine-readable long before llms

tfw I recently worked on a side project where I was too lazy to change the log level but not sloppy enough to use raw printf so I'd just throw stuff into info and then remove the statements once I solved my issue