Long past time to eliminate JavaScript from existence

krisoft 29 minutes ago | parent | next [-]

You will have a long trek to do that. We have a javascript interpreter deployed at the second Sun-Earth Lagrange point.

https://www.theverge.com/2022/8/18/23206110/james-webb-space...

	▲	dgxyz 12 minutes ago \| parent [-]
		I live happily in the knowledge that in 20000 years when that eventually drifts off into another system and is picked up by aliens that they will reverse engineer it and wonder why the fuck '5'-'4'=1

▲

dgxyz 5 hours ago | parent | prev [-]

This.

Actually fuck the whole dynamic web. Just give us hypertext again and build native apps.

Edit: perhaps I shouldn't say this on an VC driven SaaS wankfest forum...

▲

rainingmonkey 4 hours ago | parent | next [-]

You may be interested in https://geminiprotocol.net/

	▲	dgxyz 3 hours ago \| parent [-]
		Yes that's exactly what we should be using. Totally agree.

▲

dlivingston 4 hours ago | parent | prev | next [-]

I mean sure, but that's never going to happen, so complaining about it is just shaking your fist at the sky. The only way it will change is if the economics of the web change. Maybe that is the economics of developer time (it being easier/fast/more resilient and thus cheaper to do native dev), or maybe it is that dynamic scripting leads to such extreme vulnerabilities that ease of deployment/development/consumer usage change the macroeconomics of web deployment enough to shift the scales to local.

But if there's one thing I've learned over the years as a technologist, it's this: the "best technology" is not often the "technology that wins".

Engineering is not done in a vacuum. Indeed, my personal definition of engineering is that it is "constraint-based applied science". Yes, some of those constraints are "VC buxx" wanting to see a return on investment, but even the OSS world has its own set of constraints - often overlapping. Time, labor, existing infrastructure, domain knowledge.

▲

dgxyz 3 hours ago | parent [-]

I think it will change.

The entire web is built on geopolitical stability and cooperation. That is no longer certain. We already have supply chains failing (RAM/storage) meaning that we will be hardware constrained for the foreseeable future. That puts the onus on efficiency and web apps are NOT efficient however we deliver them.

People are also now very concerned about data sovereignty whereas they previously were not. If it's not in your hands or on your computer than it is at risk.

The VC / SaaS / cloud industry is about to get hit very very hard via this and regulation. At that point, it's back to native as delivery is not about being tied to a network control point.

I've been around long enough to see the centralisation and decentralisation cycles. We're heading the other way now

▲

dlivingston 2 hours ago | parent [-]

I think on a high level we're in agreement then. All of those points you mentioned are constraints.

> "VC / SaaS / cloud industry is about to get hit very very hard via ... regulation"

can you explain?

	▲	dgxyz 24 minutes ago \| parent [-]
		Why? Well mostly due to the unpredictable behaviour of the country which seems to have the control points of most infra these days. How? Well the numerous non-US sovereign technology initiatives are going to be incentivised through regulation with local compliance being the only option going forwards. As a non-US person I am already speaking to people at other orgs in similar space as ours who are looking at options there.

▲

streetfighter64 4 hours ago | parent | prev [-]

Imagine if wikipedia was a native app, what this vuln would have caused. I for one prefer using stuff in the browser where at least it's sandboxed. Also, there's nothing stopping you from disabling JS in your browser.

	▲	dgxyz 3 hours ago \| parent [-]
		Wikipedia should be straight hypermedia. Simple.