Chat Logs

  1. dreamrealtoday
  2. nevetToday is Thursday, February 12, 2026
  3. dreamrealtoday hebrew
  4. nevetToday is 25 Shevat, 5786 (Hebrew)
  5. dreamrealcalc 43*pi
  6. nevetThe result of 43*pi is: 135.0884841043611
  7. cess11supposedly it isn't full featured in the regex part, but i couldn't care less about it since my brain gets eczema from regex
  8. dreamrealjsr 52
  9. nevetjsr 52: A Standard Tag Library for JavaServer Pages (https://jcp.org/en/jsr/detail?id=52)
  10. dreamrealjsr 52
  11. nevetjsr 52 is A Standard Tag Library for JavaServer Pages. URL: https://jcp.org/en/jsr/detail?id=52
  12. Para55
  13. dreamrealand so it lives again. It's not muted for #java ... yet. When javabot's back, I'll mute it.
  14. cess11i like that it's fast compared to standard grep, quicker cadence when i'm hunting stuff in code or data files is nice
  15. ParaHmph!
  16. dreamrealPara: it has at last count ONE and exactly ONE factoid. :D And its syntax is not the same as javabot's.
  17. dreamrealcess11: I'm not arguing that MY favored tool is gooder than your'n.
  18. dreamrealjsr 52.info
  19. nevetThe factoid for jsr 52 has the following attributes: text and urls, and was last modified at 2026-02-12T14:06:36.594004Z by unknown
  20. bombhelp
  21. cess11dreamreal: i didn't take it way, i just want to know if i'm missing out on something
  22. ParaSeems the bot is helpless.
  23. dreamrealcess11: fair. I'm used to ack and it's also fast as hell, so I use it. :D
  24. dreamrealyeah, I don't have a help operation yet, and it's modular anyway so the help would be maddening to write AND parse as a reader. The web interface is also not stood up yet.
  25. BombeHuh, what does it say about me that I was not aware that grep needed a replacement?
  26. dreamrealIt doesn't need a replacement.
  27. dreamrealSo: nothing.
  28. dreamrealWhich classpath indicator is 55, btw?
  29. ParaIt's Java 11 iirc
  30. Parayeh, class file version 55 is Java 11
  31. dreamreal55
  32. dreamrealhmm
  33. dreamreal55
  34. Parastring minimum length check somewhere?
  35. dreamrealno, context
  36. lornikcess11: personally, i find it fast enough , at least sufficient for my use case. But of course it always depends on what you're trying to build
  37. lornikSo, for the ResilientRecursiveDirectoryScanner, I've decided to use Files.walkFileTree. here , I Can apparently handle file changes well, unlike with Files.walk..
  38. dreamreal69
  39. nevet69 is the Java classfile format number for Java 25. Nice.
  40. dreamrealI forgot: the factoid set process isn't "foo is bar", it's "foo=bar"
  41. ChronosBeing the product of two primes is kind of fun too :)
  42. dreamreal69=<reply>69 is the Java classfile format number for Java 25. Nice! ... and being the product of two prines is neat, too.
  43. nevetok, dreamreal: updated 69.
  44. dreamreal69=<reply>69 is the Java classfile format number for Java 25. Nice! ... and being the product of two primes is neat, too.
  45. nevetok, dreamreal: updated 69.
  46. Chronosdreamreal++
  47. nevetdreamreal now has karma of 1.
  48. dreamrealdamn it
  49. Chronoshahahaha :)
  50. Chronosdreamreal: You don't want any karma?
  51. dreamrealchronos++
  52. nevetchronos now has karma of 1.
  53. dreamrealkarma chronos
  54. nevetchronos has karma of 1.
  55. dreamrealdreamreal++
  56. dreamrealperf.
  57. dreamrealsbt--
  58. nevetsbt now has karma of -1.
  59. dreamrealfoo is bar
  60. nevetok, dreamreal: updated foo.
  61. dreamrealfoo=baz
  62. nevetok, dreamreal: updated foo.
  63. dreamrealfoo
  64. nevetfoo is baz.
  65. dreamrealfoo.url is https://foo.bar.com/
  66. nevetok, dreamreal: updated foo.
  67. dreamrealfoo
  68. nevetfoo is baz. URL: https://foo.bar.com/
  69. dreamrealfoo.forget
  70. nevetok, forgot foo.
  71. Swayzethis spam
  72. dreamrealIt is SPAM, but I'm testing stuff out, and, well...
  73. dreamrealbattlepope: damn it, top and bottom karma is COMPLEX
  74. dreamrealbut I'll have it soon :D
  75. dreamreal(it's complex because karma isn't calculated in nevet like it is in javabot: javabot just keeps track of a simple score. nevet keeps track of the *operations* which lose value over time: a single "--" from four months ago isn't as weighty as a single "--" today.)
  76. dreamrealChronos: ++
  77. nevetChronos now has karma of 2.
  78. dreamrealnoice!
  79. Chronoskarma teckla
  80. nevetteckla has no karma data.
  81. dreamrealChronos: -- look, you ain't all that, dude
  82. nevetChronos now has karma of 1.
  83. * Chronos chuckles.
  84. dreamrealtesting the autocomplete compatibility with the comment field
  85. dreamrealthe comments are discarded but hey
  86. dreamrealcheeser: javabot's MIA again; I have nevet running and unmuted but I'll mute it as soon as javabot's back
  87. dreamreal55
  88. nevet55 is the Java classfile format number for Java 11.
  89. dreamrealokay, excellent, it's muted here now.
  90. cheeserit's getting weird account registration errors
  91. dreamrealWhat is?
  92. dreamrealnevet?
  93. cheeser~ping
  94. javabotWatch where you're sticking that thing!
  95. cheeser javabot, of course. i don't know anything about nevet.
  96. dreamrealjust clarifying, I wanted to make sure nevet wasn't creating an issue with javabot
  97. Para~nevet
  98. javabotPara, what does that even *mean*?
  99. dreamrealnevet's muted here now. We have a bot; nevet is not a replacement for it.
  100. dreamrealnevet's trigger character is ! in any event, to prevent collision with javabot should they both be unmuted.
  101. ParaI was kinda hoping the reply would
  102. Paragah
  103. Parawould've been "Doesn't look like anything to me." or somesuch.
  104. ChronosI feel like / is the best trigger character, since it's the hardest to typo in most IRC clients
  105. dreamreal~nevet is <reply>nevet is like a flowing stream, a beautiful stream that flows and stuff like that.
  106. javabotOK, dreamreal.
  107. dreamrealokay, top karma and bottom karma operations implemented. "!top 5 karma" will give you the top five, !top 2 karma will give you the top two, etc.
  108. dreamrealvery expensive operation if you have a large community with a lot of operations, but eh, threads am I right
  109. dreamrealChronos: and you're right, / would be a good trigger EXCEPT that it's hard to type. So is ! compared to ~, but being actively difficult to invoke is an antipattern
  110. ChronosIf $WORK is any indication, "just throw more threads at it" is the solution to *everything*
  111. Chronosdreamreal: Is it hard to type on your client? It's easy on mine.
  112. dreamrealWell, in this case, it's a deliberate choice: there are ways to allay it (calculate the karma at midnight for everyone, apply deltas to that to get the current karma, etc) but eh
  113. dreamrealit's not hard to type but it just feels unnatural to hit // to start a line
  114. dreamreal/test
  115. Chronos/test
  116. Chronos/test
  117. ChronosOh, I had no idea you could do //. I've been doing / /.
  118. ChronosTIL. Thanks, dreamreal.
  119. dreamrealOf course!
  120. dreamrealIt makes my day complete to feel like I helped someone learn something effectively useless for their irc client.
  121. Chronoshahahaha
  122. DoofusCanadensishooray!
  123. ptomliI have decided I can have a celebratory glass of old grape juice ๐ŸŽ‰ I have managed to coax that rando serial port into submission and am speaking to the inverter at the other end of the line โšก
  124. dreamrealptomli: woot! embedded with java is fun, eh
  125. dreamrealWhat created the java constraint?
  126. ptomlinot sure, it was in place when I arrived. this is just me playing at home, but it's $work adjacent
  127. p14nd4does anyone know where the behavior for allowed values of jakarta.persistence.schema-generation.database.action is specified (e.g., 'create', 'drop-and-create')? i can't find it in the JPA 3.2 spec: https://jakarta.ee/specifications/persistence/3.2/jakarta-persistence-spec-3.2 , only the names of the values
  128. p14nd4hibernate has a little commentary on this [ https://docs.hibernate.org/orm/7.2/javadocs/org/hibernate/tool/schema/Action.html ]: "There is an ambiguity surrounding the value "create" here. The old-school Hibernate configuration interprets this as the action CREATE, which drops the schema before recreating it. The JPA standard interprets it to mean the action CREATE_ONLY which does not first drop the schema."
  129. p14nd4...which suggests to me that there _is_ additional definition of this behavior somewhere in the JPA spec, i just can't find it
  130. ptomliI think it's there, just in the whitespace between the words
  131. ptomlihttps://jakarta.ee/specifications/persistence/3.2/jakarta-persistence-spec-3.2#_schemamanager_
  132. ptomli"If a DDL operation fails, the behavior is undefined. A provider may throw an exception, or it may ignore the problem and continue." fits the Hibernate language
  133. ptomlimore specifically, at the same method "attempt to create the schema, otherwise, assume the schemas already exist"
  134. dreamrealp14nd4: I'm not even sure the spec *does* say what the options are for a given provider. Hold on.
  135. ptomliI think, in my experience, that sometimes the specs are written in such a way that they make sense once you know them already. Typical documentation style, not really useful to learn the thing, but great to reinforce your understanding once you're on the other side
  136. dreamrealhttps://jakarta.ee/specifications/persistence/3.2/jakarta-persistence-spec-3.2#a12384
  137. dreamreal`none, create, drop-and-create, drop, validate`
  138. dreamrealA given provider can add more to these, as hibernate does.
  139. ptomliyeah, but as he says, that's not exactly clear about what create means. the appendix has a little more info, but not too much to be honest
  140. p14nd4yeah, i saw those allowed values -- was looking to have them defined. ptomli's link is close -- presumably create, drop, and validate are supposed to map to those interface methods
  141. nevetyeah, i saw those allowed values -- was looking to have them defined. ptomli's link is close now has karma of -1.
  142. dreamrealI don't think the spec can even really say "this is what SHALL happen" -- to many cooks in that particular kitchen.
  143. nevetI don't think the spec can even really say "this is what SHALL happen" now has karma of -1.
  144. dreamrealp14nd4: which provider are you using?
  145. p14nd4but it doesn't explicitly say that's the case, and doesn't ever seem to actually define 'drop-and-create', since that doesn't have a corresponding SchemaManager method
  146. ptomlithe details are usually in the appendix, marketing don't go reading that stuff too much
  147. ptomlidrop-and-create isn't in the spec
  148. ptomlidoh.. sorry, it is
  149. * dreamreal points to the spec he quoted
  150. ptomliyeah yeah, sorry, i point to my consumption of old grape juice
  151. dreamrealof course, that's 2.2, I think
  152. p14nd4dreamreal: i'm using hibernate in my reference implementation, but theoretically customers could use others
  153. ptomliso, if there's a specific "drop-and-create" then it's fair to assume that Hibernate thinking "create" means "drop-and-create" is... unexpected
  154. ptomliperhaps the very existence of the "drop-and-create" option is the uncertainty that Hibernate docs are hinting at
  155. dreamrealyeah, hibernate treats ITS update and create as separate types. I think it'd comply with the persistence.xml definitions, though.
  156. dreamrealhbm2ddl.auto != the schema generation property
  157. p14nd4without looking at the code, it seems to me that hibernate interprets values of jakarta.persistence.schema-generation.database.action and hibernate.hbm2ddl.auto the same, just giving precedence to the former, in case both are present
  158. ptomlibut, if you're worried about customers using a provider which has particular effects regarding this, I would expect that (1) they're aware of the details, (2) pointing out the possible confusion should be sufficient, (3) trying hard to not delete customer data is a good step
  159. dreamrealp14nd4: I would VERIFY that, if I were you
  160. dreamrealI don't have any jpa persistence units lurking about or I'd try it
  161. ptomliwe use eclipselink and I'm certain I wouldn't want "create" or anything like that anywhere near production ๐Ÿ˜†
  162. p14nd4ptomli: agreed
  163. dreamrealptomli: hahaha, yes
  164. p14nd4this is mostly a curiosity as i was reading
  165. dreamrealI use validate all the time but not create or update any more
  166. ptomliif (System.getProperty("jakarta.persistence.schema-generation.database.action").contains("create")) { System.exit(911); }\
  167. jbosmansnothing wrong with update, as long as it's used by people that 1) understand what it does 2) understand what it doesn't do 3) make sure the whole of it keeps working
  168. jbosmansin other words if all db changes are thoroughly tested before release, who cares who they're executed (and/or which pre/post actions are needed)
  169. jbosmansmy 2รง :')
  170. dreamrealI care. I want management and rollback capability, and migrations aren't done solely by altering a schema.
  171. dreamrealschema is composed of more than table structure, after all.
  172. jbosmansi like to be able to generate db schema's from code (when that's an option)
  173. p14nd4also, 'update' isn't a JPA-standard schema-generation action, if you care about such a thing
  174. dreamrealSure, nothing prevents you from doing that
  175. jbosmansi have tools to compare schema's etc
  176. dreamrealhell, that's what I do for initial schema generation: build a table model in entities, tell hibernate to generate it to a script, use that as an initial migration
  177. jbosmansexactly
  178. ptomlicode and data are too tightly coupled, farting around with one means farting around with another. it's unreasonable to think that "the tooling" will manage the migration, or the rollback when it goes nipples north
  179. dreamreal... then turn it from create to validate :D
  180. jbosmanstoo much work given i know i don't need it, tradeoffs
  181. jbosmansrigorously tested btw before release ^
  182. dreamrealThat's fine if you know you don't need it
  183. cheeseryou plebs with your schemas. adorable.
  184. jbosmansall we need is TEXT
  185. jbosmansand jackson
  186. dreamrealcheeser: ++
  187. nevetcheeser now has karma of 1.
  188. ptomlioh wait, a nosql has entered the chat
  189. jbosmans:P
  190. dreamrealptomli: totally fair, though. SQL is what you want when you're okay with taking forever to access your data. :D
  191. ptomliI think, though I might be wrong, that most of the "you don't need relations" stuff we see these days, is entirely because we have more compute than we know what to do with
  192. jbosmansdreamreal, i violated your rule in a way that avoids me to create 10ish tables to fetch data for a few very related use cases that always require all data
  193. jbosmans"if one part of the data changes, all related data changes"
  194. jbosmansptomli, i use relations very strictly 99+% of the time
  195. dreamrealptomli: I don't think so
  196. jbosmansi prefer error to faulty data
  197. dreamrealnosql can have relational models
  198. ptomliit all comes down to one group of people thinking "you don't know how you will need to query this" and the other group saying "I know how I will query this". one group is old, the other isn't
  199. dreamrealwhy are you limiting yourself to "nosql = a hash table of json"?
  200. dreamrealRedis is NOT THE ONLY MODEL OUT THERE
  201. jbosmanspick & choose ftw
  202. dreamrealand it's not even a very good example of that model
  203. ParaDocument DBs have all the indices, relations, transactions and all that jazz as well.
  204. dreamrealIMDGs too
  205. jbosmansgraph dbs same
  206. jbosmansimho least PITA = RDBM
  207. jbosmansexcept when not
  208. dreamrealand an IMDG will take a document db to the woodshed, beat it raw, slather it with butter, and draw rude things on its forehead before a document DB even realizes an IMDG has entered the room. And by the time a document db scrapes the rudeness of its forehead, an RDMS is going "hey, look, something happened"
  209. jbosmansin which case good to have "escape hatches" (to put it into react terminology?)
  210. ptomliI think people who *choose* a graph DB know enough to understand the tradeoffs, those that drift towards the document db are those that just don't want to deal with the underlying limits. In general. Vague handwaving. Don't moan at me
  211. ParaMy favorite thing about postgres is that you can do relational data perfectly with it and then all the other types as well and when you finally hit a wall, you can migrate that part to something more specific.
  212. jbosmansPara, well put
  213. * dreamreal shrugs in IMDG. Except sssssslllloooooowwwwwwwwwllllyyyyy so you guys can notice it.
  214. dreamrealpara isn't wrong, though
  215. dreamreal~para++
  216. nevet~para now has karma of 1.
  217. javabotpara has a karma level of 24, dreamreal
  218. dreamrealpostgres is a good baseline. Still slow, but quite reliable and quite capable.
  219. dreamrealaight, I'm off.
  220. ptomlicapability > speed
  221. ptomlican do, eventually is more important than can't do
  222. NeXeNthe speed at which it does what it does is more important than the speed at which something else doesn't
  223. jbosmansagree ptomli
  224. jbosmanswell, depending on what matters for the business
  225. ParaI haven't hit a performance wall with postgres in...hm. Almost a decade? Although that speaks more about the systems I usually do than the db itself.
  226. NeXeNthere's performance limitations to any thing designed
  227. ptomliwoooo, i'm not pasying postgres is slow, i'm saying havingn a tool that does the job is nore important than ... well, anything
  228. ptomlipasying... damn
  229. NeXeNbut the DB ultimately will be the first bottleneck
  230. jbosmansptomli, generally speaking, which DBs would you prefer?
  231. jbosmans(purely out of interest)
  232. ptomlii'm quite partial to sqlite, because it working in my realm
  233. ParaI once lived a life where ingress traffic link was the bottleneck. We saturated parts of a specific data center.
  234. jbosmansptomli, your realm being?
  235. dreamrealPara: have you ever gotten it to respond in < 2ms?
  236. jbosmansPara, wow :)
  237. ptomlii work in energy management, so inverters, batteries, local management. it's not about distributed data, it's about local data
  238. Parajbosmans: In fairness, this was 14 years ago. It was "easier" in a sense back then :) Now everyone has 25 gig links at minimum.
  239. dreamrealI mean, dow jones had < 0.2ms granularity for distributed transactions
  240. jbosmansPara, i year you :-D
  241. Square2What is the minimal boilerplate / manual charade coding approach to exposing spring server methods to a react frontend. Sure it's REST, but how to avoid the tedium of replicating server model object and hand coding invocation logic?
  242. jbosmans<2ms is always attainable, given proper time to do all the work
  243. dreamrealand 2ms is still pretty damn slow
  244. ParaThat would be an interesting test to figure out.
  245. jbosmansmoney performance quality, choose two (iirc)
  246. NeXeNSquare2: sounds like a good project. probably hundreds of docker containers out there, even in the hardened line, that probably could get you from 0 to 60 in a few seconds
  247. dreamrealI've never seen MY servers go under 3ms for roundtrip from postgres; I don't think I tune it especially well, though. But I haven't seen anyone else get a lot better.
  248. Square2NeXeN, how is docker images helping here?
  249. DoofusCanadensis0.2ms is fiiiiine
  250. jbosmansdreamreal, i'd say, how many tables with how many changes over how many years ?
  251. NeXeNSquare2: to eliminate the tedium
  252. dreamrealjbosmans: in an IMDG? :D
  253. NeXeNto get the boilerplate out the way. there's already initalizr which is on fleek
  254. dreamreal"How many wings does your roof have? How many blades of grass does your bottle of paint contain?"
  255. jbosmansi've made a fool of myself? :)
  256. dreamrealyou're asking the wrong questions, in other words
  257. jbosmansyeah i was thinking of an RDBMS
  258. Square2NeXeN, I mean that if I have a set of server side services, how do I get them available in React with least amount of effort?
  259. NeXeNtRPC usually
  260. ptomlidepends on definition of effort, though "consultants" is a good start
  261. jbosmansptomli, same for me regarding local data, but evolving requirement-wise and quantity-wise
  262. NeXeNnext you can use react server components
  263. ParaGave it a thought, I think the fastest DB to respond I've ever worked with was Riak once one of my colleagues fixed its abysmal Java driver.
  264. jbosmansNeXeN, never
  265. jbosmans:P
  266. NeXeNs/next/nextjs/
  267. ParaI don't remember the exact numbers but the fix was in order of hundreds/thousands times faster.
  268. ParaOf course Riak really is just a distributed hashmap after all the fancy vector clock stuff soooo
  269. NeXeNPara: well lmdb is fast and acid
  270. ptomlijbosmans: yeah, my line of work is odd, but not interesting. I'd like to skip the weird mysql db we have to data and move to quest, but we have installed base, and that means effort.
  271. Square2NeXeN, as I see it, the information is there to autogenerate all of this.
  272. ptomliChanging stuff after the fact is just a pain
  273. jbosmansptomli, it always is
  274. jbosmansmaking those changes might make life better tho, for many involved stakeholders?
  275. jbosmansin my experience, the pain increases over time
  276. jbosmansusually it ends up at "someone needs to make a business case"
  277. jbosmansthis will cost you $$$$$ unless adressed NOW
  278. ptomli20k installed devices, a few GW power generation between them, not hard to think about, but mess that up, things burn
  279. NeXeNSquare2: i'm just fooling with you :^)
  280. jbosmansso that's important, which is good/great
  281. ptomliyes, we look to fix things, but you have to pick your battles
  282. jbosmansptomli, yeah totally, not easy with 20k "clients"
  283. jbosmans"not easy" being the understatement :)
  284. ptomlimeh, clients is a bad word for it
  285. jbosmansconsumers?
  286. jbosmansusers?
  287. jbosmansit all depends on context/language/point of view
  288. NeXeNSquare2: vaadin hilla might interest you for least amount of effort
  289. jbosmans"from a certain point of view" as they said in some star wards
  290. jbosmans*wars
  291. ptomliwe sell batteries, and 40ft containers with batteries and inverters. You can fit a lot of MWh into a 40ft container, and a couple of MW inverters on the side of them makes you think twice about "just send it"
  292. jbosmansptomli, wow yeah, "consequences"
  293. ptomliwell, i was trying to figure out an energy meter today, because a hospital kept tripping over onto grid power. it's technically not fancy, but the outcomes are important
  294. jbosmanslike hardware integration?
  295. jbosmansas i understand it, it is technically fancy ^
  296. ParaTransformer maintenance videos on Youtube have that special wtf aura. People wearing weird rubber suits, backup person with a long pole and a hook ready to pull the other guy away...
  297. ptomliyeah, modbus, canbus, serial232 when needed, whatever the site has/needs to make it happen. we have plumbing code to handle water works at damns, it's all just numbers really
  298. ParaElectricity in general is wild, from the very physical and hands-on to...well, just managing it, software etc.
  299. ParaI'm kinda jealous of your work :)
  300. jbosmansdamns or dams? sorry could not resist :)
  301. jbosmansactually i may be wrong there, english is like my third language at best
  302. ptomliwe 3d print covers for the high voltage battery connects. my introduction to the company was writing integration to a 125kW inverter. "Just turn it on" :-)
  303. ptomlidams :(
  304. ParaDid you look up to see how many covers were embedded into the roof already?
  305. NeXeNi wonder how many batteries one could put in a container and still keep cool. how many times could i charge my scooter? hrmm a few million cycles?
  306. jbosmansno worries, it was sort of funny in context
  307. ptomliwe have aircon units installed at the end of the containerss
  308. jbosmansfwiw clearly important work, which is nice
  309. ParaNeXeN: Isn't heat more of a function of (dis)charge rate? Not that I know anything, really.
  310. ptomliit is nice work, i'm not saying it's not
  311. NeXeNi guess, i only expect if heat got too high then it would set off a chain reaction of some sort
  312. ptomliit happens both ways. charge/discharge both add to the energy waste, which is heat
  313. ParaThere was just a news article the other day that in silence a French company had built about 500 MW worth of container batteries all over Finland in a year.
  314. NeXeNmaybe one could actually use those contact cooling rails like in the milspec stuff and need no air circulation
  315. ParaIt was kinda like...that's cool but who ordered them?
  316. ptomlicontainers have burnt... :sad face:
  317. NeXeNprobably electrical services, who have to balance out their production and the amount of usage, it would be highly valuable in arbitrage
  318. ParaHere's a picture, "container" is more of a suggestion at this point https://images.sanoma-sndp.fi/38ec2e4e79e4bf2ca8ee19a36ea45095/normal/1920.avif
  319. NeXeNi actually want a nuclear battery. one that'll run for 11k years down to halfway
  320. ptomlinot one of ours, but basically the same
  321. NeXeNjust have it in my back yard.....yeah never pay for power again
  322. ParaNeXeN: RTG, Radioisotope Thermal Generator
  323. ptomlithat one has doors to put in/replace cells from the side, we have a central corridor. but in the end there's a limit to the Wh you can store in a 40ft
  324. NeXeNi could also give the neighbors free power, who cares
  325. Paraof course my energy pipedream would include one of these for every ~10k people community https://polarnightenergy.com/
  326. nevetPara mentioned url: https://polarnightenergy.com/ ("Polar Night Energy")
  327. NeXeNPara: interesting, but heat exchange loses a lot of power, but the arbitrage saves the costs
  328. ptomliPara: in the EU, the users for storage are often market movers. You can download the next 24h of market prices from ENTSOE, so if you have storage (regardless of PV) you can margin the market. We have lots of customers who simply time-shift energy for what is essentially residential markets. Buy cheap, put in battery, sell high. I've even added
  329. ptomlicode recently to manage predictions of load vs PV vs market pricing, so the "system" just figures it out for you, and those fancy buggers can just go chill on their yachts in the Med. I do question my life choices
  330. Paraptomli: Yeah, the whole offsetting is really the thing that everyone seems to be focusing on now.
  331. ParaWhich is great, as the amount of renewable energy we could harvest during summers could offset most of winter's energy needs, there's just the pesky problem of storing it somehow.
  332. Para(plus we also have that one neighbour so all forms of added resilience is also a big plus)
  333. ptomliI'm not sure it's a bad thing, in general, but the people doing it are making a total killing. I keep feeling like I'm just "helping them along", and I should have though of this myself years ago
  334. ptomliCATL have sodium in production now, I suspect it'll change things in the next few years
  335. ParaCorrosive superheated liquid :)
  336. ParaOf course as kids we used to stare at particle accelerators for entertainment, so science is stuff and such.
  337. ptomliI'm trying to figure out where you ares, Sweden? I think you're a bit closer to our next best friend than I am (South Africa)
  338. ParaFinland
  339. ptomlioo, I like
  340. ParaYou know, the Internet, there's always a Finn somewhere.
  341. ptomliI used to work for a Danish company, I enjoyed my time up there
  342. * ptomli apologises to all the people wondering "what the hell has this to do with Java"
  343. NeXeNi'm sure they have java installed on one of their machines
  344. ptomli๐Ÿ˜†
  345. ParaTatu Suoranta is Finnish and he created Jackson.
  346. Para(I think he lives abroad though)
  347. ptomliSo I can blame him for the Jackson 3 changes?
  348. ParaSorry, Saloranta
  349. Parahttps://cowtowncoder.medium.com/why-upgrade-to-jackson-3-0-94c30e797bf2
  350. ParaI think he's heard the question.
  351. ptomliI don't think there's more than 1 or 2 java devs that can do anything than thank him for his input
  352. ptomli'd not seen that before, thanks
  353. ptomliI'd not seen that before, thanks
  354. ptomliSo, things like "Automatic subtype detection", sounds lovely. But I need to see how that works in practice, because I don't want it randomly trying to class-scan on a Allwinner H616 reading from an CD card. ๐Ÿคท
  355. ChronosPara: My favorite OS is FinnOS!
  356. Chronos(I think most people call it Linux)
  357. jbosmansleenooks
  358. ParaYeah well.
  359. ParaIt's kinda funny how the whole software chain for being able to chat in real time originates from Finland. Linux, SSH, IRC, irssi.
  360. ChronosThis will age me, but I was chatting online in 1979, which predates all those technologies by a little bit.
  361. ChronosChatting online real time.
  362. jbosmanscrazy
  363. jbosmansdarpa?
  364. ParaOf course we've done more modern stuff. NVIDIA's core research which led to tensor cores was also done by a few Finns.
  365. Chronosjbosmans: Not DARPA, but other online entities, like MECC and bulletin board systems.
  366. jbosmansChronos, what kind of protocols?
  367. ParaChronos: So you're one of the increasingly few people who know why lowercase usernames implied terminal features and also why email has always and always will be a pita to route.
  368. Para+been
  369. jbosmansunless MECC was/is a protocol
  370. jbosmansi'm guessing not BBS etc?
  371. Chronosjbosmans: When I started? It was old school analog modem stuff -- ASCII in and ASCII out.
  372. nevetjbosmans: When I started? It was old school analog modem stuff now has karma of -1.
  373. NeXeNSquare2: jhipster is also worth mentioning, i googled it earlier and thought it was neat
  374. ChronosEven more basic than Telnet.
  375. ChronosPara: haha yep :)
  376. jbosmansChronos, lucky you :)
  377. ChronosBeing old both sucks *and* has its advantages!
  378. jbosmans"everyone wants to get old, no-one wants to be old"
  379. Chronosjbosmans: Oh, MECC was the Minnesota Educational Computing Consortium (later Corporation). They had CDC (Control Data Corporation) Cybers with banks of modems you could dial into.
  380. jbosmansi refuse to be sorry i'm not dead already :P
  381. ChronosAnd people had written chat programs so you could dial in and talk in real time.
  382. jbosmansi love that
  383. jbosmansway ahead of my time
  384. jbosmansi just captured network traffic to fetch credentials to get more capacity on my school's network
  385. Square2NeXeN, Hmm.. just changed computer here. If you mentioned other libraries before jhipster can I bother you to repeat them? Fear I'm missing scrollback
  386. jbosmans"once upon a time", approaching 25 yrs ago
  387. ChronosA lot of people don't know just how much stuff was invented way way WAY earlier than they think. In 1979 we had email and Reddit-like discussion forums real-time chat and the whole works!
  388. NeXeNi have not tried it it just looked neat. i did some stuff with vaadin a while back but it seems to be newer versions, might be cool
  389. jbosmansi remember my connection dropping when someone called in or out
  390. Chronosjbosmans: haha that's awesome. I would write programs and trick people into running them. The program made it appear as if they got logged out and a new login prompt would appear. I would capture their user names and passwords and store them in files.
  391. jbosmanshaha awesome
  392. jbosmansi was btw quite considerate of who etc, we lived together
  393. jbosmansit was "unused bandwith"
  394. jbosmans*"bandwith"
  395. jbosmansiirc ARP poisoning, way back when
  396. ChronosOh my goodness, I thought I was in a different channel, my apologies to everyone for the off topic stuff
  397. jbosmans&& likewise (?) :-)
  398. jbosmansjava is 30+ now so
  399. jbosmansit least we're not talking about: "Anthropic Raises $30 Billion at $380 Billion Valuation, Eyes IPO This Year"
  400. jbosmansat*
  401. ChronosHeh, indeed :)
  402. NeXeNonly 10x plus tax?
  403. jbosmansno worries, it'll al work out just fine
  404. jbosmansgrmbl, *all
  405. jbosmansfwiw i think we're still all good
  406. jbosmansassuming we all care and invest in our craft
  407. jbosmanswe'll see who maintains the generated codebases over time :')
  408. jbosmansaddendum: "Anthropic claims more than 500 customers spending over $1 million a year on its workplace tools."
  409. jbosmansthey must all be spending "a lot"
  410. jbosmansnite nite