Didn’t you go into Turing machines and the Halting problem from that?
That was my intro into computation: regex, automatas, state machines, stack state machines, formal languages, grammars, Turing machines, Hanting Problem, P NP.
Didn’t you go into Turing machines and the Halting problem from that?
That was my intro into computation: regex, automatas, state machines, stack state machines, formal languages, grammars, Turing machines, Hanting Problem, P NP.
Some media organizations have started nuking old articles to please the Google algorithm
Python for excel, grafana for Bi?
I guess depends of your use case.
Sounds like a “you want us to buy Nintendo? Me too buddy…”
But you can sell everything back for full price, as always, right?
Python in the browsers seems like the only outcome worst than JavaScript in the browser.
It sends shivers down my spine.
At least half of those are patched Firefoxes, without telemetry and improved privacy.
Brave, Vivaldi, Edge etc are way more different from chromium than any of those from Firefox.
The thing is Firefox components are more tightly coupled. blink and v8 are easier to wrap in your own browser than gecko and SpiderMonkey.
Mozilla has been refactoring for ages improving the modularity of Firefox, but it may be already to late.
Firefox architecture makes remarkably difficult to spin a browser based in its rendering engine.
I can forgive the JavaScript think taking into account the specification was made in 3 days and that the suits made “looking like Java” a requirement.
Everything else is true.
I’m sorry but framework and library in this post are going to be used loosely, because even React, Vue, Angular, Svelte, etc devs use the terms loosely.
React is mostly a UI library like you would find in most native app development. Of them all them JS frameworks/libraries is one of the less opinionated and with less batteries included. By design it does not does everything. Most other frameworks do way more.
It lets you define custom components. The components can have properties that their parent component defines and internal state. If the state or the properties change the component gets redrawn (magically). There are some lifetime functionalities (things to do on first render for example) and performance improving stuff (memoization) but mostly that’s it.
All the other features you talk about are third party libraries or frameworks that can operate with react or are build on top of and cover the bases, like routing, fetching, caches, server side rendering, styling utility libraries, component libraries, animation libraries, global state management, etc.
The big difference with the vanilla way is that the approach is mostly declarative. The runtime takes charge of updating the DOM when your components state or properties change.
You take a big performance hit, and an even bigger bundle size one, but the speed of development and huge ecosystem of readymade solutions can be really important for some use cases.
Other frameworks take different approaches to solve the same problems:
It’s super funny, but if you don’t try to use things as what they are not, the type coercion can’t hurt you.
But if you make a tradition of trying to add empty objects and numbers…
The great sin of JavaScript is gracefully (silently) failing when coders do silly things.
A tree can be seen as a formal language. Look into L-systems.
If you generalize what a symbol is (the rgb value of a pixel) you can write a grammar that ends producing a list of pixels. You can then place it in a 2d matrix and you have an image.
I guess a better approach would be wave function colapse, but seems to me like it could be formally described as a grammar (CS or CF, dunno, would have to look into it)