Really what's needed is lidar. Lidar can build a 3D image that would actually be suitable to let the game AI roam around in. No one is going to do proper self driving cars without a serious lidar solution. The ones available right now (mostly Velodyne) aren't that great but, the stuff that's in the pipeline is pretty fucking amazing. You can even get doppler information out of newer lidar approaches and that's like the greatest thing since sliced bread for self driving cars.
Actually, there was a story on Slashdot a few years ago (maybe a decade ago) that was about the Navy using Windows on its newest Battleships. We were collectively in shock but, apparently they have done a good job of covering up the hours of downtime from Patch Tuesday. Make no mistake though, North Korea will strike on a Tuesday and every sailors screen will read: "Windows is updating. Do not turn off your computer".
I've seen the ZynqBerry and it's the right idea but, it's still too expensive and not quite what I'm thinking. I'd like to see a 99% open source ARM/FPGA board appear and have an entire ecosystem develop around it such that it makes Vivado look like a clunky dinosaur.
Maybe the Navy is also concerned about the health effects of nicotine vapors
Yes, I'm sure this is the reason...
or the effects of the vapors on sensitive gear.
The navy is concerned about minuscule amounts of water vapor on ships? We are totally fucked. Next you'll tell me they are running Windows on their battleships...
The Navy doesn't want vaping, and they don't have to justify it to you or anyone else.
They certainly don't have to justify it to me but, if I were knowingly sending kids off to their potential death, I'd sure as fuck let them engage in a calming activity that in no way affects their acute performance.
Why not, I dunno, sell government approved vape pens in the commissary? From what I've read, most of the incidents with vaping are from people trying to "soup up" their vape machines. This amounts to banning Honda Civics on base because a few ill informed morons cause them to ignite by modifying them in ways they don't really understand.
These little ARM boards are great but, I'd love to see some super cheap ARM/FPGA boards become available. Something like a Zybo but in the $50 price range with just enough FPGA fabric to offload tasks that the CPU is abysmal at. The RPI brought embedded computing to the masses and it's been great but, a $50 ARM board with an FPGA could bring some flavor of High Level Synthesis (and AXI) to the masses. That's whole new level of nerdiness and enables a proper next generation type of hobby embedded stuff.
Is it even possible for most people to use a modem these days? I suspect most phone traffic is already passing through an ADC->DAC translation anyway. Trying to put a modem signal through that seems like a painful exercise.
Right. Building infrastructure from the plains to the mountains is super easy because some stretches are public land. Hint: There is a reason those stretches are public land. Because it's incredibly difficult to build anything there.
Denver to Vail also seems like the hardest, by far, to physically construct. I genuinely don't think the US has it in them to construct hard infrastructure projects like that anymore. If it's not profitable by next quarter, it's not going to get built.
I keep reading stories that millennials are also woefully unemployed. It seems odd to try to court people who would literally work for peanuts. Not to mention the fact that co-working, the latest buzzword for "not valued enough to have an office", is basically the most miserable work environment I can think of. You only need one loud overtalker and productivity effectively drops to zero.
But, yeah... gig economy... millennials... open office... buzzword, buzzword. Hell, why not have a mandatory skinny jeans policy so we don't hurt the feelings of the younger guys.
It's a tarnished brand. It doesn't really matter how good their product is: People have grown up using and loathing Microsoft software. The vast majority of people will run away from a Microsoft product if they aren't forced to use it. They could sell their phones for $0 and throw in some hookers and blow to seal the deal and people still wouldn't buy them.
If they just stopped chasing the mobile platform that they'll never get, they could actually entrench themselves into their core business again: Making bloated but ubiquitous operating systems and business software. As a Linux guy, I almost feel ashamed to say it but, I actually *liked* Windows 7. Firing up a copy of Windows 10, I feel like I need an XBox controller and a touch screen to use it correctly. The first time I used it, I literally could not figure out how to make the machine shutdown.
There is a huge distinction between what you've described and how that process would work in a proprietary software environment. The moment you discovered the bug, you had the resources to debug it. The moment you debugged it, you had the resources to at least deploy it in a fashion that would allow you to continue to do work (admittedly in a possibly haphazard way). At some point in the future, your fix (or something like it) will be integrated and away you go.
Contrast that to proprietary software. You find a bug, you report it. Maybe, at some point, someone responds to your bug report. Maybe they don't. Maybe, at some point, the vendor fixes the bug. Maybe they don't. What recourse do you have between "I found a bug" and, "Woohoo! My bug is fixed"? How can you even guarantee that you even reach the latter state?
No one disputes that stack overflow is an invaluable resource for a modern programmer. But, it's also a crutch. And the programmers that lean on that crutch the most seem to be the most represented in this survey.
That's too low a bar to entry. It needs to be a socket that hangs off an IPv6 address that specifies its endianness at connection time and requires your connection to handle obscure return values from socket commands. The server may also, depending on its mood, request the client to speak EBDIC or request that it negotiates microsecond time synchronization before accepting any answers.
This seems about right. Once you've introduced proprietary software into the mix, a huge amount of your time is going to be spent fighting with the software vendor, waiting for updates from the software vendor, working around the idiocy of the software vendor, etc. So, even though 90% of the company runs on open source software, you still need 60% of the workforce to deal with the proprietary software.
To summarize, a bunch of dime-a-dozen web guys, who rely on stack overflow for every other line of code, have declared that they are underpaid. And, they would prefer to work at home so that if someone asks them a hard question, they can ask it on stack overflow before answering.
I think anyone who has been using Ubuntu for anything mission critical has been ignoring the non-LTS releases for years now. If you want to put Ubuntu on a toy, grab the latest release. If you want to put it on a real machine, grab an LTS release that is at least 6 months old.
How can you create software without Ruby, The Cloud and 37 half-baked frameworks?
Joking aside, C/C++ with a good understanding of hardware and operating systems is where older engineers shine. In fact, I'd say it's one of the few areas of software development where the term "engineer" is actually warranted. Anyone can lay 1000 layers of cruft onto a fast processor, cross their fingers and hope it works. Far fewer people can work close to the hardware, with limited resources, and take it from "it boots without emitting smoke" to "here is the API to our product". I think we are already at the point where the younger engineers are doing the boring, trendy work and the older guys are doing the fun, hard work. It's easy to find a job if you can do the latter. You don't even need to learn a new buzzword every week!
"Small amounts of water have a big effect on melting temperature, and this is the first time experiments have ever been conducted to determine precisely how the mantle's melting temperature depends on such small amounts of water"
Apparently these guys have never modified a car engine to inject water/meth. Car guys have known this for years except they use cooler words like stoichiometry.
Admittedly, it is pretty cool that they are relating it to the earths mantle but, come on... everyone knows the earth is hollow anyway...
Slashdot Mirror
Really what's needed is lidar. Lidar can build a 3D image that would actually be suitable to let the game AI roam around in. No one is going to do proper self driving cars without a serious lidar solution. The ones available right now (mostly Velodyne) aren't that great but, the stuff that's in the pipeline is pretty fucking amazing. You can even get doppler information out of newer lidar approaches and that's like the greatest thing since sliced bread for self driving cars.
Geez, I thought I was the only one...
My guess is that it's a result of the endless race to see who can pump the most watts into a sub-ohm coil with the cheapest cells they can find.
By people who wouldn't know an Ohm if a Volt kicked them in the ass.
Actually, there was a story on Slashdot a few years ago (maybe a decade ago) that was about the Navy using Windows on its newest Battleships. We were collectively in shock but, apparently they have done a good job of covering up the hours of downtime from Patch Tuesday. Make no mistake though, North Korea will strike on a Tuesday and every sailors screen will read: "Windows is updating. Do not turn off your computer".
I've seen the ZynqBerry and it's the right idea but, it's still too expensive and not quite what I'm thinking. I'd like to see a 99% open source ARM/FPGA board appear and have an entire ecosystem develop around it such that it makes Vivado look like a clunky dinosaur.
Maybe the Navy is also concerned about the health effects of nicotine vapors
Yes, I'm sure this is the reason...
or the effects of the vapors on sensitive gear.
The navy is concerned about minuscule amounts of water vapor on ships? We are totally fucked. Next you'll tell me they are running Windows on their battleships...
The Navy doesn't want vaping, and they don't have to justify it to you or anyone else.
They certainly don't have to justify it to me but, if I were knowingly sending kids off to their potential death, I'd sure as fuck let them engage in a calming activity that in no way affects their acute performance.
Why not, I dunno, sell government approved vape pens in the commissary? From what I've read, most of the incidents with vaping are from people trying to "soup up" their vape machines. This amounts to banning Honda Civics on base because a few ill informed morons cause them to ignite by modifying them in ways they don't really understand.
These little ARM boards are great but, I'd love to see some super cheap ARM/FPGA boards become available. Something like a Zybo but in the $50 price range with just enough FPGA fabric to offload tasks that the CPU is abysmal at. The RPI brought embedded computing to the masses and it's been great but, a $50 ARM board with an FPGA could bring some flavor of High Level Synthesis (and AXI) to the masses. That's whole new level of nerdiness and enables a proper next generation type of hobby embedded stuff.
Is it even possible for most people to use a modem these days? I suspect most phone traffic is already passing through an ADC->DAC translation anyway. Trying to put a modem signal through that seems like a painful exercise.
Right. Building infrastructure from the plains to the mountains is super easy because some stretches are public land. Hint: There is a reason those stretches are public land. Because it's incredibly difficult to build anything there.
Denver to Vail also seems like the hardest, by far, to physically construct. I genuinely don't think the US has it in them to construct hard infrastructure projects like that anymore. If it's not profitable by next quarter, it's not going to get built.
This isn't a slashvertisment, it's a hand wringing exercise for anyone over the age of 30.
I keep reading stories that millennials are also woefully unemployed. It seems odd to try to court people who would literally work for peanuts. Not to mention the fact that co-working, the latest buzzword for "not valued enough to have an office", is basically the most miserable work environment I can think of. You only need one loud overtalker and productivity effectively drops to zero.
But, yeah... gig economy... millennials... open office... buzzword, buzzword. Hell, why not have a mandatory skinny jeans policy so we don't hurt the feelings of the younger guys.
Those core files were probably stale anyway.
It's a tarnished brand. It doesn't really matter how good their product is: People have grown up using and loathing Microsoft software. The vast majority of people will run away from a Microsoft product if they aren't forced to use it. They could sell their phones for $0 and throw in some hookers and blow to seal the deal and people still wouldn't buy them.
If they just stopped chasing the mobile platform that they'll never get, they could actually entrench themselves into their core business again: Making bloated but ubiquitous operating systems and business software. As a Linux guy, I almost feel ashamed to say it but, I actually *liked* Windows 7. Firing up a copy of Windows 10, I feel like I need an XBox controller and a touch screen to use it correctly. The first time I used it, I literally could not figure out how to make the machine shutdown.
There is a huge distinction between what you've described and how that process would work in a proprietary software environment. The moment you discovered the bug, you had the resources to debug it. The moment you debugged it, you had the resources to at least deploy it in a fashion that would allow you to continue to do work (admittedly in a possibly haphazard way). At some point in the future, your fix (or something like it) will be integrated and away you go.
Contrast that to proprietary software. You find a bug, you report it. Maybe, at some point, someone responds to your bug report. Maybe they don't. Maybe, at some point, the vendor fixes the bug. Maybe they don't. What recourse do you have between "I found a bug" and, "Woohoo! My bug is fixed"? How can you even guarantee that you even reach the latter state?
No one disputes that stack overflow is an invaluable resource for a modern programmer. But, it's also a crutch. And the programmers that lean on that crutch the most seem to be the most represented in this survey.
That's too low a bar to entry. It needs to be a socket that hangs off an IPv6 address that specifies its endianness at connection time and requires your connection to handle obscure return values from socket commands. The server may also, depending on its mood, request the client to speak EBDIC or request that it negotiates microsecond time synchronization before accepting any answers.
This seems about right. Once you've introduced proprietary software into the mix, a huge amount of your time is going to be spent fighting with the software vendor, waiting for updates from the software vendor, working around the idiocy of the software vendor, etc. So, even though 90% of the company runs on open source software, you still need 60% of the workforce to deal with the proprietary software.
To summarize, a bunch of dime-a-dozen web guys, who rely on stack overflow for every other line of code, have declared that they are underpaid. And, they would prefer to work at home so that if someone asks them a hard question, they can ask it on stack overflow before answering.
My 4th grade English teacher used to say, "A bad workman blames his tools."
Sounds relevant to me here.
Apparently your 4th grade English teacher has never tried to use a hammer covered in spikes that arrived in a box labeled "Screwdriver".
I think anyone who has been using Ubuntu for anything mission critical has been ignoring the non-LTS releases for years now. If you want to put Ubuntu on a toy, grab the latest release. If you want to put it on a real machine, grab an LTS release that is at least 6 months old.
How can you create software without Ruby, The Cloud and 37 half-baked frameworks?
Joking aside, C/C++ with a good understanding of hardware and operating systems is where older engineers shine. In fact, I'd say it's one of the few areas of software development where the term "engineer" is actually warranted. Anyone can lay 1000 layers of cruft onto a fast processor, cross their fingers and hope it works. Far fewer people can work close to the hardware, with limited resources, and take it from "it boots without emitting smoke" to "here is the API to our product". I think we are already at the point where the younger engineers are doing the boring, trendy work and the older guys are doing the fun, hard work. It's easy to find a job if you can do the latter. You don't even need to learn a new buzzword every week!
Also, please get off of my lawn.
That's a terrible excuse. Just the other day I heard on Fox News that physics was fake.
"Small amounts of water have a big effect on melting temperature, and this is the first time experiments have ever been conducted to determine precisely how the mantle's melting temperature depends on such small amounts of water"
Apparently these guys have never modified a car engine to inject water/meth. Car guys have known this for years except they use cooler words like stoichiometry.
Admittedly, it is pretty cool that they are relating it to the earths mantle but, come on... everyone knows the earth is hollow anyway...