2024/10/13

Newest at the top

2024-10-13 22:22:25 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-13 22:19:25 +0200michalz(~michalz@185.246.207.203) (Remote host closed the connection)
2024-10-13 22:11:53 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-10-13 22:06:39 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-13 22:02:19 +0200youthlic(~Thunderbi@user/youthlic) youthlic
2024-10-13 22:01:54 +0200youthlic(~Thunderbi@user/youthlic) (Remote host closed the connection)
2024-10-13 21:55:51 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-10-13 21:50:53 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-13 21:50:44 +0200mreh(~matthew@host86-128-2-51.range86-128.btcentralplus.com) (Ping timeout: 252 seconds)
2024-10-13 21:49:56 +0200ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en)
2024-10-13 21:40:05 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-10-13 21:35:06 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-13 21:33:38 +0200ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en
2024-10-13 21:32:23 +0200ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en)
2024-10-13 21:28:11 +0200 <_d0t> except it's not exactly my own script, but otherwise correct.
2024-10-13 21:27:58 +0200 <_d0t> monochrom: yup, exactly that
2024-10-13 21:27:49 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 248 seconds)
2024-10-13 21:25:50 +0200synchromesh(~john@2406:5a00:2497:300:b017:a602:11fc:4e3b) synchromesh
2024-10-13 21:25:34 +0200mreh(~matthew@host86-128-2-51.range86-128.btcentralplus.com) mreh
2024-10-13 21:24:08 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 245 seconds)
2024-10-13 21:23:18 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-10-13 21:19:56 +0200ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en
2024-10-13 21:19:17 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-13 21:14:48 +0200machinedgod(~machinedg@d50-99-47-73.abhsia.telus.net) (Ping timeout: 252 seconds)
2024-10-13 21:14:09 +0200rvalue(~rvalue@user/rvalue) rvalue
2024-10-13 21:13:36 +0200rvalue(~rvalue@user/rvalue) (Read error: Connection reset by peer)
2024-10-13 21:08:33 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-10-13 21:08:03 +0200 <monochrom> Is it like you have your own shell script and you name it "gcc" to intercept usages of gcc and change some arguments and you would really like to avoid parsing a response file? :)
2024-10-13 21:06:42 +0200 <monochrom> _d0t: Now I'm curious. (Just curious.) What needs to be hacked around? :)
2024-10-13 21:06:18 +0200acidjnk_new(~acidjnk@p200300d6e72cfb115c8ca2f660dd1d29.dip0.t-ipconnect.de)
2024-10-13 21:05:56 +0200Pixi(~Pixi@user/pixi) Pixi
2024-10-13 21:03:56 +0200 <Square> dminuoso, "Q: how many types". Unclear. But possibly 50ish.
2024-10-13 21:03:32 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-13 21:03:00 +0200 <Square> The generation of schema + java types would be part of the build, so any changes in types would lead to compile errors - if not adapted in java.
2024-10-13 21:02:29 +0200vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2024-10-13 21:01:53 +0200 <Square> parts of a java application*
2024-10-13 21:01:38 +0200 <Square> My use case is migrating parts of an application to Haskell and having an RPC mechanism calling Haskell from Java. Ideally i would like to replicate a bunch of haskell types in java (limiting myself to constructs it supports).
2024-10-13 21:00:42 +0200caconym(~caconym@user/caconym) caconym
2024-10-13 21:00:17 +0200 <dminuoso> Also think about code generators (the other way around), they tend to be esaier.
2024-10-13 21:00:06 +0200caconym(~caconym@user/caconym) (Quit: bye)
2024-10-13 21:00:02 +0200 <dminuoso> How many data types are we talking about here?
2024-10-13 20:59:31 +0200 <dminuoso> It increases coupling, introduces bugs quickly when you make modifications, and delays separating the network representation properly, possibly with versioning even.
2024-10-13 20:58:25 +0200 <Square> s/in don't/in I don't/
2024-10-13 20:58:07 +0200 <Square> dminuoso, I know an argument, it could make my work so much easier in don't having to replicating the model by hand in another language.
2024-10-13 20:57:53 +0200lxsameer(~lxsameer@Serene/lxsameer) (Ping timeout: 245 seconds)
2024-10-13 20:57:13 +0200 <_d0t> Otherwise I'll just have to hack around this.
2024-10-13 20:57:09 +0200 <dminuoso> Certainly promoted by the ease of `Generic` and` ToJSON/FromJSON.
2024-10-13 20:57:07 +0200 <_d0t> geekosaur: i mean, i was just wondering if there was a way already.
2024-10-13 20:56:58 +0200 <dminuoso> Tying your wire format to your semantic data model is a classic mistake.
2024-10-13 20:56:43 +0200 <dminuoso> In fact, you should probably have an intermediate data type representing the format instead.