| Time |
S |
Nick |
Message |
| 02:05 |
|
|
sfisque joined ##javaee |
| 04:48 |
|
|
sajjadg joined ##javaee |
| 05:43 |
|
|
dangertools joined ##javaee |
| 05:43 |
|
|
dangertools joined ##javaee |
| 06:06 |
|
|
lolsies joined ##javaee |
| 08:11 |
|
|
weyer joined ##javaee |
| 08:54 |
|
|
SoniEx2 joined ##javaee |
| 08:54 |
|
|
SoniEx joined ##javaee |
| 08:54 |
|
|
Guest80129 joined ##javaee |
| 10:16 |
|
|
sajjadg joined ##javaee |
| 11:44 |
|
|
mrj2 joined ##javaee |
| 11:44 |
|
|
MegaMatt joined ##javaee |
| 13:04 |
|
|
sajjadg joined ##javaee |
| 13:07 |
|
|
SoniEx2 joined ##javaee |
| 13:15 |
|
|
SoniEx2 joined ##javaee |
| 13:15 |
|
|
SoniEx2 joined ##javaee |
| 14:35 |
|
|
Guest20878 joined ##javaee |
| 14:36 |
|
|
Naros joined ##javaee |
| 14:37 |
|
|
cceemm_ joined ##javaee |
| 14:58 |
|
|
weyer joined ##javaee |
| 16:04 |
|
|
neuro_sys joined ##javaee |
| 17:03 |
|
|
sajjadg joined ##javaee |
| 17:59 |
|
|
ekim left ##javaee |
| 18:04 |
|
|
lv2eof joined ##javaee |
| 18:43 |
|
|
weyer joined ##javaee |
| 18:43 |
|
SoniEx2 |
someone help me: https://github.com/SoniEx2/TheModernClassicGame |
| 18:43 |
|
SoniEx2 |
because idk wtf I'm doing |
| 19:51 |
|
|
engin_ joined ##javaee |
| 20:51 |
|
Naros |
SoniEx2: that looks so familiar :P |
| 20:54 |
|
|
cem_ joined ##javaee |
| 20:54 |
|
* cem_ |
playing game* |
| 21:39 |
|
cem_ |
have anyone played go ? |
| 21:40 |
|
sess |
yes |
| 21:40 |
|
cem_ |
wow ! |
| 21:40 |
|
sess |
wow indeed |
| 21:41 |
|
|
weyer joined ##javaee |
| 21:41 |
|
cem_ |
its very<infinity> hard game |
| 21:48 |
|
sess |
pretty much |
| 22:26 |
|
Guest20878 |
"go" is a game? |
| 22:26 |
|
sfisque |
a very old game |
| 22:28 |
|
Guest20878 |
hm |
| 22:33 |
|
whartung |
It's the last game to done well by computers (not sure if it's beating humans yet, but…it's close I think) |
| 22:41 |
|
sfisque |
i would assume it has, the rules are simpler than chess and chess computers beat humans easily |
| 22:46 |
|
semiosis |
sfisque: nr of rules are bounded, number of moves are not, and the number of moves grows much more rapidly in go |
| 22:50 |
|
sfisque |
aye but since the rules are incredibly simple, move culling would be very easy to optimize |
| 22:51 |
|
sfisque |
the hard part of chess is move weighting, because not only do you have placement, you have different pieces that attack/defend differently |
| 22:51 |
|
sfisque |
go has only two moves, acquire territory or capture, and every piece is identical |
| 22:52 |
|
semiosis |
and yet, go is still harder for computers than chess |
| 22:53 |
|
semiosis |
if you enumerate every possible move you could make per turn, there are a lot more in go. yes it's acquire or capture, but that's just one term in the expression. need to consider positions to play as well, and there's many more positions in go than chess |
| 22:54 |
|
whartung |
yea, the move space of a go board is immense |
| 22:54 |
|
sfisque |
right, but i'm operating under the assumption that culling out "dumb" moves would be easier to optimize |
| 22:55 |
|
whartung |
but you do't know it's a dumb move until later in the analysis. |
| 23:00 |
|
|
kobain joined ##javaee |
| 23:25 |
|
pdurbin |
a friend of mine is working on a program that plays go |
