This totally sucks. Now I need some complicated language-specific search tool that is sure to have fewer options than grep. It's probably not even scriptable, and surely much slower. Why do you want me to suffer?
That and the fact that C++ operates on a higher level of abstraction and therefore requires much more careful consideration and planning.
Planning... so you plan, then write, and you are done? This is a project that is expected to live for decades. The requirements change.
If you need more planning, that's a bad sign.
The problems I have seen in the past have all been centered around people not quite understanding the nature of C++ and wanting to immediately put all those bright new features to "good" use, by overloading everything and indiscriminately inheriting from any number of classes.
Yes. Expect it to happen, despite any efforts to resist. This is the nature of a project with more than one developer.
The secret to good programming has always been to keep it simple - this is twice as important in C++, and the language has some great features for doing so, but you really have to understand what it is you are trying to achieve.
Human brains are not SMP hardware. A group of people working together will not all see the same big picture.
Nobody on Earth fully understands all of C++. Every C++ programmer knows a subset. My subset is not your subset; it is unique to me as yours is to you. Features I love make you uneasy at best, and your pet features do likewise for me.
The features sneak in here and there... well I just can't resist because I really NEED my favorite feature! Think of the classic 2-circle Venn diagram for two people's C++ knowledge: you might hope for your project to be that intersection in the middle, but it's going to end up with the big fat union of pet features.
Really, you can't stop it. Resistance is futile.
You'll see exceptions, then memory leaks, an attempt to solve it with some kind of braindead "smart" pointer, somebody needs multiple inheritance, some ass overloads the comma operator or () operator, overloading gets sort of ambiguous with differences between the 32-bit and 64-bit builds, Boost gets pulled in with compile times and start-up times going to Hell, people cry for Java-style garbage collection...
What about theraputic reboots? AFAIK, these systems are persistant system images. If the hardware is flawless and the OS is bug-free, they can run forever. You can even cut power, restore it, and be right back where you were... in theory. If system state is ever corrupted however, you're in serious trouble. AFAIK a "real" reboot is like a fresh OS install with all your data gone. Those capabilities can not outlive the processes (if you call them "processes" -- persistant objects?) that create or otherwise own them.
BTW, API breakage goes way beyond GUI apps and POSIX. You broke the C language itself, both development (header file inclusion) and the standard library.
Let's ignore the API/ABI issue. Suppose a miracle happens, and every app developer decides to exclusively support native KeyKOS and EROS features.
How would it even work?
Without filenames, there is no reasonable way for the human to express things. I'm not going to type a UUID.
Without programs being able to scan directories, they can't offer nice File/Open dialog boxes. Consider the gimp, which provides a preview thumbnail.
Consider the common Edit/Insert operation. The app goes looking for a file to insert into a document.
Consider something like Open Office or Firefox. These apps have only one instance normally, even if you click the icon multiple times. This is for consistancy (multiple instances editing a single file is bad) and for memory use reduction.
What would your GUI look like? How non-desktop must it be?
You're not getting any if she's focused on the TV.
Well, maybe doggy style so she can still see the TV. If she does cum, probably she's fantasizing about some guy on TV instead of you.
Evidence suggests that people fuck like mad when they can't watch TV. South-central Florida had a bit of a baby boom about 9 months after having a week or two of hurricane-caused power loss. No power means no TV, which means passionate fucking.
People in the USA have the weird experience of public schools going on about Africa having wonderful culture and natural resources, then as adults slowly realizing that the place is totally fucked up.
Suppose a woman becomes a biology professor. She spend her fertile years studying, either in a lab or out in some horrid part of the world. Does she reproduce?
Suppose a woman goes door to door trying to save people. (from science I guess!) She meets a lot of nice guys. She has no significant way to support herself. She thinks birth control encourages sin. Does she reproduce?
Given that mental traits are largely genetic, you can tell where humanity is going. The resulting creatures ("humans") will of course **KNOW** that it was God's will to strengthen people's faith.
The founder and first few employees got rich from the business idea and the investment. They weren't really getting money from being PHP coders.
Later employees writing code probably don't earn so much. They just do PHP, which is a low-value skill.
An exception probably exists for the people who wrote a new PHP engine for facebook. This was naturally written in C, and it generates machine code on the fly. (it is a JIT engine for PHP) These people made the whole site more efficient, and probably earn pretty good pay.
Trying to get rich off of PHP is a bit like trying to get rich off of basketball. Chances are, you'll end up being the equivalent of a gym teacher.
That's because they are specifically designed to abstract away the computer hardware.
The job won't pay well if any fool can do it.
It also sounds like a world of painful "business logic" shit, which should remind you of COBOL and Visual Basic. At best you get to implement yet another shopping cart or convert the tax code into a computer program. You'll need a lot of vodka to put up with that.
Life is better when you are writing firmware, boot loaders, drivers, exploits, kernels, performance-sensitive code, and so on.
You're supposed to allocate the buffer with a guard page at the end. For example, you can use mmap() with PROT_NONE or mprotect() with only PROT_READ. You'll get a SIGSEGV or SIGBUS when gets() reaches the guard page.
Do the gets() call in a child process, let it die on the signal or call _exit() from the handler, and determine success or failure from the process exit status. Alternately you can siglongjmp() out of a signal handler, but you should assume that this leaves the stdin stream with locks taken and thus unusable.
Be sure to put this in server and setuid programs. It gets the hackers all excited, then crushes their dreams.
The USSR launched plenty of full-blown reactors, and RTGs are still popular.
You're not supposed to park ground-attack devices (like ICBMs) in space. Of course, if you imagine that Russia hasn't done that for decades, you're pretty gullible.
Look, we just need a bright flash of light. It doesn't have to be a laser.
Put up a large number of satellites, much like GPS or Iridium. Each one holds a 30 megaton nuke. When an area is affected by a tsunami, we set off all the nukes that would be visible above the horizon.
Tsunamis are rare enough that we can normally launch a replacement system fast enough, assuming we don't put spares in different orbits. Have replacements ready to launch.
You missed most of the good ones! Many are really cool ways too kill people.
A modern crossbow can be pretty small. It's less than a foot wide, and about a foot long. It takes bolts that are half a foot long. Optional: add poison, such as ricin.
The attack dog is already popular in the UK. They are fast and deadly.
A blow gun can work. Poison is required.
The molotov cocktail is good, especially if you hit the sole escape route from a building (commonly an interior staircase) or lob it into a moving car.
The compound bow, as used for hunting, is a bit large but otherwise excellent. People with balls the size of watermelons use bows to hunt bears.
The Democrats allowed a few trivial bits of Republican input in order to pretent that some silly "bipartisanship" thing was going on.
Yep, the Democrats were essentially "100 percent my way or no way". OK, 99.999% maybe. Five nines.
There was no room for any other than their ideas. They won by brute force. They knew from the start that they didn't have any reason to even listen to the Republicans regarding any issue of substance.
I should add that saying "NO" is generally the superiour option. Random shit should not become law. Law should be something that nearly everybody can agree on.
If you do allow people to sell their kidneys, would you also provide funds so that poor people could compete on equal footing with the rich when it comes to getting a life-saving transplant, so there's rough parity in opportunity to survive, much like there is with food?
I don't see why. It's not fair that somebody who has worked to earn money be unable to use it. That's like taking the money away.
There also aren't tiers of organs - it's pretty much one-size-fits-all - so in the case of a free market for vital organs you wind up with the rich getting to live and the poor getting nothing
Nope.
First there is the issue of imperfect matches. The worse the match, the more anti-rejection drugs need to be used and the more the organ will degrade.
Then there are other issues. The donar may be old, a smoker, infected, dead for quite a while, etc. Surgeons are transplanting kidneys with cancer (chop the cancer off and the kidney is good!) and lungs from smokers.
It'll take a while, because IE 9 doesn't support XP, but it'll happen. Flash dies once XP dies.
Microsoft would like to fully control the interfaces, but when they fail at that they'd at least like to stop any other company from controlling the interfaces. Microsoft will settle for open standards as required to kill things like flash.
We can thank Adobe for IE 9 getting SVG and HTML 5 video support.
Normal (to humans I guess) light is seen in the normal vertibrae way.
Infrared light needs a longer focal length, and the thing that matters is the nest below the bird. The solution is an infrared-reflective patch at the top of the eyeball, and an infrared-sensitive area at the bottom of the eyeball.
(some kind of soaring bird I don't remember, like an Eagle or vulture)
Slashdot Mirror
grep MyClassAddFloatAndInt *.c
grep add *.c
This totally sucks. Now I need some complicated language-specific search tool that is sure to have fewer options than grep. It's probably not even scriptable, and surely much slower. Why do you want me to suffer?
That and the fact that C++ operates on a higher level of abstraction and therefore requires much more careful consideration and planning.
Planning... so you plan, then write, and you are done? This is a project that is expected to live for decades. The requirements change.
If you need more planning, that's a bad sign.
The problems I have seen in the past have all been centered around people not quite understanding the nature of C++ and wanting to immediately put all those bright new features to "good" use, by overloading everything and indiscriminately inheriting from any number of classes.
Yes. Expect it to happen, despite any efforts to resist. This is the nature of a project with more than one developer.
The secret to good programming has always been to keep it simple - this is twice as important in C++, and the language has some great features for doing so, but you really have to understand what it is you are trying to achieve.
Human brains are not SMP hardware. A group of people working together will not all see the same big picture.
Nobody on Earth fully understands all of C++. Every C++ programmer knows a subset. My subset is not your subset; it is unique to me as yours is to you. Features I love make you uneasy at best, and your pet features do likewise for me.
The features sneak in here and there... well I just can't resist because I really NEED my favorite feature! Think of the classic 2-circle Venn diagram for two people's C++ knowledge: you might hope for your project to be that intersection in the middle, but it's going to end up with the big fat union of pet features.
Really, you can't stop it. Resistance is futile.
You'll see exceptions, then memory leaks, an attempt to solve it with some kind of braindead "smart" pointer, somebody needs multiple inheritance, some ass overloads the comma operator or () operator, overloading gets sort of ambiguous with differences between the 32-bit and 64-bit builds, Boost gets pulled in with compile times and start-up times going to Hell, people cry for Java-style garbage collection...
What about theraputic reboots? AFAIK, these systems are persistant system images. If the hardware is flawless and the OS is bug-free, they can run forever. You can even cut power, restore it, and be right back where you were... in theory. If system state is ever corrupted however, you're in serious trouble. AFAIK a "real" reboot is like a fresh OS install with all your data gone. Those capabilities can not outlive the processes (if you call them "processes" -- persistant objects?) that create or otherwise own them.
BTW, API breakage goes way beyond GUI apps and POSIX. You broke the C language itself, both development (header file inclusion) and the standard library.
Let's ignore the API/ABI issue. Suppose a miracle happens, and every app developer decides to exclusively support native KeyKOS and EROS features.
How would it even work?
Without filenames, there is no reasonable way for the human to express things. I'm not going to type a UUID.
Without programs being able to scan directories, they can't offer nice File/Open dialog boxes. Consider the gimp, which provides a preview thumbnail.
Consider the common Edit/Insert operation. The app goes looking for a file to insert into a document.
Consider something like Open Office or Firefox. These apps have only one instance normally, even if you click the icon multiple times. This is for consistancy (multiple instances editing a single file is bad) and for memory use reduction.
What would your GUI look like? How non-desktop must it be?
You're not getting any if she's focused on the TV.
Well, maybe doggy style so she can still see the TV. If she does cum, probably she's fantasizing about some guy on TV instead of you.
Evidence suggests that people fuck like mad when they can't watch TV. South-central Florida had a bit of a baby boom about 9 months after having a week or two of hurricane-caused power loss. No power means no TV, which means passionate fucking.
People in the USA have the weird experience of public schools going on about Africa having wonderful culture and natural resources, then as adults slowly realizing that the place is totally fucked up.
People who cheat will get executed.
It's pretty normal for serious corporate or political wrongdoing already.
Suppose a woman becomes a biology professor. She spend her fertile years studying, either in a lab or out in some horrid part of the world. Does she reproduce?
Suppose a woman goes door to door trying to save people. (from science I guess!) She meets a lot of nice guys. She has no significant way to support herself. She thinks birth control encourages sin. Does she reproduce?
Given that mental traits are largely genetic, you can tell where humanity is going. The resulting creatures ("humans") will of course **KNOW** that it was God's will to strengthen people's faith.
I suspect that Facebook is a great example.
The founder and first few employees got rich from the business idea and the investment. They weren't really getting money from being PHP coders.
Later employees writing code probably don't earn so much. They just do PHP, which is a low-value skill.
An exception probably exists for the people who wrote a new PHP engine for facebook. This was naturally written in C, and it generates machine code on the fly. (it is a JIT engine for PHP) These people made the whole site more efficient, and probably earn pretty good pay.
Trying to get rich off of PHP is a bit like trying to get rich off of basketball. Chances are, you'll end up being the equivalent of a gym teacher.
That's because they are specifically designed to abstract away the computer hardware.
The job won't pay well if any fool can do it.
It also sounds like a world of painful "business logic" shit, which should remind you of COBOL and Visual Basic. At best you get to implement yet another shopping cart or convert the tax code into a computer program. You'll need a lot of vodka to put up with that.
Life is better when you are writing firmware, boot loaders, drivers, exploits, kernels, performance-sensitive code, and so on.
You're supposed to allocate the buffer with a guard page at the end. For example, you can use mmap() with PROT_NONE or mprotect() with only PROT_READ. You'll get a SIGSEGV or SIGBUS when gets() reaches the guard page.
Do the gets() call in a child process, let it die on the signal or call _exit() from the handler, and determine success or failure from the process exit status. Alternately you can siglongjmp() out of a signal handler, but you should assume that this leaves the stdin stream with locks taken and thus unusable.
Be sure to put this in server and setuid programs. It gets the hackers all excited, then crushes their dreams.
there'll be bazillions of particles trapped in Earth's magnetic field, pounding incessantly on everything up there
just like we have today, thanks to the fusion reaction which we orbit around
FYI, the area where particles tend to get trapped is mostly avoided. LEO is below it most of the time.
It's a good thing Earth isn't constantly bathed in the light of a fusion reaction, hmmm?
Nope.
The USSR launched plenty of full-blown reactors, and RTGs are still popular.
You're not supposed to park ground-attack devices (like ICBMs) in space. Of course, if you imagine that Russia hasn't done that for decades, you're pretty gullible.
Look, we just need a bright flash of light. It doesn't have to be a laser.
Put up a large number of satellites, much like GPS or Iridium. Each one holds a 30 megaton nuke. When an area is affected by a tsunami, we set off all the nukes that would be visible above the horizon.
Tsunamis are rare enough that we can normally launch a replacement system fast enough, assuming we don't put spares in different orbits. Have replacements ready to launch.
You missed most of the good ones! Many are really cool ways too kill people.
A modern crossbow can be pretty small. It's less than a foot wide, and about a foot long. It takes bolts that are half a foot long. Optional: add poison, such as ricin.
The attack dog is already popular in the UK. They are fast and deadly.
A blow gun can work. Poison is required.
The molotov cocktail is good, especially if you hit the sole escape route from a building (commonly an interior staircase) or lob it into a moving car.
The compound bow, as used for hunting, is a bit large but otherwise excellent. People with balls the size of watermelons use bows to hunt bears.
crack babies
car crashes
infectious syringes left around (beach...)
impaired judgement leading to fights, rape, pregnancy...
economic drag on the nation
Linux has had X 11 since about 1992. It's direct, unlike on Windows where you have to run the Cygwin X 11 server.
We fully support DRM now too. The "D" stands for direct, just to be sure you know that our X 11 is really direct.
The Democrats allowed a few trivial bits of Republican input in order to pretent that some silly "bipartisanship" thing was going on.
Yep, the Democrats were essentially "100 percent my way or no way". OK, 99.999% maybe. Five nines.
There was no room for any other than their ideas. They won by brute force. They knew from the start that they didn't have any reason to even listen to the Republicans regarding any issue of substance.
I should add that saying "NO" is generally the superiour option. Random shit should not become law. Law should be something that nearly everybody can agree on.
If you do allow people to sell their kidneys, would you also provide funds so that poor people could compete on equal footing with the rich when it comes to getting a life-saving transplant, so there's rough parity in opportunity to survive, much like there is with food?
I don't see why. It's not fair that somebody who has worked to earn money be unable to use it. That's like taking the money away.
There also aren't tiers of organs - it's pretty much one-size-fits-all - so in the case of a free market for vital organs you wind up with the rich getting to live and the poor getting nothing
Nope.
First there is the issue of imperfect matches. The worse the match, the more anti-rejection drugs need to be used and the more the organ will degrade.
Then there are other issues. The donar may be old, a smoker, infected, dead for quite a while, etc. Surgeons are transplanting kidneys with cancer (chop the cancer off and the kidney is good!) and lungs from smokers.
It'll take a while, because IE 9 doesn't support XP, but it'll happen. Flash dies once XP dies.
Microsoft would like to fully control the interfaces, but when they fail at that they'd at least like to stop any other company from controlling the interfaces. Microsoft will settle for open standards as required to kill things like flash.
We can thank Adobe for IE 9 getting SVG and HTML 5 video support.
When at least one side is foreign, we can just say we're searching that side. It's in transit to/from him, so that just makes sense.
It'll get searched by his government too. That's how things have worked for millenia.
"from" the United States: foreign
"to" the United States: foreign
"through" the United States: foreign
(the missing possibility is "within")
I take "any health care" to include non-genetic fixes for genetic (and other) troubles.
Even the article isn't about germ line modification. We can inject into the eyes, not bothering with the gonads.
The issue is having humanity become unable to survive a collapse of the medical infrastructure.
Normal (to humans I guess) light is seen in the normal vertibrae way.
Infrared light needs a longer focal length, and the thing that matters is the nest below the bird. The solution is an infrared-reflective patch at the top of the eyeball, and an infrared-sensitive area at the bottom of the eyeball.
(some kind of soaring bird I don't remember, like an Eagle or vulture)