00:00:00 --- log: started forth/19.05.29 00:03:20 --- quit: clog (Ping timeout: 245 seconds) 00:03:20 --- log: stopped forth/19.05.29 00:03:27 --- log: started forth/19.05.29 00:03:27 --- join: clog (~nef@bespin.org) joined #forth 00:03:27 --- topic: 'Forth Programming | logged by clog at http://bit.ly/91toWN | If you have two (or more) stacks and speak RPN then you're welcome here! | https://github.com/mark4th' 00:03:27 --- topic: set by proteusguy!~proteus-g@cm-134-196-84-89.revip18.asianet.co.th on [Sun Mar 18 08:48:16 2018] 00:03:27 --- names: list (clog +proteusguy dave0 alexshpilkin jimt[m] siraben bb010g tabemann gravicappa nighty pareidolia john_cephalopoda rdrop-exit Keshl dys X-Scale ashirase Zarutian zy]x[yz mstevens pointfree moony muzgo WilhelmVonWeiner jedb lonjil chunkypuffs Croran djinni jpsamaroo phadthai jhei dave9 rprimus the_cuckoo ttmrichter Kumool +crc dzho C-Keen rpcope- jackdaniel malyn irsol koisoke yunfan presiden arrdem__ ullbeking nonlinear catern ovf amuck CORDIC lchvdlch gabc) 00:03:27 --- names: list (+KipIngram vxe gaze___ jn__ diginet2 bluekelp remexre nerfur a3f dne ghostyy MrMobius rann cheater reepca Lord_Nightmare APic rain1) 00:37:41 --- quit: dys (Ping timeout: 252 seconds) 00:48:05 --- join: xek_ (~xek@apn-37-248-138-80.dynamic.gprs.plus.pl) joined #forth 02:03:16 --- quit: ashirase (Ping timeout: 246 seconds) 02:09:54 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 02:20:26 --- quit: proteusguy (Ping timeout: 258 seconds) 03:11:18 --- join: pierpal (~pierpal@host201-184-dynamic.11-87-r.retail.telecomitalia.it) joined #forth 03:45:36 --- quit: nighty (Read error: Connection reset by peer) 03:45:53 --- join: nighty (~nighty@b157153.ppp.asahi-net.or.jp) joined #forth 03:49:52 --- quit: nighty (Client Quit) 03:59:25 --- join: kaun_ (~kaun@117.230.153.214) joined #forth 04:58:55 --- join: nighty (~nighty@b157153.ppp.asahi-net.or.jp) joined #forth 05:12:00 re c[_] :) 05:18:18 heyo 05:18:32 Hi WilhelmVonW 05:42:47 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 05:53:32 --- quit: rdrop-exit (Quit: Lost terminal) 06:20:35 how are you mate 06:46:23 --- quit: muzgo (Quit: leaving) 06:47:51 --- quit: pierpal (Ping timeout: 268 seconds) 06:58:13 --- join: kaun_2 (~kaun@117.230.147.207) joined #forth 06:59:49 --- quit: kaun_ (Ping timeout: 248 seconds) 07:28:50 --- join: pierpal (~pierpal@host201-184-dynamic.11-87-r.retail.telecomitalia.it) joined #forth 07:57:41 --- quit: tabemann (Ping timeout: 252 seconds) 08:00:59 i've spent the past week having this debate in my head, and i think i've reached a conclusion: floating point is a terrible thing with no real-world use case 08:06:44 what about muh mathematics 08:07:00 rendering and that 08:07:07 fixed-point is better 08:07:20 --- quit: Zarutian (Read error: Connection reset by peer) 08:07:35 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 08:07:37 yeah 08:07:39 agreed 08:07:44 and SIMPLER 08:07:44 namely you get to control your epsilon 08:08:09 for anything non-academic i can't reason out how having this variable epsilon is ever desirable or even acceptable 08:09:08 and yeah, because of that it introduces wacky gotcha's that make it very challenging to use effectively 08:15:18 what if you need 2^2^23 worth of numbers 08:15:42 floats won't give you that, anyway 08:15:56 if you need to work with larger values, redefine your units 08:16:34 working with floats hides this from you and you end up losing resolution without realizing it 08:18:00 floats only give you 2^24 values, or 2^53 in the case of doubles. you actually /lose/ range by using floats. if you use fixed-point, you could get the full 2^32 or 2^64 range 08:18:35 it gives you some illusion of having a greater range because of that variable epsilon, but like i said before, i can't imagine any non-academic scenario where that's at all acceptable 08:39:59 --- quit: pierpal (Ping timeout: 258 seconds) 08:46:07 --- quit: dave0 (Quit: dave's not here) 10:07:42 --- quit: kaun_2 (Quit: AtomicIRC: The nuclear option.) 12:33:44 did yall hear the new GreenArrays board is out 12:33:48 --- quit: gravicappa (Ping timeout: 268 seconds) 12:33:55 and they're working on a new GA144 12:33:59 like a V2 12:34:45 GA145? 12:41:04 G144A2x 12:41:15 sounds like a typo tbh 12:41:31 GA144V2 would've made more sense 12:42:00 how about GA1728 12:42:44 $495 for the board. (http://www.greenarraychips.com/home/products/index.html) 12:42:57 pointfree: do you have an ETA on your homebrew GA144 dev boards? 12:43:29 500 bones I might consider shelling out, but I kind of want to wait for the G144A2x for that money 12:45:16 also there's no more colorForth? just arrayForth based on a more-regular Forth 12:45:20 it might be worthwhile if I had an actual application where I could use the GA144, but I don't currently; I'd just want one to play around with, and that's outside of my fun budget 12:45:51 tell your kids to save up pocket money for a EVB002 evaluation board 12:46:01 then, ground them, when they've bought it 12:46:13 the lack of colorforth is disappointing 12:46:40 polyFORTH (yawn), saneFORTH (a windows Forth, afaict) 12:47:16 I don't use Windows except at work, so saneFORTH would be out of the picture anyway 12:47:56 I have a windows computer for the 4 hours of the month where I play MudRunner, a game about driving your truck through mud 12:48:34 wonder why they dropped colorForth 12:49:24 maybe it was too complicated to train people in? 12:50:10 complicatedly simple, lol. 12:51:31 too unconventional probably :( 12:51:56 http://www.greenarraychips.com/blog2/2019/05/26/documentation-for-saneforth/ 12:52:09 http://www.greenarraychips.com/home/documents/greg/SFW32PR-190525.pdf 12:54:03 neither saneFORTH nor polyFORTH have the simulator the colorFORTH environment had... too unconvential is also my guess 13:21:29 --- quit: xek_ (Ping timeout: 244 seconds) 13:25:28 --- join: john_metcalf (~digital_w@host86-146-151-103.range86-146.btcentralplus.com) joined #forth 13:33:47 --- join: dys (~dys@tmo-119-29.customers.d1-online.com) joined #forth 16:13:47 --- quit: john_cephalopoda (Ping timeout: 252 seconds) 16:27:38 --- join: john_cephalopoda (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 16:51:07 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 16:51:26 hi 18:06:10 --- join: tabemann (~tabemann@rrcs-162-155-170-75.central.biz.rr.com) joined #forth 19:59:12 --- quit: bluekelp (Remote host closed the connection) 20:05:32 --- join: gravicappa (~gravicapp@h37-122-123-170.dyn.bashtel.ru) joined #forth 20:08:27 --- quit: tabemann (Ping timeout: 258 seconds) 20:41:34 --- join: tabemann (~tabemann@2600:1700:7990:24e0:b944:a349:56b9:12fb) joined #forth 20:42:23 --- quit: dave0 (Quit: dave's not here) 20:49:32 --- quit: dddddd (Read error: Connection reset by peer) 21:28:16 --- join: bluekelp (~pp@bluekelp.com) joined #forth 21:55:27 --- join: rdrop-exit (~markwilli@112.201.166.63) joined #forth 22:10:14 --- join: proteusguy (~proteusgu@cm-114-109-129-168.revip13.asianet.co.th) joined #forth 22:10:14 --- mode: ChanServ set +v proteusguy 22:43:38 --- quit: proteusguy (Ping timeout: 244 seconds) 22:46:20 --- quit: Keshl (Read error: Connection reset by peer) 22:46:37 --- join: Keshl (~Purple@207.44.70.214.res-cmts.gld.ptd.net) joined #forth 22:59:04 --- quit: nerfur (Ping timeout: 246 seconds) 23:11:55 --- join: proteusguy (~proteusgu@mx-ll-14.207.209-205.dynamic.3bb.co.th) joined #forth 23:11:55 --- mode: ChanServ set +v proteusguy 23:59:59 --- log: ended forth/19.05.29