38

agreed the format parser is stupid, but thats more a cosmetic issue. its had the ability to create location aware dates since the first version 12 years ago

about time, Go has had this since 2012:

https://pkg.go.dev/time#Date

> none of those options are alternatives to serde_json, unless you restrict yourself to serde_json::Value - which no one does in practice.

check your facts, all the above options have derive support, serde is not special in that.

more like an orange versus a slightly better orange

thats over the course of like 5 years. maybe they get lost, or when I am jogging I am pouring sweat into them, so eventually they give out. they are cheap enough that I can stock up and then I dont have to go hunting for ones I like if I lose one

and this folks is why I will never buy airpods. for $249, I can get 8 pairs of these:

https://electronics.sony.com/audio/headphones/in-ear/p/mdrex...

have purchased 4 already, happy with my decision

this 100%. serde is a bloated monster, its sad that its the popular JSON, because all it does is make Rust look bad in my opinion. here are some smaller options:

https://lib.rs/crates/humphrey_json

https://lib.rs/crates/rust_json

https://lib.rs/crates/sj

this will panic:

v := hello.(world)

this never panic:

v, ok := hello.(world)

and yes, its awesome. people rag on Go because BLARG ERRORS BOILERPLATE, but if you can get over that Go is not Python/JavaScript, you're left with a simple powerful language

that an who the fuck uses interface literals? I do Go personally and professionally for years and never seen it.

duh, its localhost:

https://github.com/biemster/FindMy/blob/113ebf4017729b92a381...

what does that have to do with anything?

> I think returning an iterator is acceptable, the docs could explain the expense of the operation, and the implementation could change in the future as needed. But that does hide some complexity.

if a function returns an iterator, it should be iterating the input. thats impossible in this situation. you'd need to loop the entire map, then return an iterator that tricks the user into thinking they are getting better performance when they are getting the worst possible performance.

no windows

https://github.com/zed-industries/zed/issues/5394

if you want your comments to make any sense, you need to use "key value" with every usage of "value", otherwise people are going to think "container value"

> This type is about the order of its contents by value.

No, by key.

its completely pointless to make this an iterator, because you have to loop the entire map to do so, which kills any benefit of using iterators

the point is you dont need it. by your own admission, it would save literally 0 lines of code from your current example. you need discipline when adding sugar otherwise you can ruin a language.

> maps.SortedByKeys

thats what you call overfitting kids

sense... this comment makes none.

this 100%

he really doesn't need the make up - just makes him seem like a joke. otherwise great content

Why is it not dated?

Those methods are not magic pixy dust. Chain a few a those and you've looped through the entire array 3 times, instead of one for loop.

> lean and kiss

da fuq

good point about the lindy

infinitely doesn't mean what you think it means

why fork chrome rather than another browser, or starting from scratch?

are you being intentionally ignorant? the more browsers in popular use, the less control each has. currently Chrome has more usage than the other browsers combined:

https://gs.statcounter.com/browser-market-share

which means Google has significant control over web standards

doesn't work with windows

https://github.com/versotile-org/verso/issues/118