| 00:11.48 | *** join/#utah tiwula (~lane@174-23-227-156.slkc.qwest.net) |
| 01:58.45 | *** join/#utah jnbek_ (~jnbek@pdpc/supporter/active/jnbek) |
| 12:24.43 | *** join/#utah Bloodythorn (~Bloodytho@c-76-27-46-75.hsd1.ut.comcast.net) |
| 14:21.12 | *** join/#utah pmcnabb (~peter@gecko.mcnabbs.org) |
| 14:48.04 | *** join/#utah aeryndunham (~quassel@ip-64-134-191-165.public.wayport.net) |
| 15:18.26 | *** join/#utah tiwula (~lane@63.78.215.2) |
| 16:47.45 | *** join/#utah josephscott (~josephsco@2601:681:8001:c340:39f3:dd81:9ca7:a634) |
| 18:03.26 | *** join/#utah tiwula (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 18:09.44 | frostyfrog | https://hardware.slashdot.org/story/17/10/09/0019212/linux-now-has-its-first-open-source-risc-v-processor I think I remember someone here talking about RISC-V processors before. |
| 21:25.33 | levi | Yay, now we can have another arch tree in Linux? And we can run crappy Unixoid operating systems on RISC-V now? Bring out the party horns. :P |
| 21:39.06 | frostyfrog | xD |
| 21:40.49 | frostyfrog | On the plus side, it'll quite possible bring more developers over to RISC-V machines and help the development of better processors. |
| 22:06.58 | jfindlay | anyone here have experience programming POS terminals? |
| 22:10.22 | frostyfrog | besides casual research, not really. |
| 22:19.10 | jfindlay | it seems I may become an expert soon |
| 22:32.25 | levi | RISC-V has the potential to be a pretty cool thing, but it also has the potential to be yet more of the same mess. I guess time will tell. |