Us young guys still have to use VB for some shops, but I don't know of anybody who likes it. Most of the guys I know are big into C# if they really like programming for Windows. Personally, I am a fan of D and Vala. Unfortunately, these languages aren't quite where they need to be, so most of my personal projects tend to focus around C++ or Java.
I'm talking about a monitor itself acting as a device on the network, so that it could operate without being directly connected to a box. Remote desktop still requires a box with some sort of OS and client to connect to a remote box. I would like VNC or simliar capabilities built into a monitor.
They would be better off with a wired solution. Interference is going to big a big problem for anyone who might want to use this. Some sort of ethernet interface would probably be much better for keeping displays and computers far away from each other.
In theory, OpenGL 4 could take advantage of the new hardware, but Intel would have to write good OpenGL drivers. Future versions of DirectX may require new hardware. We won't know until there is a spec. If it does require new hardware, then people would have to replace their DX11 cards anyway.
Being an atheist in the midwest can be tough. As long as you keep your mouth shut, you will generally be ok. That doesn't mean you won't hear very insulting things from those around you. Many a good, loving christian has insulted me without knowing it. I really feel for the middle eastern looking people in America. I can get by without targeted hatred since my looks aren't strongly associated with my personal beliefs. I can barely imagine how tough it must be to try to live with everybody giving you strange looks or being outright hateful.
Then there is the taste itself - insects are arthropods, and hence are very closely related to shrimp, crabs, lobster, etc. A big tarantula (yes, yes, not an insect but a terrestrial arthropod nonetheless) has a taste not unlike a crab, though less salty for obvious reasons.
Maybe that is why I don't like shrimp, crabs, lobster, etc.
I was referring to the $50+ figure that the AC listed. Still, free documentation is better. Maybe some of these books are good for a starting point, but I almost always end up using the official docs. Most of these mobile and web 2.0 books look like a quick way to make a buck, providing basically the same information that the original authors of the software provide.
I prefer my CPU to be running in a low power mode most of my session. TurboBoost also serves to keep power consumption and thermals within a good range while allowing single threaded tasks to run a bit faster than they would normally.
It has worked just fine for me on every environment I have tried it on (Win7 x64, OSX 10.6, various versions of Ubuntu.) It also didn't require me to spend 50 dollars on a book that wouldn't have much more information than the official developer site.
I think the biggest problem we have is how we pay for our connection. Back when speeds were fairly limited and the data we were retrieving was fairly small, a monthly rate tied to connection speed made sense. People got used to this scheme. If you wanted pages to load faster, you paid more for you your service. It was easy to understand and didn't take much to manage.
As speeds increased, the types of data accessed changed and more data was consumed. Now that we have the potential for really fast connections, we also have the potential for enormous data usage. Services like Netflix get noticed because they use an incredible amount of data. You have some households that are using enormous amounts of data while others are using far less. It would make sense to scale based on usage, like all other utilities. I think we get into very tricky issues when we look at wireless services. You can physically transmit only so much data. While your speeds can be fast, in order to make sure that as many customers as possible can use the service, you have to do some type of limiting. This normally comes as a data cap. People don't like those because it makes them think about their usage.
While I think all services should be allowed, and we need to make sure one isn't getting an unfair advantage over another, we have to get our expectations back in line. Many providers don't have the backbone to support all of their users maxing their connections 24/7. The ultimate solution would be a unified, equally shared network. As long as we have various companies owning various portions of our network, we will always have problems. The only other fair solution is to pay for your usage.
The game crashing on exit isn't necessarily his fault. The 3D library he is using, LWJGL, has some problems freeing the GL context when it shuts down. I've dealt with those errors in Linux and it appears it is some combination of how LWGL creates its context and what X expects. This of course doesn't excuse the rest of his code.
The main reason I went for a Software Engineering degree over a Computer Science degree is the job market. While the typical math heavy CS skillset is important and very useful, it does very little to teach you about design processes or communicating with the client. I found the focus on "real world" problems and solutions to be very useful. It is also a good chance to get used to working with those who don't speak geek.
Slashdot Mirror
You're a monster!
I need my anime, damn it!
Same here. I've also been waiting on that last season of Lost. I'm sure it will have a thrilling conclusion.
There were 13 dwarves.
Us young guys still have to use VB for some shops, but I don't know of anybody who likes it. Most of the guys I know are big into C# if they really like programming for Windows. Personally, I am a fan of D and Vala. Unfortunately, these languages aren't quite where they need to be, so most of my personal projects tend to focus around C++ or Java.
How does this stack with deals made with a shinigami? Does the one hour come before or after half of my remaining life is taken?
They don't collect paychecks. They have to tunnel into GameStops to get their games. Why do you think there are no good links provided?
I'm talking about a monitor itself acting as a device on the network, so that it could operate without being directly connected to a box. Remote desktop still requires a box with some sort of OS and client to connect to a remote box. I would like VNC or simliar capabilities built into a monitor.
They would be better off with a wired solution. Interference is going to big a big problem for anyone who might want to use this. Some sort of ethernet interface would probably be much better for keeping displays and computers far away from each other.
In theory, OpenGL 4 could take advantage of the new hardware, but Intel would have to write good OpenGL drivers. Future versions of DirectX may require new hardware. We won't know until there is a spec. If it does require new hardware, then people would have to replace their DX11 cards anyway.
Being an atheist in the midwest can be tough. As long as you keep your mouth shut, you will generally be ok. That doesn't mean you won't hear very insulting things from those around you. Many a good, loving christian has insulted me without knowing it. I really feel for the middle eastern looking people in America. I can get by without targeted hatred since my looks aren't strongly associated with my personal beliefs. I can barely imagine how tough it must be to try to live with everybody giving you strange looks or being outright hateful.
Then there is the taste itself - insects are arthropods, and hence are very closely related to shrimp, crabs, lobster, etc. A big tarantula (yes, yes, not an insect but a terrestrial arthropod nonetheless) has a taste not unlike a crab, though less salty for obvious reasons.
Maybe that is why I don't like shrimp, crabs, lobster, etc.
I was referring to the $50+ figure that the AC listed. Still, free documentation is better. Maybe some of these books are good for a starting point, but I almost always end up using the official docs. Most of these mobile and web 2.0 books look like a quick way to make a buck, providing basically the same information that the original authors of the software provide.
But then I've been wrong before.
Well, so has Goldman.
I prefer my CPU to be running in a low power mode most of my session. TurboBoost also serves to keep power consumption and thermals within a good range while allowing single threaded tasks to run a bit faster than they would normally.
Havo dad, jd.
I teach people Sindarin, you insensitive clod. Why would I teach them a language that nobody speaks?
It has worked just fine for me on every environment I have tried it on (Win7 x64, OSX 10.6, various versions of Ubuntu.) It also didn't require me to spend 50 dollars on a book that wouldn't have much more information than the official developer site.
The editors only post what the users send in and the users only submit news articles they have read or blog posts they have made.
I think the biggest problem we have is how we pay for our connection. Back when speeds were fairly limited and the data we were retrieving was fairly small, a monthly rate tied to connection speed made sense. People got used to this scheme. If you wanted pages to load faster, you paid more for you your service. It was easy to understand and didn't take much to manage.
As speeds increased, the types of data accessed changed and more data was consumed. Now that we have the potential for really fast connections, we also have the potential for enormous data usage. Services like Netflix get noticed because they use an incredible amount of data. You have some households that are using enormous amounts of data while others are using far less. It would make sense to scale based on usage, like all other utilities. I think we get into very tricky issues when we look at wireless services. You can physically transmit only so much data. While your speeds can be fast, in order to make sure that as many customers as possible can use the service, you have to do some type of limiting. This normally comes as a data cap. People don't like those because it makes them think about their usage.
While I think all services should be allowed, and we need to make sure one isn't getting an unfair advantage over another, we have to get our expectations back in line. Many providers don't have the backbone to support all of their users maxing their connections 24/7. The ultimate solution would be a unified, equally shared network. As long as we have various companies owning various portions of our network, we will always have problems. The only other fair solution is to pay for your usage.
The game crashing on exit isn't necessarily his fault. The 3D library he is using, LWJGL, has some problems freeing the GL context when it shuts down. I've dealt with those errors in Linux and it appears it is some combination of how LWGL creates its context and what X expects. This of course doesn't excuse the rest of his code.
The main reason I went for a Software Engineering degree over a Computer Science degree is the job market. While the typical math heavy CS skillset is important and very useful, it does very little to teach you about design processes or communicating with the client. I found the focus on "real world" problems and solutions to be very useful. It is also a good chance to get used to working with those who don't speak geek.
Maybe only the US government is important.
We're number one! We're number one!
Yeah, but you guys are a real distraction at movie theaters.
They said that around 60 years ago.