Chat Logs

  1. NeXeNi love backported stories, they get all the details right, ...or wait do they get them wrong? hell i forget how the story goes
  2. DrixtanI am building native binaries with java projects - In Your Teeth Mr. GoLang... No but seriously, no trash talking here; that's pretty awesome if you ask me - but since you didn't... :D
  3. jreichermlxdy: I use Emacs for Java development
  4. jreicherdreamreal: is the c64 you're using new?
  5. dreamrealjreicher: yes
  6. dreamrealhttps://bytecode.news/posts/2026/05/kirk-pepperdine-ships-gc-log-analysis-tool squeeeee
  7. dreamrealhttps://googlebook.google/ OMG
  8. javabotdreamreal's title: "Googlebook: Designed for Gemini Intelligence | Coming Fall 2026 - Googlebook"
  9. nevetGooglebook: Designed for Gemini Intelligence | Coming fall 2026
  10. dreamreal"phone with android 17 or above required" and what a freaking name
  11. Drixtanis it free? since we are the product, I guess it's going to be free isn't it?
  12. dreamrealsomehow I doubt it
  13. Drixtanafter the mac neo, I don't know what google expect with this one.
  14. Chronosdreamreal: Impressive lack of details on that Googlebook page...
  15. dreamrealyeah, I laughed
  16. dmlloydhere's a question for any windows dev people here: why can I not resolve the `GetComputerNameW` symbol using FFM? do I have the wrong symbol name, or do I need a specific library for this, or does the JVM block some symbols, or...?
  17. ChronosI could be wrong, but it looks like it's Google's first Android-for-the-desktop-that-replaces-ChromeOS.
  18. GreenResponseit only lacks Musk’s NeuraLink to ask Gemini just by thinking–save your vocal cords for dealing with other humans!
  19. dreamrealneuralink would ask grok anyway
  20. GreenResponsetrue
  21. deebowhere's my AskJeevesBook, with a mos6510
  22. dreamreal8510 now
  23. dreamrealActually, I can't remember the differences between the 6510 and the 85xx series the commodore 128 had - page switching for RAM banks, at least, I think?
  24. * dreamreal runs to ask whatever the AI du jour is
  25. dreamrealoh, 8502
  26. dmlloydthe differences were very very minor IIRC
  27. dreamrealyeah; 6510 added some I/O states, 8502 was the memory flipping stuff
  28. dreamrealyou RC
  29. dmlloydin general the customizations to the 6502 that were added *after* the initial runs were all really minor
  30. dmlloyduntil the 65C02
  31. dmlloydwhich was a redesign
  32. cheeseri still want to write an emulator for that cpu
  33. dmlloydit's a nifty design, very efficient and clever
  34. dreamrealdmlloyd: incidentally I used your methodhandle article for work yesterday - the semantics around invokeExact() are ... interesting. I ended up going with invoke() instead, but I literally could not call invokeExact() on a method that returned a long without consuming the long.
  35. dreamrealI'm going to have to defend the way I used it ("couldn't this have been a lambda?") but I'm sticking to it
  36. dmlloydyeah you have to consume it or else throw it away ahead of time. `mh.invoke()` is semantically identical to `mh.asType(<the way you are going to invoke it>).invokeExact()`
  37. cheeserstupid things I want to write: 6502/C-64 emulator (using javafx, natch), ext4 fs, mongodb/lsm in-memory (h2-inspired mini version)
  38. cheeseri once debated writing a minecraft mod layer on top of mongodb query visualizations
  39. dreamrealdmlloyd: I don't even know how that's *enforced*. invoke() was fine, and I almost went with the lambda but screw that
  40. dreamrealI was mostly vaguely amused that the method I was invoking *returned* a long... and did nothing with it. A *private* method!
  41. dmlloydwell `invoke` is a special magic case
  42. dmlloydimagine that it's like a macro, and the JVM expands it on first use
  43. dreamrealA smart developer would say "why not make those void" but um
  44. dmlloydwell you can make it void: `mh = mh.asType(void.class, arg1Type, arg2Type, ...)` boom now it's void
  45. dmlloydand you can `invokeExact` it
  46. dreamrealHah. Is that worth it, though?
  47. dmlloydif you call it more than once, yes
  48. dmlloydthe JVM can theoretically inline any `invokeExact` on a method handle living someplace stable (like a final static field) into basically being equivalent to calling the method directly (possibly including more inlining)
  49. dreamrealhmm, hmm. I'll have to see how often that gets called - it's mostly called in an outlier data condition on multipart emails. And I HATE that method - it's nearly 200 lines long, and the cyclomatic complexity is unbelievable.
  50. dreamrealFor those who have been around #java on IRC for a long time: MaggieL passed away on May 7. Hasn't been seen on libera that I know of, and left freenode a long time ago, but MaggieL was knowledgable, irascible, and a valued and trusted friend and contributor. Pour one out for her.
  51. jbosmansdidn't know her but may she rest in peace + cheers with a belgian beer
  52. dreamreal"The sunk cost fallacy feels like conviction if you squint hard enough. Look, we get it, Groovy sounded like a great idea at first."
  53. dreamreal... one part of that is going to get dropped in the next draft :D
  54. ParaGroovy was fun.
  55. dreamrealSo was UML.
  56. ParaNah.
  57. dreamrealpfffft, now we know yet another person who never used together/j
  58. ParaI had to learn Rational Rose to get through school.
  59. dreamrealI thought together/j was good enough that I was willing to try IDEA
  60. cheeseri miss the remote collaboration it had. too bad the internet wasn't fast enough to make that practical then.
  61. Paratrac was magical
  62. ParaWe've lost so much.
  63. dreamrealAt least we have copilot 365 teams with copilot to pilot us co-ly along with a copilot (tm)
  64. Para(School or Enterprise)
  65. cheeserhttps://x.com/maxandersen/status/2054453325320352119
  66. NeXeNsweet, vaadin has hmr with vite ? awesome just notice that
  67. NeXeNhere my dumbasscus steel knogging been bashing away at the refresh not realizing the changes were there already