51–60 of 68 posts
I keep an IRC client (Colloquy for OSX) open everyday when I get home from work. However, it crashes a few times a day and I think it's about time to switch. Is this a suitable replacement for Colloquy? Any recommendations on a better IRC client to use, web-based or OSX, are much appreciated. Thanks!
Earlier quoted context omitted.
Building things with js, css, html, takes much less time than writing the same thing in objective-c. Also, way easier to build cross platform.
Not sure why anyone interested in writing a cross-platform application would even think of Objective-C. You must be an OSX user. Just as one example, Komanda could've been done with Python and any of the variety of cross-platform GUI toolkits available for that language. It would run everywhere, faster, using native widgets, and in a language designed for the desktop.
If I am lazy and I write in Python 2.7 are you sure you can run my code on your Python 3.4 branch without using 2to3 tool?
Are you sure all the GUI library will work on every popular platform (Windows XP, Vista, 7, 8, Mac OSX 10.6+, Ubuntu 10-14, Arch, never mind all XDE, KDE, GNOME, XFCE, etc dealing with native widget???) I really don't think the development experience would be as seamlessly as you think.
Earlier quoted context omitted.
Building things with js, css, html, takes much less time than writing the same thing in objective-c. Also, way easier to build cross platform.
Not sure why anyone interested in writing a cross-platform application would even think of Objective-C. You must be an OSX user. Just as one example, Komanda could've been done with Python and any of the variety of cross-platform GUI toolkits available for that language. It would run everywhere, faster, using native widgets, and in a language designed for the desktop.
It's beyond me why anyone would write a desktop application in JS, CSS, and HTML, and require node as a dependency. These technologies are already bastard children of the 'just make it work' mentality. Using them for an environment they were never designed for, when there is decades of existing infrastructure purpose-built (and far easier to use), makes no sense. The only reason that I can come up with for why someon…
Node - for node-webkit, I believe. As for the general question - why use web technologies for desktop app, I think it's like "Qt for those who don't want to use C++". Cross-platform GUI toolkit. As someone who used Qt extensively in the past I don't see a lot of value in using web technologies to develop desktop apps, unless there's a plan to use the same codebase on the real web. But it's just me.
I'm currently building a desktop application for work, and this is the reason we've got with node-webkit -- we are using the same code-base for a client side web application with slightly different uses. Being able to do so is quite a boon, to be honest, and is cutting down dev time dramatically.
Earlier quoted context omitted.
Not sure why anyone interested in writing a cross-platform application would even think of Objective-C. You must be an OSX user. Just as one example, Komanda could've been done with Python and any of the variety of cross-platform GUI toolkits available for that language. It would run everywhere, faster, using native widgets, and in a language designed for the desktop.
Python is not faster than Node.
The OP saying the app will run faster is not refuted even if NodeJS runs some things faster than Python.
It's beyond me why anyone would write a desktop application in JS, CSS, and HTML, and require node as a dependency. These technologies are already bastard children of the 'just make it work' mentality. Using them for an environment they were never designed for, when there is decades of existing infrastructure purpose-built (and far easier to use), makes no sense. The only reason that I can come up with for why someon…
In the end, optimization forces operating at levels beyond our comprehension and ability to fully model will determine whether or not this project sees continued development. Personal lives, adcademic interest, social proliferation of memes, economic constraints...all serve as inputs. Don't force an outcome like this. You might damage the author's impetus to try again with more ambition in the future. Let nature run its course; you may occasionally find yourself surprised by the outcome.
In general, it is pointless to rationalize your choices to the rest of the world, which frankly doesn't put as much effort into listening as you might think.
Sorry if I come across as rude. I just think this could be better framed as constructive criticism.
Earlier quoted context omitted.
Building things with js, css, html, takes much less time than writing the same thing in objective-c. Also, way easier to build cross platform.
Not sure why anyone interested in writing a cross-platform application would even think of Objective-C. You must be an OSX user. Just as one example, Komanda could've been done with Python and any of the variety of cross-platform GUI toolkits available for that language. It would run everywhere, faster, using native widgets, and in a language designed for the desktop.
Python is probably the worst choice you could make for a desktop application.
If you're recommending it, you're either trolling, or you have no idea what you're talking about.
Earlier quoted context omitted.
Python is not faster than Node.
Perhaps not, but he didn't say that. There is more than just language at play in this scenario. Will a native widget, initiated by Python, out perform JS/CSS/Node-Webkit ... maybe. The OP saying the app will run faster is not refuted even if NodeJS runs some things faster than Python.
I use it daily and at my job, and it's flat out slower than node for desktop applications.
(caveat; the pypy isn't as bad, but it has a terrible start up time and no widget libraries worth talking about)
It's beyond me why anyone would write a desktop application in JS, CSS, and HTML, and require node as a dependency. These technologies are already bastard children of the 'just make it work' mentality. Using them for an environment they were never designed for, when there is decades of existing infrastructure purpose-built (and far easier to use), makes no sense. The only reason that I can come up with for why someon…
It's beyond me why anyone would write a desktop application in JS, CSS, and HTML, and require node as a dependency. These technologies are already bastard children of the 'just make it work' mentality. Using them for an environment they were never designed for, when there is decades of existing infrastructure purpose-built (and far easier to use), makes no sense. The only reason that I can come up with for why someon…
This kind of elitism is what turns so many people off about technology. What if these are kids that are building this? Do you care so much about your view that you would want to shut them down? Not everyone has the time or interest in learning systems programming or C/C++. In the end, optimization forces operating at levels beyond our comprehension and ability to fully model will determine whether or not this project…
Hacker News is a place where people discuss technology. Opinion is inherent in discussion. I don't apologize for anything I wrote.