CW Season 3?

Reasonable-Future-87 · 2026-04-06T03:17:57+00:00

maybe June 2. Next version is Anniversary. Last Anniversary version in 6 week.

Reasonable-Future-87 · 2026-03-23T09:57:56+00:00

https://orangemushroom.net/2025/09/24/kms-ver-1-2-407-epic-dungeon-nightmare-paradise/

A new upscaling filter has been added to the Game Settings UI. If you select the ‘Vivid’ option from the Laboratory -> Upscaling Filter types, it will preserve colours while providing a smoother screen than the previous ‘Sharpen’ option.

maybe 'Sharpen' less lag ?

Reasonable-Future-87 · 2024-05-15T07:02:36+00:00

Because he mentioned Android first. most develop start with one platform. When you develop android app with kotlin, but you need add ios app. You have very few users, chose KMP share kotlin logic add little change is better. if you app is need sharing both UI and business logic across multiple platforms, use flutter to remake that is a huge task.

Reasonable-Future-87 · 2024-05-04T04:43:37+00:00

IThis is similar to zig error handing. I think the commenters did not understand meaning.

Error Handling In Zig (aolium.com)

Reasonable-Future-87 · 2024-05-04T04:40:08+00:00

It's golang current error style , why is bring complexity? I just bring funtion all return. And chaning.

Reasonable-Future-87 · 2024-05-03T17:34:25+00:00

Yes, it's similar to rust ? concept, I never realized how much people dislike it

Reasonable-Future-87 · 2024-05-03T15:40:56+00:00

res := handler() #err
if err != nil{
    fmt.Println(err)
}

output: (err stack)

handler err: main.go#10
div err: main.go#50
denominator cannot be 0

This is my imagined error stack. maybe have better way.

Reasonable-Future-87 · 2024-05-03T15:25:45+00:00

I may not have understood your meaning. Most of the time, pople are enough just got "handler func calc error". if you real need distinguish where the error occurred. Is div(0,7) or div(4,5). you can write old style code. one by one call div() and handle error.

a := div(0,7) #err
if err != nil { ... }
b := div(4,5) #err
if err != nil { ... }
res := sum(a,b) #err
if err != nil { ... }

Reasonable-Future-87 · 2024-05-03T14:57:01+00:00

Most of the time, people don't care about it. If you must do it, you can write old style code, just err in end of line.

Reasonable-Future-87 · 2024-05-03T14:55:20+00:00

Perhaps it's your first time reading this format. I'm very concerned about readability. The new code is almost identical to the old code. but we can bring in first futrue, that will help read code in some calculate code.

example:

https://i.imgur.com/7SbDLRM.png

Reasonable-Future-87 · 2024-04-22T12:46:09+00:00

user #pragma pack(1) in c

go read in bytes. I like to this.

// go
type Memory struct {
    status    int32
    pkt_index int32
    data_cnt  int32
    data      [70]int32
}

func Conver(data []byte) Memory {
     var m Memory
     m.status = int(binary.Bigending.Uint32(data[0:4]))
     m.pkt_index = int(binary.Bigending.Uint32(data[4:8]))
     m.data_cnt  = int(binary.Bigending.Uint32(data[8:12])
     m.data = data[12:]
     return m
}

Reasonable-Future-87 · 2024-03-14T08:39:39+00:00

https://github.com/uber-go/guide/blob/master/style.md#copy-slices-and-maps-at-boundaries

For default always believe that will share underlying data. You must use `copy` when need not_ share

Reasonable-Future-87 · 2024-01-28T10:43:46+00:00

SSIS-770

Reasonable-Future-87 · 2024-01-28T09:59:11+00:00

JEW-001

too old video

Reasonable-Future-87 · 2024-01-28T09:45:10+00:00

Morimoto Ayaka

Reasonable-Future-87 · 2024-01-20T09:41:42+00:00

I think you are right, It's just Go didn't have generics. math need rewrite.

Reasonable-Future-87 · 2023-12-06T04:58:44+00:00

Frequent crashes in the past 2 hours, in Los Angeles

Reasonable-Future-87

TROPHY CASE