178 karma · joined December 7, 2022
https://en.wikipedia.org/wiki/Quine_(computing)#Ouroboros_pr...
[1]: https://en.wikipedia.org/wiki/Hand_with_Reflecting_Sphere
[2]: https://en.wikipedia.org/wiki/Three_Spheres_II
[3]: https://en.wikipedia.org/wiki/Still_Life_with_Spherical_Mirr...
The browser add-on is unfortunately not open source and I don't want to spend a lot of time to investigate it. According an earlier issue (#1437), they should have fixed it already. I guess the later envolvements changed that.
I agree with you that what DOMPurify does should be cared of by the Browser.
They said in previous posts that they are using `DOMPurify` to sanitize the code, but it turns out that it did not work well.
Prof. Elias Wegert, the author who actively contributes to these calendars, also wrote Visual Complex Functions: An Introduction with Phase Portraits[1].
The life is more complex because of the muddled and complex intellectual frameworks. This is because the 3-5 letter word concepts need to be defined to make sure everybody is talking about the same thing when people have to interact with more people.
Most of the arguments can be seen as overthinking. This is how we make our life worse.
It includes 12 visualizations of selected complex functions and their background and related mathematicians. I would highly recommend reading them. Prof. Dr. Elias Wegert, the author who actively contributes to this calendar, also wrote Visual Complex Functions: An Introduction with Phase Portraits which is mentioned by another comment here.
[1]: https://blogs.hrz.tu-freiberg.de/mathekalender/english/
Edit: Navigate to the german page if you want to buy it
EDIT: I was wrong. See comments.
Does anyone have any suggestions?
But the browser evolves:
- Convenient and flexible browser APIs totally replaced jQuery
- HTTP2 HPACK, multiplexing and connection coalescing make SPA and bundlers unnecessary
- Web Component and Shadow DOMs helps you write modular HTML and CSS
etc etc
And developer needs to evolve, too! These frameworks make too many leaky abstractions that developers should think about. It turns out if they don't encounter problems at the beginning, they will meet them later with interest.
I was going to write a similar document, but thankfully you write it so well!
P.S. I'm also not against the framework to solve engineering problems like testing or CI/CD.
It is a framework, but just vanilla :)
Apps nowadays don't need a manual because they have very low density of information and very low density of functions. Engineers who refuse to maneuver anything without reading the manual first becomes rare. This is not completely bad because it means the living condition of engineers improved.