The Official Status Thread
-
Therefore...?
-
Why would anyone waste $100 dollars?
-
Have you met people? People are stupid; they'll waste money on all sorts of pointless junk.
-
Unfortunately, the server room is hard wired to route all power through the UPS, so no temporary workaround is possible.
Turns out an electrical fault in the circuit before the UPS caused a switch to battery backup. The power lasted about 5 minutes instead of the specced 40. This is apparently because the AC unit for the server room gets its power through the UPS.
-
Hey, you've gotta keep the servers cool when they have no power!
-
It's defined as a Jeffgression IIRC. Which I might not.
Just a regression:
Regression
nounNew bug
-
In theory, before the UPS dies, the backup diesel generator should automatically turn on.
Today showed that it's dead. Our warehouse manager laughed and said "duh!" He will probably be graduating from the shit list to the unemployment line.
-
Status: wondering why Discourse is giving me notifications of Jeffed posts in the Discopodiatrist.
-
Status: it's the middle of my sleeping time and I'm wide awake for no apparent reason. I wonder if it means I'm doing it right?
-
Status: uploading a 500MB video file.
-
-
-
I had to enter my PIN number first.
-
-
Status: sigh
-
-
Jesus, Jeff, don't you have any bugs to fix?
-
Oh fuck me. You know it's bikeshedding. You know it's pointless. You know that the majority of users won't give a shit, and the rest will be pissed.
And yet you go ahead and not only do it, not only make a thread out of it like it's some hot new feature, but you aknowledge all the above problems and just shrug them off.
The only thing worse than a fool not knowing his foolishness is the one who laughs at it.
-
@jeffwood said:
I feel the more columns you have, the better zebra striping is, and we've steadily pared down the number of columns in the topic list over the last year and a half .
@jeffwood said:
You definitely associate tiger striping with spreadsheets and tabular data in many, many columns...
Well then, where's the problem? Leave the zebra striping alone, just be careful you don't add any tiger striping by accident.
-
STATUS: Writing my own CSV parser, what's that, I DON'T HEAR YOU LALALALALA
-
They should give us the CSS powers to switch between tiger, zebra and polar bear mode ...
-
Also:
Pretty!
-
polar bear mode
Have +䝣 as well, a like is not enough
Pretty!
Bumblebee mode?
-
I like that change
-
Status: Works on my machine. Doesn't work on test server. I wouldn't mind if it's something I need to compile, but it's PHP.
-
E: Expected ending to word "bananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananananaStackOverflowException" on line 1</doce>
EWRONGSITE
-
Bee Stripes!
-
Status For a while, loading a discourcepage looked like this for me:
(Same text remained at the bottom of the screen.)
Reloading the page got rid of it, though. Pity, otherwise I might have had a chance to create a new topic.
-
This little monkey looks like it's had to much Guinness and is about to throw up:
-
Either that, or it's just walked in on its parents as they're getting intimate…
-
It's for that reason we also have
-
Except that one's smiling, so it's clearly playing Peek-A-Boo™
-
According to dicsource, it's @faoileag's thread?
When has dishnorse been right about anything?
-
@Lorne_Kates said:
When has dishnorse been right about anything?
The thread owner does in fact not have to be the OP, yes.
Although, it's @faoileag in both cases here.
The servercooties website thread, for example, is owned by me (topic list, first avatar) and started by @Onyx (opening post).
It's safe to say that this is not your thread, though.
-
For posterity.
-
Bets on how quickly Blakey's post gets jeffed to
/dev/null
and blakey gets banned?[poll]
- -1s
- 10 minutes
- 1 hour
- More than one hour
- E_POST_NOT_FOUND
[/poll]
-
Oh I'm sure it already has been. I'm not going back there to check, fuck Atwood.
EDIT: I mean I know the answer. The answer it: "dicking around with CSS is easy, diving in their confused spaghetti multi-language, multi-framework, RegEx-heavy codebase to fix real bugs is nightmarish."
A.k.a. "Lazy as fuck."
The open source philosophy at work: only do the easy stuff, never do the challenging work. Hypnotize yourself into believing you've solved all the major bugs. Then pat yourself on the back for being such a great software developer and "giving back" your project to the people.
Probably the same reason the menus in Notepad++ and Audacity still don't work after 10+ years.
-
You're totally right too... This kind of crap really bugs the hell out of me, especially when they do have bugs to fix... Come on guys, really? Really??
-
I mean I'm new to the word "bikeshedding", but isn't the entire point that when someone points out that the work you're doing is bikeshedding, you stop doing it!?
I thought that was the point!
-
Oh I'm sure it already has been
Actually, no; it's still there.I might check later, I might not. Depends on how bored I am I guess. But here's the link if anyone feels like checking.
-
Maybe I'm missing an old discussion on this and how Jeffdown is supposed to work differently, but according to John Gruber, list numbering is working as intended in Markdown:
It’s important to note that the actual numbers you use to mark the list have no effect on the HTML output Markdown produces.
-
Which is still a fault, as it's not an intuitive behaviour. And for a 'markup' language that's meant to be more intuitive than HTML, that's a big
-
You still can't type in "3." at the beginning of a line and have "3." appear on the screen.
And so, an unstoppable force meets an immovable object.
By now not accidentally fixing this is probably Jeff's top priority.
-
From the... I'm assuming definitive source on this?
"The really, really short answer is that you should not. The somewhat longer answer is that just because you are capable of building a bikeshed does not mean you should stop others from building one just because you do not like the color they plan to paint it. This is a metaphor indicating that you need not argue about every little feature just because you know enough to do so. Some people have commented that the amount of noise generated by a change is inversely proportional to the complexity of the change."
So yeah, pretty much that's the point. Jeff seems to think it's a complement though....
-
list numbering is working as intended in Markdown:
Then the bug is in the spec. Atwood's spec says different.
In any case, the point is: it's a bug. It's an OBVIOUS EMBARRASSING BUG. It hasn't been fixed in two years.
(Actually I'm pretty sure it was fixed for about a week, but then got permanently regressed. But the more time passes, the more I'm starting to think that was a hallucination or daydream.)
-
Jeff seems to think it's a complement though
Jeff has a… unique view on feedback ;)
-
Oh I'm sure it already has been. I'm not going back there to check, fuck Atwood.
Still there...I Liked it:
The open source philosophy at work: only do the easy stuff, never do the challenging work.
I don't think that's true in this case. But I don't see Jeff as doing the challenging work, ever. That's just not his role. But he has to do something to pass the time.
-
Wouldn't part of his role be to determine the priority of issues?
Of course they're using a bug tracker where you can't even sort by priority.
I think his role is "egotistical blabbermouth who knows nothing but somehow came into possession of enough money to hire a couple people who kind of sort of are slightly better at developing software to write his products for him."
Where "slightly better" is still a huge exaggeration, considering he only hires people who haven't heard of the term "quality assurance" before. It's probably on his application form, "have you hard of QA? Y/N."
-
Maybe I'm missing an old discussion on this and how Jeffdown is supposed to work differently, but according to John Gruber, list numbering is working as intended in Markdown:
That's true, but Jeff was a part of a group trying to get a real spec out there: CommonMark. And there, they have what is the obvious behavior as spec. But Jeff's project doesn't use that.
-
Wouldn't part of his role be to determine the priority of issues?
Yes, but him (or his designer on the payroll) fucking around with bullshit like this doesn't prevent someone capable of other work from doing that work.
Not that I'm defending his ability to prioritize or even pick a tool to use for prioritizing. Total adhocracy.