I completely agree. I taught JS/TS for 5yrs and I always emphasised that the ‘class’ keyword was just syntactic sugar for what was already available in prototype inheritance of JS.
I completely agree. I taught JS/TS for 5yrs and I always emphasised that the ‘class’ keyword was just syntactic sugar for what was already available in prototype inheritance of JS.
Huh? I’ve worked with TypeScript + React for the last 5yrs and the only time I see OOP is when someone’s done something wrong.
Maybe you’re thinking of old react with class based components?
You know Dropbox? Google drive? OneDrive? That’s file synchronisation. Files across multiple devices kept in sync by the software provider. Except in the named cases above, all your data is uploaded to their servers. With syncthing there’s no cloud server, just your devices operating over the internet. So you have some backup responsibility to cover.
Caveat: I’ve never used syncthing and I wrote the above with a total of 10 seconds of reading their website and so it is entirely possible I’m completely wrong about everything and so I emplore you to do your research.
Thankfully the only interaction I have with teams is when a supplier arranges the call. Once every two weeks. It grosses me out every time…and that’s the Web app.
Do you really think they have done such optimisation efforts as minimising function calls? I can’t imagine it’s required for what is actually a fairly simple frontend app. The complexity is the enabling stack on the backend.
Something has gone horribly wrong if you’re trying to do such optimisations when you’ve already chosen JavaScript…let alone Electron.
Why would you be using JS in this scenario?
Yeah the US differs by a couple of weeks iirc