I believe the opt out is only in relation to the law banning the use of wireless electronic devices. That would mean that only being charged under that statute would potentially allow interpretation of his duties to qualify. Other distracted driving statues and reasonable care would still apply.
I've written services/daemons using Qt simply to make it easily extensible because the framework I built was multi-process with IPC and each process could be heavily multi-threaded.
Qt abstracted away a lot of things that would have made the project difficult to build on many *nix platforms.
One of the overlooked advantages with using Java on the server/middleware side is that long running processes in real production environments often have to deal with memory fragmentation, with C++ this is often a very serious, and sometime virtually impossible situation to deal with (writing a pre-allocating memory manager is a non trivial task and you have to worry about people misusingit.) In Java (which I don't personally enjoy working in, but can appreciate), this issue is, for the most part, gone - and in those rare cases where you have to directly intervene, it is trivial to do so.
Given the skill of the average "I work at a bank building IFX/OFX software" developer, I'd rather they stuck to Java...
I can't use a statically typed language without being constantly pelted with reminders of their limitations. No, you can't compile that, you didn't use quite the right punctuation in the type name. Sorry, I couldn't protect you from that null pointer, even though I have decades of research and all the source code available to me. Oh, you want a type that could be one of several types? Have fun with those runtime downcasts, or null pointers, or whatever.
Personally, it sounds like you want to be as sloppy as you like... Nobody should be protecting you from null pointers except yourself.
I don't particularly care for Java primarily because it really is verbose, but the reason Java is so prevalent is that it is an excellent middleware language solution that made it possible in the late 90's and early aughts for companies that would never have managed to build these systems with C++ (just not enough C++ people who don't hang themselves and your company 5 times a day.)
You could argue that if they couldn't do it with C++ they shouldn't have been doing it anyhow, but there'd be hundreds of thousands fewer jobs in the software industry as a result.
Ours was first semester of second year, computer engineering and assembly language. We used an old MIPS chip. Started with 27 people including 3 women, finished with 6. I had the highest grade in the course, a B-. It was rough, but not necessarily because of the topic - more that we covered so much so quickly.
I think the scariest API doc I ever read was the one for Word's *.doc format. The stuff Microsoft has/had to support for the sake of backward's compatibility was simply astounding.
Honestly, from reading the translated article, I get the feeling that a lot of the issues were because other agencies outside of Munich had difficulty interacting with them and this translated into Munich user unhappiness.
It is charmingly naive to think that morality/ethics would prevent a CEO (in ANY country) from doing whatever they thought would generate them the most money with the smallest risk...
That doesn't mean it's good enough, but having 20% female tech workers? That's great compared to my experience in the industry.
It was 4 years into my career before I met my first female software engineer at work, and there were two out of 80. This was the valley back in the 90's though.
Why did someone mark this as troll when it's clear I'm simply saying that Microsoft treats the Surface as a "loss leader" in business market?
FFS people, get over yourselves. I don't care what OS you use or whose latest 'shiny thing' you want to buy. They're all tools in the toolbox as far as I'm concerned.
They both want profits and revenue, they just look to different markets to do it. (There is, of course, overlap.)
Apple is all about the consumer space, and very little about business.
Microsoft is all about the business space, and very little about the consumer except in the console space (and the way the XBox One is going, that may not be for long anyhow...)
I'll be honest, I didn't expect much from the initial Surface and so I wasn't disappointed. The Surface 2 I thought was a mistake. The Surface 3 Pro that I used a few months ago - is pretty freaking awesome.
While Apple is pushing the consumer entertainment perspective of devices, Microsoft is going to lead the way to the PC/tablet/phone convergence in the work place. Yet again, they will succeed through Exchange and Office.
The irony being that Microsoft doesn't mind making money in the tablet space, but they really don't care about that. They care about ensuring that in 2018, whatever Phablet your company supplies you with (or requires you to buy to work there) is running MS Office 2018 and connecting to Exchange Server 2018...
Slashdot Mirror
Talk about ugly as f***...
That's exactly the law I am referring to.
California state law has an explicit provision for 'emergency vehicle' use.
I believe the opt out is only in relation to the law banning the use of wireless electronic devices. That would mean that only being charged under that statute would potentially allow interpretation of his duties to qualify. Other distracted driving statues and reasonable care would still apply.
As one would expect given that whites get treated better than any other ethnic group in the U.S.
...or am I missing something?
This.
I've written services/daemons using Qt simply to make it easily extensible because the framework I built was multi-process with IPC and each process could be heavily multi-threaded.
Qt abstracted away a lot of things that would have made the project difficult to build on many *nix platforms.
One of the overlooked advantages with using Java on the server/middleware side is that long running processes in real production environments often have to deal with memory fragmentation, with C++ this is often a very serious, and sometime virtually impossible situation to deal with (writing a pre-allocating memory manager is a non trivial task and you have to worry about people misusingit.) In Java (which I don't personally enjoy working in, but can appreciate), this issue is, for the most part, gone - and in those rare cases where you have to directly intervene, it is trivial to do so.
Given the skill of the average "I work at a bank building IFX/OFX software" developer, I'd rather they stuck to Java...
I can't use a statically typed language without being constantly pelted with reminders of their limitations. No, you can't compile that, you didn't use quite the right punctuation in the type name. Sorry, I couldn't protect you from that null pointer, even though I have decades of research and all the source code available to me. Oh, you want a type that could be one of several types? Have fun with those runtime downcasts, or null pointers, or whatever.
Personally, it sounds like you want to be as sloppy as you like... Nobody should be protecting you from null pointers except yourself.
I don't particularly care for Java primarily because it really is verbose, but the reason Java is so prevalent is that it is an excellent middleware language solution that made it possible in the late 90's and early aughts for companies that would never have managed to build these systems with C++ (just not enough C++ people who don't hang themselves and your company 5 times a day.)
You could argue that if they couldn't do it with C++ they shouldn't have been doing it anyhow, but there'd be hundreds of thousands fewer jobs in the software industry as a result.
Wait... is this in lieu of 'Federal pound you in the ass' prison? ;)
You cynical old bastard ;).
I know what you mean though. It is incredibly difficult to assess the valuable from the detritus.
Apparently wisdom doesn't come with age...
Atlanta too.
That's like saying that the way to learn how to swim is to dump everyone in deep water and see who takes to it naturally...
Ours was first semester of second year, computer engineering and assembly language. We used an old MIPS chip. Started with 27 people including 3 women, finished with 6. I had the highest grade in the course, a B-. It was rough, but not necessarily because of the topic - more that we covered so much so quickly.
I think the scariest API doc I ever read was the one for Word's *.doc format. The stuff Microsoft has/had to support for the sake of backward's compatibility was simply astounding.
You had me at Bacon...
Honestly, from reading the translated article, I get the feeling that a lot of the issues were because other agencies outside of Munich had difficulty interacting with them and this translated into Munich user unhappiness.
...seriously, why wouldn't they?
It is charmingly naive to think that morality/ethics would prevent a CEO (in ANY country) from doing whatever they thought would generate them the most money with the smallest risk...
...tech companies.
That doesn't mean it's good enough, but having 20% female tech workers? That's great compared to my experience in the industry.
It was 4 years into my career before I met my first female software engineer at work, and there were two out of 80. This was the valley back in the 90's though.
Why did someone mark this as troll when it's clear I'm simply saying that Microsoft treats the Surface as a "loss leader" in business market?
FFS people, get over yourselves. I don't care what OS you use or whose latest 'shiny thing' you want to buy. They're all tools in the toolbox as far as I'm concerned.
...Apple.
They both want profits and revenue, they just look to different markets to do it. (There is, of course, overlap.)
Apple is all about the consumer space, and very little about business.
Microsoft is all about the business space, and very little about the consumer except in the console space (and the way the XBox One is going, that may not be for long anyhow...)
I'll be honest, I didn't expect much from the initial Surface and so I wasn't disappointed. The Surface 2 I thought was a mistake. The Surface 3 Pro that I used a few months ago - is pretty freaking awesome.
While Apple is pushing the consumer entertainment perspective of devices, Microsoft is going to lead the way to the PC/tablet/phone convergence in the work place. Yet again, they will succeed through Exchange and Office.
The irony being that Microsoft doesn't mind making money in the tablet space, but they really don't care about that. They care about ensuring that in 2018, whatever Phablet your company supplies you with (or requires you to buy to work there) is running MS Office 2018 and connecting to Exchange Server 2018...
Don't be such an arsoe...
...that's pretty effin' amazing. From video, 15 feet away. Not using a laser, FROM VIDEO! Lol.