It allocates 2 collections for every compare call and obfuscates the comparison logic. Personally I find that extremely inelegant. Different strokes I suppose.
I've been on and off thinking about this problem for years. Very excited to see an ecosystem popping up.
But I wonder, why JSON if the web is already built on HTML documents? Is it possible to just store our data in a web of authenticated html documents and have the protocol be built on that? Are there other open standards we can leverage to reduce the amount of new infra / protocols? I wonder if there's a less complex "good enough" mvp version.
If you like these, check out the INFOBAR phones from a few years prior. https://platform.theverge.com/wp-content/uploads/sites/2/cho... People like the multi-colored one, but I've always been partial to the green. I believe there's been a few newer homages to these over the years.
The color line up reminds me of the au MEDIA SKIN phones (Japanese carrier) circa 2007. Maybe it's because I had one back in the day, but I can't help but think they took some influence.
> having spoken with US colleagues, much higher than state-side (although I imagine that varies from state to state).
You know, it does vary but relative to any other developed country it's pitiful in every state. The reality is we just hand out driver's licenses to whomever.
Rattlesnake is actually pretty good. I also like CrabML but I wouldn't expect that to be popular though.
In general, I don't love Rust's choice of sigils (::, <>, etc), but the language reads well enough. That inner/outer function thing is legit the compiler model leaking into user code though.
Yea, sorry I'm not super familiar with the project, but that is the general vibe I get about Perl.
Interestingly enough 落(raku) also has the connotation of failure or missing the target, so not very auspicious in the context of a new language either!
So as a Japanese speaker, I don't think I ever would have made the 'raku' == 'rakuda' camel connection.
Also, while 'raku' is the reading for 楽, which connotes easy, simple and other good things, it is also the reading for a bunch of other characters--namely, 落, which means or carries the connotation of falling, declining or otherwise missing the mark.
When I see the 'raku' transliteration in the context of Perl, I think of 落. Not sure if that says something about my subconscious perception of Perl or not, but I can't help but think 'Raku' is a bad choice for the name of a language mired in indecision and falling from public favor.
On another note, I find the inclination of tech projects towards poorly translated Japanese words amusing. It nicely compliments the phenomena you see in the use of random English words for the naming of Japanese cars, condo buildings, and other 'prestigious' products. So if you find that ridiculous, you should find these 'Japanese' technology names ridiculous as well.
