> Note: Since we do not in any way modify the code of Qt and only link to it dynamically, I beleive we are in compliance with the LGPL license requirements of QT. And hence this library can be licensed under its own License (for which we have chosen MIT License). The links to QT source code and appropriate license notices are attached. We try our best to abide by the software licenses and any non compliance is not by will. If there is some discrepancy please let us know in the issues and we will try and fix it up. If you follow the recommended build steps and do not statically link QT libraries on your own you are safe to use this library for commerical puropses (provided you abide by MIT License).
Anyone familiar with licensing, is the author's note here correct, and can we use NodeGUI just like any other MIT libraries, eg. bundling the GUI part for distribution?
1. To use it in a closed-sourced application you have to keep the Qt libraries dynamically linked and bundled with the application. The license is fine as long as it is dynamically linked.
2. Static linking however requires you to either purchase a commercial license or you release your source under GPL-3.0 and then you can statically link your app.
...except everyone is sitting at desks typing, there's no blood or surf rock or chases or self-indulgent soliloquies, and the cursing is much less creative?
I'm curious why Google doesn't sell its Chromebooks in Europe? Is it because of some EU regulations or it's just Google that's not willing to expand its Chromebook territory here? I can definitely see the market here.
I agree that the web platform is kind of messed up, but web apps are just so accessible and convenient...
For essential apps, I believe most people would always prefer native versions. They are more convenient that way. (I don't want my local media player to be a tab in Chrome.) People generally are not using Google Docs because they are robust or feature packed. They use them because they could just load it up in a few seconds on a new machine, with nothing to install and everything synced in the cloud.
Actually, I think if there is a platform which allows users to run ANY apps with just one click, it has to be a platform just like the web we have right now. Sure, if JavaScript were not made in a hurry, we could have got a lot of efforts spared - but dialects and attempts to “reimagine” and "personalize" our weapons are still going to show up, maybe just like all those frameworks and workflows we have right now. (Seriously, why are there so many NATIVE UI libraries? So many OS's? So many NATIVE programming languages?)
Yes, we ARE reinventing the wheels, but for a good reason - accessibility. All apps from every generation do similar things: typing docs, filling in spreadsheets, instant messaging, playing music... In fact, humans ALWAYS have done similar things - they wrote stuff and kept lists long before MS Office came along. The web is an upgrade, thanks to the better computing power we have to allow "inefficient" non-native rendering nowadays. The "native" apps we have now can do their fancy new 2017 stuff. Maybe soon we will have full blown AutoCAD as a web version. Many native apps we have today are almost awesome enough - the natural tendency would be to make them more accessible.
A bit off-topic but I wonder if it is possible that Electron team distribute something like the VS C++ Runtimes on Windows? And release patches for different versions/updates?
Haven't used a Windows machine for a while but I remember there were bunches of different VS Runtime version installed on my PC before. Some app installers came with a runtime installer, but if the required runtime version was installed it would just use that one. I think this might somewhat reduce the installed app size for Electron apps as at least some stuff got reused.
You can approximate this somewhat today by distributing only an .asar or .zip archive of an application package and encouraging:
npm install -g electron
electron ./myapp
Or as npx gets more widely deployed:
npx electron ./myapp
That's not a particularly "robust" way to install applications and you can't use native libraries outside of the base Electron distribution, and you'd mostly only be useful to devs with NodeJS already installed, but it's an option of a sort.
(It still won't share as much runtime memory as you might want, but it would reduce install footprints at least.)
There's also experiments like electrino [1] to force more use of platform webviews since all of our platforms have a webview built in anyway, trading some additional testing for bundling Chromium everywhere.
I'm surprised that I haven't yet seen a fork of electron-windows-store [2] that makes use of the UWP webview, as that seems an obvious enhancement to me. The Electron remoting between webviews and Electron code is already setup well enough you should be able to run the Node app as a UWP background app and use UWP remoting.
I second this. Linear Algebra Done Right is an awesome book. It also comes with a helpful selection of exercises after each chapter with detailed answers available on the website, which is great for self-learners. If you are a student and your Uni has a Springer subscription, you might be able to get the PDF for free.
A new "made by Google" Chromebook codenamed "Eve" is rumored to be unveiled on the Oct 4 Google event. If the rumor is true then I think Google is now really paying more attention to the laptop market, and the whole Chrome OS ecosystem is very likely to get more mature in the near future. I would love to see JetBrains tools running natively on Chrome OS one day.
Oh, they are definitely paying more attention to the laptop market. They partnered with Samsung recently to make Chromebook Plus/Pro models, and the ARM version came with a strange 6-core processor only described as, 'OP1.'
It looks like it's a Rockchip with two Cortex-A72s, four Cortex-A53s, and a recent Mali GPU. But the 'OP' branding is apparently an attempt by Google to brand or designate ARM chips that have certain peripherals, performance-enhancing features, and support for ChromeOS stuff.
I was surprised how good the Samsung Chromebook (ARM version) was - it worked decently well, ran pretty much all Android apps I tested (which filled the gaps in ChromeOS very well!) and the stylus was useful for notetatking.
It sounds reasonable. More thinking that Microsoft Windows and notebooks don't get along and have plenty of issues. This makes competition easier. If Chrome OS is well integrated with the hardware that makes a difference abd follows the Apple route.
I hope it does more than simply ChromeOS... the $200 dollar beaters are fine for what ChromeOS is. There are very few reasons to buy a "Chromebook Pixel" in 2017... unless it does something more than Chrome.
You should have included another functionality to check the current date, like, it should stop spreading and just delete itself if it's already in April. ;)
Good thought :)
When I put out the first version, I haven't really understood the consequences or its effectiveness; In fact it had my code name in the greeting :(
When it first appeared, people found it amusing; but it quickly went out of control and kept appearing again and again. This annoyed people. I was in trouble. I had to quickly find a solution in that panic.
Anyone familiar with licensing, is the author's note here correct, and can we use NodeGUI just like any other MIT libraries, eg. bundling the GUI part for distribution?