News for hackers. Stuff that matters.
Re:Electron 1.0 is here by gbugniot on Wednesday May 11, 2016 @03:47AM (#11673354)
"Electron has lowered the barrier to developing desktop applications". Nope, I don't think so. Perhaps for web developers.

For non-web developers, there are already well-suited technologies to develop desktop applications: Swing, Qt, Cocoa, GTK, WPF/WinRT, and so on. Maybe theses technologies seem less sexy but there are here from the beginning to do that kind of job.

Please, use the right tool for the right job.

Re:Electron 1.0 is here by usaphp on Wednesday May 11, 2016 @04:08AM (#11673440)
Why didn't you quote the full sentence: "Electron has lowered the barrier to developing desktop applications, making it possible for developers to build cross-platform apps using HTML, CSS, and JavaScript"

I don't see anything wrong with that statement, Electron really lowered the barrier of entry by allowing using HTML, CSS and Javascript to build cross platform apps, before you had to learn a new language to make it happen (Swift, QT etc).

> "Please, use the right tool for the right job."

I would rather use a tool that I know and build something functional fast, than spending many months learning new language just to make my app cross platform and losing interest because of that.

Re:Electron 1.0 is here by svink on Wednesday May 11, 2016 @05:36AM (#11673837)
You realize that maybe for someone, C++/QT isn't a new technology but HTML/CSS/JS are? Or neither are new, or both are new? The person who replied to you was right, you are making the assumption that everyone knows the web stack and knows nothing else.

Electron tries to break the same barrier WebForms did but in the opposite direction. Hopefully it turns out better and doesn't result in a bunch of shitty desktop apps like WebForms resulted in a bunch of shitty web sites.

Re:Electron 1.0 is here by kedean on Wednesday May 11, 2016 @11:05AM (#11675980)
In all fairness, that's still a lowered barrier. The barrier is the sum of all parts, if desktop gui dev is easy for systems programmers and really hard for web devs, and this project makes it easy for web devs, then it has objectively lowered the barrier for entry. It doesn't matter if it's still just as hard for systems programmers.
Re:Electron 1.0 is here by rayiner on Wednesday May 11, 2016 @07:51AM (#11674379)
I never thought I'd see something that made Swing seem approachable, but now we have it.
Re:Electron 1.0 is here by gbugniot on Wednesday May 11, 2016 @04:21AM (#11673481)
It's wrong because that tends to persuade developers that there is one tool for every situation.

If you build something functional fast with your favorite tool (not suited for the job), then you will probably spend many months maintaining/hacking your codebase to keep it functional and well designed.

Re:Electron 1.0 is here by usaphp on Wednesday May 11, 2016 @04:37AM (#11673561)
It's still better than spending many months learning new language and not building anything functional at all. I would rather build something functional fast and see if it works and has demand.
Re:Electron 1.0 is here by gbugniot on Wednesday May 11, 2016 @04:43AM (#11673584)
If someone spend many months learning a new language, but still can't be able to build something functional with it, I think he has a bigger problem...
Re:Electron 1.0 is here by efrafa on Wednesday May 11, 2016 @04:52AM (#11673622)
Its more about why would you go spend few months learning something, if you can build it in few days with electron.
Re:Electron 1.0 is here by fredsir on Wednesday May 11, 2016 @05:27AM (#11673789)
Because you can't.

An Electron app is not equal to a native app when it comes to UX and UI. Right off the bat: they require more resources to run, thus making your computer slower, a laptops battery last less on a single charge, and don't look and work like native apps thus requires the user to learn a new paradigm.

So instead of you, the developer, using a couple of months to learn a new paradigm, you put that burden on your users, and end up with something that is a whole lot worse than standard native apps on Mac, Linux and Windows.

If you only have 1 user, that is no hassle, but if you have 5 million users, that is a whole lot of time that a whole lot of users needs to spend collectively because you are lazy and want to ship something fast instead of shipping something great.

And no, I have never tried a great Electron app. I don't think they exist.

Re:Electron 1.0 is here by TeMPOraL on Wednesday May 11, 2016 @07:04AM (#11674174)
> If you only have 1 user, that is no hassle, but if you have 5 million users, that is a whole lot of time that a whole lot of users needs to spend collectively because you are lazy and want to ship something fast instead of shipping something great.

Exactly. That's the externality a lot of software companies nowadays generate.

Re:Electron 1.0 is here by oceanswave on Wednesday May 11, 2016 @09:33AM (#11675076)
"they require more resources to run, thus making your computer slower, a laptops battery last less on a single charge,"

But yet you used a either a browser or the HN mobile app (cordova) to post here... guess that means function > fitness.

Re:Electron 1.0 is here by fredsir on Wednesday May 11, 2016 @01:20PM (#11677215)
That is one browser. Because of work, I also need Slack. That is two.

You get the picture.

Re:Electron 1.0 is here by oceanswave on Wednesday May 11, 2016 @02:07PM (#11677707)
I've also got Outlook open, so that's at least 25.
Re:Electron 1.0 is here by oblio on Wednesday May 11, 2016 @08:29AM (#11674617)
What new paradigm? Almost every computer user out there knows the web paradigm. They use it on every platform.

The barrier to entry for Electron apps is 0, the same as for native apps.

Re:Electron 1.0 is here by fredsir on Wednesday May 11, 2016 @01:18PM (#11677191)
What are you talking about? Are you saying that because someone is adept at browsing Wikipedia or Hacker News, they intuitively know how to use Spotify and Slack and Atom?
Re:Electron 1.0 is here by threatofrain on Wednesday May 11, 2016 @05:34AM (#11673828)
How are you evaluating tool fitness here? The ultimate criteria for fitness are organizational / business goals, and that business or organization may have to juggle various constraints. Electron offers extra flexibility for businesses to make tradeoffs on app performance and size versus engineering cost, and that's its most important value.

At first glance, Electron apps should be more maintainable, not less, because it's one toolset for multiple platforms, which should translate to faster development time and less total cost of maintenance at the tradeoff of app performance and size.

Also, whether an app is difficult to maintain ought owe more whether (1) you have multiple diverse codebases and toolchains to maintain, and (2) that you have a disciplined engineering strategy.

Again, whether or not Electron is the right tool for the job is a business decision based on business constraints.

Re:Electron 1.0 is here by TeMPOraL on Wednesday May 11, 2016 @07:02AM (#11674166)
> How are you evaluating tool fitness here? The ultimate criteria for fitness are organizational / business goals, and that business or organization may have to juggle various constraints

Unfortunately, usability and ergonomics are rarely reflected in business "fitness functions" (hell, even making an actually useful tool rarely is these days, thanks in part to marketing having better ROI than delivering value). Business people take care of business goals, and I think it's our responsibility as developers to make applications that don't suck, whether or not it is reflected in the organizational "fitness function".

Re:Electron 1.0 is here by wjoe on Wednesday May 11, 2016 @05:53AM (#11673902)
It's certainly lowered the barrier of entry for me, and I'm no web developer - my background is mostly back-end Java. Sure, I started out by making websites when I was younger, and a few of my jobs have involved a bit of front end, but I'd be surprised if there are many developers that don't know the basics of HTML, CSS, and JavaScript.

Using web technologies to develop a GUI has been so much easier than learning a new toolkit, or even language. For one thing, some of the options you mentioned are OS specific. There are benefits to OS-native toolkits, but as a one-man team with a small project, the benefits are small and the time investment large. With Electron, I can build on Linux and release for Win/Mac without any concerns.

Qt is the best option of those you mentioned, and I considered it. But I was never great with C++, and learning a whole new markup language (or being tied to Qt Creator) for the UI was an extra barrier for entry. And I've often found that Qt programs don't look or feel right outside of Linux.

Personally, I find developing a UI on HTML/CSS/JS much easier than any desktop UI toolkit I've tried in the past. Updating the UI from the code, and calling code from the UI is s simple, because that's what it was designed to do. And having a browser console makes debugging and trying things so much easier.

I was never a fan of using JS for anything but websites before, but I decided to give Electron a try and I'm a convert. Perhaps there's enough of a speed difference between JS and native code that it would matter for more complex programs, but for my uses I don't notice a difference, thanks to the speed of JS engines now.

Maybe from someone that's starting with no coding knowledge would find Qt and C++ just as easy to pick up as HTML and JS, and certainly a C++ developer would find Qt a better choice. And sure, I don't expect anyone to be able to build Photoshop on top of Electron. But there are plenty of programs that aren't that complex.

While in theory I agree with not using the "new sexy technologies" for the sake of it, and "using the right tool for the job", I don't think that applies here. It works both ways, don't stick with old technologies just because that's what you're used to. What specific benefits do you get from using one of those toolkits for a simple desktop program?

Re:Electron 1.0 is here by bengotow on Wednesday May 11, 2016 @04:13AM (#11673456)
I think it's easy to argue about tools, but take a look at popular desktop apps these days: Slack, Atom, VSCode, Spotify, WhatsApp Desktop... they're all built on Electron or the Chromium Embedded Framework. It seems the community has spoken, and no longer considers Java / Qt the right tool for many jobs.
Re:Electron 1.0 is here by sievebrain on Wednesday May 11, 2016 @05:37AM (#11673842)
Comparing the developer experience between them makes it hard to argue that HTML/CSS/JS are the right tool for building GUI apps. The awkwardness of the web 'platform' is just huge, in comparison, even ignoring the performance issues. Atom and VSCode, for instance, have a long way to go to catch up with the real Visual Studio or IntelliJ.

The real reason you're seeing apps based on Electron these days is that it's easy to hire HTML/CSS developers. That doesn't mean these are good platforms though. I remember when the bulk of apps were being written in Visual Basic because it was easy to hire VB devs (lots of people learned VBA via MS Office).

Re:Electron 1.0 is here by oceanswave on Wednesday May 11, 2016 @03:10PM (#11678288)
"Atom and VSCode, for instance, have a long way to go to catch up with the real Visual Studio or IntelliJ."

You're right. They need to catch up to using 5.8 GB for Visual Studio and 480MB for IntellJ to start. :)

Re:Electron 1.0 is here by royjacobs on Wednesday May 11, 2016 @04:26AM (#11673504)
I think you have a very narrow view of "the community" and what constitutes "popular desktop apps".

What about applications like Photoshop, Premiere, Cubase, Logic? Basically anything that does more than show a couple of editor panes. I'd love to see these kinds of things built in Electron but as far as I can tell this has not happened yet. In these areas languages like C++ and frameworks like Qt are still really really popular. Not to mention embedded development, of course.

Re:Electron 1.0 is here by TeMPOraL on Wednesday May 11, 2016 @07:08AM (#11674186)
> What about applications like Photoshop, Premiere, Cubase, Logic?

That's the difference between toys and tools. Most of the popular applications are toys, and this saddens me a lot personally, because humanity is wasting the potential it has with all that cheap computing available.

> I'd love to see these kinds of things built in Electron but as far as I can tell this has not happened yet.

I don't see it happening any time soon. Web is not meant for serious tools. Compare Microsoft Office and Google's butt office suite. One is a tool, other is a toy that looks nice for simple documents, but is utterly unusable when your document/spreadsheet grows beyond more than a couple of pages.

Re:Electron 1.0 is here by patates on Wednesday May 11, 2016 @08:31AM (#11674641)
> Web is not meant for serious tools. Compare Microsoft Office and Google's butt office suite.

Well, isn't that an ambiguous claim with a weak anecdotal evidence. What is a "serious tool"? We have our email, crm, analytics, (only) shop, document versioning, etc. online. Actually, the native applications I use are just Visual Studio (can be replaced by code), Sql Management Studio (many web-based alternatives) and the browser itself - that being the only type of application I use with no web-based alternative, which could be seen as an operating system.

Re:Electron 1.0 is here by TeMPOraL on Wednesday May 11, 2016 @08:47AM (#11674737)
> Well, isn't that an ambiguous claim with a weak anecdotal evidence.

Try working on a 20-page document or 5-page-long spreadsheet and see how long it takes before you get pissed off at the performance. Unless you're oblivious to it - I'm starting to believe more and more people don't even expect anymore that computers can work without constant lags and pauses.

> the native applications I use are just Visual Studio (can be replaced by code)

Now can it, really?

> Sql Management Studio (many web-based alternatives)

With even remotely similar feature sets?

Re:Electron 1.0 is here by patates on Wednesday May 11, 2016 @09:06AM (#11674883)
We have a giant list of archived support tickets in Office 365. They can be navigated nearly as fast as they can be navigated in native Excel app, through the 365 web app.

I replaced Visual Studio already with Code for my personal projects. I expect it is just a matter of time before companies start to consider doing that too. Is it feature-complete? No, but not because it is an Electron-app, but because it's just young.

SQL Server doesn't work on platforms other than Windows so the motivation for coming-up a feature-complete alternative is little. I could even then find a couple promising projects with a web search. For other databases such as Postgres and Mongo, there are many alternatives which provide more than their native GUIs. Rethink's main GUI is web-based, for example. A database management interface isn't challenging to implement as a web-app because web-apps are limited toys, but it is hard to do right in general.

Re:Electron 1.0 is here by pritambaral on Wednesday May 11, 2016 @05:54PM (#11679652)
SQL Server now runs on Linux.
Re:Electron 1.0 is here by marknutter on Wednesday May 11, 2016 @08:24AM (#11674580)
> That's the difference between toys and tools. Most of the popular applications are toys, and this saddens me a lot personally, because humanity is wasting the potential it has with all that cheap computing available.

I always wonder if pretentious people realize their pretentious and simply don't care, or they're actually oblivious. Perhaps you could enlighten me?

The difference between a "toy" and a "tool" is whether or not something is mainly for fun or mainly for being productive. It has nothing to do with the process used to build it.

Re:Electron 1.0 is here by soundwave106 on Wednesday May 11, 2016 @10:14AM (#11675438)
I think the previous author's point was more on point without using judgement-loaded words like "toy". There certainly are definitely classes of applications where sheer computing complexity or responsiveness probably means that we're a long way off from using web wrapped applications (eg Electron). High end graphics editing, video editing, and music DAWs certainly qualify in this category.

Then again, from what I know, Premiere, Photoshop, and DAWs like Cubase and Logic are straight-up C++ applications, and don't even go into Java / Qt territory.

I would say that something like Google Apps vs Microsoft Office is a lot closer than it used to be. Native-app Excel sheets for instance still have the edge in speed overall, especially for large datasets (say, >10,000 rows) better, and Excel has a pretty significant edge in my opinion for analysis (pivot tables, charts, etc.). Google Sheets however are very capable for a large percentage of documents, with the added benefit of being so much easier to share and collaborate. Neither use case is a "toy" scenario in my opinion.

Re:Electron 1.0 is here by TeMPOraL on Wednesday May 11, 2016 @10:47AM (#11675771)
Maybe I'm conflating several of my issues with webapps in the word "toy". One thing is ergonomics, bloat and lag issues. But the other thing is that webapps trying to fill in the role that originally belonged to desktop apps are more often than not pretty dumbed down. There are several reasons for that - one is performance, which makes you unable to add more complex features without making the entire webapp unbearably slow. Another is the business approach of sticking to MVPs and not really progressing beyond them.

Also, lag issues are not really limited to high-end graphics / video editing. Sure, lag/low performance makes those tasks basically not doable in the browser. But even "ordinary" webapps - like word processors or issue trackers - are annoyingly slow. Take Jira for example - I'm probably wasting a few (billable) hours every month just because it's not a desktop app. So are all of my co-workers. It's most likely also the reason people tend to batch time reporting and do it once a week or so (it's much less distracting then), which as a result precludes management from having access to up-to-date information about time spent on tasks.

Trivial inconveniences can have non-obvious impact.

Re:Electron 1.0 is here by marknutter on Wednesday May 11, 2016 @11:10AM (#11676028)
> Take Jira for example - I'm probably wasting a few (billable) hours every month just because it's not a desktop app.

I think you'll find that Desktop apps often have to communicate with with centralized servers as well.

Re:Electron 1.0 is here by soundwave106 on Wednesday May 11, 2016 @02:20PM (#11677829)
I definitely get what is being said here about web apps feeling slower. I've personally found desktop apps to in general be more responsive / quicker than web apps, and I think it's more than the communication layer. (Actually, I think REST is far more responsive than some of the previous middle tier communication methods used by desktop apps...).

From what I've heard (no in depth knowledge so I welcome corrections), the DOM / CSS model itself really wasn't designed for fast, responsive applications and thus tends to under-perform in that department. So even a fully internal network app with comparable communication speed may seem slower on the browser from the get go.

Many web apps often also tend to be a little bit laggy just based on their cloud based nature. Load a random spreadsheet on Google docs, and you are probably talking 100-200 requests and (depending on your network) perhaps a 5-7 second delay. Change a tab, and you probably have another 2-4 second delay. Compared to the 1 second load time of a spreadsheet and nearly instantaneous tab switching time on a native spreadsheet app, it feels slower... especially for the power users, I'm sure...

Re:Electron 1.0 is here by TeMPOraL on Wednesday May 11, 2016 @11:20AM (#11676104)
Communication overhead (which could be reduced with some additional caching client-side) is not the only source of the lag. User interface is a problem too. Sure, with enough work you may be able to overcome the problem in this (and similar) cases - but web apps are usually developed around a particular style, which involves AJAXing around way too much data way too often.
Re:Electron 1.0 is here by TeMPOraL on Wednesday May 11, 2016 @08:42AM (#11674701)
> I always wonder if pretentious people realize their pretentious and simply don't care, or they're actually oblivious. Perhaps you could enlighten me?

They're just tired and try to highlight some problems that others don't care about.

> The difference between a "toy" and a "tool" is whether or not something is mainly for fun or mainly for being productive. It has nothing to do with the process used to build it.

The difference is the goal - is it supposed to help people be productive at their task, or is it just supposed to make such impression while in fact being there to extract money from naive customers? (Or is it a worse-is-better half-assed 20% solution?). Whether you like it or not, performance is a big part of usefulness of application. I brought up MS Office and Google's cloud-based solutions for a reason - only one of them can handle the load a professional user needs to handle.

Quite often it's literally like a difference between a metal hammer[0] and a plastic one[1]. Both can, in theory, be used to drive nails, but there is kind of a difference in performance.

[0] - https://upload.wikimedia.org/wikipedia/commons/8/84/Claw-ham...

[1] - http://thumbs.dreamstime.com/z/plastic-hammer-2181534.jpg

Re:Electron 1.0 is here by marknutter on Wednesday May 11, 2016 @11:09AM (#11676016)
So what you're saying is, all tools need to be designed for the power user or they're toys. I guess I should return my $10 hammer I bought from Home Depot and replace it with the $225 Stiletto TB15MS solid titanium hammer (http://www.amazon.com/Stiletto-TB15MS-TiBone-Titanium-Straig...).
Re:Electron 1.0 is here by TeMPOraL on Wednesday May 11, 2016 @11:21AM (#11676114)
No, I'm saying that plastic hammers shouldn't be sold in hardware stores, and also that trying to push plastic hammers on normal users and $10 hammers on power users is a very bad trend.
Re:Electron 1.0 is here by wstrange on Wednesday May 11, 2016 @10:11AM (#11675403)
For 99% of business documents, Google Docs works just fine.

Your needs are different, and that is cool - but it does not relegate web apps to "toy" status.

Re:Electron 1.0 is here by TeMPOraL on Wednesday May 11, 2016 @10:39AM (#11675697)
My needs are pretty standard. I run an NGO and have some amount of paperwork and data tracking to do in a word processor and spreadsheet application. Due to the collaboration requirements, we're stuck with Google cloud suite (the choice was made back when there were zero reasonable cloud-enabled alternatives). Google's office suite is theoretically capable of doing most of the things I need[0], but the omnipresent lag when you try to work with a bigger document or (more often) several documents at once is very annoying and slows things down. Half a second here, five seconds there, and it all adds up to significant frustration.

There's a significant difference between "theoretically X can be done with it" and "it is useful for doing X". You can drive nails with a plastic hammer after all (and most people don't even need the "additional" feature of pulling them out).

[0] - which is partly because I reduce expectations of what I can do. Think of it as generalized Blub paradox - you think in terms of the tools you use. Get a better tool, and suddenly you can do more, do it better and do it faster.

Re:Electron 1.0 is here by enraged_camel on Wednesday May 11, 2016 @09:19AM (#11674966)
Meh. Microsoft Office pisses me off more with its constant crashes and weird bugs than Google Docs does. The latter has less functionality, but at least it's stable. Not to mention the vast majority of users don't need the advanced functionality anyway. If you're doing serious publishing work, sure, go ahead and use MS office. But 90% of common use cases are easily satisfied with Google Docs.
Re:Electron 1.0 is here by TeMPOraL on Wednesday May 11, 2016 @10:28AM (#11675578)
> Microsoft Office pisses me off more with its constant crashes and weird bugs than Google Docs does.

Crashes / weird bugs and MS Office... that's something new to me. I always considered MS Office to be a set of some of the most stable applications I've ever seen. Do you do something atypical, so that the bugs/crashes could be related to a platform or some rarely used features? I'm asking out of curiosity.

Google Docs et al. don't just lack advanced functionality, they lack a lot of quite basic functionality too. But my point wrt. webapps is also one of ergonomics. I do a lot of work in Google Docs and Spreadsheets due to external reasons, and I absolutely hate the experience. No matter how fast a computer I use, the lag on the Google's office suite is very annoying and distracting. Like with some IDEs which are slow enough to make one unable to ever enter the state of flow, Google's spreadsheets routinely double the time I am spending on a task due to simple lag on almost every operation.

Re:Electron 1.0 is here by enraged_camel on Wednesday May 11, 2016 @04:48PM (#11679125)
>>Do you do something atypical, so that the bugs/crashes could be related to a platform or some rarely used features? I'm asking out of curiosity.

Not that I can tell. I mean I run it inside a Windows 7 VM, but other than that, nothing atypical.

One example of a bug that I can think of (because it happens consistently) is that Outlook 2013 taskbar icon shows the orange envelope to indicate that I have unread mail... when I don't have any. It drives me absolutely bonkers. I've also ran into more serious issues, for example yesterday when I pasted something from a web page into MS Word and it froze and crashed.

Re:Electron 1.0 is here by blub on Wednesday May 11, 2016 @05:24AM (#11673773)
The world development community is a weee bit larger than five. Neither is text editor and wrapper for a website "many jobs" ;)

I've seen many complaints about Spotify on e.g. Reddit - specifically about the fact that it's no longer native. Seen also many complaints about bloat and slowness in Atom & VScode.

I understand why this toolkit is chosen, but companies can only push so much before the customers also push back against the decrease in qulity.

Re:Electron 1.0 is here by wiz21 on Wednesday May 11, 2016 @02:59PM (#11678185)
I love your comment. But it basically says something else : programming is a lot about fashion. And nowadays, HTML/JS/CSS is fashionable and Qt is not anymore.

Everybody can yell that Qt/Gtk or even the MS stuff is the better tool for desktop apps, it won't change anything.

There's 0 objectivity in the choice. The young boys just think in HTML/JS, so we'd better adapt :-)

Re:Electron 1.0 is here by gbugniot on Wednesday May 11, 2016 @04:25AM (#11673495)
So tell when a Photoshop, a real Visual Studio, a SolidWorks, or any big/professional software written with Electron-like tech will be out there.
Re:Electron 1.0 is here by albeva on Wednesday May 11, 2016 @05:13AM (#11673716)
Atom and VSCode despite all the hype are subpar editors. Slow and resource hungry. Maybe suitable for script kiddies of today ... Slack is by no means a good sample of solid engineering. Spotify last I checked was native app written in c++. What's App is just wrapped website.
Re:Electron 1.0 is here by ntlve on Wednesday May 11, 2016 @07:53AM (#11674388)
Spotify used to be fully native, nowadays the UI is done in various web technologies while the heavy lifting (streaming audio etc) is done in c++.
Re:Electron 1.0 is here by svink on Wednesday May 11, 2016 @05:15AM (#11673730)
Your examples kind of prove the opposite point, these are not ALL popular apps, they are just popular "toy" apps. You weren't able to give a single example of a popular major application.
Re:Electron 1.0 is here by BHSPitMonkey on Wednesday May 11, 2016 @05:35AM (#11673833)
How exactly are Atom and Code "toy applications"?
Re:Electron 1.0 is here by royjacobs on Wednesday May 11, 2016 @05:45AM (#11673875)
They are vastly less complex than other applications listed here (e.g. Photoshop).
Re:Electron 1.0 is here by patates on Wednesday May 11, 2016 @08:37AM (#11674670)
There are many web based ERPs and CRMs, some of which are way, way more complex than Photoshop. Given one has access to their algorithms, I don't see why Photoshop would be impossible to implement on top of WebGL. Photoshop UI doesn't have the "native feel" anyway. I think it's just a matter of time until Adobe comes with a 90% feature-complete web-based PS.
Re:Electron 1.0 is here by royjacobs on Wednesday May 11, 2016 @09:36AM (#11675096)
I'm sorry I wasn't more clear but I'm not talking just about the UI. It's also being able to give realtime feedback and do hugely CPU consuming tasks, which is essentially the core of Photoshop.

Can you give examples of ERPs or CRMs that are "way, way more complex than Photoshop" though? It would be nice to be able to compare.

Re:Electron 1.0 is here by svink on Wednesday May 11, 2016 @06:22AM (#11674025)
By "toy" I don't mean that their purpose is necessarily entertainment, but that the difficulty of building them is not comparable to many popular desktop apps - the list is not representative. Like building a toy plane vs a real plane - the difficulty, not the purpose. Major computer games are not "toy apps" in this sense. Sorry if I was unclear.
Re:Electron 1.0 is here by spiderfarmer on Wednesday May 11, 2016 @04:06AM (#11673432)
As as webdeveloper, I am now starting to think about desktop applications, where I would have ignored the platform before.

It's not at all about how sexy a technology or framework is. I just think I can do a better job in a framework that's adapted to my skillset, instead of adapting myself to a new framework.

Re:Electron 1.0 is here by dagw on Wednesday May 11, 2016 @06:10AM (#11673969)
I'm someone who's cut his teeth developing desktop apps the 'old' way and came rather late to the whole modern web-development thing. And I have to say that going zero to a good enough prototype app is dramatically easier with web based stuff in most cases. Sure going from good enough to a polished high performing product can often be a massive pain, but that's a different story.
Re:Electron 1.0 is here by mattmanser on Wednesday May 11, 2016 @06:28AM (#11674049)
It didn't used to be that way.

You used to be able to use Delphi or VB6 to make working desktop apps in very short times. I'm sure other will reminisce about other older desktop techs that were a breeze to use.

MS severely dropped the ball with WPF by making it have a very high learning curve just when javascript was really exploding. So not only was it easier to distribute web apps, they were cross platform and it was easier to make them too (although the massive pain of SPAs has changed that).

There was also Adobe Flash Builder that very briefly looked like it would be a competitor when Balsamiq was a big new thing, but it never really took off (only other thing I've seen use it is salesforce's SOQL tool). At that point everyone hated Adobe though, so it didn't have much chance.

Re:Electron 1.0 is here by dagw on Wednesday May 11, 2016 @06:38AM (#11674096)
Yea, for all the flack VB gets, it was pretty amazing. VB4 was what got me from writing silly little scripts for my own amusement to writing applications that could actually be used for something.
Re:Electron 1.0 is here by rtpg on Wednesday May 11, 2016 @04:16AM (#11673469)
Honestly, at this point, HTML + associated frameworks like React/Angular are more mature for a lot of UI development than Qt is. Well, if you buy into the FRP/stateless UI things anyways.

Though interface builders help a lot, I've always had a problem building more dynamic interfaces through any of the native tools. React, for example, makes that a lot easier.

Re:Electron 1.0 is here by blub on Wednesday May 11, 2016 @05:32AM (#11673821)
How can something that's ~3 years old be more mature than something that's 20 years old? Even QML is 7 years old at this point and that is reactive.

Try to stay at least a little bit realistic...

Re:Electron 1.0 is here by rtpg on Wednesday May 11, 2016 @10:00AM (#11675321)
Mature and old are not the same thing. I don't think TkInter is stronger than React +Electron for building stable, large apps despite the large age difference.

One thing is that React is the newest iteration of production-quality declarative UI management. Angular, Backbone, a lot of stuff came bdfore. And all that contributes to a mature understanding

That being said, I forgot about QT quick. That is also pretty powerful stuff. Though the web influence seems there ( correct me if the causality is wrong).

Re:Electron 1.0 is here by albeva on Wednesday May 11, 2016 @05:19AM (#11673754)
While I consider web-tech in native a cancer I can't help, but agree. There is no good cross platform native UI library today. Few that are are stuck in 90s metaphor or poorly designed. Which I think is partly the reason why html-css-js is spreading everywhere.
Re:Electron 1.0 is here by sievebrain on Wednesday May 11, 2016 @05:42AM (#11673867)
Which ones have you tried?

I ask because I quite like JavaFX. The developer/documentation website is fusty and old-fashioned looking, but the tech itself is just really solid. You can tell it's been made by people who have spent their whole careers doing UI toolkits.

Re:Electron 1.0 is here by based2 on Saturday May 14, 2016 @06:13AM (#11695414)
Re:Electron 1.0 is here by Kiro on Wednesday May 11, 2016 @06:48AM (#11674118)
If it has become easier for web developers to create desktop applications the statement still holds.
Re:Electron 1.0 is here by serge2k on Wednesday May 11, 2016 @04:05AM (#11673429)
> Please, use the right tool for the right job.

Which part of Electron makes it wrong?