Python is a great replacement for bash with much better library and testing support. How many horrible bash scripts have you seen? I promise that with Python they can be far better.
However, I'm not actually a huge fan of dynamic languages, because there are a whole class of bugs that the compiler can't catch.
So, I love Python, but I don't use it for anything too large.
UK citizens that are already living in the EU (and vice-versa) get to stay with the original rules from when they moved, but future migrants will have to play by the new rules.
Similarly, if you are a UK citizen legally living in the EU, I'm sure that they will let you keep your EU domain.
I don't see the problem (as a UK citizen that would have voted against Brexit but couldn't because I've been overseas for more than 10 years).
I've been on both sides of the Dev/QA divide. I'm strongly in the camp that developers should be responsible for writing automated (possibly unit) tests of their own code. However, before the code is shipped to the customer QA should have a go. It is way too easy for a lazy or even well meaning developer to ship something out of spec.
Having the developer do all their own QA is like letting the prosecutor also be your defense attorney. It's patently and obviously wrong.
You can say "we practice continuous deployment" without saying "to production servers." CI/CD is about your development branch never getting so shitty that the average engineer can't do meaningful work on it. Or, the other thing that used to happen: make a bunch of components and then try to stitch them together at the end; act surprised when nothing works.
Seriously, we have the protocol. We also have 12 competing standards from 12 different walled gardens, the only one that added anything of value being Signal.
I assume that the RAM is soldered to the motherboard? What Wi-Fi module are you using? These would be good things to add to the website. Either way I am happy to see this in the marketplace. I'm typing this on a Dell XPS 13 but not everyone has $950 to spend on a laptop.
I loved my Nexus 4, I liked my Nexus 5. I couldn't figure out why to upgrade to a 5X. I will never buy a Pixel while an iPhone SE is $400 (that is, approximately as much as a Nexus 4 or 5).
My first computer was a 33MHz 386SX with 1MB of RAM and a 110MB HDD. In today's dollars it cost $2,835. Today you can get a Dell XPS 13 Developer Edition for $950 and still have enough money left over to bathe in BeagleBone Blacks, or a lifetime subscription to Linode if you want. There are a bunch of crappy products on the market, but I would never choose to go back to expensive slow computers.
I sure hope that they release a new Mac mini with user replaceable RAM. I don't have enough money for a Mac Pro and I refuse to buy an iMac since I have an expensive high gamut color calibrated screen.
I have the 2015 Dell XPS 13 Developer Edition and I have been very happy with it. I was actually an HP employee when I purchased it and I would buy it again. I got the base model with a 1080p non-touch display for $950. It is incredibly small and light with amazing battery life. My touchpad sucks (I use a mouse), hopefully the new on is better.
It takes work to write safe code in C. Your worst developers will use uninitialized variables, pointers to previously freed memory, and overflow buffers. But not in Rust.
I am a Senior Embedded Software Engineer at a Fortune 500 company. I work on a code-base of millions of lines of C with 300 of my closest development buddies who are located all over the world. The distribution of abilities is as you would expect with this statistically significant sample of developers. I spend a lot of my time tracking down tricky memory corruption bugs in C by hand that would have been caught by the Rust compiler. What's more, dangling pointers and buffer overflows are the worst kinds of bugs because they often lead to security vulnerabilities.
An excellent engineer can write excellent C, but a poor engineer can overflow buffers and leave dangling pointers hanging around... but not in Rust.
I'm one of those widely available replacement developers that spends a lot of time tracking down bugs in C that would have been caught at compile time in Rust.
Slashdot Mirror
Python is a great replacement for bash with much better library and testing support. How many horrible bash scripts have you seen? I promise that with Python they can be far better. However, I'm not actually a huge fan of dynamic languages, because there are a whole class of bugs that the compiler can't catch. So, I love Python, but I don't use it for anything too large.
This millennial household replaced one of our cars with Uber to good effect, but we still have more desktops than people in the house.
...my house has three Macs and a bunch of Linux boxes (all of which are used for real, paid work), but no Windows.
UK citizens that are already living in the EU (and vice-versa) get to stay with the original rules from when they moved, but future migrants will have to play by the new rules. Similarly, if you are a UK citizen legally living in the EU, I'm sure that they will let you keep your EU domain. I don't see the problem (as a UK citizen that would have voted against Brexit but couldn't because I've been overseas for more than 10 years).
Sure, if it ran Ubuntu, I'd consider buying it. But honestly, I'm very happy with my Dell XPS13, so it's going to need to work well.
I've been on both sides of the Dev/QA divide. I'm strongly in the camp that developers should be responsible for writing automated (possibly unit) tests of their own code. However, before the code is shipped to the customer QA should have a go. It is way too easy for a lazy or even well meaning developer to ship something out of spec. Having the developer do all their own QA is like letting the prosecutor also be your defense attorney. It's patently and obviously wrong.
You can say "we practice continuous deployment" without saying "to production servers." CI/CD is about your development branch never getting so shitty that the average engineer can't do meaningful work on it. Or, the other thing that used to happen: make a bunch of components and then try to stitch them together at the end; act surprised when nothing works.
I'm a professional developer. But I have two active GitHub accounts. One for work, and one for personal stuff.
Seriously, we have the protocol. We also have 12 competing standards from 12 different walled gardens, the only one that added anything of value being Signal.
I assume that the RAM is soldered to the motherboard? What Wi-Fi module are you using? These would be good things to add to the website. Either way I am happy to see this in the marketplace. I'm typing this on a Dell XPS 13 but not everyone has $950 to spend on a laptop.
I loved my Nexus 4, I liked my Nexus 5. I couldn't figure out why to upgrade to a 5X. I will never buy a Pixel while an iPhone SE is $400 (that is, approximately as much as a Nexus 4 or 5).
My first computer was a 33MHz 386SX with 1MB of RAM and a 110MB HDD. In today's dollars it cost $2,835. Today you can get a Dell XPS 13 Developer Edition for $950 and still have enough money left over to bathe in BeagleBone Blacks, or a lifetime subscription to Linode if you want. There are a bunch of crappy products on the market, but I would never choose to go back to expensive slow computers.
I sure hope that they release a new Mac mini with user replaceable RAM. I don't have enough money for a Mac Pro and I refuse to buy an iMac since I have an expensive high gamut color calibrated screen.
I have the 2015 Dell XPS 13 Developer Edition and I have been very happy with it. I was actually an HP employee when I purchased it and I would buy it again. I got the base model with a 1080p non-touch display for $950. It is incredibly small and light with amazing battery life. My touchpad sucks (I use a mouse), hopefully the new on is better.
It takes work to write safe code in C. Your worst developers will use uninitialized variables, pointers to previously freed memory, and overflow buffers. But not in Rust.
This is very true, but...
I am a Senior Embedded Software Engineer at a Fortune 500 company. I work on a code-base of millions of lines of C with 300 of my closest development buddies who are located all over the world. The distribution of abilities is as you would expect with this statistically significant sample of developers. I spend a lot of my time tracking down tricky memory corruption bugs in C by hand that would have been caught by the Rust compiler. What's more, dangling pointers and buffer overflows are the worst kinds of bugs because they often lead to security vulnerabilities.
An excellent engineer can write excellent C, but a poor engineer can overflow buffers and leave dangling pointers hanging around... but not in Rust.
I'm one of those widely available replacement developers that spends a lot of time tracking down bugs in C that would have been caught at compile time in Rust.