I agree with everything you said. To Apple, however, developers are now a minority in their minority PC market share - they've Crossed The Chasm and are now more interested in the greater consumer market which they can hook into iTunes' music, movies, videos and apps.
Yes, this. Good management knows that you know your trade and accepts your estimates. Bad management thinks they know better and try to negotiate on estimates.
Over the years I've found that feature development, particularly adding to existing systems, will get better estimates if we're allowed a spike to review the affected areas up front - this is when you discover unexpected dependencies or just sheer awful spaghetti. When you're not allowed to do this up front is when you come across the unexpected gotchas that blow out the best estimate you could provide at the time.
Your argument is that paying customers were given a choice in the matter and so should vote with their feet. Normally I would agree with that assertion except that most ISPs don't offer a choice of modem to customers or even alert them that they have a choice. Often they'll grumble about incompatibility issues if a new customer says, "I already have a modem."
Modems are just another way for ISPs to milk money out of their customers. e.g.: ISPs bulk buy these modems from whomever they can source them for $10 each and then charge customers a once-off connection fee ($80-$100) or ongoing monthly rentals ($10-$20/month).
BrickerBot and their ilk are still punishing the unwary customers for the incompetence of the manufacturers and ISPs.
I wouldn't the author a hero of any kind. Sure, he's removing insecure devices from the internet but at great inconvenience to the end-users that depend on them and a lot of these people will be small business owners or home office types. It's the fault of Zyxel for producing such insecure crap in the first place but also the ISP for issuing them to their customers and then failing to secure their management interfaces from the internet at large.
Some businesses can't help using old hardware or operating systems, because they use specialized software that also hasn't been brought up-to-date.
Nonsense! Virtualize that crap and run everything else on shiny new hardware. I'm sure there are still brain-dead banking applications that require ActiveX controls to run in MS-IE 5.5 or 6.x but that shouldn't stop everything else in the world from progressing.
You're kidding, right? "Google has confirmed with the Journal that the restriction is courtesy of the licensing agreements the broadcast industry forced Google to adhere to in order to offer the service." The largest portion of Google/Alphabet's income is advertising revenue - I'd be surprised if they protested the broadcasters' request in any way, shape or form.
Although Microsoft claims that the three browsers are being tested on "the same Vimeo video" I'm betting that the three browsers are being served different versions of said video. This kind of test is entirely dependant on CODEC selection and video resolution, both of which affect hardware-based decoding and battery efficiency. To be a valid test the browsers should be playing back the same video file from local media.
I agree that third party repairs should invalidate an Apple warranty, but refusing to repair a device at all (even at the owner's expense) is completely wrong... especially when it was an Apple software update that bricked the device.
http://ar5-syr.ipcc.ch/topic_o... does describe solar irradiance and even puts a figure on the estimated amount it provides to the total radiative forcing.
The IPCC doesn't do any such thing. The IPCC Charter and IPCC Document Submission Guidelines forbid it accepting or analysing any material that shows natural climate variability. It is only allowed to accept or analyse documents that show human-induced climate change.
When Enterprise looks at IoT you can bet they're thinking INTRAnet of Things, not INTERnet of Things.
With all the safety regulations on mine sites no sane mine site operator is going to be putting INTERnet of Things VIMS interfaces on their equipment to report running statistics back to their ERP, its going to INTRAnet back to the C.O., maybe traversing the internet via a site-to-site VPN.
There are cross platform libraries that work equally well on Linux and Windows.
OpenCV isn't one of them and it's not even OpenCV's fault. Try opening a USB-based stereo camera with OpenCV under Linux and you get an error best summarised as "the USB bus doesn't have enough bandwidth to open the device." This is wrong because the same stereo camera devices work just fine with OpenCV under Windows and MacOS.
There are reasons to run Blender in a Windows guest instead of Blender in the Linux/MacOS host, not the least of which is add-ons. A number of Blender add-ons only run on Windows, e.g.: Bos FBX Importer/Exporter requires 64-bit Windows due to the Autodesk FBX library dependency.
For starters it doesn't support GPU pass-through. If you try to use the VirtualBox Guest Additions video driver then you'll be limited to DirectX 9 and OpenGL 2.1 (but only if you enable OpenGL through registry settings).
If you pay money for VMware Workstation for Linux/MacOS/Windows then you'll be upgraded to DirectX 10 and OpenGL 3.3 but, as far as I know, still no GPU pass-through support.
This must be a late April Fool's thing. TFA's picture shows the gas turbines installed on his hands backwards - the intakes are pointing towards his elbows, the exhausts towards his hands. Unless you're expected to fly backwards and land using hand-stand maneuvres.
I think it's simpler than that. I've not seen an organization where marketing people actually talk to engineers, let alone listen to them, so likely the marketing people have said "people need to work eight hour days, let's just market this thing as having an eight hour battery life" and the engineers were never even consulted about it.
There can be a number of benefits to developing in a VM, at least when what you're developing allows you to do it. One of the main benefits is hardware independence - it's very easy to pick up your VM guest and move it to a shiny new computer, such as getting new hardware upgrades every year, or even changing host operating systems from Windows 7/8/10 to Linux or MacOS.
If your host dies, due to a hardware problem, power spike, etc., you can run your guest(s) up on a new host from backups very quickly, avoiding the days of setup from scratch you might need otherwise. Restoring host backups to a new one doesn't always work for you due to hardware differences.
If you're developing multi-OS stuff it's very handy to have a bunch of VM guests on your machine for unit testing, but you'd normally have a test farm of servers/VMs/containers that run tests for the build servers.
VMs aren't perfect, though, (there are performance impacts for one thing) and not everyone can develop inside VMs due to requirements to access funky hardware or even recent OpenGL/DirectX implementations.
There are still people developing outside of a VM????
Yes, believe it or not VM's aren't perfect. They can't virtualize everything.
Game developers, for example, can't run in VM environments because even the "best" of VMware's offerings for Linux, MacOS and Windows only support OpenGL 3.3 and DirectX 10. If you want to be a cheap-ass and try to use VirtualBox then you're limited to OpenGL 2.1 and DirectX 9 which is basically unusable for anything modern.
I agree with everything you said. To Apple, however, developers are now a minority in their minority PC market share - they've Crossed The Chasm and are now more interested in the greater consumer market which they can hook into iTunes' music, movies, videos and apps.
Yes, this. Good management knows that you know your trade and accepts your estimates. Bad management thinks they know better and try to negotiate on estimates.
Over the years I've found that feature development, particularly adding to existing systems, will get better estimates if we're allowed a spike to review the affected areas up front - this is when you discover unexpected dependencies or just sheer awful spaghetti. When you're not allowed to do this up front is when you come across the unexpected gotchas that blow out the best estimate you could provide at the time.
It's only 95% ok. They still contain 5% virgin plastic.
Your argument is that paying customers were given a choice in the matter and so should vote with their feet. Normally I would agree with that assertion except that most ISPs don't offer a choice of modem to customers or even alert them that they have a choice. Often they'll grumble about incompatibility issues if a new customer says, "I already have a modem."
Modems are just another way for ISPs to milk money out of their customers. e.g.: ISPs bulk buy these modems from whomever they can source them for $10 each and then charge customers a once-off connection fee ($80-$100) or ongoing monthly rentals ($10-$20/month).
BrickerBot and their ilk are still punishing the unwary customers for the incompetence of the manufacturers and ISPs.
The link is in the article title, https://www.bleepingcomputer.c...
I wouldn't the author a hero of any kind. Sure, he's removing insecure devices from the internet but at great inconvenience to the end-users that depend on them and a lot of these people will be small business owners or home office types. It's the fault of Zyxel for producing such insecure crap in the first place but also the ISP for issuing them to their customers and then failing to secure their management interfaces from the internet at large.
Any junior aeronautical engineer will tell you that roll stability is achieved by using wing dihedral. Now go away.
Nonsense! Virtualize that crap and run everything else on shiny new hardware. I'm sure there are still brain-dead banking applications that require ActiveX controls to run in MS-IE 5.5 or 6.x but that shouldn't stop everything else in the world from progressing.
How do I sign up? I'd love to play games all day and get paid for it!
You're kidding, right? "Google has confirmed with the Journal that the restriction is courtesy of the licensing agreements the broadcast industry forced Google to adhere to in order to offer the service." The largest portion of Google/Alphabet's income is advertising revenue - I'd be surprised if they protested the broadcasters' request in any way, shape or form.
Although Microsoft claims that the three browsers are being tested on "the same Vimeo video" I'm betting that the three browsers are being served different versions of said video. This kind of test is entirely dependant on CODEC selection and video resolution, both of which affect hardware-based decoding and battery efficiency. To be a valid test the browsers should be playing back the same video file from local media.
I agree that third party repairs should invalidate an Apple warranty, but refusing to repair a device at all (even at the owner's expense) is completely wrong... especially when it was an Apple software update that bricked the device.
Apple stopped selling Ink when they killed the Stylewriter printer line.
The IPCC doesn't do any such thing. The IPCC Charter and IPCC Document Submission Guidelines forbid it accepting or analysing any material that shows natural climate variability. It is only allowed to accept or analyse documents that show human-induced climate change.
When Enterprise looks at IoT you can bet they're thinking INTRAnet of Things, not INTERnet of Things.
With all the safety regulations on mine sites no sane mine site operator is going to be putting INTERnet of Things VIMS interfaces on their equipment to report running statistics back to their ERP, its going to INTRAnet back to the C.O., maybe traversing the internet via a site-to-site VPN.
Webcam.
No kidding. If HR was there to protect the employees it would be called Human Treasures.
There are cross platform libraries that work equally well on Linux and Windows.
OpenCV isn't one of them and it's not even OpenCV's fault. Try opening a USB-based stereo camera with OpenCV under Linux and you get an error best summarised as "the USB bus doesn't have enough bandwidth to open the device." This is wrong because the same stereo camera devices work just fine with OpenCV under Windows and MacOS.
There are reasons to run Blender in a Windows guest instead of Blender in the Linux/MacOS host, not the least of which is add-ons. A number of Blender add-ons only run on Windows, e.g.: Bos FBX Importer/Exporter requires 64-bit Windows due to the Autodesk FBX library dependency.
Don't use VirtualBox.
For starters it doesn't support GPU pass-through. If you try to use the VirtualBox Guest Additions video driver then you'll be limited to DirectX 9 and OpenGL 2.1 (but only if you enable OpenGL through registry settings).
If you pay money for VMware Workstation for Linux/MacOS/Windows then you'll be upgraded to DirectX 10 and OpenGL 3.3 but, as far as I know, still no GPU pass-through support.
This must be a late April Fool's thing. TFA's picture shows the gas turbines installed on his hands backwards - the intakes are pointing towards his elbows, the exhausts towards his hands. Unless you're expected to fly backwards and land using hand-stand maneuvres.
I think it's simpler than that. I've not seen an organization where marketing people actually talk to engineers, let alone listen to them, so likely the marketing people have said "people need to work eight hour days, let's just market this thing as having an eight hour battery life" and the engineers were never even consulted about it.
There can be a number of benefits to developing in a VM, at least when what you're developing allows you to do it. One of the main benefits is hardware independence - it's very easy to pick up your VM guest and move it to a shiny new computer, such as getting new hardware upgrades every year, or even changing host operating systems from Windows 7/8/10 to Linux or MacOS.
If your host dies, due to a hardware problem, power spike, etc., you can run your guest(s) up on a new host from backups very quickly, avoiding the days of setup from scratch you might need otherwise. Restoring host backups to a new one doesn't always work for you due to hardware differences.
If you're developing multi-OS stuff it's very handy to have a bunch of VM guests on your machine for unit testing, but you'd normally have a test farm of servers/VMs/containers that run tests for the build servers.
VMs aren't perfect, though, (there are performance impacts for one thing) and not everyone can develop inside VMs due to requirements to access funky hardware or even recent OpenGL/DirectX implementations.
Yes, believe it or not VM's aren't perfect. They can't virtualize everything.
Game developers, for example, can't run in VM environments because even the "best" of VMware's offerings for Linux, MacOS and Windows only support OpenGL 3.3 and DirectX 10. If you want to be a cheap-ass and try to use VirtualBox then you're limited to OpenGL 2.1 and DirectX 9 which is basically unusable for anything modern.
You're only being charged $2/ATM transaction? Unfortunately that's considered a good deal.