Knusper

joined 2 years ago
[–] [email protected] 21 points 1 year ago (2 children)

What kind of shit senior devs are you working with?

[–] [email protected] 27 points 1 year ago (1 children)

If you're incapable of building a secure service, maybe you shouldn't be routing people's camera feeds through that service.

[–] [email protected] 41 points 1 year ago (1 children)

Well, customers will sometimes ask for certain solutions to be used. Solutions for problems they don't have...

[–] [email protected] 2 points 1 year ago

Yep, that's the framework, I'm using, too. But most frameworks in the Rust ecosystem can do DOM interop, as the heavy lifting for that is provided by the wasm-bindgen library.

[–] [email protected] 0 points 1 year ago

They're not that dumb, to just pull it completely. That would obviously result in a successful fork.

Companies usually start with e.g. the BUSL, so source-available but proprietary restrictions.
For TypeScript/Microsoft, I could imagine some variation of their EEE playbook.

But really, the whole point of avoiding Microsoft et al, is that I don't want to think about, how they could fuck this whole thing up. They've proven quite creative in this regard for as long as they've existed.

[–] [email protected] 3 points 1 year ago (1 children)

"Omnibar" is Chrome's naming, though. Firefox's component is technically called "Awesomebar", although most folks do just call it "address bar", "URL bar", "nav bar" etc..

[–] [email protected] -2 points 1 year ago (2 children)

If it's dumped under an open-source license, but still developed exclusively by one corporation, they can swap out that license pretty easily.

[–] [email protected] 7 points 1 year ago (2 children)

You can have frameworks which fully generate the JS DOM code for you, allowing you to write complete single-page applications without writing a single line of JS.

[–] [email protected] 10 points 1 year ago

No, but GUI frameworks can generate it for you. Same goes for DOM access, for which there's normally only a JavaScript API.

So, you'll likely want to read JS, when researching what events or properties you can read/write for certain HTML nodes in the DOM, but with a mature GUI framework, you should not need to write any JS.

[–] [email protected] 6 points 1 year ago

They used to be more attractive around the 2000s, before type inference became commonplace and when IDEs/editors were still a lot less powerful.

As for making a dynamically typed language, to my knowledge, they are actually easier to create than statically typed languages...

[–] [email protected] 46 points 1 year ago (4 children)

I once read about a study, which genuinely found the sex drive of women lowered, if they need to care for their partner like a small child.
Their theory was that the relationship transitions from romantic love to maternal love, and mothers just don't tend to find their children sexy...

[–] [email protected] 69 points 1 year ago (8 children)

I'm choosing the third side: WebAssembly

view more: ‹ prev next ›