Sure, this is possible -- but if we're going to get that hysterical about the potential of ebola, then there are hundreds of other things we should be getting hysterical about first.
For the record, although there is some uncertainty about it, it appears that ebola may be able to exist for only a few hours outside the body (some studies say as long as a couple of days, though) on hard surfaces. It doesn't last more than a handful of minutes on soft surfaces such as fabrics.
Indeed it is. However, that's still a very poor method of transmission. Just getting infected fluids on your skin isn't enough for transmission to take place. The fluid has to enter a cut, abrasion, or mucous membrane.
I don't know. Given that most of the CSS-heavy sites I see routinely break or suck as a direct result of using CSS, its clear that most web developers don't know how to properly use it. And if, after 20 years, most developers don't know how to use a tool then I tend to think the fault is not the developers, the tool.
The problem with tables is that they generally were very inflexible.
True, but this problem can be worked around by using dynamically generated web pages -- which brings an additional benefit of still separating layout from content, if you feel that's important.
Trying to resize your browser (back in the day) often caused strange layout issues (and lets not forget the 1px transparent GIFs).
A problem that CSS has not actually resolved, judging by the number of websites that become unusable when I make my browser window my preferred size.
I do for my own web pages. The problem is that most of the pages on the web at large use CSS, and so the problems with CSS remain my problem regardless.
CSS has been a thorn in my side since it came out, and it still is (even though I don't do web development anymore). It's because of the difficulties with CSS that we have such terrible things as my personal pet peeve -- web pages that have fixed minimum or maximum widths. While CSS does have advantages, it also has disadvantages -- and the effects of those disadvantages on web site design in general very often makes the web less useful to me than it would otherwise be.
Am I the only one who isn't even slightly scared about ebola? It isn't transmitted through the air or casual contact, so its' pretty easy to avoid. What is there to be scared of?
And while you're at it stop trashing good work that's going on in other projects - even if you don't agree with the direction it's going in.
What do you mean by "good work"? If I don't agree with the direction a project is going, then -- by definition -- I cannot consider that project to be "good work."
That list is meaningless, since you could easily put together an even longer list of things that have changed without anyone complaining about it.
In all fairness, the reason I have a problem with everything on that list (except Gnome 3, which I've never used) is because none of them meet my needs, desires, or solve problems I have. At the same time all of them presented additional problems that I didn't have before.
It's not a general "resistance to change" problem. It's a resistance to cost without benefit that's the "problem."
Well said, I agree. I never liked Gnome, not even the most popular versions of it. I love KDE (although I've been loving the more recent versions less and less).
since everyone uses them it's better to collect everything under one roof where it's easier to make things work well together.
This is where we differ. I don't think that's better at all. We should not be sacrificing functionality and flexibility just because it makes system developer's lives easier.
If that were true, then I wouldn't get upset about it. If that were true, then there wouldn't be package or build dependencies on systemd. If that were true, the systemd wouldn't be causing so much fallout with the rest of the system. The fact is that systemd is so monolithic and broad that you can't call it "just an init system".
I don't really buy the "people hate change" thing - sure, some people hate change, but a lot of the time changes are good.
While the "people hate change" argument is misused and overstated, there is truth to it. Changing your work habits and routines is always painful to some degree, and people hate pain. Regardless of that, people will willingly change their habits when they see a value to doing so that is greater than the pain of the change.
Where both Windows 8 and Gnome 3 (and a few other Linux DEs) went wrong is a combination of two things: for most users the changes they presented did not offer benefits that exceeded the amount of pain they caused, and those changes were forced on the users regardless of their wants and needs.
I unfortunately live in an area where the only choice for broadband internet is Comcast, so I can only speak to them -- they have no problem with people using their own modems. I've been using my own for years without an issue.
Red Hat has been dead to me for years now, so I don't care what they do. However... why, Debian, are you requiring this systemd bullshit? I used to love you, but you've changed.
most people (even power users) really don't measure what they're spending time doing and get into unproductive patterns.
Perhaps because for most people, shaving a half second here and there is meaningless. It's much better to have a UI that is understandable, intuitive, and comfortable than one that is technically as "efficient" as it could possibly be.
The problem with GNOME was that they also didn't listen to usability experts.
Given the utter crap that the UX crowd has been coming out with over the past few years, I'm not sure this is a problem.
Yes, and that usage makes sense. But we aren't talking about endpoint devices like phones or tablets. We're talking about routers. On routers, this makes zero sense and is objectively bad.
Oh, I totally understand why people are angry about it -- I'm one of those people. I think the anger is totally justified. It's the hate I have a problem with.
Your example is one of how ads are a benefit to you, but it doesn't work for me. A coupon to save a couple of bucks isn't something that I consider a benefit for myself. If I'm so shy of money that a coupon is worth the hassle (and, if it's an electronic coupon, further tracking) then I'll be putting the purchase off or buying it used anyway.
Why are ads such garbage?
The thing about this that actually depresses me is that I took the fact that the (few, thanks to NoScript) ads that I see are never relevant to me personally as a sign that I'm effectively hiding and obfuscating my info in the ad companies' databases. Perhaps that's not true after all, and I have no good way to tell how effective my efforts actually are.
No router should ever be dependent on phoning home to a server in order to work. (No router should be engaging in any communication at all that I haven't told it to!) This is BAD - Broken As Designed. I'm awfully glad that I don't use Belkin stuff.
Slashdot Mirror
Sure, this is possible -- but if we're going to get that hysterical about the potential of ebola, then there are hundreds of other things we should be getting hysterical about first.
For the record, although there is some uncertainty about it, it appears that ebola may be able to exist for only a few hours outside the body (some studies say as long as a couple of days, though) on hard surfaces. It doesn't last more than a handful of minutes on soft surfaces such as fabrics.
Indeed it is. However, that's still a very poor method of transmission. Just getting infected fluids on your skin isn't enough for transmission to take place. The fluid has to enter a cut, abrasion, or mucous membrane.
I don't know. Given that most of the CSS-heavy sites I see routinely break or suck as a direct result of using CSS, its clear that most web developers don't know how to properly use it. And if, after 20 years, most developers don't know how to use a tool then I tend to think the fault is not the developers, the tool.
The problem with tables is that they generally were very inflexible.
True, but this problem can be worked around by using dynamically generated web pages -- which brings an additional benefit of still separating layout from content, if you feel that's important.
Trying to resize your browser (back in the day) often caused strange layout issues (and lets not forget the 1px transparent GIFs).
A problem that CSS has not actually resolved, judging by the number of websites that become unusable when I make my browser window my preferred size.
I do for my own web pages. The problem is that most of the pages on the web at large use CSS, and so the problems with CSS remain my problem regardless.
CSS has been a thorn in my side since it came out, and it still is (even though I don't do web development anymore). It's because of the difficulties with CSS that we have such terrible things as my personal pet peeve -- web pages that have fixed minimum or maximum widths. While CSS does have advantages, it also has disadvantages -- and the effects of those disadvantages on web site design in general very often makes the web less useful to me than it would otherwise be.
Then making it a point to shake hands with a lot of people in multiple areas.
That's fine. You won't catch ebola just by shaking their hand. You have to come into contact with their bodily fluids.
Am I the only one who isn't even slightly scared about ebola? It isn't transmitted through the air or casual contact, so its' pretty easy to avoid. What is there to be scared of?
It adds some, yes. But it also takes away other. BTW, by "functionality," I don't mean "features". I mean it more in terms of "fitness of purpose".
And while you're at it stop trashing good work that's going on in other projects - even if you don't agree with the direction it's going in.
What do you mean by "good work"? If I don't agree with the direction a project is going, then -- by definition -- I cannot consider that project to be "good work."
That list is meaningless, since you could easily put together an even longer list of things that have changed without anyone complaining about it.
In all fairness, the reason I have a problem with everything on that list (except Gnome 3, which I've never used) is because none of them meet my needs, desires, or solve problems I have. At the same time all of them presented additional problems that I didn't have before.
It's not a general "resistance to change" problem. It's a resistance to cost without benefit that's the "problem."
But on a desktop or a laptop? It's kinda appropriate there to be honest.
It's certainly not appropriate on my desktops and laptops. I hate it there just as much as on my servers.
Well said, I agree. I never liked Gnome, not even the most popular versions of it. I love KDE (although I've been loving the more recent versions less and less).
Viva la difference!!
since everyone uses them it's better to collect everything under one roof where it's easier to make things work well together.
This is where we differ. I don't think that's better at all. We should not be sacrificing functionality and flexibility just because it makes system developer's lives easier.
it's just an init system
If that were true, then I wouldn't get upset about it. If that were true, then there wouldn't be package or build dependencies on systemd. If that were true, the systemd wouldn't be causing so much fallout with the rest of the system. The fact is that systemd is so monolithic and broad that you can't call it "just an init system".
I don't really buy the "people hate change" thing - sure, some people hate change, but a lot of the time changes are good.
While the "people hate change" argument is misused and overstated, there is truth to it. Changing your work habits and routines is always painful to some degree, and people hate pain. Regardless of that, people will willingly change their habits when they see a value to doing so that is greater than the pain of the change.
Where both Windows 8 and Gnome 3 (and a few other Linux DEs) went wrong is a combination of two things: for most users the changes they presented did not offer benefits that exceeded the amount of pain they caused, and those changes were forced on the users regardless of their wants and needs.
I unfortunately live in an area where the only choice for broadband internet is Comcast, so I can only speak to them -- they have no problem with people using their own modems. I've been using my own for years without an issue.
Red Hat has been dead to me for years now, so I don't care what they do. However... why, Debian, are you requiring this systemd bullshit? I used to love you, but you've changed.
I've been seriously looking at FreeBSD, but Slackware is also still in the running.
most people (even power users) really don't measure what they're spending time doing and get into unproductive patterns.
Perhaps because for most people, shaving a half second here and there is meaningless. It's much better to have a UI that is understandable, intuitive, and comfortable than one that is technically as "efficient" as it could possibly be.
The problem with GNOME was that they also didn't listen to usability experts.
Given the utter crap that the UX crowd has been coming out with over the past few years, I'm not sure this is a problem.
In any case, I'm not buying a router unless I can install DD-WRT or OpenWRT on it.
This is what I do. I can't think of a company that makes routers whose firmware I trust, so I only use routers where I can install my own.
Of course, with Comcast now pushing integrated router/cable modem setups
You don't have to use their equipment. You can get your own cable modem for under $200 and use that.
Yes, and that usage makes sense. But we aren't talking about endpoint devices like phones or tablets. We're talking about routers. On routers, this makes zero sense and is objectively bad.
Oh, I totally understand why people are angry about it -- I'm one of those people. I think the anger is totally justified. It's the hate I have a problem with.
Your example is one of how ads are a benefit to you, but it doesn't work for me. A coupon to save a couple of bucks isn't something that I consider a benefit for myself. If I'm so shy of money that a coupon is worth the hassle (and, if it's an electronic coupon, further tracking) then I'll be putting the purchase off or buying it used anyway.
Why are ads such garbage?
The thing about this that actually depresses me is that I took the fact that the (few, thanks to NoScript) ads that I see are never relevant to me personally as a sign that I'm effectively hiding and obfuscating my info in the ad companies' databases. Perhaps that's not true after all, and I have no good way to tell how effective my efforts actually are.
No router should ever be dependent on phoning home to a server in order to work. (No router should be engaging in any communication at all that I haven't told it to!) This is BAD - Broken As Designed. I'm awfully glad that I don't use Belkin stuff.