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)
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.
Python for excel, grafana for Bi?
I guess depends of your use case.
It’s funny how computers are almost the only human invention that for some reason must be able to be used without learning anything.
We don’t do that for almost anything else. We expect people to learn how to drive, how to fill taxes, how to buy things on the store, how to cook, how to play chess. It seems like the only cases when someone decides learning stuff is an inconvenience is when tech people get into another field and tries to disrupt it.
I am all about making things as simple as they can be, but not simpler. Intuitive is a super relative term that depends on your knowledge and life experience. People find Office intuitive after using it for twenty years, but for me is a nightmare where legacy features intermingle with weird cloud and AI shit, and most of the time I only need a markdown file. No interface is intuitive, they are only familiar, clear, accesible, discovereable, etc.
Interface Design goes in cycles of skeuomorphism and simplification because computer stuff is not Intuitive, you have to open the way with metaphors people can understand, and when they are part of everyday life you can make the app for the virtual credit cards not look like it’s made of leather.
Refresh speed, font rendering, integrated features like multiplexing, theming…
So why would anyone hate Denuvo? Nobody is forcing you to play Denuvo-using games. It was your choice.
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:
Corps need a self destruct mechanism for when they get out of control.
Maybe is time to leave Fedora (and Nobara) behind. Not really feeling that great right now doing free testing for Red Hat, having so many alternatives.
I know it’s a joke, but it’s an old one and it doesn’t make a lot of sense in this day and age.
Why are you comparing null to numbers? Shouldn’t you be assuring your values are valid first? Why are you using the “cast everything to the type you see fit and compare” operator?
Other languages would simply fail. Once more JavaScript greatest sin is not throwing an exception when you ask it to do things that don’t make sense.
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.
Yeah, writing prompts it’s the long term goal, programming will be obsolete.
Nobody that can write a problem in a structured language, taking edge cases into account, will be able to write a prompt for a LLM.
Prompt writers will be the useful professionals, because NO big tech company is trying to make it obsolete making AI ubiquitous and transparent, aiming it to work for natural language requests made by normal users or simply from context clues. /s
Prompt engineering it’s the griftiest side of the latest AI summer. Look a who is selling the courses. The same people that sold crypto courses, metaverse courses, Amazon dropship store courses…