I agree, the only reason I can see for TypeScript's existence is that people were coding poorly. Many of the mistakes people claim to have made as a result of dynamic typing, I simply did not make because I learned dynamic first, then static second. Also, it's solved by literally 1 test, and people are touting an extra compilation step with errors to solve that problem. This eco-system is a poisoned-well of bloat, and I'll be redoubling my efforts with Rust to leave it as soon as possible.
What is Typescript providing that you don't get by writing 1 test that checks type and by following modern ECMAScript specs? Does that justify a new syntax? The answer I think is no. I see much praise in this thread, but very little definition of why that praise is merited.
There is no point in Typescript, as new ECMAScript specs provide most of the syntactic sugar and compile-time type checking is obviated by exactly 1 test, which people using it are writing anyway; this is not a compelling use-case for an entirely new syntax, and it needs to die, instead of contributing to the already-bloated ecosystem.
The framework / tooling bloat is causing a bubble to form; it needs to be simplified, now. It can be done cleanly, but SPA often is not. You are correct in your assessment, even though the cargo-cultists will say otherwise. It doesn't need to be thrown out, it needs improved standards, focusing on simplicity, http >= 2, and domain-specific concerns, such as state management, routing, etc. The innovation in the space is mostly over, time to give it an injection of standard and boring. And, for the love of God, can we really not do better than the virtual-DOM for updates? In-memory copies? Really?
So, they're exploiting users in some of the ways banks are, but not all ways currently. Other banks do all of the things listed above already, have been for decades.
Go camping for an extended period of time, where you are squatting over holes in the ground. Squatting is how we shat before toilets, and it's definitely easier, quicker, less stressful on rectum. I don't own one of these, but immediately understood the benefit. Really, since the toilet came after this, the onus of proof is on the sitting toilet. As an interesting side-note, squatting births are purported as being easier as well.
As a side note: myself and the public fully retain the rights to Google's self-driving cars, as my work has created it through answering captchas. We observe our rights through force, if necessary. This is where we're heading.
Alternate title: the front-end sucks now because we have too many options for doing generally the same thing, and they all aren't compatible with each other, but my way, the way I first learned, is best, and something about functional programming even though UIs arbitrarily necessitate or do not necessitate state.
I, personally, place blame on WC3 for this state of affairs, as Web components should have solved the UI interoperability problem, observed objects were dropped which regardless of what one thinks of them (I think a trie is better) would have unified state management clearly (replaced by Proxy? yeah, I see everyone using that string-only thing for state), and various other specs should have solved most of these issues, but I guess they were too busy making people leave their org over DRM, rather than making a useful, consistent, easily-produced internet. Who needs standards when all of the for-profit board members have their own un-interoperable libraries?
Plugin fingerprint protection was removed 3 years ago by a poorly-reasoned patch, favoring the large bug of unimpeded surveillance over the very tiny bug of sites looping through non-existent lists if and only if they need to interact with a plugin. Seeing the conversation, I'm looking for a different browser.
"remove_plugins-enumerable_names.patch
Bug 757726 hid most plugins from navigator.plugins enumeration to reduce fingerprinting. Plugin detection scripts could ask for a plugin or MIME type by name, but they couldn't get a list of all installed plugins. Unfortunately, the feature had to be disabled because it broke pretty much all plugin detection scripts because they naively search for the desired plugin using an O(n) loop instead of a O(1) query.
This patch removes the disabled code because it is unlikely we could ever re-enable it. In addition to removing the obsolete navigator.plugin tests for detecting hidden plugins, it adds tests for detecting click-to-play and disabled plugins."
Yes, it's important to note that the "Right" in Venezuela, aided by the US, is the most likely culprit in these assassination attempts. This is the same "Right" that has a monopoly on certain foodstocks, such as butter and flour and has been stock-piling them, while the US media reports on food shortages as a socialist problem.
Investors need to re-imagine epic games as platforms, a movie that plays for twenty-plus years, iteratively developed. This also tends to collapse genres (markets): the World-of-Warcraft effect, wherein all other games of the genre bleed-out to the big platform. Good if you're the Star Citizen in the room and succeed.
Thank you for that input; yes, the solution is a narrow bridge that has to balance the needs of people who use it as medicine with the potential for addiction (especially in the case of previous opiate dependency). This balancing act, though, gets severely unbalanced in the presence of profit incentives, leading to the media maximization of the addiction potential (or any negative really).
I agree with this; I have witnessed Kratom aid people in quitting opioids, and when used properly as a quitting aid, it could help a great many people, should not be made illegal or placed under regulatory capture, and should be studied and brought into formal treatment. I personally keep some around in the rare instances where I would take ibuprofen or something similar.
In a similar vein, the generic drug tianeptine, prescribed for over 30 years in other countries for depression & anxiety, is now a schedule 2 controlled substance in Michigan (https://www.usnews.com/news/best-states/michigan/articles/20...), one of the major base states for the Johnson & Johnson corp, which studied the substance (https://adisinsight.springer.com/drugs/800039841) entering clinical trails for release here, but was dropped with no reasoning. Before some talking-head chimes in that tianeptine is a μ-opioid receptor, read the atypical part and addiction data in countries where it has been prescribed widely. It is the only drug which effectively treats my depression and anxiety, it is generic so large drug companies cannot make an exorbitant profit off of it, and they are keeping it from the US through media scare-tactics, like Kratom, to ensure their profitability and the reception of their patented drugs like https://en.wikipedia.org/wiki/Esketamine. We should stop them.
I think what we'll see next is something like react rendering to a canvas, beating html rendering & dom manipulation, maybe subsets of the good parts of the DOM, dropping old-cruft support, but all rendered on a canvas. This will, in turn, create framework cults.
The reason companies shouldn't use each other's proprietary code for basic operations: it's insecure, there's little-to-none of your interests being protected.
The new boss: just like the old boss, but gets to have her ivy league friends write sexism articles about her, despite courts with lower burdens of proof (preponderance) finding none.