6,940 karma · joined December 27, 2012
"Some people tell me it's inconsistent with human nature to operate this way--that people need to be protected from harsh truths and that such a system could never work in practice. Our experience--and our success--have proven them wrong."
That is from Principles by Ray Dalio about sensitive people being confronted with radical honesty.
Our Wasm investigations started in August 2020, when we built some prototypes to compare the performance of Wasm VMs and JavaScript VMs in simulations involving the type of work our low-level JavaScript components were doing. In those experiments, code written in Rust and compiled to Wasm was 10 to 25 times as fast as JavaScript.
For video processing, especially high fidelity, high frequency, and high resolution video, I can see WASM crushing JavaScript performance by orders of magnitude. But, that isn’t this. They are just launching an app.
I have verified in my own personal application that I can achieve superior performance and response times in a GUI compared to nearly identical interfaces provided by the OS on the desktop.
There are some caveats though.
First, rendering in the browser is offloaded to the GPU so performance improvements attributed to interfaces in the browser are largely a reflection of proper hardware configurations on new hardware. The better the hardware the better a browser interface can perform compared to a desktop equivalent and I suspect the inverse to also be true.
Second, performance improvements in the browser apply only up to a threshold. In my performance testing on my best hardware that threshold is somewhere between 30000 to 50000 nodes rendered from a single instance. I am not a hardware guy but I suspect this could be due to a combination of JavaScript being single threaded and memory allocation designed for speed in a garbage collected logical VM opposed to allocated for efficiency.
Third, the developers actually have to know what they are doing. This is the most important factor for performance and all the hardware improvements in the world won’t compensate. There are two APIs to render any interface in the browser: canvas and the DOM. Each have different limitations. The primary interface is the DOM which is more memory intense but requires far less from the CPU/GPU, so the DOM can scale to a higher quantity of nodes without breaking a sweat but without cool stuff like animation.
There are only a few ways to modify the DOM. Most performance variations come from reading the DOM. In most cases, but not all, the fastest access comes from the old static methods like getElementById, getElementsByTagName, and getElementsByClassName. Other access approaches are faster only when there is not a static method equivalent, such as querying elements by attribute.
The most common and preferred means of DOM access are querySelectors which are incredibly slow. The performance difference can be as large as 250,000x in Firefox. Modern frameworks tend to make this slower by supplying additional layers of abstraction and unnecessarily executing querySelectors with unnecessary repetition.
* Sunset on Nov 2018.
* Support and compatibility from other MS products for IE terminated in Nov 2020.
* Security support terminated 15 June 2022.
Employment route:
Learn React. Then React stuff like Next.js, GraphQL, Redux, and whatever. Your code will be short, declarative, and possibly OOP.
Actually build stuff route:
Avoid all the bullshit. You don’t need it. This work takes practice but it isn’t that hard if you can actually program.
Avoid OOP where possible. It buys you nothing in JavaScript and will make your code much larger. Simply don’t use this keyword. Get cozy with functions and the concept of functions as first class citizens (they can go anywhere and contain anything).
You can write code with interactions faster than OS desktop equivalents with JavaScript in the browser (presuming the latest hardware and drawing less than 50,000 nodes simultaneously) if you know what you are doing. Get cozy with the DOM, especially the old static methods. Everything else is sugar on top of it. Query selectors are slow. The DOM is a tree so walking that tree requires a formal appreciation of node relationships and your code will be highly imperative.
Understand events. Event handlers receive an implicit event object that probably contains everything you need. With a thorough understanding of events and custom event declarations you can write user interaction automation.
Return key on a control in a form will fire a submit event. Check for cursor position in your submit handler.
The one event that cannot be automated is cursor movement/position. Put a check into your event handlers that check that the cursor is actually over the event target.
A uniform minimal accepted standard and ethics. Excuses against licensing generally arise from people who don’t understand it from a lack of experience, an argument from ignorance.
https://www.logicallyfallacious.com/cgi-bin/uy/webpages.cgi?...
There are two options of leet code: some compound algorithm that you would never use in production coded live or homework conducted over 4-6 hours on your own time. Given the extreme subjectivity of software hiring I am not inclined to do either. The homework approach is far more practical and realistic but is a complete waste of time. Never do hiring homework without grading criteria supplied in advance.
There are far more effective ways of assessing competence with simple cognitive exercises unless you are in an area of software that doesn’t primarily favor competence, such as preferences towards tools.
Other crafts define their professionalism according to a standard baseline defined by governance and credentials. Examples of credentials are licenses and certifications. Examples of other crafts that require credentials: medicine, law, engineering, flying, driving, real estate, information security, networking, food preparation, education, public securities, and many more. When this is brought up in software the result is excuses and whining, hardly an indication of maturity.
The problems with the industries exaggerated immaturity result in profuse subjectivity. There is always a perception, at hiring, that software developers are rare. Perhaps poorly trained or developed less than desired expectations but software developers are not rare. Nonetheless the problem is exaggerated in a cycle of attempts to increase availability among an undesirable candidate pool by abstracting away many challenges inherent to the practice. This is cyclical because instead of bridging a training or development gap it instead breeds entitlement and insecurity that is paid forward. Since there are no industry standards of acceptable practice this cycle becomes a race to the bottom.
This is the very essence of young.
This is the compelling motivator of decentralization.
Decentralization isn't blockchain, web3, or whatever. Blockchain is third party storage.
In a decentralization scheme data resides at destinations. Nobody owns it but the destinations. Nobody observes it but destinations. There is no third party censorship.
The only users that have to suffer third party censorship are influencers and broadcasters who don't want decentralization.
But… you can only do that so many times. Eventually you will conquer those performance pressures as well and need something more. I used to dread boredom and the slow pace of other peoples inefficiencies but now I find comfort appreciating the relaxed life.
Why? Fixed assets exist outside the supply/demand cycle of high school economics. You can’t make more land but you can always build more houses irrespective of demand. Aside from conjecture and speculation there is no evidence (data) linking house price reduction (not rent) to new housing availability.
I suspect the deviation would most largely result from the parameters of a given test itself. Redefining the test content, subject matter, test environments, conditions, and/or other factors may grow or shrink that gap. If that is so there is cause for research to determine why certain test factors are preferential and if removing such preferential factors does/does not result in higher quality student performance.
https://www.archives.gov/federal-register/constitution/artic...
So, if as a politician you want to amend the constitution it needs to be that figurative hill you are willing to die on, everything else be damned, and have sufficient leverage to ensure other politicians don’t have to suffer your early career death.
I have had many software job interviews that were illegal. Most of that were interviewers asking about my familial status because parents are perceived as more dependent upon the employment with less mobility and spouses are perceived as more stable and less likely to commit inter-personnel policy violations. I just disclose the requested information.
If you actually are a senior manager you should already know this is illegal.
* Objective
* Analytical
* Humble
* Focused
People who qualify according to that list are perceived as more intelligent irrespective of actual intelligence confirming selective biases from others.
So despite how you wish to define the technology there exists maximum centralization.
SSH is not the web. The web is HTTP.