I disagree over the degree of which this would be a problem - think of it more like the free market. Under ideal conditions, the best ideas with the broadest appeal tend to win, grow and evolve, while the worst ideas with little appeal tend to fade away relatively quickly.
That's fantasy. The best ideas often wither while mediocre - even bad ones - flourish. It also makes the foolish assumption that "best" conflates with "broadest appeal".
MacDonalds didn't get where they were because their products were the best. Their milkshakes taste like library paste. They got there because once they'd achieved critical mass in the market - as the old saying goes: Nothing Succeeds Like Success. Once customers knew that they could obtain a consistent product from coast-to-coast, even though it was consistently second-rate, growth was assured.
Or perhaps an example closer to home. The Commodore Amiga. The first mass-market computer to include Total Harmonic Distortion and Stereo Separation specs on the outside of the package. The first mass-market computer to come out-of-the-box with color graphics (accelerated), Hi-fi stereo sound and full pre-emptive real-time multi-tasking. Even most modern-day systems aren't real-time.
This was the company that "succeeded in spite of itself". Demonstrating that incompetent government isn't the only way to kill competitiveness, Commodore fielded a superior product which could have been even more successful if they hadn't been cursed with incompetent management.
But bad management or not, I'm really doubtful that they'd own the market today. The Wintel platform was already too well entrenched and "Nobody Ever Got Fired for buying IBM/Microsoft/Intel". Even Apple is just an also-ran. The competiton was inferior, but it was sufficient and these days only a few tattered remnants are all that remains of the Amiga.
I've no doubt that the overhead of https can be more than paid for if website designers would lay off the Singing Flowers and Dancing Fairies. Toss the gratuitous multi-media. Especially the auto-playing stuff. It's cheap and cheesy and makes me seriously think of avoiding the site altogether, whether it's local content or 3d-party adverts.
And while you're at it, calculate the slow-filling parts of the page in advance so that the [censored] thing doesn't bounce up and down like a demented ping-pong ball as it loads. The only thing more irritating than having a page continually re-map itself while you're reading it is to have the stupid thing auto-reload and throw you back to the top of it.
Jesus fucking christ, give it a break. Your kid is 4.
Indeed. Why can't she be both a princess and a scientist? Why can't engineers wear a tiara, nice gowns, and be feminine? I think the problem here is the dad's attitude, not the daughter's.
Indeed. She's 4. At 4, wearing a lab coat and a tiara at the same time is hardly remarkable. On the other hand, wanting to be a princess when you're 14 is another matter. Unless you're Princess Bubblegum.
Maybe she'll turn out to be scientifically inclined. Maybe not. I wouldn't force it - that's a pretty certain recipe for failure. You can encourage it by preferring to suggest ways for her to find answers when she asks questions instead of simply giving answers straight up.
Nonsense. I've known way too many animals, from way too many phylums, that will go to great lengths to get a good stiff drink (Or lick toads, etc.) to give any credence to the idea that the appeal of consuming mind-altering substances is tied to some human evolutionary shift.
One thing I've discovered over the years is that any sentence that begins with "Man is the only animal who..." is probably incorrect.
No matter HOW bizarre it is.
Somewhere there's probably an animal species that files Income Taxes.
Back in the time of Fairies and Unicorns, every software release was a visit from Santa Claus. Each new release was more wonderful and feature-laden than the one before.
Then came Windows 2000. This was when it all changed, I think. ET began to "phone home" via the Internet, the software license keys weren't just something that you could type in - now they had to be "real" keys. And Microsoft decided that they would be selective about what multi-media formats they supported. As in, if they didn't "own" it, they wouldn't support it. The Grinch was beginning to appear.
But the happy little penguins played on, and each new Linux release was Christmas.
Until certain developers decided that they "knew" what was best for the unwashed masses. One of the first examples was when Nautilus lost one of its most popular window display options. That caused a mighty uproar, to the point where after many futile attempts to persuade the masses, a solution was presented that more or less restored what the Grinch had taken.
Gnome3 brought the Grinch out into the open. Yes, it was a cleaner, more dynamic display. It was certainly prettier. But some of us aren't using our computers to look good, we're using them to (allegedly) be productive. And the Gnome3 Grinch stole our applets.
As usual, the apologists had all sorts of excuses why I was wrong not to be properly awed. But all those grody little applets served very important purposes. Since they were in the margins of the display, they couldn't be covered up by sliding windows. They were always visible from every desktop. And this was important because when the machine went South, it was often the case that the reason could be seen from those applets even though the display was too paralyzed to permit switching to another desktop or launching a diagnostic app.
Which is why I'm now a happy little Cinnamon user. It gave me my applets back. And, from what I can see, it's actually a lot easier to write Cinnamon applets than it ever was to write Gnome applets, should I be so inclined.
But the Grinch is still creeping around. Gnome3 fixed a lot of the things that offended people, but as far as I know, the applets weren't among them. And now we have systemd playing Grinch as well. What's next? I shudder to think, but I may drop my longstanding relationship with Red Hat for Debian if systemd is going to stay the way it is.
I whine. I complain loudly. But given a choice, I also vote with my feet. Which is why I'm running Cinnamon.
You were more forgiving than I was. Gnome3 was pretty much the Poster Child for the Grinch paradigm of software design that's become so prevalent these days. As in, "Here's our new, wonderful product. Isn't it wonderful? Don't you just love it? What do you mean it doesn't do something essential that you've been able to do for years and you don't like it? You ingrate! You're GOING to like our new product! We're not going to fix it just because you and 100,000 whiny little dweebs claim to need those missing functions!"
So I switched to Cinnamon and have been perfectly happy ever since. I've even kept some of the Gnome3-like options turned on. But I have all those little bits of clutter that keep me attuned to systems operation that Gnome 3 took away from me.
We don't need full on product protectionism. What could work well is a tax system that rewards domestic wages.
And what good is that going to do? A 50% tax cut on zero income isn't worth much, and that's what they'd like - free labor.
Or did you mean tax cuts on the employer side? Funny, all those savings on productivity gains didn't cause employers to go out and hire more people, so why do you expect saving on taxes to be magically different? All they do is pocket the difference.
This is all nonsense. Converting data from a format that's directly accessible by general purpose utilities to one that requires a gatekeeper application just to get it exported in human-readable format is NOT "making it easier to get". It's making it HARDER to get, and that's what all the screaming is about. It takes log access from direct processability by the rich suite of text utilities that made Unix/Linux what it is and forces it to only be accessible by those utilities after exporting. You don't want to jump through hoops to get critical diagnostic information when things are on fire. You want the data NOW, and as easy work with as possible, not after struggling with a gatekeeper that by Murphy will itself provide an extra opportunity for failure. You don't want to discover that your analysis system has journalctl v5.4 but the failing system was v6.2 and cannot read the new format properly. You don't want to be the one that found the undiscovered null pointer exception in the text converter that only comes out at high tide on alternate Blue Moons.
Virtual machines don't even figure. If logs only covered hardware problems, they'd of little account in VMs.
There have been several attempts to provide better logging over the years, but up to now, they've been things that didn't take away functionality. And they didn't wedge themselves so tightly into the system that one had no choice. This is like the Gnome3 debacle all over again, except that with Gnome, when they took away critical daily functions, I was able to switch to Cinnamon.
The journalctl mess is essentially an Apple approach. You'll take what we give you and you'll LIKE it. And that's not what people are expecting in Linux. Otherwise they'd have bought Apple.
It isn't just me that's furious. I, at least can appreciate the more useful parts of systemd. I'm not rejecting for the sake of rejection. But take away functions I use every day and replace them with a second-rate black-box substitute and I'll definitely howl.
Capturing information is useless unless you can access it. Systemd logging does require special decoding.
All of those "decoders" you are talking about are automatic and part of the infrastructure. If a disk drive - ssd or not - is removed from a dead Linux system and jacked into another machine, about the only intermediary function that's likely to be unavailable would be a filesystem driver, and those are usually pretty easy to get, even if the new system is something completely different, like Windows. A version-compatible log reader facility, however, stands a very good chance of not being so easy to get. And, as I've said elsewhere, a damaged disk may be able to return useful fragments of text files, but typically, binary files are either not recoverable or would require more time and effort than an emergency situation allows.
If I sound extreme, it's because I've spent a lot of time with various binary loggers and have found them to be counter-productive on the whole, and especially frustrating when things have gone to hell. Logging should be a resource, not a primary activity that distracts from the task at hand. Logs should be readily accessible, not require spooling out to an external format before they're usable. Why introduce a middleman, especially for something that - as I said - needs to be easy to get at in times of emergency? That's like packing your fire extinquishers in a safe and writing the combination on a flammable post-it note.
If the systemd logger had left the text logs alone and augmented them with an improved log management facility - binary or not - I'd probably think it was great. But this is yet another example where a bunch of designers replaced something that was very functional with something new, shiny - and missing critical functions. And then getting all huffy because the Unwashed Masses don't properly appreciate their genius.
For me, genius only manifests when you can add features without discarding abilities that more people than not found essential in the old system. I didn't complain when iptables replaced its predecessor, because iptables didn't drop abilities relative to ipfwadm. Likewise, the up-and-coming replacements for iptables seem to add value without losing essential functionality. But I've already experienced what systemd logging can take away and I'm not amused.
decades ago, Cray Computers were assembled by people (housewives) who were allowed to spend no more time than they could be maximally effective in, using wires cut to millimeter-precise lengths.
Yes, and there's a Cray I at the Computer Museum here in Silicon Valley, upholstered base and all. You can sit on it if you like. It's not useful for much else.
All modern supercomputers are composed of a large number of microprocessors. The interconnects are faster than with ordinary hosting/cloud operations, but the CPUs are the same. The biggest supercomputer in the world, in China, is 3,120,000 cores of Intel Xeons, running at 2.2GHz each.
The question is whether the problem you're solving needs tight interconnection. If not, you can run it on a large number of ordinary computers. Weather may not be that tightly coupled; propagation time in air is kind of slow.
The visualizations of weather modelling I've seen involved an entire planet's worth of sub-cells each acting on its neighbors. Kind of like Conway's Game of Life, but instead of dots popping in and out, you get high pressure zones, low pressure zones, wind movement, humidity, temperature, all of which themselves interrelate. Plus not all cells are equal, since the curvature and axial alignment of the planet subject different areas to different levels of solar radiation. And then, of course, there's different types of land and water and mountains and currents within the water. All of which interact and that's how a hurricane near Singapore can end up as a massive snowstorm in Kansas.
So yes, expect LOTS of parallel processes.
I briefly owned a supercomputer once, but it was more of a FLOPs-optimized PC.
The economy is not a zero-sum game. This is not a race to the bottom. As low cost-of-living places get more and more jobs, their standard of living rises and costs go up accordingly.
If your job doesn't require an in-person presence, then you're competing on a global market. Best get used to that fact - it's not going away, and isolationism spells certain death for modern economies.
And don't overlook the key fact that more people buy a given product than work to make it. If lower pay means lower costs, net advantage is had to the economy: that's been studied for e.g. Walmart selling lots of stuff made in China. The total amount saved by all Americans in buying these products is several times larger than the total lost wages. For business-to-business products, maybe it doesn't work that way, I don't know, but I wouldn't just assume it's bad for the economy.
You're missing a couple of key items.
When we started shipping those white-collar jobs that were supposed to replace the blue-collar ones that we automated out overseas, they went to people whose cost of living was ONE-TENTH of what ours is. We could literally starve competing against that kind of arbitrage.
It's true. They did get more prosperous, and they did demand more. Last time I computed, the arbitrage had shrunk from 10-to-1 to 8-to-1. Maybe more now, but not enough that bean counters care much yet. It's going to be many a long year before we all approach parity at this rate.
Because of this massive differential, we don't have a "global" enconomy, we have an outsourced economy. It's well that we've been at relative peace for the last several decades because I'm not sure where the US military gets their computer display screens if they don't get them from Communist China like the rest of us do.
There's another problem there. When you make 1/10th - or even 1/8th what the people you displace did, you're not going to be buying some of the things that those people bought. Because the global absolute price of a PC or an automobile is about the same anywhere. You're also shipping a lot of tax revenue over to someone else's tax authority so that local infrastucture has less income to pay for it. When the goverment is already in the hands of a crazed bunch of tax-cut-and-spend politicians, it isn't just the boondoggles that get hit - it's roads and schools and other stuff.
The great depression was caused by a stock market and real estate bubble which triggered a massive recession, not by tariffs. Actually with higher tariffs probably it wouldn't have spread abroad so much. And the crisis itself, which started in the most efficient markets possible (the stock exchanges) also proves that adam smith's theories are purely delirious....
OMFUG! An economic LITERATE amongst the Randian clueless clones. When did the web start growing up? I mean, idiots are still calling for lower taxes, like 34 years of 78% lower taxes on the top 10% somehow created a lasting peace time boom (not).
It didn't grow up much, I think. Looks like they modded you down.
I'm still waiting for that trickle-down prosperity myself. So far all the gold coming down smells like ammonia or something.
But I'm sure if we keep doing it over and over again, eventually it will all work.
I don't normally disassemble my computer when it stops running after a software upgrade. I don't normally expect a software upgrade to make the system unbootable. Maybe it's because I don't run Windows.
And when I do have problems, I normally start by trying to boot into single-user mode and looking at the logs. Assuming that - as the case used to be - I didn't see something alarming flash up on the console while it booted.
I lost the better part of a day's productivity learning about this USB quirk after I couldn't get access to the logs - or at least the stuff I was used to seeing. I really wasn't in the mood to wait while it rattled up and down 2 years worth of binary data while disconnected from help resources on the Internet. I didn't used to keep 2 years of logs, but systemd's default is based on how full your disk drive is, not how much info you really need. And as far as I've ever determined, there's no simple systemd equivalent to relocating the primary log, starting a new one, chopping out just the parts you want to retain via head/tail/grep/snip, whatever. OR just having it sliced into tidy chunks automatically via logrotate.
I've got to stop now. My blood boils just thinking about it.
Well process management is the baggage. The stuff being replaced are the parts of legacy Linux that for one reason or another are incapable of handling chains of dependencies. If you mean why not just init, that's because initialization is just one possible state from the process manager needs to handle. Why not have it handle other states like suspending, hibernating, recovering, shutting down, daemon crashing.... ?
No, what we're referring to is that abominiation of a logging system that latched itself onto the process management.
Traditional Linux logging isn't perfect - otherwise we wouldn't have to endure consoles rolling with firewall messages or risk hiding unrelated but important messages. But at least it doesn't require a binart decoder, an intact filesystem (broken text logs may still be useful, broken binary files rarely are), or a whole new set of long-winded commands to work with it.
The process management lacks critical functions that system init had, but it's salvageable, I think. The logging can go the same way the binary logs in OS/2 did.
I can assure you 95%+ of the time the person with the badge and gun will be reasonable if you are courteous.
And white.
But definitely, "standing up to the Man" isn't going to help. The primary difference skin color will make at that point is how many bones you have left intact afterwards.
The French do enjoy longer annual leave, but I suspect that in the US, the productivity gains resulting from a little more rest at certain points in the year would more than make up for the lost working time.
21st-Century business axiom:
"If you have time to rest, we need to lay some people off and add their job responsibilities to yours".
I'm sure that they learned a valuable lession from that and will never do anything like that again. I'm also sure that pigs fly and cows routinely jump over the moon.
This is a good illustration of the folly of top-down "waterfall" methodology. Too much micro-planning in advance, no action.
Well, they also think that they're "agile". And have another expensive trendy tool to ensure it.
Couple of big shops in my town. Take one for example. They had a 2-year window for a very important project.
Bought (expensive trendy tool) from (major software vendor). Spent 18 months drawing stick-figure diagrams with (expensive trendy tool). Realized they only had 6 months for implementation and panicked. Basically tossed the stick-figure diagrams because they had to drastically modify expectations to make it in 6 months of 100-hour programming weeks. Using contract laborers who didn't know the company and how it operated, because they'd taken a chain-saw to the ranks of the in-house experienced staff.
I'm sure that they learned a valuable lession from that and will never do anything like that again. I'm also sure that pigs fly and cows routinely jump over the moon.
Slashdot Mirror
My very favoritest thing is when an element moves over just slightly just as I was about to click it, and I click its neighbor instead.
Isn't it everyone's?
I think there's an xckd for this.
I disagree over the degree of which this would be a problem - think of it more like the free market. Under ideal conditions, the best ideas with the broadest appeal tend to win, grow and evolve, while the worst ideas with little appeal tend to fade away relatively quickly.
That's fantasy. The best ideas often wither while mediocre - even bad ones - flourish. It also makes the foolish assumption that "best" conflates with "broadest appeal".
MacDonalds didn't get where they were because their products were the best. Their milkshakes taste like library paste. They got there because once they'd achieved critical mass in the market - as the old saying goes: Nothing Succeeds Like Success. Once customers knew that they could obtain a consistent product from coast-to-coast, even though it was consistently second-rate, growth was assured.
Or perhaps an example closer to home. The Commodore Amiga. The first mass-market computer to include Total Harmonic Distortion and Stereo Separation specs on the outside of the package. The first mass-market computer to come out-of-the-box with color graphics (accelerated), Hi-fi stereo sound and full pre-emptive real-time multi-tasking. Even most modern-day systems aren't real-time.
This was the company that "succeeded in spite of itself". Demonstrating that incompetent government isn't the only way to kill competitiveness, Commodore fielded a superior product which could have been even more successful if they hadn't been cursed with incompetent management.
But bad management or not, I'm really doubtful that they'd own the market today. The Wintel platform was already too well entrenched and "Nobody Ever Got Fired for buying IBM/Microsoft/Intel". Even Apple is just an also-ran. The competiton was inferior, but it was sufficient and these days only a few tattered remnants are all that remains of the Amiga.
I've no doubt that the overhead of https can be more than paid for if website designers would lay off the Singing Flowers and Dancing Fairies. Toss the gratuitous multi-media. Especially the auto-playing stuff. It's cheap and cheesy and makes me seriously think of avoiding the site altogether, whether it's local content or 3d-party adverts.
And while you're at it, calculate the slow-filling parts of the page in advance so that the [censored] thing doesn't bounce up and down like a demented ping-pong ball as it loads. The only thing more irritating than having a page continually re-map itself while you're reading it is to have the stupid thing auto-reload and throw you back to the top of it.
Jesus fucking christ, give it a break. Your kid is 4.
Indeed. Why can't she be both a princess and a scientist? Why can't engineers wear a tiara, nice gowns, and be feminine? I think the problem here is the dad's attitude, not the daughter's.
Indeed. She's 4. At 4, wearing a lab coat and a tiara at the same time is hardly remarkable. On the other hand, wanting to be a princess when you're 14 is another matter. Unless you're Princess Bubblegum.
Maybe she'll turn out to be scientifically inclined. Maybe not. I wouldn't force it - that's a pretty certain recipe for failure. You can encourage it by preferring to suggest ways for her to find answers when she asks questions instead of simply giving answers straight up.
Thats fucking retarded. Just offer a damn pdf like everyone else. Self righteous fuckholes.
Terry Pratchett wrote of grimoires in the Unseen University libary that were perilous. While you read them, they read you.
Now they really exist. Oracle keeps sending me such publications.
And that's not even counting the tattling that e-reader systems like Kindle, Nook, and Adobe do.
Nonsense. I've known way too many animals, from way too many phylums, that will go to great lengths to get a good stiff drink (Or lick toads, etc.) to give any credence to the idea that the appeal of consuming mind-altering substances is tied to some human evolutionary shift.
One thing I've discovered over the years is that any sentence that begins with "Man is the only animal who..." is probably incorrect.
No matter HOW bizarre it is.
Somewhere there's probably an animal species that files Income Taxes.
Back in the time of Fairies and Unicorns, every software release was a visit from Santa Claus. Each new release was more wonderful and feature-laden than the one before.
Then came Windows 2000. This was when it all changed, I think. ET began to "phone home" via the Internet, the software license keys weren't just something that you could type in - now they had to be "real" keys. And Microsoft decided that they would be selective about what multi-media formats they supported. As in, if they didn't "own" it, they wouldn't support it. The Grinch was beginning to appear.
But the happy little penguins played on, and each new Linux release was Christmas.
Until certain developers decided that they "knew" what was best for the unwashed masses. One of the first examples was when Nautilus lost one of its most popular window display options. That caused a mighty uproar, to the point where after many futile attempts to persuade the masses, a solution was presented that more or less restored what the Grinch had taken.
Gnome3 brought the Grinch out into the open. Yes, it was a cleaner, more dynamic display. It was certainly prettier. But some of us aren't using our computers to look good, we're using them to (allegedly) be productive. And the Gnome3 Grinch stole our applets.
As usual, the apologists had all sorts of excuses why I was wrong not to be properly awed. But all those grody little applets served very important purposes. Since they were in the margins of the display, they couldn't be covered up by sliding windows. They were always visible from every desktop. And this was important because when the machine went South, it was often the case that the reason could be seen from those applets even though the display was too paralyzed to permit switching to another desktop or launching a diagnostic app.
Which is why I'm now a happy little Cinnamon user. It gave me my applets back. And, from what I can see, it's actually a lot easier to write Cinnamon applets than it ever was to write Gnome applets, should I be so inclined.
But the Grinch is still creeping around. Gnome3 fixed a lot of the things that offended people, but as far as I know, the applets weren't among them. And now we have systemd playing Grinch as well. What's next? I shudder to think, but I may drop my longstanding relationship with Red Hat for Debian if systemd is going to stay the way it is.
I whine. I complain loudly. But given a choice, I also vote with my feet. Which is why I'm running Cinnamon.
tl;dr version:
Time dilation is a hyperbolic curve. The fun stuff doesn't start showing up until you get VERY near the speed of light.
For the math purists, forgive me if "hyperbolic" is the wrong term. The active ingredient is something like 1/(c**2 - v**2)
You were more forgiving than I was. Gnome3 was pretty much the Poster Child for the Grinch paradigm of software design that's become so prevalent these days. As in, "Here's our new, wonderful product. Isn't it wonderful? Don't you just love it? What do you mean it doesn't do something essential that you've been able to do for years and you don't like it? You ingrate! You're GOING to like our new product! We're not going to fix it just because you and 100,000 whiny little dweebs claim to need those missing functions!"
So I switched to Cinnamon and have been perfectly happy ever since. I've even kept some of the Gnome3-like options turned on. But I have all those little bits of clutter that keep me attuned to systems operation that Gnome 3 took away from me.
We don't need full on product protectionism. What could work well is a tax system that rewards domestic wages.
And what good is that going to do? A 50% tax cut on zero income isn't worth much, and that's what they'd like - free labor.
Or did you mean tax cuts on the employer side? Funny, all those savings on productivity gains didn't cause employers to go out and hire more people, so why do you expect saving on taxes to be magically different? All they do is pocket the difference.
This is all nonsense. Converting data from a format that's directly accessible by general purpose utilities to one that requires a gatekeeper application just to get it exported in human-readable format is NOT "making it easier to get". It's making it HARDER to get, and that's what all the screaming is about. It takes log access from direct processability by the rich suite of text utilities that made Unix/Linux what it is and forces it to only be accessible by those utilities after exporting. You don't want to jump through hoops to get critical diagnostic information when things are on fire. You want the data NOW, and as easy work with as possible, not after struggling with a gatekeeper that by Murphy will itself provide an extra opportunity for failure. You don't want to discover that your analysis system has journalctl v5.4 but the failing system was v6.2 and cannot read the new format properly. You don't want to be the one that found the undiscovered null pointer exception in the text converter that only comes out at high tide on alternate Blue Moons.
Virtual machines don't even figure. If logs only covered hardware problems, they'd of little account in VMs.
There have been several attempts to provide better logging over the years, but up to now, they've been things that didn't take away functionality. And they didn't wedge themselves so tightly into the system that one had no choice. This is like the Gnome3 debacle all over again, except that with Gnome, when they took away critical daily functions, I was able to switch to Cinnamon.
The journalctl mess is essentially an Apple approach. You'll take what we give you and you'll LIKE it. And that's not what people are expecting in Linux. Otherwise they'd have bought Apple.
It isn't just me that's furious. I, at least can appreciate the more useful parts of systemd. I'm not rejecting for the sake of rejection. But take away functions I use every day and replace them with a second-rate black-box substitute and I'll definitely howl.
Capturing information is useless unless you can access it. Systemd logging does require special decoding.
All of those "decoders" you are talking about are automatic and part of the infrastructure. If a disk drive - ssd or not - is removed from a dead Linux system and jacked into another machine, about the only intermediary function that's likely to be unavailable would be a filesystem driver, and those are usually pretty easy to get, even if the new system is something completely different, like Windows. A version-compatible log reader facility, however, stands a very good chance of not being so easy to get. And, as I've said elsewhere, a damaged disk may be able to return useful fragments of text files, but typically, binary files are either not recoverable or would require more time and effort than an emergency situation allows.
If I sound extreme, it's because I've spent a lot of time with various binary loggers and have found them to be counter-productive on the whole, and especially frustrating when things have gone to hell. Logging should be a resource, not a primary activity that distracts from the task at hand. Logs should be readily accessible, not require spooling out to an external format before they're usable. Why introduce a middleman, especially for something that - as I said - needs to be easy to get at in times of emergency? That's like packing your fire extinquishers in a safe and writing the combination on a flammable post-it note.
If the systemd logger had left the text logs alone and augmented them with an improved log management facility - binary or not - I'd probably think it was great. But this is yet another example where a bunch of designers replaced something that was very functional with something new, shiny - and missing critical functions. And then getting all huffy because the Unwashed Masses don't properly appreciate their genius.
For me, genius only manifests when you can add features without discarding abilities that more people than not found essential in the old system. I didn't complain when iptables replaced its predecessor, because iptables didn't drop abilities relative to ipfwadm. Likewise, the up-and-coming replacements for iptables seem to add value without losing essential functionality. But I've already experienced what systemd logging can take away and I'm not amused.
I dunno. Are gamma rays the ones that they try and capture down at the bottoms of mine shafts?
decades ago, Cray Computers were assembled by people (housewives) who were allowed to spend no more time than they could be maximally effective in, using wires cut to millimeter-precise lengths.
Yes, and there's a Cray I at the Computer Museum here in Silicon Valley, upholstered base and all. You can sit on it if you like. It's not useful for much else.
All modern supercomputers are composed of a large number of microprocessors. The interconnects are faster than with ordinary hosting/cloud operations, but the CPUs are the same. The biggest supercomputer in the world, in China, is 3,120,000 cores of Intel Xeons, running at 2.2GHz each.
The question is whether the problem you're solving needs tight interconnection. If not, you can run it on a large number of ordinary computers. Weather may not be that tightly coupled; propagation time in air is kind of slow.
The visualizations of weather modelling I've seen involved an entire planet's worth of sub-cells each acting on its neighbors. Kind of like Conway's Game of Life, but instead of dots popping in and out, you get high pressure zones, low pressure zones, wind movement, humidity, temperature, all of which themselves interrelate. Plus not all cells are equal, since the curvature and axial alignment of the planet subject different areas to different levels of solar radiation. And then, of course, there's different types of land and water and mountains and currents within the water. All of which interact and that's how a hurricane near Singapore can end up as a massive snowstorm in Kansas.
So yes, expect LOTS of parallel processes.
I briefly owned a supercomputer once, but it was more of a FLOPs-optimized PC.
The economy is not a zero-sum game. This is not a race to the bottom. As low cost-of-living places get more and more jobs, their standard of living rises and costs go up accordingly.
If your job doesn't require an in-person presence, then you're competing on a global market. Best get used to that fact - it's not going away, and isolationism spells certain death for modern economies.
And don't overlook the key fact that more people buy a given product than work to make it. If lower pay means lower costs, net advantage is had to the economy: that's been studied for e.g. Walmart selling lots of stuff made in China. The total amount saved by all Americans in buying these products is several times larger than the total lost wages. For business-to-business products, maybe it doesn't work that way, I don't know, but I wouldn't just assume it's bad for the economy.
You're missing a couple of key items.
When we started shipping those white-collar jobs that were supposed to replace the blue-collar ones that we automated out overseas, they went to people whose cost of living was ONE-TENTH of what ours is. We could literally starve competing against that kind of arbitrage.
It's true. They did get more prosperous, and they did demand more. Last time I computed, the arbitrage had shrunk from 10-to-1 to 8-to-1. Maybe more now, but not enough that bean counters care much yet. It's going to be many a long year before we all approach parity at this rate.
Because of this massive differential, we don't have a "global" enconomy, we have an outsourced economy. It's well that we've been at relative peace for the last several decades because I'm not sure where the US military gets their computer display screens if they don't get them from Communist China like the rest of us do.
There's another problem there. When you make 1/10th - or even 1/8th what the people you displace did, you're not going to be buying some of the things that those people bought. Because the global absolute price of a PC or an automobile is about the same anywhere. You're also shipping a lot of tax revenue over to someone else's tax authority so that local infrastucture has less income to pay for it. When the goverment is already in the hands of a crazed bunch of tax-cut-and-spend politicians, it isn't just the boondoggles that get hit - it's roads and schools and other stuff.
The great depression was caused by a stock market and real estate bubble which triggered a massive recession, not by tariffs. Actually with higher tariffs probably it wouldn't have spread abroad so much. And the crisis itself, which started in the most efficient markets possible (the stock exchanges) also proves that adam smith's theories are purely delirious....
OMFUG! An economic LITERATE amongst the Randian clueless clones.
When did the web start growing up?
I mean, idiots are still calling for lower taxes, like 34 years of 78% lower taxes on the top 10% somehow created a lasting peace time boom (not).
It didn't grow up much, I think. Looks like they modded you down.
I'm still waiting for that trickle-down prosperity myself. So far all the gold coming down smells like ammonia or something.
But I'm sure if we keep doing it over and over again, eventually it will all work.
I don't normally disassemble my computer when it stops running after a software upgrade. I don't normally expect a software upgrade to make the system unbootable. Maybe it's because I don't run Windows.
And when I do have problems, I normally start by trying to boot into single-user mode and looking at the logs. Assuming that - as the case used to be - I didn't see something alarming flash up on the console while it booted.
I lost the better part of a day's productivity learning about this USB quirk after I couldn't get access to the logs - or at least the stuff I was used to seeing. I really wasn't in the mood to wait while it rattled up and down 2 years worth of binary data while disconnected from help resources on the Internet. I didn't used to keep 2 years of logs, but systemd's default is based on how full your disk drive is, not how much info you really need. And as far as I've ever determined, there's no simple systemd equivalent to relocating the primary log, starting a new one, chopping out just the parts you want to retain via head/tail/grep/snip, whatever. OR just having it sliced into tidy chunks automatically via logrotate.
I've got to stop now. My blood boils just thinking about it.
Well process management is the baggage. The stuff being replaced are the parts of legacy Linux that for one reason or another are incapable of handling chains of dependencies. If you mean why not just init, that's because initialization is just one possible state from the process manager needs to handle. Why not have it handle other states like suspending, hibernating, recovering, shutting down, daemon crashing.... ?
No, what we're referring to is that abominiation of a logging system that latched itself onto the process management.
Traditional Linux logging isn't perfect - otherwise we wouldn't have to endure consoles rolling with firewall messages or risk hiding unrelated but important messages. But at least it doesn't require a binart decoder, an intact filesystem (broken text logs may still be useful, broken binary files rarely are), or a whole new set of long-winded commands to work with it.
The process management lacks critical functions that system init had, but it's salvageable, I think. The logging can go the same way the binary logs in OS/2 did.
Nope.
Obama got his peace prize for not being George Bush.
However it does seem that he got it under false pretences, as he seems to be George's harder working brother.
He talks smoother, the skin's darker. But the ears are a giveaway!
Eh, you can just SAY you'll do something good in a few to get your nobel peace prize. Worked for Obama.
BS. He got the prize for Not Being Bush.
A container of yogurt could have done as much.
I can assure you 95%+ of the time the person with the badge and gun will be reasonable if you are courteous.
And white.
But definitely, "standing up to the Man" isn't going to help. The primary difference skin color will make at that point is how many bones you have left intact afterwards.
Some law-enforcement experts say the NYCLU is going beyond civics lessons and doling out criminal-defense advice.
So wait, we're assuming that they're all criminals to begin with?
Welcome to post-1984 USA. Now take off your shoes and drop your pants and be prepared to show your papers.
The French do enjoy longer annual leave, but I suspect that in the US, the productivity gains resulting from a little more rest at certain points in the year would more than make up for the lost working time.
21st-Century business axiom:
"If you have time to rest, we need to lay some people off and add their job responsibilities to yours".
I'm sure that they learned a valuable lession from that and will never do anything like that again. I'm also sure that pigs fly and cows routinely jump over the moon.
This is a good illustration of the folly of top-down "waterfall" methodology. Too much micro-planning in advance, no action.
Well, they also think that they're "agile". And have another expensive trendy tool to ensure it.
Couple of big shops in my town. Take one for example. They had a 2-year window for a very important project.
Bought (expensive trendy tool) from (major software vendor). Spent 18 months drawing stick-figure diagrams with (expensive trendy tool). Realized they only had 6 months for implementation and panicked. Basically tossed the stick-figure diagrams because they had to drastically modify expectations to make it in 6 months of 100-hour programming weeks. Using contract laborers who didn't know the company and how it operated, because they'd taken a chain-saw to the ranks of the in-house experienced staff.
I'm sure that they learned a valuable lession from that and will never do anything like that again. I'm also sure that pigs fly and cows routinely jump over the moon.