Live data from Hacker News

An unofficial WWDC app for OS X

github.com

11–20 of 44 posts

Re: An unofficial WWDC app for OS X

#11

So refreshing to see a nice desktop app built without Electron. A well defined interface, designed specifically for the platform the author targeted. Major props to the author!

I am not understanding what all the hype is about "Electron". What does it bring to the table that I can't code myself? So many apps are based upon Electron.

> What does it bring to the table that I can't code myself?

The ability to create reasonably good-looking cross-platform desktop applications using Node.js. Obviously Electron is not much use to you if you're already experienced in the native development kit of your platform, but if your main expertise is Node.js (which is the case for an increasing number of developers), Electron is quite handy.

Re: An unofficial WWDC app for OS X

#12

So refreshing to see a nice desktop app built without Electron. A well defined interface, designed specifically for the platform the author targeted. Major props to the author!

Curious, what do you have against Electron built apps? I feel like the last few apps I've used that were built on Electron actually worked quite nicely. Wondering what you found bad with them...

As a JavaScript developer, I use and don't dislike Electron apps (currently running Atom!) but one thing I do have to say is that they use a lot more battery power and CPU. As much as I like Feross' work, I tried using WebTorrent Desktop[1] but after some hours of running it my Macbook's fans turned on. To me, a torrent client should always sit quietly in the background taking up as little resources as possible.

[1] https://webtorrent.io/desktop

I can imagine it feels worse in older hardware. For an app meant to be used only in one OS, it makes more sense to just go native.

Re: An unofficial WWDC app for OS X

#13

Earlier quoted context omitted.

I am not understanding what all the hype is about "Electron". What does it bring to the table that I can't code myself? So many apps are based upon Electron.

> What does it bring to the table that I can't code myself? The ability to create reasonably good-looking cross-platform desktop applications using Node.js. Obviously Electron is not much use to you if you're already experienced in the native development kit of your platform, but if your main expertise is Node.js (which is the case for an increasing number of developers), Electron is quite handy.

Also, it can conveniently turn your run-of-the-mill XSS bug into remote code execution! Welcome to 2016, everybody.

Re: An unofficial WWDC app for OS X

#14

So refreshing to see a nice desktop app built without Electron. A well defined interface, designed specifically for the platform the author targeted. Major props to the author!

Curious, what do you have against Electron built apps? I feel like the last few apps I've used that were built on Electron actually worked quite nicely. Wondering what you found bad with them...

Their UI feels alien on every platform. The startup time, memory consumption and general performance is subpar to native applications. Generally, I feel like developers who make software for platforms individually care more for user experience. Like this app, for example, it feels polished, uses the native OS X UI elements and performs super fast (much due to Swift in its nature being faster than JavaScript).

I certainly see the point and some use cases for Electron, however I dislike the recent trend of reinventing the wheel of every application using Electron.

Re: An unofficial WWDC app for OS X

#16

Earlier quoted context omitted.

> What does it bring to the table that I can't code myself? The ability to create reasonably good-looking cross-platform desktop applications using Node.js. Obviously Electron is not much use to you if you're already experienced in the native development kit of your platform, but if your main expertise is Node.js (which is the case for an increasing number of developers), Electron is quite handy.

Also, it can conveniently turn your run-of-the-mill XSS bug into remote code execution! Welcome to 2016, everybody.

I am a person who always wanted to develop native desktop applications, but ended up developing for the web instead because the barrier to entry is lower.

Now I have the opportunity to do what I actually wanted to do.

Re: An unofficial WWDC app for OS X

#18

Earlier quoted context omitted.

Also, it can conveniently turn your run-of-the-mill XSS bug into remote code execution! Welcome to 2016, everybody.

I am a person who always wanted to develop native desktop applications, but ended up developing for the web instead because the barrier to entry is lower. Now I have the opportunity to do what I actually wanted to do.

The comment you replied to explains the problem with your logic: the easy creation of apps using Electron exposes nontrivial security issues that will likely not get caught because speed is a priority.

Re: An unofficial WWDC app for OS X

#19

I wish there was an easy way to support projects like this. Click a button? Put a quarter in the tip jar.

Click the link that says "Psst, want me to love you? Then check this out "

I mean in a general sense. I'd pay for all sorts of things I currently get for free — writing, art, software, videos — if it was as easy as clicking a button. Getting out my wallet, entering a credit card number, and going through the payment steps is too much work for a quarter.

Re: An unofficial WWDC app for OS X

#20

So refreshing to see a nice desktop app built without Electron. A well defined interface, designed specifically for the platform the author targeted. Major props to the author!

Curious, what do you have against Electron built apps? I feel like the last few apps I've used that were built on Electron actually worked quite nicely. Wondering what you found bad with them...

Poor native integration; slow; memory hogs; sucks battery life even at idle. Chrome is a battery killer on Mac.
Post reply on HN