Ah, but when you buy a few drives for your RAID array, with the same model and revision, and give them all very similar usage patterns, in the same exact location, then it's a lot more likely that more than one drive will fail on you in quick succession. making your RAID array a lot less safe than it seemed at first.
A conversion layer is wasteful when there's only one way to look at your data. In that case, key value pairs can perform better, no question.
The problem lies in situations where you need to look at the data in 5 different ways. or 50. Then, a single object model for your data is a whole lot less practical than having a conversion layer, and have the data in a very flexible format, like a relational model.
The PostgreSQL documentation is about as good as I've ever seen in an Open Source product. The manual is typically well written, and it is full of good examples. It makes something like JBoss look line an underdocumented mess.
And if at any point you find that a page of documentation is missing some detail, you can always post it as a comment in that same page, and save the rest of us some grief.
Working those hours, in a night shift, that far from home, seems to me like a terrible long term arrangement. You'll cut years off your life. It'll make sure you can't get even a semblance of a social life. As a support job, it might not even pay enough as to allow you to see it as a temporary sacrifice for a better lifestyle later.
It also appears that both articles base their study largely on BMI, which is well-known for being an outdated indicator of health in relation to weight. It works for those that are not athletic or abnormal, but is unreliable for anyone in those two categories. What might have been a better criterion for this study was body fat, which correlates much better to a person's weight.
So? It's an analysis of populations. BMI is terrible if you are dealing with individuals, but when dealing with a large population in a study, it's just as good a measurement, and much easier to obtain: Going over records of physicals will easily give you BMIs. How many physicals look at body fat?
It's just like gambling: It's very risky to put all your money into a single heads or tails coin flip, even if someone gave you 2.2:1 odds. But it's not foolish to open a casino where you give the house a very slim advantage. The statistical anomalies even out in the end.
I think those comments can be meaningful. I avoid doing massive ad blocking, but in some cases, I've blocked ads from locations that created major slowdown in page loads.
It's an example of why ad delivery services are failing us: In modern browsers, delays for ad loading do happen from time to time, regardless of the size of your internet tubes. Bad performance makes even users that aren't ad averse want to block them, just for the performance gain, just like aggressive DRM makes users that have no problem paying for software be tempted to become pirates.
You might find that the theoretical extra buying power on an international market withers and dies when it comes to consumer prices, and it's not just about software. From videogames, to cameras and bell peppers, it's very rare to see an euro buying more stuff than a dollar can, even after taking VAT into account. I had that issue last summer, on a trip to Spain: Pretty much every item was more expensive than the equivalent in middle America, including housing. The one thing that was lower was salaries, even before taxes.
Friends and family that came to the US on vacation have been making cheap purchases to take home for a few decades, even before the euro started. The only exception was the late 90s, where the dollar traded so high as to reach price parity at retailers.
So, you see, retail prices do not really react that much to currency volatility, because retail prices have relatively little to do with the cost of goods. Only in an Argentinian-style devaluation do prices actually change with the exchange rate. Now, if we were talking commodities, it'd be a completely different story
God of war for difficult platforming??! Mario Galaxy, the easiest 3D Mario game by a longshot? Did you really play those games?
You seem to like to use words like hardcore game and hardcore genre, but that's all a bunch of bologna. There's no such thing as a hardcore genre. The concept of hardcore game is meaningless, and only a way for stupid teens to claim that other games don't have enough childish violence to appeal to them.
Some parts of education are better deal with at the local level, true, but doing everything at the local level just leads to an even higher politization.
In pretty much any other Western country, you'll see that Curriculum guidelines are given all the way from the national government. Having a state decide what can be covered in a biology class makes as much sense as a school board trying to redefine gravity. Let the local governments deal with their local problems, but don't just get rid of every federal guideline in the name of federalism. Making every single decision locally can be very inefficient.
But in C++, many programs don't really deal with resource deallocation directly: That's what reference counting pointers are for. The resources get wiped the moment nothing references them anymore, and we can release both memory and connections at the exact moment they are not used anymore. In Java, just as you said, we end up doing it explicitly, doing a lot more work by hand, and risking destroying a resource that someone still has a reference to.
Sure, the code can still work, but it's a lot harder to get that done than to just let the destructors do their job when the reference counter reaches 0.
I write in Java every day, but if my code was running on anything other than an application server that takes care of most of my non-memory resources, I'd be wishing for the equivalent of a destructor every week.
It's not really about memory management though, but about resource management. Initialize your resources at object construction and release them at destruction is a very simple and elegant solution that is common on many C++ projects. In Java, we can't really do anything like that. We can't really encapsulate the resources without jumping through hoops.
In my Job in the US, I'd take that in a heartbeat. However, Salaries in Spain don't really compare. Every time I visit, I test the market to see if it'd be worth coming back, but the salary I'd get for a similar position is about 1/4th of what I make. And that's comparing Spain and Missouri, not Bay Area salaries.
Spain has an entire underclass of young university graduates, called the 'mileuristas', because they make about a thousand euros a month. Many bank employees don't make much more than that, and Spain's living expenses are higher than those in middle America, except for the free universal health care. As a rule of thumb, what you can buy for a dollar costs a euro in Spain.
Would you drop your job for 5 years if all you were getting back was $300-$400 a month? I sure wouldn't. Most American severance packages for a programmer have similar values, once you take into account that in the US you get the money upfront.
Even in modern C++, memory allocation and destruction is commonly done behind the scenes using reference counting pointers.
Whenever you are dealing with anything that resembles a complex data structure, making sure that the programmer has to think very little about memory allocation is a huge boon. Programmer productivity across the alst 50 years hasn't changed much, if we look at statements written per month. The main difference is that 50 years ago, our statements did a lot less than they do now. A programmer that doesn't have to think of memory requirements can spend more time thinking about the actual business requirements, and improving the core algorithms.
Leaving the memory management to a library is also a good way of minimizing the damage that a careless programmer can make. I remember the cost of a bad programmer in a team coding in C: It'd take longer to track his memory leaks, pointer overlaps buffer overruns than it would have taken the more reliable programmers to write the code from scratch. In languages like Java and C#, one has to really be working hard to be a true liability. There's just a lower barrier of entry. In a world that's not filled with uberprogrammers, but barely competent ones, this is a huge boon.
And that's why few shops making business software would even dare to start a new project in a language without garbage collection: Unless you have quite a special team, a great QA process and are memory constrained, you'll be more productive in a language that is further away from the metal.
But it's an item that he could never get! If someone's right hand get cut off in an accident, should someone crippled in that way be considered in violation of US law if they try to enter the country? We scan both hands, you know...
A person coming to the US is accepting to be subject to biometric scans. If the biometric methodology that we have at the border happens to be unable to cope with someone's disability, it's the system that is the problem for not being able to handle edge cases.
The difference is optimization cost: Run time recompilation happens automagically in java 6: if the same branch of any loop happens to be hit 90% of the time, the VM will change its implementation for free, to make sure the right branch is in the pipeline already. You can technically do the same thing in C, but the effort required stops paying off quite quickly: C can theoretically beat Java every time if the programmer has infinite time and resources. In practice, it's faster many times, but sometimes it will lose.
Probably the fact that, as private citizens, we'd be arrested if we were trying the same strategy on police cars. We are allowed to follow a policeman walking down the street, right?
There's also the fact that the GPS device would be attached to our property, which seems to me like a pretty significant change. A cop could put your home under surveillance, but could they drill holes into your siding to attach the cameras?
Oh well, that's what we get in a country that has no clear provisions for a right to privacy.
I've talked to a few former developers: Few people that started the project where working for 3D Realms last year. Some core positions were abandoned twice during development.
The project never had real focus or a clear schedule. The programmers would work on adding feature X or Y to their engine of the year. Those features were chosen because important people thought they were cool, not because they were in a design document. They continued adding random features until the next engine came to market, and management decided that they had to switch engines, throwing most of the work away, including large chunks of game assets. By the second time that happens, morale is a disaster, so performance suffers. Eventually, people quit, because saying that you worked for 5 years in DNF is not exactly a good resume builder. Then, the exact same thing happens to the replacements.
When your intended result is to make a very interactive game that also has the best graphics in the industry, you need either a well defined target in the future and someone that can design an engine that will be the top engine by the day you want to release, or have a very reduced schedule, and a ridiculous amount of manpower, with the risk that involves. 3D Realms didn't do either.
When a flight takes about an hour, high speed rail will beat it in both real door-to-door speed and price. This doesn't just help the NE corridor, but allows for lines like Columbus-Chicago-St Louis-Kansas.
Well, on a console you can still get discounts, or go to a used market for games. If the only way to get a game was at full price, without discounts or secondary market, consoles wouldn't be doing so good.
And that is why electronic only, DRMd purchases will lower sales: People that are unwilling to pay full price are subsidizing sales to people that do pay full price and resell.
The H1-B program is evil, but even if anyone that qualified for an H1-B could ask for a green card instead, it'd still be painfully slow. Let's look at the Green Card process. How long does it take for people who have jumped through all the hoops to get one?.Take into account that, depending or where you come from, it could have taken close to a decade to get to this step:
I-485 processing times, the last, step in the process: It takes over 9 months for people seeking asylum, And close to two years for employment-based applications. Someone with an October 2007 filing date probably has another year or two left, given the flood of applications they had that summer.
So it's not just the H1-B process that is slowing people's mobility. The H1-B's trying to stay, and that work for companies willing to jump through all the hoops for them, have flooded the Green Card process anyway.
There aren't anywhere as many forests in Spain as there used to be in 1600, but mostly a desert? you've got to be kidding! There's a desert near Almeria, but it doesn't account for even close to 10% of the land area. If that's enough for you to qualify the country as a desert, I bet you'd claim that Africa, Asia and North America are mostly deserts too!
That $4,000 I speak of is our out-of-pocket costs. We have insurance for the rest.
You must have good insurance then. The best my company offers will still charge %20 of the hospital bill. 10K a day worth of hospital bill for a stay in the ICU is common around here, so the 20% of that reaches OOP maximums real quick.
Slashdot Mirror
Ah, but when you buy a few drives for your RAID array, with the same model and revision, and give them all very similar usage patterns, in the same exact location, then it's a lot more likely that more than one drive will fail on you in quick succession. making your RAID array a lot less safe than it seemed at first.
A conversion layer is wasteful when there's only one way to look at your data. In that case, key value pairs can perform better, no question.
The problem lies in situations where you need to look at the data in 5 different ways. or 50. Then, a single object model for your data is a whole lot less practical than having a conversion layer, and have the data in a very flexible format, like a relational model.
The PostgreSQL documentation is about as good as I've ever seen in an Open Source product. The manual is typically well written, and it is full of good examples. It makes something like JBoss look line an underdocumented mess.
And if at any point you find that a page of documentation is missing some detail, you can always post it as a comment in that same page, and save the rest of us some grief.
Working those hours, in a night shift, that far from home, seems to me like a terrible long term arrangement. You'll cut years off your life. It'll make sure you can't get even a semblance of a social life. As a support job, it might not even pay enough as to allow you to see it as a temporary sacrifice for a better lifestyle later.
Look for another job, pronto.
It also appears that both articles base their study largely on BMI, which is well-known for being an outdated indicator of health in relation to weight. It works for those that are not athletic or abnormal, but is unreliable for anyone in those two categories. What might have been a better criterion for this study was body fat, which correlates much better to a person's weight.
So? It's an analysis of populations. BMI is terrible if you are dealing with individuals, but when dealing with a large population in a study, it's just as good a measurement, and much easier to obtain: Going over records of physicals will easily give you BMIs. How many physicals look at body fat?
It's just like gambling: It's very risky to put all your money into a single heads or tails coin flip, even if someone gave you 2.2:1 odds. But it's not foolish to open a casino where you give the house a very slim advantage. The statistical anomalies even out in the end.
I think those comments can be meaningful. I avoid doing massive ad blocking, but in some cases, I've blocked ads from locations that created major slowdown in page loads.
It's an example of why ad delivery services are failing us: In modern browsers, delays for ad loading do happen from time to time, regardless of the size of your internet tubes. Bad performance makes even users that aren't ad averse want to block them, just for the performance gain, just like aggressive DRM makes users that have no problem paying for software be tempted to become pirates.
You might find that the theoretical extra buying power on an international market withers and dies when it comes to consumer prices, and it's not just about software. From videogames, to cameras and bell peppers, it's very rare to see an euro buying more stuff than a dollar can, even after taking VAT into account. I had that issue last summer, on a trip to Spain: Pretty much every item was more expensive than the equivalent in middle America, including housing. The one thing that was lower was salaries, even before taxes.
Friends and family that came to the US on vacation have been making cheap purchases to take home for a few decades, even before the euro started. The only exception was the late 90s, where the dollar traded so high as to reach price parity at retailers.
So, you see, retail prices do not really react that much to currency volatility, because retail prices have relatively little to do with the cost of goods. Only in an Argentinian-style devaluation do prices actually change with the exchange rate. Now, if we were talking commodities, it'd be a completely different story
God of war for difficult platforming??!
Mario Galaxy, the easiest 3D Mario game by a longshot?
Did you really play those games?
You seem to like to use words like hardcore game and hardcore genre, but that's all a bunch of bologna. There's no such thing as a hardcore genre. The concept of hardcore game is meaningless, and only a way for stupid teens to claim that other games don't have enough childish violence to appeal to them.
Some parts of education are better deal with at the local level, true, but doing everything at the local level just leads to an even higher politization.
In pretty much any other Western country, you'll see that Curriculum guidelines are given all the way from the national government. Having a state decide what can be covered in a biology class makes as much sense as a school board trying to redefine gravity. Let the local governments deal with their local problems, but don't just get rid of every federal guideline in the name of federalism. Making every single decision locally can be very inefficient.
But in C++, many programs don't really deal with resource deallocation directly: That's what reference counting pointers are for. The resources get wiped the moment nothing references them anymore, and we can release both memory and connections at the exact moment they are not used anymore. In Java, just as you said, we end up doing it explicitly, doing a lot more work by hand, and risking destroying a resource that someone still has a reference to.
Sure, the code can still work, but it's a lot harder to get that done than to just let the destructors do their job when the reference counter reaches 0.
I write in Java every day, but if my code was running on anything other than an application server that takes care of most of my non-memory resources, I'd be wishing for the equivalent of a destructor every week.
It's not really about memory management though, but about resource management. Initialize your resources at object construction and release them at destruction is a very simple and elegant solution that is common on many C++ projects. In Java, we can't really do anything like that. We can't really encapsulate the resources without jumping through hoops.
In my Job in the US, I'd take that in a heartbeat. However, Salaries in Spain don't really compare. Every time I visit, I test the market to see if it'd be worth coming back, but the salary I'd get for a similar position is about 1/4th of what I make. And that's comparing Spain and Missouri, not Bay Area salaries.
Spain has an entire underclass of young university graduates, called the 'mileuristas', because they make about a thousand euros a month. Many bank employees don't make much more than that, and Spain's living expenses are higher than those in middle America, except for the free universal health care. As a rule of thumb, what you can buy for a dollar costs a euro in Spain.
Would you drop your job for 5 years if all you were getting back was $300-$400 a month? I sure wouldn't. Most American severance packages for a programmer have similar values, once you take into account that in the US you get the money upfront.
Even in modern C++, memory allocation and destruction is commonly done behind the scenes using reference counting pointers.
Whenever you are dealing with anything that resembles a complex data structure, making sure that the programmer has to think very little about memory allocation is a huge boon. Programmer productivity across the alst 50 years hasn't changed much, if we look at statements written per month. The main difference is that 50 years ago, our statements did a lot less than they do now. A programmer that doesn't have to think of memory requirements can spend more time thinking about the actual business requirements, and improving the core algorithms.
Leaving the memory management to a library is also a good way of minimizing the damage that a careless programmer can make. I remember the cost of a bad programmer in a team coding in C: It'd take longer to track his memory leaks, pointer overlaps buffer overruns than it would have taken the more reliable programmers to write the code from scratch. In languages like Java and C#, one has to really be working hard to be a true liability. There's just a lower barrier of entry. In a world that's not filled with uberprogrammers, but barely competent ones, this is a huge boon.
And that's why few shops making business software would even dare to start a new project in a language without garbage collection: Unless you have quite a special team, a great QA process and are memory constrained, you'll be more productive in a language that is further away from the metal.
But it's an item that he could never get! If someone's right hand get cut off in an accident, should someone crippled in that way be considered in violation of US law if they try to enter the country? We scan both hands, you know...
A person coming to the US is accepting to be subject to biometric scans. If the biometric methodology that we have at the border happens to be unable to cope with someone's disability, it's the system that is the problem for not being able to handle edge cases.
The difference is optimization cost: Run time recompilation happens automagically in java 6: if the same branch of any loop happens to be hit 90% of the time, the VM will change its implementation for free, to make sure the right branch is in the pipeline already. You can technically do the same thing in C, but the effort required stops paying off quite quickly: C can theoretically beat Java every time if the programmer has infinite time and resources. In practice, it's faster many times, but sometimes it will lose.
Exactly in the same way that you only need two sports fans to get accurate knowledge of who is going to win every baseball game this season.
Probably the fact that, as private citizens, we'd be arrested if we were trying the same strategy on police cars. We are allowed to follow a policeman walking down the street, right?
There's also the fact that the GPS device would be attached to our property, which seems to me like a pretty significant change. A cop could put your home under surveillance, but could they drill holes into your siding to attach the cameras?
Oh well, that's what we get in a country that has no clear provisions for a right to privacy.
I've talked to a few former developers: Few people that started the project where working for 3D Realms last year. Some core positions were abandoned twice during development.
The project never had real focus or a clear schedule. The programmers would work on adding feature X or Y to their engine of the year. Those features were chosen because important people thought they were cool, not because they were in a design document. They continued adding random features until the next engine came to market, and management decided that they had to switch engines, throwing most of the work away, including large chunks of game assets. By the second time that happens, morale is a disaster, so performance suffers. Eventually, people quit, because saying that you worked for 5 years in DNF is not exactly a good resume builder. Then, the exact same thing happens to the replacements.
When your intended result is to make a very interactive game that also has the best graphics in the industry, you need either a well defined target in the future and someone that can design an engine that will be the top engine by the day you want to release, or have a very reduced schedule, and a ridiculous amount of manpower, with the risk that involves. 3D Realms didn't do either.
When a flight takes about an hour, high speed rail will beat it in both real door-to-door speed and price. This doesn't just help the NE corridor, but allows for lines like Columbus-Chicago-St Louis-Kansas.
Time to wrap our keyboards with tinfoil, or at least put a tinfoil filter in the tube that connects our computer with slashdot's servers.
Well, on a console you can still get discounts, or go to a used market for games. If the only way to get a game was at full price, without discounts or secondary market, consoles wouldn't be doing so good.
And that is why electronic only, DRMd purchases will lower sales: People that are unwilling to pay full price are subsidizing sales to people that do pay full price and resell.
The H1-B program is evil, but even if anyone that qualified for an H1-B could ask for a green card instead, it'd still be painfully slow. Let's look at the Green Card process. How long does it take for people who have jumped through all the hoops to get one?.Take into account that, depending or where you come from, it could have taken close to a decade to get to this step:
https://egov.uscis.gov/cris/jsps/Processtimes.jsp?SeviceCenter=NSC
I-485 processing times, the last, step in the process: It takes over 9 months for people seeking asylum, And close to two years for employment-based applications. Someone with an October 2007 filing date probably has another year or two left, given the flood of applications they had that summer.
So it's not just the H1-B process that is slowing people's mobility. The H1-B's trying to stay, and that work for companies willing to jump through all the hoops for them, have flooded the Green Card process anyway.
There aren't anywhere as many forests in Spain as there used to be in 1600, but mostly a desert? you've got to be kidding! There's a desert near Almeria, but it doesn't account for even close to 10% of the land area. If that's enough for you to qualify the country as a desert, I bet you'd claim that Africa, Asia and North America are mostly deserts too!
Did they hack the ATM machines after stealing the PIN numbers?
I have to go work in some CSS style sheets for a web site that links ISBN numbers to UPC codes. I hope they don't make me redundant.
That $4,000 I speak of is our out-of-pocket costs. We have insurance for the rest.
You must have good insurance then. The best my company offers will still charge %20 of the hospital bill. 10K a day worth of hospital bill for a stay in the ICU is common around here, so the 20% of that reaches OOP maximums real quick.