dreamrealmaven is a build tool for many languages, but focusing particularly on JVM languages; it prefers convention over configuration and is horribly stable and the build files tend to be horribly verbose. If you need it to work, this is your tool.
dreamrealgradle is a build tool for many languages; it uses a Groovy or Kotlin DSL, and provides a configurable as well as a conventional build model. It's very terse but can be absolutely maddening if you color outside the lines at all.
dreamrealant is one of the oldest Java build tools, generally supplanting make for Java; XML-based and fully imperative, it does exactly what you tell it and nothing more, which means dependency management is your problem (see: Ivy). New projects should use something else.
dreamrealmill is a Scala-based build tool with a cleaner composability model than Gradle and genuine modularity baked in from the start. Requires comfort with Scala concepts, but rewards that investment with a build system that mostly behaves like it should. But then: Scala.
dreamrealbld is a build tool where build logic is written in pure Java — no Groovy, no Kotlin, no Scala, no XML. If you already know Java, you already know how to write your build. Part of the RIFE2 ecosystem.
dreamrealamper is JetBrains' experimental YAML-configured build tool, currently in preview and aimed primarily at Kotlin and Kotlin Multiplatform projects. Opinionated in ways that will either feel liberating or confining depending on whether your project fits the mold. Not yet ready for general production use.
dreamrealsavant is a Groovy DSL build tool with a plugin-as-dependency model and explicit per-machine JDK configuration. New enough that its differentiating value over Gradle, Mill, Amper, and Bld is not yet clear. Documentation was incomplete at launch. Worth watching; too early to recommend.
dreamrealivy is Apache Ant's dependency manager, bolted on to give Ant what it was missing. If you're reaching for Ivy you're probably already committed to an Ant build that you can't escape. Consider this a sign.
dreamrealrife2 is a full-stack Java web framework descended from the original RIFE framework, built around minimizing boilerplate and keeping everything in plain Java. Also the home of bld. Opinionated, coherent, and focused on a continuations model.
nevetbld is a build tool where build logic is written in pure Java — no Groovy, no Kotlin, no Scala, no XML. If you already know Java, you already know how to write your build. Part of the RIFE2 ecosystem. URL: https://rife2.com/bld Tags: build tool, java, and jvm
dreamrealgot frustrated that I didn't fix factoid syntax the way he wanted
dreamreal"foo is bar" -- YOU CAN'T DO THAT! IS IS EVERYWHERE!
dreamrealdecided that was a breaking point for him, that the responses weren't conciliatory as he wanted
dreamrealinfobots haven't existed for 40 years and a' that
dreamrealblue is good people but has a relatively low open and agreeable personality from what I've seen
dreamrealHe has good ideas and purposes, but he's easily frustrated when he doesn't get his way
dreamrealso for factoids, he wants a prefix: !factoid foo etc., which is NOT a bad idea, honestly
dreamrealbut the problem is that infobots HAVE existed since IRC was a thing
ChronosOh, hmmm, that's too bad, he was interesting.
dreamrealhe is, I'm trying to convince him the world doesn't have to dance to his tune
dreamrealSo what do YOU think? How do YOU see working with the bot?
ChronosI haven't really been paying too much attention; life keeping me too busy and distracted
dreamrealcertainly understandable
ChronosFrom what I see above, though, looks quite good
dreamrealwell, there're two different possibilities: he wants operations to be scoped for clarity, but that's not how infobots typically work, since they're supposed to be human-ish
dreamreallike, if you have to EXPLICITLY invoke karma, that's a lot; the "ideal infobot" doesn't use a trigger at all, it just infers proper usage, but that gets noisy FAST if it's populated well
dreamrealso a light trigger with human-centric operation is the ideal, depending
dreamrealmcp is the Model Context Protocol — an open standard by Anthropic for connecting AI models to external tools and data sources via a structured client/server interface.
dreamrealmcp is the Model Context Protocol - an open standard by Anthropic for connecting AI models to external tools and data sources via a structured client/server interface.
neveta poem: Morning light spills through the door,/A smile, a wave, nothing more—/Yet in that simple, sweet hello,/Two souls meet and gently glow.
dreamreala poem: Morning light spills through the door,/A smile, a wave, nothing more—/Yet in that simple, sweet hello,/Two souls meet and gently glow.
nevetAnalysis: This poem follows an AABB rhyme scheme with iambic tetrameter (four iambic feet per line). It's a quatrain, a four-line stanza, exploring the intimate connection found in a brief greeting. The regular meter and rhyme create a gentle, harmonious tone matching the tender subject matter.
dreamrealtamboui
nevettamboui is a Java TUI framework inspired by Rust's ratatui; offers immediate-mode rendering, a managed event loop, and a declarative DSL. GraalVM native compatible. Snapshot only; APIs unstable. URL: https://tamboui.dev/ Tag: consoleio See also: lanterna, jexer, textio, and zircon
dreamrealmaven
nevetmaven is a build tool for many languages, but focusing particularly on JVM languages; it prefers convention over configuration and is horribly stable and the build files tend to be horribly verbose. If you need it to work, this is your tool. URL: https://maven.apache.org Tags: build tool, xml, and jvm
dreamrealno help, unfortunately, because the resultset is too big
dreamrealthere're probably 40 operations
jbosmansoh right
dreamrealtoday
nevetToday is Monday, March 23, 2026
dreamrealversion
nevetnevet 1.0 | 544314f (main) | Built 2026-03-23 13:02:19 EDT
jbosmansbotwise could be useful
dreamrealwhat do you mean?
jbosmansencouraging adoption
jbosmanssorta like "cmd --help" etc
dreamrealoh, yeah
jbosmansmaybe response as PM ?
jbosmansif feasible ^
dreamrealwell, I have a parser in place, so adding such things is more doable than it was: PM is rough because IRC is easy to overwhelm
jbosmansspring shell ?
jbosmansalthough that's kinda .. not there yet i guess
dreamrealthe bot is not really a shell application
dreamrealit has a console but it's pretty simple, you wouldn't use it for more than bootstrapping
jbosmanswell it kinda could be
dreamrealyou wouldn't RUN THE SYSTEM to add a factoid, you'd run the system to set up ingress where you could set factoids
jbosmansinput -> output
dreamrealsure
dreamrealbut it's a big system: you wouldn't ... well, what I just said
dreamrealyou *could* but why
jbosmansyeah no i understand
dreamrealif it stopped once you added a factoid, why did you add a factoid: you'd want to provide access
jbosmansthat'd depend on the command implementation i guess
jbosmansi was just wondering how to get an overview of what i can do with nevet
jbosmansirc-wise it's usually !help or a PM !help or ..
dreamrealyeah, I know, it's a problem
jbosmanslike ChanServ let's say
jbosmansnah it's not a problem
dreamrealI don't have a good solution yet. Chanserv has access a bot like nevet does not.
jbosmansRome wasn't built in a day :)
dreamrealChanserv *cannot flood itself* off of irc.
dreamrealnevet can, and trivially so.
jbosmans"a simple Stream.limit()"
jbosmansfamous last words ^ :)
dreamrealyeah.
dreamrealIt's not been unthought of.
jbosmansi don't doubt it
jbosmansis there a webpage or alike?
jbosmanspoem hamburger
neveta poem: Sizzle and smoke, the patty sings,/Between soft buns, joy it brings./Lettuce crisp and pickles tart,/This simple stack—a work of art.
a poem: Sizzle and smoke, the patty sings,/Between soft buns, joy it brings./Lettuce crisp and pickles tart,/This simple stack—a work of art.
nevetAnalysis: This poem is written in iambic tetrameter with an AABB rhyme scheme (couplets). It's a quatrain, a four-line stanza form. The regular meter and simple rhyme structure create a light, playful tone befitting its subject matter—a hamburger.
jbosmanshaha great
dreamrealbytecode.news!
dreamrealThat's the website! It's driven BY nevet. It's all one application.
dreamrealthis codebase and the data repository is NOT old
jbosmans:D
dreamrealspring is Java application framework providing a DI container and vast ecosystem of modules. Foundation for Spring Boot, Spring Security, Spring Data, Spring Integration, and more.
dreamrealspring is a Java application framework providing a DI container and vast ecosystem of modules. Foundation for Spring Boot, Spring Security, Spring Data, Spring Integration, and more.
dreamrealspring boot is an opinionated convention-over-configuration layer on Spring. Auto-configuration, embedded servers, starter dependencies. De facto standard for Java microservices and web apps.
dreamrealquarkus is a Kubernetes-native Java framework from Red Hat. GraalVM native-first, fast startup, low memory. CDI-based with MicroProfile support. Designed for containers and serverless.
dreamrealmicronaut is a JVM framework from Object Computing targeting fast startup and low memory without GraalVM required. Compile-time DI and AOP — no reflection at runtime. Supports Java, Kotlin, and Groovy.
dreamrealRight, that's what I'm talking about: like, if it has a url property, make the link active, and if it has a text property, maybe include some of it
dreamrealit's not static, but yeah
jbosmansit's not ?
dreamrealALL of bytecode.news is generated
dreamrealdynamically
dreamrealeven the features at the bottom
jbosmanson every request ? :s
jbosmansi mean
dreamrealit's controlled by api.bytecode.news/features
jbosmanslike, not by an llm i hope ?
dreamrealit's not by an LLM, no
dreamrealit's a REST backend
jbosmansyeah so that's standard
dreamrealthe front end queries the backend for what to render and how
jbosmans(i'd say)
dreamrealwell, there's also an SSR - reference.bytecode.news is an SSR representation
jbosmansyou could put a caching thing in front of that
dreamrealThat's sort of what happens
dreamrealyou see how fast it renders
dreamrealit actually tracks updates so the actual webapp has "live data" and it caches what is relatively constant
jbosmansyeah it does
jbosmansand i noticed because i (think i try to) make the same effort for same reasons in my projects