Newest at the top
| 2025-03-01 02:35:32 +0100 | stiell | (~stiell@gateway/tor-sasl/stiell) stiell |
| 2025-03-01 02:35:12 +0100 | stiell | (~stiell@gateway/tor-sasl/stiell) (Remote host closed the connection) |
| 2025-03-01 02:34:40 +0100 | stiell | (~stiell@gateway/tor-sasl/stiell) stiell |
| 2025-03-01 02:33:48 +0100 | stiell | (~stiell@gateway/tor-sasl/stiell) (Remote host closed the connection) |
| 2025-03-01 02:32:06 +0100 | califax | (~califax@user/califx) (Remote host closed the connection) |
| 2025-03-01 02:28:09 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 260 seconds) |
| 2025-03-01 02:23:40 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-01 02:20:53 +0100 | bilegeek | (~bilegeek@123.sub-174-228-103.myvzw.com) (Ping timeout: 248 seconds) |
| 2025-03-01 02:17:28 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 245 seconds) |
| 2025-03-01 02:15:37 +0100 | alp | (~alp@2001:861:8ca0:4940:cf02:35f:1502:8681) (Ping timeout: 268 seconds) |
| 2025-03-01 02:14:11 +0100 | tessier | (~tessier@ec2-184-72-149-67.compute-1.amazonaws.com) (Quit: leaving) |
| 2025-03-01 02:08:01 +0100 | <haskellbridge> | <Liamzee> ugh |
| 2025-03-01 02:08:00 +0100 | <haskellbridge> | <Liamzee> i mean, you can still opt to go the compiler plugin route |
| 2025-03-01 02:07:47 +0100 | <haskellbridge> | <Liamzee> but c_wraith, I'm still wondering, if you have a simple datatype of backend, frontend, client |
| 2025-03-01 01:55:45 +0100 | sprotte24 | (~sprotte24@p200300d16f44db00402a6a5cf9d1162b.dip0.t-ipconnect.de) (Quit: Leaving) |
| 2025-03-01 01:51:31 +0100 | acidjnk_new | (~acidjnk@p200300d6e7283f90d472fd3bae079d4a.dip0.t-ipconnect.de) (Ping timeout: 252 seconds) |
| 2025-03-01 01:48:26 +0100 | k_hachig_ | (~k_hachig@bras-base-toroon0247w-grc-123-70-29-50-103.dsl.bell.ca) (Ping timeout: 244 seconds) |
| 2025-03-01 01:40:54 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 252 seconds) |
| 2025-03-01 01:40:48 +0100 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
| 2025-03-01 01:36:37 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-01 01:14:30 +0100 | Everything | (~Everythin@46.211.105.36) (Quit: leaving) |
| 2025-03-01 01:12:33 +0100 | <haskellbridge> | <Liamzee> that also brings miso into play, which advertises itself as isomorphic |
| 2025-03-01 01:06:16 +0100 | <haskellbridge> | <Liamzee> also this is basically what i was looking for, oh well |
| 2025-03-01 01:06:10 +0100 | <haskellbridge> | <Liamzee> https://en.wikipedia.org/wiki/Isomorphic_JavaScript |
| 2025-03-01 01:02:43 +0100 | <haskellbridge> | <Liamzee> tbh with CPP, you don't actually need Haskell |
| 2025-03-01 01:02:15 +0100 | <haskellbridge> | <Liamzee> but the entire point is so that you're building full stack in one module, one module at a time |
| 2025-03-01 01:02:05 +0100 | <c_wraith> | But it involves a lot of manual work, and a good platform would have a better abstraction for that. |
| 2025-03-01 01:01:42 +0100 | <c_wraith> | You can put platform-specific stuff in separate trees and conditionally include those trees depending on platform in cabal |
| 2025-03-01 01:01:14 +0100 | <c_wraith> | You can do better than that |
| 2025-03-01 01:01:07 +0100 | <haskellbridge> | <Liamzee> you could hack it with CPP, i suppose |
| 2025-03-01 01:00:18 +0100 | ell | (~ellie@user/ellie) ellie |
| 2025-03-01 00:59:44 +0100 | <c_wraith> | They have to have built before that. |
| 2025-03-01 00:59:36 +0100 | <c_wraith> | Only at link time |
| 2025-03-01 00:59:26 +0100 | <haskellbridge> | <Liamzee> no, but if the functions aren't used at all, shouldn't they be excluded from the binary? |
| 2025-03-01 00:58:48 +0100 | <haskellbridge> | <Liamzee> ah, yes, i see what you mean |
| 2025-03-01 00:58:45 +0100 | <c_wraith> | so... different dependencies on each target? |
| 2025-03-01 00:58:33 +0100 | <haskellbridge> | <Liamzee> libraries |
| 2025-03-01 00:58:21 +0100 | <c_wraith> | Well then, you need to have different dependencies on each target |
| 2025-03-01 00:58:07 +0100 | <c_wraith> | No? |
| 2025-03-01 00:58:03 +0100 | yegorc | (~yegorc@user/yegorc) () |
| 2025-03-01 00:58:00 +0100 | <c_wraith> | Do you want to compile the postgres driver into your frontend? |
| 2025-03-01 00:57:00 +0100 | <c_wraith> | that doesn't work when you have to compile eagerly |
| 2025-03-01 00:55:45 +0100 | yegorc | (~yegorc@user/yegorc) yegorc |
| 2025-03-01 00:55:30 +0100 | <haskellbridge> | <Liamzee> data Object = MkObject {frontend :: FrontEnd, client :: ClientCode, backend :: BackEnd} |
| 2025-03-01 00:55:14 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 260 seconds) |
| 2025-03-01 00:54:08 +0100 | <c_wraith> | doing that was a major pain point when I tried it out |
| 2025-03-01 00:53:37 +0100 | <c_wraith> | obelisk also needed a better story for server-side services - a way to say "this calculation needs to run on the server. If this is a client, make a remote call" |
| 2025-03-01 00:53:25 +0100 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 248 seconds) |
| 2025-03-01 00:52:32 +0100 | <c_wraith> | But yeah, being dependent on ghcjs definitely hurt it |
| 2025-03-01 00:52:16 +0100 | <c_wraith> | there's still room for something like obelisk when the new JS backend for GHC stabilizes |