HN user

donut2d

207 karma
Posts9
Comments83
View on HN

This looks great. I'll have to play around with it.

For once, I'd love to have a nice UI around this so I don't need to search docs, google mongo syntax, check the schema, and edit the code in different spots

Wonder if it can it write data pipelines with unit/regression testing and model the data for decision making. Probably not but one day it might. Generally I see tools like these as potential supplements for what my team does, not replacements.

[dead] 4 years ago

"not just for electric vehicles, but all cars" -- this is good news for the planet, regardless of what you think of $TESLA.

You can actually compile ReasonML to native code with dune.

What are some of the things that weird you out about OCaml's syntax?

A fun way I've been thinking about all this is what nanotech/nanobots are actually going to look like. Tiny little protein machines doing what they've been doing since the dawn of life. We now have a library of components, and as we start figuring out what they can do, and how to stack them, we can start building truly complex machinery for whatever crazy tasks we can imagine. The impact goes so far beyond drugs and treatments.

So I had a thermal problem with my 2018 15" i7 MBP that sounds very similar to what you describe. Temps hit 60° and then get heavily throttled. It started happening after a repair to the keyboard. After dealing with that for 6 months I brought it in to Apple and they fixed the issue by replacing the mainboard, I think. Since it's very rare I see throttling for my use cases (compiling, some gaming).

Last year all of my photos and presets had disappeared after updating the Lightroom app. That was 2+ years of edits that are just gone, lost, unrecoverable.

I do photography as a hobby so I never saw a need for backing up photos and I never paid for the subscription (which would include cloud storage) because I didn’t use any of the tools that came along with the subscription.

The most common emotions were "joy (65%), trust (63%), surprise (61%), love (59%), kindness (56%), friendship (48%), and fear (41%) during the encounter experience, with smaller proportions reporting emotions such as sadness (13%), distrust (10%), disgust (4%), or anger (3%)." Interestingly, 58 percent of respondents said the being also had an emotional response, almost always a positive one.

Wow!

Yeah! I'll code for days without running the app. In OCaml, it's as you say, mostly correct when I actually get around to running it. With PHP/JS, I still have a lot of work ahead of me. With OCaml I feel like I'm thinking much more about the problem and less about the language I'm using.

This is really cool. One issue: I accidentally created a checkbox card with no text and there's no way to edit or remove it (Safari). I can tick the checkbox and move it around and connect it to other cards, but I can't bring up the edit window.

Correction: there is a small area just below the checkbox in the card that I can click to bring up the edit window. Was difficult to discover.

Reason/BuckleScript has always been about attracting JS developers to the powerful type system of OCaml. That was the reasoning for the Reason syntax. This, to me, feels like another step in accommodating developers who are coming from outside the OCaml ecosystem. When I was a less experienced developer, and even still sometimes now-a-days, as I approached a new language, the difficulties I often had were more with the tooling surrounding a language rather than the language itself.

As a language ages and evolves, I think it's easier for the authors and contributors to forget what it's like approaching it fresh. Many times documentation is written with an unintended assumption of an understanding of the ecosystem. Coming to the OCaml/Reason/BuckleScript ecosystem could definitely be confusing.

I definitely had the same positive experience with using OCaml/Reason at my job as well. There's so much power in being able to accurately represent the data model in the type system.

What's BuckleScript then? How is it related to Reason? If it's related why did it have such a seemingly unrelated name in a first place?

My understanding, is that confusion is part of why they're rebranding everything to ReScript. The language and compiler are now all ReScript.

I think the reasoning for the difference in naming is likely historical. I'm not sure, but I think BuckleScript came before the Reason syntax was developed. But it's not like BuckleScript has any connection to OCaml, either. So I dunno.

js_of_ocaml and ReScript (BuckleScript) have different goals. js_of_ocaml is optimized for working with existing OCaml libraries. ReScript is optimized for working with the JS ecosystem. That's my understanding at least as someone who has only worked in native OCaml and BuckleScript, but hasn't touched js_of_ocaml.

You’re right about the advantages of Haskell regarding side-effect strictness and refactoring. That’s a huge win. I think now that I have significant experience with OCaml it’d make going back to Haskell easier for me. That’s probably something I’ll do. But right now I’m finding OCaml has been great for me.

I’ll look into Racket and friends. Thanks

It holds less closely to the ideal of being a purely functional language. It gets out of my way and let’s me get things done. But I think I misspoke a bit. A big part of what has made OCaml better for me is that the tooling has been easier for me to jump into as a beginner.