Yeees, we have two dozen people here complaining about these "someone reverted it for no reason" cases and not a single one of them bothers providing a link to their edit.
We'd like to judge the circumstances ourselves and not rely on unsubstantiated hearsay, thank you very much!
I reckon it might be Apple's influence. They have this feature where you "right click" by holding down Option when clicking the left mouse button. [1]
I happen to think Apple's behaviour is very handy, especially on laptops. Right clicking on every track pad I've run across has been an ergonomic nightmare. (The bad part, of course, is that you have to have a hand on the keyboard.)
It doesn't excuse GNOME's behaviour though (assuming what you say is true).
[1] or "only mouse button", if you're one of those silly Apple-bashers.
I discovered a simple but critical bug in the MariaDB database server returning incorrect results on a SELECT statement. The test case was extremely simple and verified within an hour or two of the bug report being submitted. A couple weeks went by, no work happened on it.
I've found that a large amount of open source projects are run by developers who don't actually use their bug tracker. They don't read the bugs. They don't act on them. Every twelve months you get someone commenting "does this still apply to version xyz? if not, we can close this" in batches, trying to clean the bug tracker. It bloody well applies to version xyz -- the developer hasn't actually touched any of the relevant code in the past two years, has he?
A couple of years later you get "sorry, the tool abc has been replaced by tool def and we're closing all bugs filed against abc..." (I'm looking at you, GNOME...)
The 40 decibels is probably A-weighted and they do make much louder infrasounds and other low-pitched sounds that might affect human health. (And sounds that low certainly do pierce walls.) I know there have been cases in the press here about people getting sick after wind turbines were installed, kilometres away.
I don't know if it's true or not. I think the people here on slashdot are quite ready to dismiss it as 'wi-fi allergy' though.
I don't sanitise my input. I sanitise my output. And you should too.
Besides, "sanitise" is the wrong word. "Escape" is better. "Sanitise" tends to be irreversible. If it fails, you can try to do a post-mortem and still have no clue what went wrong since sanitising threw away everything important.
People keep saying that TMTOWTDI is harmful but nobody ever bothers citing a single example where there are actually more than two obvious ways of doing something.
This rather irritates me. So please provide a concrete example where TMTOWTDI is harmful.
Anyway, I now realise that you already mentioned that it was a redirect.
The redirect was created with the note:
redirect, per result of many, many, many, many discussions
And that brings to a complaint of mine of Wikipedia: If you aren't "in the know", there's no way you can find these "many" discussions. They're hidden somewhere in the Wikipedia: or Talk: namespaces, but I wouldn't even know where to start searching for them.
Pretty much every crash investigation will give at the very least 2-3 contributing factors to the crash. It's very very rarely that a pilot error alone that leads to the crash.
Bad maintenance. Lacking training. Failed instrument. Weather. Pilot error. Crew confusion. ATC error. Pick at least two.
The news outlets though, they try to simplify the cause to fit their headline.
The problem with mod_perl was one of perception: It was meant to extend Apache, and its documentation reflected that. Easy writing of Apache modules without touching C code. Its primary aim was to be a Perl API to Apache. This is very much comparable to the recent Lua extensions on the NetBSD kernel.
You did not need mod_perl to run Perl code on Apache. In fact, it was probably one of the less efficient ways to do so: if your script needed large amounts of memory, the memory remained mapped to the relevant Apache process and wouldn't get freed. Swapped out perhaps, but not freed.
Besides, global variables were shared so mod_perl was definitely not a good way to run multiple "web applications", much less user-installed ones!
(In case you ask: to run Perl code on a web server today, you should use Plack; back then you should have used FastCGI.)
I guess the confusion was driven by mod_php which was the de facto way of running PHP on Apache, without resorting to the terrible slowness of CGI.
I take RoxTerm which has everything you listed, and probably no more.
The only annoyance with it is that it brings up a help HTML document if you press F1. I've accidentally hit the key and opened a browser too many times.
Although, my usual go-to terminal is urxvt. But I use roxterm too because it has GTK2 which works nicer with the IME, and renders multibyte characters in a non-cramped way.
People just need to run these tests a single time on every browser, and then immediately scrap them and make them unavailable. Then build a new one from scratch.
Personally, I'm not interested the slightest bit in JavaScript speed and equating browser speed with JavaScript speed like these articles keep doing is silly. I'm much more interested in the rendering speed, and UI efficiency. But those are difficult to measure! The bottleneck for me is almost always the network anyway -- I tend to be 50-150 ms away from any server except the ones that happen to be hosted in my country. And then the ASP or PHP or JSP on the other end takes 400 ms to respond because nobody bothered to optimise it or the server config the slightest bit.
Are/were there actually routers that didn't default to NAT?
Because NAT is enough to kill all the probes that can infect or bluescreen a post-install Windows.
(I got hit by a post-install bluescreen on Win2k when I happened to re-install with NAT disabled. I disconnected the ethernet cable and redid the install.)
The sad thing is, they justify a healthcare system's cost by saying that the new software will save the doctors 1-2 minutes per patient -- the old software is rubbish and has UI latency issues --, and multiplies that by the doctors' salaries.
You do in fact get "this software will save billions of pounds" based on those calculations, but that doesn't make its price any more palatable.
So, how come you're only getting 20 % compression with JPEGs? StuffIt (a Mac-only compression program/format) could do around 50 % thanks to a specialised algorithm, or so I heard. And that was ten years ago.
Reading comprehension: Because the official NTPD often loses the connection to the servers and bails out.
I've had it happen. I've seen it happen on someone else's server as well. The clock ended up off by well over an hour. Switched to OpenNTPD. Very happy with it.
In short, you're comparing a simple client that just looks at the time on the wall vs something that's trying to be accurate and can act as the server side of the equation.
48 hours? Seriously? Is that what counts as 'good' battery life these days?
I want a phone to last a week on a single charge. Especially if all it's doing is lying on the table, screen off. Mine currently feels like a Tamagotchi that needs to be fed every two days.
often some of the biggest single contributors of calories and sugar to our diets
Last I checked, a 0,33-litre tin of fizzy drink is about 100 kcal. You need three such tins to reach the calorie level of a light meal. How much do you drink daily anyway?
(Oh, by the way, you get a similar amount of sugar and calories from orange juice.)
Yes, I found it difficult as well, took a while to figure what it was referring to. And I *know* Japanese.
'Japanese hiragana character "no"' and I'll understand it. Hopefully even add a unicode codepoint (U+306E HIRAGANA LETTER NO), maybe even a link to that character's data on e.g. fileformat.info.
Of course, it's still a sentence fragment, and that's pretty jarring.
Slashdot Mirror
Yeees, we have two dozen people here complaining about these "someone reverted it for no reason" cases and not a single one of them bothers providing a link to their edit.
We'd like to judge the circumstances ourselves and not rely on unsubstantiated hearsay, thank you very much!
I reckon it might be Apple's influence. They have this feature where you "right click" by holding down Option when clicking the left mouse button. [1]
I happen to think Apple's behaviour is very handy, especially on laptops. Right clicking on every track pad I've run across has been an ergonomic nightmare. (The bad part, of course, is that you have to have a hand on the keyboard.)
It doesn't excuse GNOME's behaviour though (assuming what you say is true).
[1] or "only mouse button", if you're one of those silly Apple-bashers.
I discovered a simple but critical bug in the MariaDB database server returning incorrect results on a SELECT statement. The test case was extremely simple and verified within an hour or two of the bug report being submitted. A couple weeks went by, no work happened on it.
I've found that a large amount of open source projects are run by developers who don't actually use their bug tracker. They don't read the bugs. They don't act on them. Every twelve months you get someone commenting "does this still apply to version xyz? if not, we can close this" in batches, trying to clean the bug tracker. It bloody well applies to version xyz -- the developer hasn't actually touched any of the relevant code in the past two years, has he?
A couple of years later you get "sorry, the tool abc has been replaced by tool def and we're closing all bugs filed against abc..." (I'm looking at you, GNOME...)
The 40 decibels is probably A-weighted and they do make much louder infrasounds and other low-pitched sounds that might affect human health. (And sounds that low certainly do pierce walls.) I know there have been cases in the press here about people getting sick after wind turbines were installed, kilometres away.
I don't know if it's true or not. I think the people here on slashdot are quite ready to dismiss it as 'wi-fi allergy' though.
I don't sanitise my input. I sanitise my output. And you should too.
Besides, "sanitise" is the wrong word. "Escape" is better. "Sanitise" tends to be irreversible. If it fails, you can try to do a post-mortem and still have no clue what went wrong since sanitising threw away everything important.
People keep saying that TMTOWTDI is harmful but nobody ever bothers citing a single example where there are actually more than two obvious ways of doing something.
This rather irritates me. So please provide a concrete example where TMTOWTDI is harmful.
Anyway, I now realise that you already mentioned that it was a redirect.
The redirect was created with the note:
redirect, per result of many, many, many, many discussions
And that brings to a complaint of mine of Wikipedia: If you aren't "in the know", there's no way you can find these "many" discussions. They're hidden somewhere in the Wikipedia: or Talk: namespaces, but I wouldn't even know where to start searching for them.
Wikipedia
DELETED.
https://en.wikipedia.org/wiki/...
HTH, HAND.
Pretty much every crash investigation will give at the very least 2-3 contributing factors to the crash. It's very very rarely that a pilot error alone that leads to the crash.
Bad maintenance. Lacking training. Failed instrument. Weather. Pilot error. Crew confusion. ATC error. Pick at least two.
The news outlets though, they try to simplify the cause to fit their headline.
The problem with mod_perl was one of perception: It was meant to extend Apache, and its documentation reflected that. Easy writing of Apache modules without touching C code. Its primary aim was to be a Perl API to Apache. This is very much comparable to the recent Lua extensions on the NetBSD kernel.
You did not need mod_perl to run Perl code on Apache. In fact, it was probably one of the less efficient ways to do so: if your script needed large amounts of memory, the memory remained mapped to the relevant Apache process and wouldn't get freed. Swapped out perhaps, but not freed.
Besides, global variables were shared so mod_perl was definitely not a good way to run multiple "web applications", much less user-installed ones!
(In case you ask: to run Perl code on a web server today, you should use Plack; back then you should have used FastCGI.)
I guess the confusion was driven by mod_php which was the de facto way of running PHP on Apache, without resorting to the terrible slowness of CGI.
Roxterm. Matches everything you want. Depends on Gtk and that's about it.
Although I can't fathom why anyone'd want transparency.
I take RoxTerm which has everything you listed, and probably no more.
The only annoyance with it is that it brings up a help HTML document if you press F1. I've accidentally hit the key and opened a browser too many times.
Although, my usual go-to terminal is urxvt. But I use roxterm too because it has GTK2 which works nicer with the IME, and renders multibyte characters in a non-cramped way.
People just need to run these tests a single time on every browser, and then immediately scrap them and make them unavailable. Then build a new one from scratch.
Personally, I'm not interested the slightest bit in JavaScript speed and equating browser speed with JavaScript speed like these articles keep doing is silly. I'm much more interested in the rendering speed, and UI efficiency. But those are difficult to measure! The bottleneck for me is almost always the network anyway -- I tend to be 50-150 ms away from any server except the ones that happen to be hosted in my country. And then the ASP or PHP or JSP on the other end takes 400 ms to respond because nobody bothered to optimise it or the server config the slightest bit.
Are/were there actually routers that didn't default to NAT?
Because NAT is enough to kill all the probes that can infect or bluescreen a post-install Windows.
(I got hit by a post-install bluescreen on Win2k when I happened to re-install with NAT disabled. I disconnected the ethernet cable and redid the install.)
The sad thing is, they justify a healthcare system's cost by saying that the new software will save the doctors 1-2 minutes per patient -- the old software is rubbish and has UI latency issues --, and multiplies that by the doctors' salaries.
You do in fact get "this software will save billions of pounds" based on those calculations, but that doesn't make its price any more palatable.
I know I shouldn't expect much from two-year-olds, but you should correct her grammar. It's "daddy's phone", not "daddies phone".
She'll thank you later.
Of course the database should be red. Why else would slashdot's logo for databases be a red wheelbarrow?
So, how come you're only getting 20 % compression with JPEGs? StuffIt (a Mac-only compression program/format) could do around 50 % thanks to a specialised algorithm, or so I heard. And that was ten years ago.
OpenBSD 3.6 (Nov 2004) changelog:
New functionality:
- A new NTP daemon written from scratch, which ought to fit the needs of most NTP users.
Man page for 3.6
Ergo, OpenNTPD has been a server since its birth. New information indeed.
Reading comprehension: Because the official NTPD often loses the connection to the servers and bails out.
I've had it happen. I've seen it happen on someone else's server as well. The clock ended up off by well over an hour. Switched to OpenNTPD. Very happy with it.
In short, you're comparing a simple client that just looks at the time on the wall vs something that's trying to be accurate and can act as the server side of the equation.
OpenNTPD does run as a server. Or have I been syncing my clocks all these years to something non-existent?
listen on address [rtable table-id]
Specify a local IP address or a hostname the ntpd(8) daemon should listen on.
48 hours? Seriously? Is that what counts as 'good' battery life these days?
I want a phone to last a week on a single charge. Especially if all it's doing is lying on the table, screen off. Mine currently feels like a Tamagotchi that needs to be fed every two days.
often some of the biggest single contributors of calories and sugar to our diets
Last I checked, a 0,33-litre tin of fizzy drink is about 100 kcal. You need three such tins to reach the calorie level of a light meal. How much do you drink daily anyway?
(Oh, by the way, you get a similar amount of sugar and calories from orange juice.)
OK. The sun rises here at 2:00 UTC and sets 19:00 UTC. What are the business hours here?
In January, the sunrise will be at 7:00 UTC and sunset at 14:00 UTC.
(The day of the summer solstice is 19 hours long.)
Yes, I found it difficult as well, took a while to figure what it was referring to. And I *know* Japanese.
'Japanese hiragana character "no"' and I'll understand it. Hopefully even add a unicode codepoint (U+306E HIRAGANA LETTER NO), maybe even a link to that character's data on e.g. fileformat.info.
Of course, it's still a sentence fragment, and that's pretty jarring.