seagreen

14 ms·

91.
by seagreen 9y ago
It's only like Haskell's type system compared to other schema languages (most of which don't even have product and sum types). Plate has parametric polymorphism, phantom types, and algebraic data types. It doesn't have t
92.
by seagreen 9y ago
Great questions (author here). > The argument against JSON Schema presented in the readme is that is is too expressive. Can someone explain to me, as someone who's used JSON Schema before, why this should concern me? If it doesn&#x2
93.
by seagreen 9y ago
There's been a simple counter to trusting trust attacks since 2009: https://www.dwheeler.com/trusting-trust/
94.
by seagreen 9y ago
> The religious focus on purity. The elm maintainer is an haskell user, and it shows. Can you believe that to read the current time or generate a random number, you must be within a component's update function, ask for one or the ot
95.
by seagreen 9y ago
Could you help clarify this? My guess is that you're saying that you have some data type with (eg) strings and timestamps. When encoded to binary these are encoded differently, resulting in hash A. But if you roundtrip the data through
96.
by seagreen 9y ago
Have you seen my Son project? ( https://github.com/seagreen/Son ) I think I may have gotten JSON canonicalization right. Also, I'm collecting a list of all subsets of JSON here if anyone knows of more: https:/
97.
by seagreen 9y ago
First: XML is a markup language for encoding documents, JSON is a data-interchange language. Each can be twisted to do the job of the other, but they don't naturally do the same job. Second, XML is extraordinarily complicated. Flipping
98.
by seagreen 10y ago
I should have written libre not free. That has a clear meaning (and it's what I use in the followup comment). Do you have a better suggestion than "open" for "no restrictions on use"? > Personally, if I'm wr
99.
by seagreen 10y ago
I understood you! I just wanted to add a few reasons why I (generally an open > libre guy) don't mind the AGPL in this case.
100.
by seagreen 10y ago
Weirdly I think free licenses are great for businesses to use and open licenses are great for personal projects. If I'm writing a hobby project, I want it to help the ecosystem as much as possible. If businesses want to use it then gre
101.
by seagreen 10y ago
I read this comment before looking at the site, but I still wasn't expecting that. It's bad. SUDEP is a thing. Come on people: https://en.wikipedia.org/wiki/Sudden_unexpected_death_in_epi...
102.
by seagreen 10y ago
" When OpenAI launched, it characterized the nature of the risks - and the most appropriate strategies for reducing them - in a way that we disagreed with. In particular, it emphasized the importance of distributing AI broadly; our cur
103.
by seagreen 10y ago
> Meanwhile programming languages should be optimised for reading first. Interesting, because I totally disagree with this. My preference is for programs designed for safety and amenability to static analysis first. Maybe there's a
104.
by seagreen 10y ago
> My early OOP/C++ books are finally more intuitive than something. Ouch! But seriously, this page is just a someone's jotted out notes. Haskell Programming from First Principles and What I Wish I Knew When Learning Haskell ( h
105.
by seagreen 10y ago
I posted that because I think it's the best you're going to get. Monads can be two things: (1) a concept in category theory, (2) a rough implementation of that concept in a programming language. If you want to learn about monads f
106.
by seagreen 10y ago
http://dev.stephendiehl.com/hask/#monads
107.
by seagreen 10y ago
Replying again since I can't edit my comment: Idris, Elm and PureScript.
108.
by seagreen 10y ago
In addition to the others mentioned, PostgREST: https://github.com/begriffs/postgrest
109.
by seagreen 10y ago
Sure thing. And thanks, that made me smile.
110.
by seagreen 10y ago
> it's a float; calling it a fraction is kinda-of-a-lie This happens not to be correct. By specification JSON numbers are just a series of characters, arranged in a certain way: https://tools.ietf.org/html/rfc71
111.
by seagreen 10y ago
I love that we both started our comments with "jq is great". I hadn't seen yours either=)
112.
by seagreen 10y ago
Why no top level lists?
113.
by seagreen 10y ago
Great point about new languages meaning language-aware sorting systems will definitely have breaking changes.
114.
by seagreen 10y ago
By the way, I love that Bencode is bijective. That's a really nice property for a serialization format, and even though I don't mention it on the README it's one of the goals of Son.
115.
by seagreen 10y ago
Son's a niche tool to allow talking to JSON services in a more consistent way. It's not meant as an competitor to any other data format. EDIT: s/alternative/competitor
116.
by seagreen 10y ago
Dang, `protobuf` doesn't support proto2? I'm kind of a Haskell die-hard, this is a big hole in our ecosystem=(
117.
by seagreen 10y ago
> I ended up allowing both "1" and "1.0" so I could distinguish integer and floating point literals Definitely the toughest call when making a JSON subset like this.
118.
by seagreen 10y ago
This is a great name. I'll probably stick with Son because it's already released, but honestly this would have been better.
119.
by seagreen 10y ago
There's an issue for min and max number values here: https://github.com/seagreen/Son/issues/3 Son seems like a natural place to put restrictions on them, but I'm not sure if there's way to do i
120.
by seagreen 10y ago
The plan is to go codepoint by codepoint in ascending order: `{"Z":3,"a":0,"\u0073\u0323\u0307":1,"\u1E69":2}` See this issue for the discussion: https://github.com/seagreen/Son&#

More ›