You must log in or register to comment.
Lol, server side JavaScript far predates nodejs.
Do you mean Rhino? This is the first time I come across it and the fact that it’s written in Java completes a full circle of hell
Ha, yeah that’s one I remember using. I believe there were other implementations of interpreting javascript on the server. LiveWire, maybe? It’s been so long since I even attempted it, honestly. I will say, nodejs is clearly far superior to them all, especially with how lean a nodejs service runs on the server.
I get these vibes when WASM introduced C# to the frontend via Blazor.
Feels wrong. Feels like it shouldn’t be possible.
But binaries on the frontend are so. cot. dayum. fast
Blazor has been my favourite framework to do my side projects in for the past couple years now.
While I love it and use it wherever I can, TBF it’s mainly a frontend technology for people who are stronger in the .NET stack than the JS/TS ecosystem. The latter is miles ahead on tooling, size of the ecosystem and the pace of innovation/improvement.
Hasn’t this been the case for a looong time?
All I see is haters.
Cries in Polkit
- argv_minus_one ( @argv_minus_one@beehaw.org ) 1•11 months ago
Out of curiosity, which language would you prefer Polkit policies be written in?
Tbh I wouldn’t use languages but rather chainable configurations. Those could be yaml, JSON, toml etc.
I really dislike running any dynamic code for those things. I mean you really only need rbac providers and/or auth providers.
Maybe I underestimate Polkit by a far at the current state, but the 2 times I used it could have been a config file.
- argv_minus_one ( @argv_minus_one@beehaw.org ) 2•11 months ago
That’s how polkit used to work. It was changed, presumably because the old system was excessively complex and inflexible. Arbitrary code is the correct solution when the set of potentially needed behaviors is unbounded, which in this case it is.
Another example of this is CSS. The vast majority of its features today—shadow effects, filter effects, animations, layout modes, even text colors—could have been implemented with WebAssembly and shaders. Instead, all of this stuff is implemented by the browser, and as a result, there are only three browser engines, two of them are on life support, and there is zero hope of meaningful competition among browsers ever arising again.
Let’s not overcomplicate polkit, please. It’s more than enough of an attack surface already.
Everyone wants to removed about JavaScript. How about using languages like Python and Java to create websites? You have to use an entire bloated framework and compilation just to be able to use a language that was never intended to be used for websites. Java web frameworks are atrocious.
The experience of using these JS frameworks is not comparable to using Java or Python as if they were PHP. There’s tangible (and monetary) benefits to using web tool for the web.
Right. JavaScript is a web tool and is used for the web. The other two I mentioned are not, yet they don’t get anywhere near the same amount of hate as JavaScript does. We get it, JavaScript has loose typing and was primarily a scripting language 30 years ago. Things change. JavaScript is a robust language capable of OOP now, and you can even add typing if that’s your hangup