401–410 of 505 posts
I wish someone would take a web renderer, took the Javascript away, made a native react-like library for it, and made a universal interface to it so any language could use it. That would finally fix the problem with the UI building issue, while allowing flexible language access. That would be the best of both worlds.
Earlier quoted context omitted.
Sad for who? Yes and a long time ago Sun came out with Swing. How did that work out? Even before that MS came out with P-Code and the abomination that was Word 6 for the Mac.
Sad for developers. What I had in mind regarding desktop were big tools like Blender, Photoshop, Blender, IntelliJ IDEs, which existed long before Electron. I think it clearly shows that complex UI apps require cross platform UI, or will remain single platform (Xcode, Visual Studio).
Earlier quoted context omitted.
I think the top comment should offer a solution, not only a critique. This dependency graph includes the development environment, which I feel is an unfair assessment. Why not re-run with only the production dependencies?
No, thats a logical fallacy. critiques don’t need to provide solutions. It does not make the critique any less valid. This sentiment gets brought up so often here, I really don’t understand the reasoning behind it.
Earlier quoted context omitted.
I remember when Spotify 'upgraded' from a native to a js application on MacOS. It bricked my wife's computer. She never installed Spotify again. This is someone who doesn't usually care about software. She did care about that annoyance.
It works fine for hundreds of millions of other users
Earlier quoted context omitted.
Slack: usually ~300MiB of RAM for one account. The Ripcord [1] Slack/Discord client written in C++ and Qt: currently using 33MiB. Qt is not the native toolkit on Windows/Mac, but Qt apps typically follow platform conventions far better than Electron apps. This also voids the argument "we need Electron, because it reduces development costs, and we can get truly cross-platform apps". Ripcord is written by a single indi…
People don’t care. The vast majority of people don’t ever use their computers for anything heavy, so it’s not like saving a few hundred mb of ram is going to be noticeable for them. It’d be nice to have a lighter, more performant app but if the cost is that it looks like what you posted (no offence to the dev of ripcord; IMO qt and gtk stuff always just looks super outdated) then I’d bet most people would prefer the…
They will definitely notice. E.g. baseline MacBooks (which is probably what most people outside developers buy) still come with 8GB RAM. If you subtract the OS, video memory, and some disk caching. There is not that much left on modern macOS (or Windows).
Having Slack + Skype in the background and some tabs open with modern web sites/applications can easily much a few GBs of RAM, slowing down quite a lot of 8GB machines. I guess most developers just don't notice, because their employer give them development machines with 16 or 32GB RAM.
People don’t care.
They don't care because they don't understand. They will just believe that their computers are slow and that they have to throw more money at it. Or they just buy an iPad and it will feel fast, because Apple does not allow every application to ship and run its own web browser.
no offence to the dev of ripcord; IMO qt and gtk stuff always just looks super outdated
That's because the developer decided to use their own theme. I have made a few Qt apps and on macOS and Windows you can barely distinguish them from a native app, unless you know where to look. Fully agree with Gtk+ though, it does not follow platform styling and conventions and is very slow on macOS (don't know about Windows).
Earlier quoted context omitted.
Sad for developers. What I had in mind regarding desktop were big tools like Blender, Photoshop, Blender, IntelliJ IDEs, which existed long before Electron. I think it clearly shows that complex UI apps require cross platform UI, or will remain single platform (Xcode, Visual Studio).
I don't think Microsoft is worried about Visual Studio being single platform, if the platform is Windows.
I can copy couple of dlls in a project folder, and run npm / yarn install, but that is the most I am willing to do.
So, my question is: is there a VS Code / npm only demo?
As an ex-windows developer, turned react dev - I am excited.
While personally I dislike React Native in the strongest terms possible for the number of nigh impossible to debug technical issues it has brought the projects that tried to tame it, there is a really interesting moment happening here. Microsoft is embracing Facebook's cross-platform tools to eventually compete with Google's cross-platform Electron. Microsoft currently relies on Google for the internals of VS Code, G…
V8, Chromium and Blink are an Open Source projects that Google is one of the main contributors to, but they're not 'Google'. If Google went away tomorrow, V8, Chromium and Blink would still exist, and Microsoft would be able to use all projects.
We do pretty complex stuff with RN as does Facebook and it's been serving us well. I don't know why someone would want to use it with Windows, but this tells how far the project has gotten.
I would love to developed native, but you just save a lot (maybe half) time using RN if you need the app for both platforms.
Earlier quoted context omitted.
I had the same experience. Expo is wonderful for prototyping and quick iteration. The ability to use Snacks online and see them working on the phone is great. But beyond that everything in RN feels hacky and unfinished. While working with it I had some silly issues with Metro, and found some subtle bugs in Text and Button components. About the "Native" part. I think that a lot of people have the expectation that doin…
I had the opposite experience actually. Expo made it difficult to accomplish anything with their ever changing sdk and (what felt like) never ending version deprecations and I found sooner or later for any serious project one would inevitably need to eject. As of RN 0.60 it has been completely smooth sailing developing a react native app sans expo IMO