I've never had a robo call in my life. I don't live in America. I don't know the laws in my country, but the problem just does not exist here. I've had the occasional (like once every 2 years) have a random person call me regarding a survey or trying to sell me something.
Iâ(TM)ve been a long time Android user and was dismayed by all the manufacturer environmental records. Apple rate along side the Fairphone (https://www.greenpeace.org/usa/reports/greener-electronics-2017/) on Greenpeaceâ(TM)s guide to green electronics. Apple is definitely not a perfect corporate citizen, but there are some things they are doing much better than the rest.
It's Switzerland (at least when I was last there) it's legal to download copyrighted material as long as you're not uploading it and you're using it for private purposes.
They are not all the same thing, but they have components which are similar, like overlapping circles in a Venn diagram.
DevOps is the result of Lean IT. If you need to make things such as release cycles go faster, then you will end up with automation of manual and repetitive tasks, hence DevOps.
Lean IT is largely about reducing waste. So if you reduce the size of the development cycle, you reduce the likelihood of a large amount waste occurring. From that comes Agile, small bite-size chucks of work. Although lean IT is not just about development.
I started with Debian back as my primary desktop in 1998, but have been using different flavours of Ubuntu since it arrived. Currently using Ubuntu GNOME have used Xubuntu extensively too. Keep up the good work. Although, I have tried Debian again and may go back if the Ubuntu experience does not get better (unlikely).
Biggest gripe is the state of screen rendering on Linux. Wayland is so important to get going.
Web Browser: Firefox for personal stuff, Chrome for work.
Email Client: Gmail for work and personal.
Terminal: Tilix recently, but Terminator for sometime before that.
IDE: Atom (if you call that an IDE), sometimes Eclipse or WebStorm.
File manager: midnight commander, then default gnome.
Basic Text Editor: vim.
IRC/Messaging Client: web based clients only.
PDF Reader: default gnome.
Office Suite: Libre office, then Google Docs.
Calendar: Google Calendar, integration with Gnome using online accounts.
Video Player: vlc.
Music Player: Rhymbox.
Photo Viewer: Default Gnome, gThumb.
Screen recording: For snapshots default Gnome app, for videos I use recordMyDesktop.
I've been running Linux almost exclusively for almost 20 years on my primary desktop. I've tried many many desktop environments, but I've come back to GNOME 3 and I actually really like it... once I got used to it. It's not cluttered, it's one of the most polished DE's available and relatively bug free. There are a few small issues, but not nearly as much as other DEs.
I've been using Linux for almost 20 years (I'm old you see). I suggest some flavour of Ubuntu, either Ubuntu itself, Xubuntu (it's light), Gnome Ubuntu (it's what I run) or Mint (although I was never really happy with this when I used it.... quite some time ago)
Actually I grew up with C, Pascal, Assembly (for many different processors), C++, then learned and taught Java at University. I enjoyed Matlab, Mathematica, Python and Fortran while studying Physics. Now I've landed on JavaScript and if you avoid the ugly bits, it's fun.
This is a discussion about platforms that would buckle under the bulk of a micro-OS and a JS interpreter/VM stack. And that's not even handling the issue that most of these devices use embedded hardware platforms that you need to access with specific assembler calls - how would you do that in JS or Python!?
Most mods will probably flag this as trolling. But I believe JavaScript is a great language for IoT. There are a few advantages of using JavaScript, it's actually very easy to get networking to work well and reliably. A programmer will be able to write front-end, server-side/less back-end and IoT back-end all in one language. The code will be portable across all these bases (not always needed, but some functions will be universal). There are now a proliferation of embedded devices that support JavaScript "natively" (ESP32, RedBear Duo, and many more). It might not be as fast as C, but it's fast enough.
Here is a project I created using JavaScript at every level: https://www.hackster.io/anemoi...
Good point. The reason I like to use JS everywhere is that I only need to learn one language. And it means I can learn it really well. Until I did full-stack JavaScript I had only done front-end JS and it was pretty wonky. Using Node.js means that you need to learn some of the great parts of JS well (closures, async, etc). This drastically improved my front-end JS. If you used the LAMP method for full stack development, you would need to learn Apache config (although once it's running it's okay), PHP, JavaScript and SQL, and I would not have the time to learn the subtleties of each language.
I agree that the object model and patterns for MongoDB are different, the object mode and patterns for front-end and back-end are very similar in many cases, there is a big overlap. Things you use on all three are:
- Callbacks
- Closures
- Prototypical inheritance (front-end and back-end)
- Event emitters (front-end and back-end)
- And many more like described here: https://www.smashingmagazine.c...
Code re-usability is useful at times, I was able to write a library (https://github.com/psiphi75/web-remote-control) that was used on the server, on the front-end and on an embedded device and I guess around 80% of the code is shared across all three. Imagine writing and debugging that code in three different languages.
I dove straight into Node.js to develop a platform around 3 years, I don't regret using Node.js, in fact I am glad that I used it. I essentially used the MEAN stack (MongoDB, Express, Angular and Node.js). It was great to: 1) use JS everywhere: back-end (including the DB) and front-end. 2) use JS: it's fun (for me) - if you use the right parts. And it performs fast enough, on par with PHP, if not faster. 3) have an experienced community - JS and Node.js has gone through it's teething issues already. 4) do async programming - if you do it right, you tend to keep your code more modular.
What was painful: 1) Learning to write JS the "right way" and how to avoid the bad and ugly parts. 2) At the time there was no great CMS, I believe Keystone is the best at the moment, but it looks very light when compared to Wordpress.
What you need to do if you go with Node.js: 1) Learn JS well, learn "The Good, The Bad and The Ugly", such that you can avoid the Bad and Ugly. The good is actually awesome. 2) Understand prototypical inheritance, it's not your classical classes, but it a powerful and memory efficient way create objects. 3) Use a linter to write your code, like eslint, it will help you avoid the bad and ugly parts.
I still use Node.js today, but now for the Internet of Things and my embedded device runs Node.js. JS is everywhere and it's going to remain everywhere.
Taking the numbers at face value you get the following stats:
- with 4000 developers
- 2.7 lines of code added per day per developer
- 1.3 lines of code removed per day per developer
- 0.47 lines of code changed per day per developer
Not only that, the disc pads on a vehicle are very small compared with the fuel burned. Imagine a 0.1kg brake pad that lasts 200,000km verses 160'000 Litres of fuel burned over the same distance.
Electric and hybrid cars use regenerative breaking, such that when the driver brakes lightly the car will use the electric motor as a generator and recharge the battery, hence the braking emissions would be largely reduced. Heavy breaking will use the disc brakes as well as regenerative braking at the same time, so there will be some emissions then, but still less than classical vehicles.
I reply to my own post to ask another question, because the context is relevant.
Are there any solutions / techniques out there that simplify driver installation and configuration in Linux / Ubuntu? I am ask just in-case I am missing it.
I have been using Linux since the good old days of the late 90's. I was using Debian until Ubuntu came around in 2004 and switched. Ubuntu was amazing in terms of how it made Linux more usable. However, as time went along Ubuntu was no longer so cutting edge and no longer resonated with me, so I have switched back to Debian. Anyway, all this time as a Linux user it's been a rough ride, every laptop I have purchased (I haven't had a desktop for 15 years) has had issues with Linux. Most common issues for me are that wi-fi drivers don't work and graphics card drivers are unstable. I choose Laptops that are going to give me the least problems by researching them thoroughly beforehand. The most recent laptop (HP ProBook) came with the option of having SUSE Linux installed by default, I thought this would be perfect, but the wi-fi did not work unless you had the correct version of SUSE installed. I am experienced at debugging and resolving issues, a new user would require a lot of patience, technical no-how just to get Linux functioning before they can use their PC. Although you can use Linux without the console, it is difficult to never have to go to the console. The console requires a paradigm shift for many users. In a nutshell the first hurdle for Linux is a massive jump, and only few are brave/curious enough to take it.
So my question is: What support channels would you recommend for new Linux users?
About a year ago I completed the Weka Mooc (https://weka.waikato.ac.nz/explorer). Weka is an opensource machine learning / data mining tool that has many different machine learning tools and algorithms.
The mooc part is the course. It was free at the time I did it, but I don't know if it still is. The mooc is run by an experienced machine learning professor. Weka is also maintained and developed in the same department as his.
I highly recommend this course, it was informative, gave me a grasp of machine learning, as well as experience of a popular tool (weka). I was also able to complete it in my own time while working full time and having a family.
Slashdot Mirror
I've never had a robo call in my life. I don't live in America. I don't know the laws in my country, but the problem just does not exist here. I've had the occasional (like once every 2 years) have a random person call me regarding a survey or trying to sell me something.
I have to say that this finding has made the whole system more secure. This is difficult to say for closed source systems.
Iâ(TM)ve been a long time Android user and was dismayed by all the manufacturer environmental records. Apple rate along side the Fairphone (https://www.greenpeace.org/usa/reports/greener-electronics-2017/) on Greenpeaceâ(TM)s guide to green electronics. Apple is definitely not a perfect corporate citizen, but there are some things they are doing much better than the rest.
It's Switzerland (at least when I was last there) it's legal to download copyrighted material as long as you're not uploading it and you're using it for private purposes.
They are not all the same thing, but they have components which are similar, like overlapping circles in a Venn diagram. DevOps is the result of Lean IT. If you need to make things such as release cycles go faster, then you will end up with automation of manual and repetitive tasks, hence DevOps. Lean IT is largely about reducing waste. So if you reduce the size of the development cycle, you reduce the likelihood of a large amount waste occurring. From that comes Agile, small bite-size chucks of work. Although lean IT is not just about development.
I started with Debian back as my primary desktop in 1998, but have been using different flavours of Ubuntu since it arrived. Currently using Ubuntu GNOME have used Xubuntu extensively too. Keep up the good work. Although, I have tried Debian again and may go back if the Ubuntu experience does not get better (unlikely). Biggest gripe is the state of screen rendering on Linux. Wayland is so important to get going. Web Browser: Firefox for personal stuff, Chrome for work. Email Client: Gmail for work and personal. Terminal: Tilix recently, but Terminator for sometime before that. IDE: Atom (if you call that an IDE), sometimes Eclipse or WebStorm. File manager: midnight commander, then default gnome. Basic Text Editor: vim. IRC/Messaging Client: web based clients only. PDF Reader: default gnome. Office Suite: Libre office, then Google Docs. Calendar: Google Calendar, integration with Gnome using online accounts. Video Player: vlc. Music Player: Rhymbox. Photo Viewer: Default Gnome, gThumb. Screen recording: For snapshots default Gnome app, for videos I use recordMyDesktop.
I've been running Linux almost exclusively for almost 20 years on my primary desktop. I've tried many many desktop environments, but I've come back to GNOME 3 and I actually really like it... once I got used to it. It's not cluttered, it's one of the most polished DE's available and relatively bug free. There are a few small issues, but not nearly as much as other DEs.
I've been using Linux for almost 20 years (I'm old you see). I suggest some flavour of Ubuntu, either Ubuntu itself, Xubuntu (it's light), Gnome Ubuntu (it's what I run) or Mint (although I was never really happy with this when I used it.... quite some time ago)
Actually I grew up with C, Pascal, Assembly (for many different processors), C++, then learned and taught Java at University. I enjoyed Matlab, Mathematica, Python and Fortran while studying Physics. Now I've landed on JavaScript and if you avoid the ugly bits, it's fun.
Or even javascript and C: http://jsish.sourceforge.net/
Duktape is along a similar line: http://duktape.org/
This is a discussion about platforms that would buckle under the bulk of a micro-OS and a JS interpreter/VM stack. And that's not even handling the issue that most of these devices use embedded hardware platforms that you need to access with specific assembler calls - how would you do that in JS or Python!?
There are a few JavaScript interpreters that use very minimal resources and have access to all the necessary hardware (wifi, BLE, SPI, UART, i2c, etc), these are Duktape http://duktape.org/, Espruino https://github.com/espruino/Es..., JerryScript https://github.com/jerryscript..., and more. These are all designed for IoT devices. For performance this is an interesting read: https://www.espruino.com/Perfo...
Most mods will probably flag this as trolling. But I believe JavaScript is a great language for IoT. There are a few advantages of using JavaScript, it's actually very easy to get networking to work well and reliably. A programmer will be able to write front-end, server-side/less back-end and IoT back-end all in one language. The code will be portable across all these bases (not always needed, but some functions will be universal). There are now a proliferation of embedded devices that support JavaScript "natively" (ESP32, RedBear Duo, and many more). It might not be as fast as C, but it's fast enough. Here is a project I created using JavaScript at every level: https://www.hackster.io/anemoi...
And there is the opensource https://farmbot.io/
My bot is better than your bot, it got an extra 0.453% discount.
After using Linux for 18 or so years, I think it's time to switch back to Windows..... actually, nah.
Woot! Next they will be paying people for their operating system.
Good point. The reason I like to use JS everywhere is that I only need to learn one language. And it means I can learn it really well. Until I did full-stack JavaScript I had only done front-end JS and it was pretty wonky. Using Node.js means that you need to learn some of the great parts of JS well (closures, async, etc). This drastically improved my front-end JS. If you used the LAMP method for full stack development, you would need to learn Apache config (although once it's running it's okay), PHP, JavaScript and SQL, and I would not have the time to learn the subtleties of each language.
I agree that the object model and patterns for MongoDB are different, the object mode and patterns for front-end and back-end are very similar in many cases, there is a big overlap. Things you use on all three are:
- Callbacks
- Closures
- Prototypical inheritance (front-end and back-end)
- Event emitters (front-end and back-end)
- And many more like described here: https://www.smashingmagazine.c...
Code re-usability is useful at times, I was able to write a library (https://github.com/psiphi75/web-remote-control) that was used on the server, on the front-end and on an embedded device and I guess around 80% of the code is shared across all three. Imagine writing and debugging that code in three different languages.
I dove straight into Node.js to develop a platform around 3 years, I don't regret using Node.js, in fact I am glad that I used it. I essentially used the MEAN stack (MongoDB, Express, Angular and Node.js). It was great to:
1) use JS everywhere: back-end (including the DB) and front-end.
2) use JS: it's fun (for me) - if you use the right parts. And it performs fast enough, on par with PHP, if not faster.
3) have an experienced community - JS and Node.js has gone through it's teething issues already.
4) do async programming - if you do it right, you tend to keep your code more modular.
What was painful:
1) Learning to write JS the "right way" and how to avoid the bad and ugly parts.
2) At the time there was no great CMS, I believe Keystone is the best at the moment, but it looks very light when compared to Wordpress.
What you need to do if you go with Node.js:
1) Learn JS well, learn "The Good, The Bad and The Ugly", such that you can avoid the Bad and Ugly. The good is actually awesome.
2) Understand prototypical inheritance, it's not your classical classes, but it a powerful and memory efficient way create objects.
3) Use a linter to write your code, like eslint, it will help you avoid the bad and ugly parts.
I still use Node.js today, but now for the Internet of Things and my embedded device runs Node.js. JS is everywhere and it's going to remain everywhere.
Taking the numbers at face value you get the following stats:
- with 4000 developers
- 2.7 lines of code added per day per developer
- 1.3 lines of code removed per day per developer
- 0.47 lines of code changed per day per developer
Thanks for pointing out the typos. My spelin is bahd at the best of tymes.
Not only that, the disc pads on a vehicle are very small compared with the fuel burned. Imagine a 0.1kg brake pad that lasts 200,000km verses 160'000 Litres of fuel burned over the same distance.
Electric and hybrid cars use regenerative breaking, such that when the driver brakes lightly the car will use the electric motor as a generator and recharge the battery, hence the braking emissions would be largely reduced. Heavy breaking will use the disc brakes as well as regenerative braking at the same time, so there will be some emissions then, but still less than classical vehicles.
I reply to my own post to ask another question, because the context is relevant.
Are there any solutions / techniques out there that simplify driver installation and configuration in Linux / Ubuntu? I am ask just in-case I am missing it.
I have been using Linux since the good old days of the late 90's. I was using Debian until Ubuntu came around in 2004 and switched. Ubuntu was amazing in terms of how it made Linux more usable. However, as time went along Ubuntu was no longer so cutting edge and no longer resonated with me, so I have switched back to Debian. Anyway, all this time as a Linux user it's been a rough ride, every laptop I have purchased (I haven't had a desktop for 15 years) has had issues with Linux. Most common issues for me are that wi-fi drivers don't work and graphics card drivers are unstable. I choose Laptops that are going to give me the least problems by researching them thoroughly beforehand. The most recent laptop (HP ProBook) came with the option of having SUSE Linux installed by default, I thought this would be perfect, but the wi-fi did not work unless you had the correct version of SUSE installed. I am experienced at debugging and resolving issues, a new user would require a lot of patience, technical no-how just to get Linux functioning before they can use their PC. Although you can use Linux without the console, it is difficult to never have to go to the console. The console requires a paradigm shift for many users. In a nutshell the first hurdle for Linux is a massive jump, and only few are brave/curious enough to take it.
So my question is: What support channels would you recommend for new Linux users?
About a year ago I completed the Weka Mooc (https://weka.waikato.ac.nz/explorer). Weka is an opensource machine learning / data mining tool that has many different machine learning tools and algorithms.
The mooc part is the course. It was free at the time I did it, but I don't know if it still is. The mooc is run by an experienced machine learning professor. Weka is also maintained and developed in the same department as his.
I highly recommend this course, it was informative, gave me a grasp of machine learning, as well as experience of a popular tool (weka). I was also able to complete it in my own time while working full time and having a family.