1. What does garbage collection have to do with C++?
What you call "garbage collection" is an abbreviation of "automatic garbage collection", so called to distinguish it from the manual garbage collection done with malloc/free and such.
RAII memory management is a manual garbage collection discipline.
How do you "demonstrate" the whole planet will warm into an unstoppable Venus like unlivable atmosphere? Because that's why we were told to fear CO2.
Nobody sane has been saying that scenario is likely. If that's what people you are listening to are either saying or claiming that other people are saying, then you should consider listening to other people.
Not that it isn't possible. You mentioned the incontrovertible evidence yourself: Venus. It's just that the climate models don't predict it. Of course, if you believe the climate models are unreliable and untrustworthy, then a Venusian scenario is back on the table, and you really should worry about it.
But when sane people talk about runaway effects, they are talking about scenarios that merely kill hundreds of millions of people and ruin the lives of billions more. Nothing really to worry about from a species extinction point of view, but personally I'd like to avoid that.
Your assumption that the idea stems from assumptions is erroneous.
The idea that you develop more rapidly in dynamically (FTFY) typed languages stems from observation and measurement. Like this one.
So, maybe Scala would do better than Java and C++ in such a study, I'm not saying it wouldn't. It would be interesting to see a newer study with contemporary languages.
If we wanted, we could invade Africa, one country at a time, bankroll select warlords, flood the place with guns and provide all the necessary items to shatter the local economy. That was the idea in Somalia, and unsurprisingly it blew up in our faces.
What actually happens when the US imagines itself fixing things at gunpoint.
But this is still just one study. One study that relies on self-reporting. It's a lot easier to get a high number of participants if your methodology is cheap garbage.
By sheer chance it might happen to be right, who knows? But don't base any health decisions on this just yet.
The pollution that you cause by driving your groceries home in any sort of fossil fuel car is way higher that the pollution from transporting the goods to the store. Semis and container ships don't actually pollute very much per kilogram of cargo.
That's not saying we shouldn't do something about the remaining diesel pollution. Several countries are already planning to phase out fossil fuel cars in just a few decades from now. If your country isn't, take it up with your politicians.
People died. They died from respiratory problems, heart failure or stroke, because that's what air pollution does. We don't know the names of the people that died, they are just a statistic, and we would have a hard time getting a reliable estimate of how many people died. Maybe just a few. Maybe hundreds. But people did die, and this guy made it happen.
No, it's finally making sense: Microsoft Office is an adventure game. That's why there's no documentation. That's why all the features are randomly patched together instead of being joined by a common design concept. That's why the ribbon shuffles around and changes whenever you resize the window. And "This product doesn't have a valid license" is really the grue, which sneaks up on you if you stand still too long.
So obvious in hindsight, how did I not see it before? I can't believe I didn't get the ironic joke of calling them "productivity aplications". I actually thought they were being serious!
You are in a twisty maze of spreadsheet cells, all alike.
You: In my experience there is plenty of room for improvement, therefore I do not believe this.
I hope you can see the flaw in that logic yourself. They're improving exactly the thing you say you want improved, and you're being all pissy about it.
This is a "using a desktop operating system for an embedded product" problem.
When you do that, you get millions of lines of code that are not strictly relevant to your application along for the ride. And every time there's an update, hundreds of thousands of lines may have changed, that you have to review, test, compile, and transmit the result to the device somehow, even if the actual security fix you care about is only a handful of lines.
So, judging by the comments so far, all you have to do is say "terrorists", and then all of slashdot becomes a fan of faceless, unaccountable censorship.
Let's all join hands and create a world where content is filtered by the anonymous minions of a few megacorporations, and you absolutely do not have the right to face your accuser, challenge the decision, or even know the rules by which you are being judged.
HTML has had those since the very start. The current crop of web browsers stink at how they display it: They could so very easily display a TOC based on the headings, and provide controls for navigating sections. They don't, but that's not the markup language's fault.
Why would you care? You can make your editor show whatever indent you like. Just tell it to display leading spaces double-wide or half-wide or whatever you want.
Your current editor may not have that feature, but it could have. As long as the format stored on disk uses spaces, then it is trivial to infer which indent was used. Emacs (and many other editors I'm sure) can do that part already. So even if spaces are used on disk, your editor UI could display it to you exactly as if tabs were used.
But it doesn't work the other way around: If tabs are stored on disk, then the information is just not there. You can't reliably guess the indent the previous author used. That's why the files stored on disk need to use spaces.
FTFY. If you go down that road, it'll never stop. There's always going to be one more feature that's missing, and with new features comes bugs, and with bugs come security holes.
At the end of the day, you need something that's Turing-equivalent, so you can recombine known features in new and interesting ways. I just hope CSS doesn't end up being that Turing-equivalent something.
Actually breakthroughs were planned, 20 years ago. Everyone was used to CPU speed doubling every other year, so they planned accordingly, and that included pouring enough resources into R&D to make it happen. Because everyone knew that if they didn't, two years from now their product would be obsolete because someone else would have made a breakthrough.
What you call "garbage collection" is an abbreviation of "automatic garbage collection", so called to distinguish it from the manual garbage collection done with malloc/free and such.
RAII memory management is a manual garbage collection discipline.
Nobody sane has been saying that scenario is likely. If that's what people you are listening to are either saying or claiming that other people are saying, then you should consider listening to other people.
Not that it isn't possible. You mentioned the incontrovertible evidence yourself: Venus. It's just that the climate models don't predict it. Of course, if you believe the climate models are unreliable and untrustworthy, then a Venusian scenario is back on the table, and you really should worry about it.
But when sane people talk about runaway effects, they are talking about scenarios that merely kill hundreds of millions of people and ruin the lives of billions more. Nothing really to worry about from a species extinction point of view, but personally I'd like to avoid that.
Don't worry. It'll kill brain cells just as fast as it always has.
Exactly, so what are you complaining about?
What you should do is read the fine article, which actually answers your question.
Your assumption that the idea stems from assumptions is erroneous.
The idea that you develop more rapidly in dynamically (FTFY) typed languages stems from observation and measurement. Like this one.
So, maybe Scala would do better than Java and C++ in such a study, I'm not saying it wouldn't. It would be interesting to see a newer study with contemporary languages.
If we wanted, we could invade Africa, one country at a time, bankroll select warlords, flood the place with guns and provide all the necessary items to shatter the local economy. That was the idea in Somalia, and unsurprisingly it blew up in our faces.
What actually happens when the US imagines itself fixing things at gunpoint.
But this is still just one study. One study that relies on self-reporting. It's a lot easier to get a high number of participants if your methodology is cheap garbage.
By sheer chance it might happen to be right, who knows? But don't base any health decisions on this just yet.
The pollution that you cause by driving your groceries home in any sort of fossil fuel car is way higher that the pollution from transporting the goods to the store. Semis and container ships don't actually pollute very much per kilogram of cargo.
That's not saying we shouldn't do something about the remaining diesel pollution. Several countries are already planning to phase out fossil fuel cars in just a few decades from now. If your country isn't, take it up with your politicians.
People died. They died from respiratory problems, heart failure or stroke, because that's what air pollution does. We don't know the names of the people that died, they are just a statistic, and we would have a hard time getting a reliable estimate of how many people died. Maybe just a few. Maybe hundreds. But people did die, and this guy made it happen.
Tell me again that 40 months is harsh.
No, it's finally making sense: Microsoft Office is an adventure game. That's why there's no documentation. That's why all the features are randomly patched together instead of being joined by a common design concept. That's why the ribbon shuffles around and changes whenever you resize the window. And "This product doesn't have a valid license" is really the grue, which sneaks up on you if you stand still too long.
So obvious in hindsight, how did I not see it before? I can't believe I didn't get the ironic joke of calling them "productivity aplications". I actually thought they were being serious!
You are in a twisty maze of spreadsheet cells, all alike.
Tortious interference.
I'm not saying they would win, but there's no reason for Linus to stir up that kind of trouble.
So you trust the slashdot summary, do you? You must be new here. Read the linked article. Look at the numbers for the first version you haven't tried.
Article: Improvements have been made.
You: In my experience there is plenty of room for improvement, therefore I do not believe this.
I hope you can see the flaw in that logic yourself. They're improving exactly the thing you say you want improved, and you're being all pissy about it.
This is a "using a desktop operating system for an embedded product" problem.
When you do that, you get millions of lines of code that are not strictly relevant to your application along for the ride. And every time there's an update, hundreds of thousands of lines may have changed, that you have to review, test, compile, and transmit the result to the device somehow, even if the actual security fix you care about is only a handful of lines.
They're channeling money to organised crime. Legal or not, that makes them crooks in my book.
So, judging by the comments so far, all you have to do is say "terrorists", and then all of slashdot becomes a fan of faceless, unaccountable censorship.
Let's all join hands and create a world where content is filtered by the anonymous minions of a few megacorporations, and you absolutely do not have the right to face your accuser, challenge the decision, or even know the rules by which you are being judged.
about:memory would probably tell you something useful to put in the bug report.
Pro tip: slashdot AC commenting is not the optimal way to report bugs that you want fixed.
The markup you are looking for is H1/H2/H3/...
HTML has had those since the very start. The current crop of web browsers stink at how they display it: They could so very easily display a TOC based on the headings, and provide controls for navigating sections. They don't, but that's not the markup language's fault.
Perhaps you live in a region of the world where MS has chosen not to serve ads? I'm pretty sure the EU is one such region.
No I did not.
I'm sorry I didn't log in sooner to notice your reply; by now the discussion is long gone and I'm not going to take the time to explain.
Why would you care? You can make your editor show whatever indent you like. Just tell it to display leading spaces double-wide or half-wide or whatever you want.
Your current editor may not have that feature, but it could have. As long as the format stored on disk uses spaces, then it is trivial to infer which indent was used. Emacs (and many other editors I'm sure) can do that part already. So even if spaces are used on disk, your editor UI could display it to you exactly as if tabs were used.
But it doesn't work the other way around: If tabs are stored on disk, then the information is just not there. You can't reliably guess the indent the previous author used. That's why the files stored on disk need to use spaces.
The next thing missing are animation actions
FTFY. If you go down that road, it'll never stop. There's always going to be one more feature that's missing, and with new features comes bugs, and with bugs come security holes.
At the end of the day, you need something that's Turing-equivalent, so you can recombine known features in new and interesting ways. I just hope CSS doesn't end up being that Turing-equivalent something.
Actually breakthroughs were planned, 20 years ago. Everyone was used to CPU speed doubling every other year, so they planned accordingly, and that included pouring enough resources into R&D to make it happen. Because everyone knew that if they didn't, two years from now their product would be obsolete because someone else would have made a breakthrough.
Those "bloated libraries and OS processes" are at 0% CPU most of the time. They take up space, but they have no impact on peak CPU performance.