So no, a new UI toolkit is not going to revive Java in the mainstream.
452 karma · joined July 6, 2021
So no, a new UI toolkit is not going to revive Java in the mainstream.
All that being said: i think that censorship does way more harm than whatever nonsense these channels put out.
Yes, economic sanctions have limited potential to actually topple a totalitarian leadership. With Russia, the concern goes deeper. This country is armed to the teeth and poses a massive threat to Europe. Hence, the point of these sanctions is very much to also weaken the Russian economy and curb its capacity to finance more wars.
For the record: Nobody with a sane state of mind believes that the Russian people are “evil” or guilty of their leadership’s atrocities in Ukraine. They just happen to be the subjects of an authoritarian government and an onslaught of propaganda. At best, one could say that far too many are complicit and too few stand up to Putin. But admittedly, it’s a tough ask for people to protest a government that murders journalists and poisons opposition politicians.
Or it’s simply that deep voices mean a larger pharynx, which is a proxy for more testosterone.
For me, coffee isn’t only the welcome stimulant in the morning. It’s also childhood memories of the smell of Sunday morning breakfast at my grandparents’ place.
But anyway, I think you confuse my point: the very fact that threading isn't fully covered by the core wasm programming model, but relies on a "hybrid" approach where the embedder needs to plug in those capabilities is a problem. Before wasm, I used Google's PNaCl quite heavily, which didn't suffer this problem and was fully self-contained.
Like the inability of interact with the DOM (or other browser APIs) without calling out to JavaScript.
Or the fact that you had to split up the code on your side into a JavaScript part (these days, perhaps transpiled from Typescript) and a part that was Java code then and is now Rust or C/C++ in case of WebAssembly. It goes without saying that these are very different developer experiences with virtually no overlap in toolchains and programming languages.
Oh and of course even WebAssembly suffers from browser fragmentation. Not only will performance be different, depending on whether you run your wasm module in Chrome, Safari or Firefox. These browsers do also not implement the same feature set (atop the basic wasm MVP). Like Safari doesn’t have SIMD. Other important additions (like tail calls, garbage collection and others) are also not yet universally supported.
For the sake of WebAssembly I do hope that they’ve learned their lessons from why Java applets (and Silverlight, Flash, PNaCl) all failed.
Then there is the plain fact that it requires a compilation step, which is OK for large apps. But it makes me wonder if wasm really is the natural replacement for JavaScript in serverless cloud apps (aka “FaaS”).
So yes, WebAssembly has potential and is almost without an alternative for in-browser apps that do some heavy compute. But I am less convinced about server-side. Time and again, we’re told how great portability across architectures supposedly is. And time and again, the only cloud architecture that matters is x86-64. Maybe ARM or even RISC-V in some cases, but let’s not fool ourselves about these niche platforms.
But I guess very little counts as exercising (like talking a walk).
I totally get the performance argument. That’s why I will never use a Java-based IDE again. Like JetBrains IDEs are just painfully slow where every key stroke has this additional lag before something appears on screen. But thankfully VSCode isn’t like that. Whatever upside another editor might be offering wouldn’t make much of a difference for me.
I fear that the days of native productivity apps are over.
Re exposing an entire database of static content: again, reality gets in the way. Websites want to keep control over how they present their data. Not to mention that many news sites segregate their content as public and paywalled. Making raw content available as a structured and query able database may work for the likes of Wikipedia or arxiv.org. But it’ll not likely going to be adopted by commercial sites.
The question is rather: would the US step up and put pressure on the French if events would unfold in this way?
Honestly, AirTags invading on people’s privacy are the latest fad. And as with any story about the dangers of “Big Tech”, they make for good headlines. Only that nobody bothers to do some basic due diligence on the truthfulness of these reports in the first place. This one is littered with nonsensical facts that makes me not believe in this story for a second.
Which has nothing to do with the fact that there is indeed abuse potential with Apple’s AirTags.
So no, this story doesn’t line up and looks more like cheap attention grabbing at the expensive of a real problem with Apple’s AirTags.
Hence, legislation shouldn’t target individual companies, but “features” that harm people or lead to bad outcomes for society at large. One such example is Europe’s GDPR, which imposes some fundamental limitations on what companies can and cannot do with their users’ personal data. And as negative consequences of poor social media design becomes more apparent, legislators must expand on that and ban more of the malicious practices that are at fault.
It may take time for the US to deliberately damage national champions like Facebook and Google. Other countries will be less patient to act. I cannot imagine democratically elected governments idly standing by as Facebook drags their people into a dystopian Metaverse where there’s no more escaping the misinformation and manipulation that’s already rampant on current-generation social media platforms.
Once again though, the FSF makes “free software” less relevant and harder to use. Who will want to use such software for anything when being threatened with costly litigation and bad press?