ByteCode.News
Submit RSS Atom Podcast Sign in

Back to the channels

#java

  1. Square I'm replacing a JSF frontend with React for a semi big java application . What approach do you feel is more natural and easy to work with: A) npm/webpack(possibly Vite later) or B) frontend-maven-plugin?
  2. Square Claude answered it.
  3. Square Anyone using "Jetbrains Gateway" for local container development? I wonder if it creates a directory called '~' in your home folder? Feels like a bug to me.
  4. sirecmg man jsf is the worst ><
  5. sirecmg it is probably easy to work with jsf with claude though
  6. deebo don't do react, do htmx or something :)
  7. deebo unless you're 100% client side, having to deal with SSR is pure satan
  8. Square deebo: SSR?
  9. Square oh server side rendering?
  10. deebo server side rendering
  11. Para Server Side Rendering. Acronym made to justify doing stupid things; not really the concept as a whole but more of a "I want to run React on server because durrrr".
  12. Square deebo: I thought react didn't ship with SSR out of the box?
  13. Square I've seen the horrors in Next.js
  14. deebo depends on how you serve it
  15. Square For vanilla React it's not a problem right? This is just a low traffic admin application.
  16. deebo nextjs does it ok, i'd actually use it isntead of anything self bootstrapped from a template that will be obsolete next week
  17. deebo we have a 10+ year big react+ssr project and the constant upgrading is the biggest hassle, on nextjs there would at least be more help and possibly tooling
  18. deebo unless you're working on it at least weekly for the foreseeable future, don't roll your own webpack/whatever/etc build, just use nextjs
  19. deebo especially for a backoffice app
  20. deebo antd + nextjs is a good way to go there (we run a few of these), not sure if htmx has anything comparable for components
  21. comrad Para: SSR is the proof to me, that we just went to hell and back. First everyone wanted to render on the client, now it's all back to server rendering again.
  22. Para And the reason of course was that wait, this is actually slow when we take into account all the necessary things!?
  23. Para With a good helping of forcing one trick as solution for all of it.
  24. Square deebo: I don't see the need for server side rendering for a low traffic admin application.
  25. Para All software could be made with just a single megafunction.
  26. Square now you sound like a functional programmer =D
  27. Square deebo: (but maybe I'm wrong)
  28. Square SSR is for a snappy feel was my understanding.
  29. Para At least part of it is/was motivated by Google's millisecond golfing.
  30. Square wdym? I think I've missed this. For ad brokering?
  31. Para It used to be that Google's indexer refused to render more than one full redraw, and people made shit frontends which would redraw wildly during initial load. Google also timeouted the process quickly (remember when CPU was expensive?), and site rank algorithm would use snappiness as driving factor.
  32. Para There was endless papers and blog posts about how small ms loads would lead to tens of percents of higher sales.
  33. Square ah ok
  34. Square So none of you use "Jetbrains Gateway"?
  35. Square ...what do you use instead?
  36. Para ...have to look up first what that even is.
  37. Square It's Jetbrains Dev Container take is my understanding
  38. Para Oh I don't use Dev Containers, those are shit.
  39. Square haha
  40. Para The idea is OK but so far I've only seen failures and even worse build setups with them in projects than what they are supposed to fix.
  41. Square So you let the agents have free reign on you system?
  42. Square your*
  43. Para I generally don't let agents run things :) I do per-command verification, and most often tool calling agents tend to deteriorate on themselves as well.
  44. Para The issue is that the "thinking" process does 20 mistakes to get 1 result, and while this could be ignored, it also means 20x cost. So don't let them think.
  45. Para Also I think at least Anthropic's models are deteriorating in general. I'm fairly certain e.g. Sonnet used to be better half a year ago than today.
  46. Square Ah interesting perspective. I've been so non curious about agentic coding so I started using it this week for the first time.
  47. deebo for anything actual user facing with SEO needs, you need SSR (still), for backoffice tooling we just have "use client;" in every component so it only works on the client
  48. Square I thought the hole industry was diving into it
  49. deebo i just give claude/copilot access to IDEA MCP and if it want's do something stupid like download jars and decompile them i tell it to just stop, and sometimes it even listens!
  50. comrad that's what their marketing wants you to think ;)
  51. deebo it's a good tool when you need to do something in bulk, or repeat the same thing over many repositories, but anything "new" still needs a few passes to clean up
  52. comrad i am lousy with webdesign, but claude did some nice sketches, so i iterated over them. not agent, but generated and tried.
  53. comrad i had so add some more prompts to stop it from remaking the whole thing, just to move a button more to the left
  54. deebo we did a few spring boot 4 upgrades manually with verification of proper configurations etc, then just pointed claude to the repos with the PRs: "look at these PRs and do the same upgrade in this repo"
  55. Para Square: On paper agentic workflows are pretty neat, it's just that the tooling seems to be focused on making an expensive mess.
  56. Square haha
  57. Para And yeah, using LLMs to generate some corners/bits which you then massage manually into shape is a pretty good way to utilize them.
  58. Square I must say this port of JSF -> React is going like proceding like a steam engine train.
  59. Para Are they even concept compatible?
  60. Para I'd probably create an extensive suite of E2E tests first.
  61. deebo yeah for agentic stuff you need tests to make sure everything actually works
  62. deebo and not tests by the agent itself :) it can create some insanely stupid tests
  63. Square I feel we've mad a big win just by cutting off the jsf dependencies. It's holding the app back in many ways.
  64. Square it's quite a simple app, but you know how things were back in the days. Tons of code for even minor things.
  65. comrad Square: that Port is a whole Concept Shift, you pretty much can start over as well
  66. Square I haven't inspected the end result yet, just checkpoints along the way. You guys don't seem convinced so maybe I'll get a sad surprise in the end.
  67. comrad but jsf is not so bad, if you know why you want it
  68. Square comrad: "that Port"?
  69. comrad Square: JSF -> React
  70. Square ah ok
  71. Square Sure, JSF is page based, React is SPA by default.
  72. Para Remains to be seen. It might work.
  73. Para The real cost is always in maintenance.
  74. Square I hoped I be able to massage away the quirks that comes with it.
  75. Square I imagine you can do React more page based too no?
  76. deebo you can
  77. deebo but no one is going to get a malicious jsf.jar of a 5 year old version in mavencentral
  78. deebo someone is going to get a malicious dependency of dependency of dependency in npm, and you're fucked if you don't have alerts etc set up for these :)
  79. Para Hm, that perks an idea. I wonder if Maven plugin ecosystem would have some kind of killswitch for downloading too old deps.
  80. deebo does age directly matter?
  81. Para There probably could be a good curve of CVE rating + time.
  82. Para OWASP has a config flag for plain CVE score.
  83. dreamreal morning
  84. julemand101 hi
  85. Bombe Good morning.
  86. dreamreal l'shana tova
  87. sbalmos yarr
  88. Para I wish you all 3 parts grapefruid flavored soda, 2 parts white grapefruit juice, 2 parts gin, half part fresh lemon juice, splash/dash club soda, slice of grapefruit for garnish or whatever else might be your thing this Friday.
  89. Bombe That sounds nice.
  90. Para It's the recipe for Finnish long drink, "lonkero". Drink mix which was invented for the Summer Olympics 1952 and is to this day really super popular over here.
  91. Bombe Oh, that’s what that is? I always assumed it was either a beer or contained copious amounts of Salmiakki.
  92. Para We like to scare tourists with Salmiakki.
  93. Para Once we've slapped them good enough, we'll give them the pleasant stuff. Or Gambina.