ReScript is a robustly typed language that compiles to efficient and human-readable JavaScript. It comes with a lightning fast compiler toolchain that scales to any codebase size.
ReScript 12 arrives with a redesigned build toolchain, a modular runtime, and a wave of ergonomic language features.
If you're a fan of both Daft Punk and the 80s City Pop genre and if you were around when City Pop was rising in 2019 then you could have listened to the mashup "Something about Plastic Love"[1]. Beautiful blend. The original got taken down - and second grade recreations remain.
Also Plastic Love is the best Pop song if you go by Vice[2].
When we talk about cities with a grid plan, all the cited examples in sibling comments pale in comparison to Mohenjo-daro. It existed around 2500 BC and one of the iconic places is the Great Bath which is the "earliest public water tank of the ancient world".
Tenochtitlan existed in the 15th century which is fairly recent.
One of the reasons that comes to my mind is - it could have been problematic look for only Microsoft (Copilot) to have access to GitHub for training AI models - à la monopolizing a data treasure trove. With anti-competitive legislation catching up to Google to open up its Play Store, this could have been one of key reasons why this deal came about.
If only projects like Bun/Deno/Node added runtime support for ReScript instead of TypeScript, collectively as the web-tooling industry, we'd be in a better place. But you can't win against the MS's marketing budget.
Also in hindsight, ReScript diverged away from OCaml, but the ReScript development team could have gone further by creating a runtime for ReScript. Then again I don't blame them - they are polishing the dev experience of ReScript and React.
This is the decade of writing shiny new runtimes - I hope somebody writes a ReScript runtime. Imageine ReScript, Core, rescript-webapi, typechecker, re-analyze, plus a bundler minifier etc baked into the runtime like Bun. Sounds like an interesting value proposition. Fingers crossed.
> I use TS because of its ubiquity, but I think there's the possibility for a future where a system a little more like Flow gets baked into the language.
Have you looked into ReScript? It is basically a sound type system + JavaScript-like syntax. It inherits the type system from OCaml. You might like it. They recently released version 11.
They do in many ways. Pixels have clean focused software that are excellent at what they do - it makes you want them. Also they dont include bloatware unlike Samsung.
1. Pixel Camera taught Samsungs and iPhones about computational photography pipelines and Night Sight,
2. Recorder,
3. Photos + various editing features (Top Shot / Best take / Magic Eraser),
4. Phone + various features (Call Screening(US) / Hold for Me(US) / Spam Protection)
5. Google Pay (UPI - India specific)
6. Gestures - Flip to Shh / Double Tap to open Camera / Twist twice in camera for Selfie mode.
One of the underrated achaar is Ber ka Achaar or pickled Indian Jujube[1]. It is a perfect spicy blend of sweet, salty, sour and heat. It smells mouth-watering too and is very delectable - you can gorge on them on their own. These days you'd hardly find people who can make it as good as I used to get back in 00's decade.
For a second, ignore Hooks, Signals and Runes, and look at the way Runes were presented in the video "Introducing Runes.. with Rich Harris". You will find this presentation very similar to but much shorter than "React Today and Tomorrow and 90% Cleaner React With Hooks" video. Both of them talk about:
1. primitives for managing state - $state vs useState
2. removal of lifecycle mechanisms - onMount vs componentDidMount
3. replacing lifecycle mechanisms with new primitives - $effect vs useEffect
It's like the Svelte team took a leaf out of React team's book on how to upgrade a framework - this is evident by the way these features are presented as opt-in like how React marketed Hooks as opt-in. I would go on to predict that the upgrade to Runes will just like the upgrade to Hooks. Developers will use it and then love it - because it presents improvements to the way codebases will be structured and maintained just like React did with Hooks. This is really a Hooks moment for Svelte. Good job Rich and the Svelte team!
You are going to do the same things in a new language whatever you were doing in Python. I understand you are working on web and data science domains.
So I would recommend you check out F# which is like OCaml but runs on the Common Language Runtime. While it is really good on web platform, you might want to investigate the state of data science domain in F#. There are some guides here[1] and here[2].
If the performance improvements are that extensive, it would be interesting to see how close JavaScript + bun would get us to Go or Java on the backend. It would be a game changer if that gap can be closed.
If the performance improvements are that extensive, it would be interesting to see how close JavaScript + bun would get us to Go or Java. It would be a game changer if that gap can be closed.