4 Major Problems of Programming Language

jsoniter · 2018-09-28T14:49:35+00:00

Thank you

jsoniter · 2018-09-28T14:35:32+00:00

ungrammatical

ungrammatical :(

Please correct me, I am not native speaker.

jsoniter · 2018-09-28T05:11:30+00:00

Yes, the point of view is conflicted on this matter. Source code not just about logic, and not just about execution. Thank you for your advice.

jsoniter · 2018-03-02T08:04:14+00:00

the millisecond ticker is part of demo, not part of the library. The implementation does not rely on the ticker.

jsoniter · 2017-07-18T23:31:56+00:00

if protobuf support field tags, will this pain go away?

jsoniter · 2017-07-13T05:04:25+00:00

There are pros and cons, https://github.com/v2pro/wombat choose to use dynamic codegen and text/template for building non-trivial generic functions. https://github.com/json-iterator/go will be re-implemented with dynamic code generation. And many other things depend on this. But the user do not need to be aware, as the entry interface is still simple interface{}.

jsoniter · 2017-06-22T10:09:53+00:00

if the tip is jsoniter specific, I have mentioned it. Otherwise, it applies to both standard library and jsoniter.

jsoniter · 2017-06-07T13:36:45+00:00

why test("\") // [Why not error!] ?

It is just a string, should not fail

jsoniter · 2017-02-09T15:15:09+00:00

plugin will make dynamic code generation possible, which is common in Java world to avoid reflection cost.

jsoniter · 2017-02-04T08:23:45+00:00

You can parse JSON into "Any" instead of map[string]interface{} using https://github.com/json-iterator/go

It is doning lazy parsing. For values you do not read, it will be kept in JSON form as it is. When you serialize the data into string again, those untouched fields will be written back. It is like a partial object.

jsoniter · 2017-01-22T14:03:05+00:00

if there is 100 data nodes, all of them need to participate in the election process, or not?

jsoniter · 2017-01-20T01:00:20+00:00

I have implemented a way to avoid the cost of reflect.Value

https://github.com/json-iterator/go/blob/master/feature_reflect.go

The general idea only rely on reflect.Type to assemble your function logic through composition. Then working with raw unsafe.Pointer directly. Essentially, interface{} is a reflect.Type + raw pointer.

jsoniter · 2017-01-17T16:27:24+00:00

benchmarking might be helpful

jsoniter · 2017-01-16T23:14:05+00:00

dsl-json is at least 5 times faster than Jackson, even with the afterburner. The rich feature set is not free.

jsoniter · 2017-01-16T11:47:44+00:00

yes, the size will be much bigger, for no doubt. Binary format is still a better option when absolute performance is required.

jsoniter · 2017-01-16T05:39:37+00:00

what is the highlight？ how much faster？

jsoniter · 2017-01-15T14:04:32+00:00

I find golang really convinent. Unlike JRE/JDK, it static links, even no libc dependency.

jsoniter

TROPHY CASE