3 ms·
> Frameworkism isn't delivering. Correct. The reason is not the frameworks but the languages. What is needed is a much more high-level and feature-powerful lan
by valenterry 2y ago
> Frameworkism isn't delivering.
Correct. The reason is not the frameworks but the languages. What is needed is a much more high-level and feature-powerful language.
Just look at react. Passing down dependencies/values is a pain. So what did react do? It introduced contexts. Similar, other react addons try to solve this problem. But they all sacrifice type-safety in the process.
They simply cannot solve this problem; only a better language can. Typescript maybe could, but they restrict themselves to not generate code (or at least very limited, I think for enums they do it).
Without a change here, nothing can ever improve.
- klysm 2y agoThis is straight up not true. React state management is very flexible and requires you to think about what your problem is and the nature of state. There is absolutely nothing preventing you from keeping those safety - I’m not sure what you mean by that. The typescript type system is very advanced, maybe even too advanced! I disagree that more sophisticated languages are required.
- valenterry 2y agoSee what Peter Kelly wrote. For example.
- peterkelly 2y agoThe React team should have done their own language, rather than making it a framework/library. Then they could ensure the absence of side effects in rendering code, and had a better way of detecting updates. The knowledge about how to do this was already out there for many years before they started: https://en.wikipedia.org/wiki/Functional_reactive_programming https://en.wikipedia.org/wiki/Functional_reactive_programmin...
- CityOfThrowaway 2y agoYes, but if they did their own language it would have almost certainly died in obscurity. React won because it solved a real pain point for a group of people, using the techniques they were already using... but better! Having built large apps in angular, handlebars, and jquery... it was (and still is) a godsend for building highly interactive, stateful web applications. I am deeply skeptical of some of the stuff that people are doing now wrt. putting backend logic into React components, but the fundamentals of React are still very reasonable to me.
- valenterry 2y agoThat's exactly my point.
- reconvene1290 2y agoIsn’t that ReScript? https://rescript-lang.org/ https://rescript-lang.org/
- andrewstuart 2y agoDon’t use state, except within a component. I build all my react this way. No prop drilling, no Redux, no context, no mobx no state. If you need to communicate between components then send a document event. Your react application will be dramatically more simple without state.
- Cotterzz 2y agoThis new language. Do you mean something that compiles down to JS like Typescript, Coffescript & Dart? Or a language that compiles to WASM like C, C++ or Rust?
- valenterry 2y agoDoesn't matter, as long as the language directly supports the required features.