Incoming Discourse WTFs
-
They're rewriting Ember's rendering engine.
... also a JavaScript library has a rendering engine that isn't just "the DOM, duh".
-
Oh fuck.
Hundreds of white screens coming to a Discourse near you soon™.
-
I, for one, welcome our new rendering overlords. Hilarity is sure to ensue as soon as it hits this place.
-
Surely they'll test it before deplo....nah, I couldn't even say it.
-
You mean this isn't the testing server?
-
I still haven't updated even to htmlbars yet. A bunch of little glitches all over the place. I don't know if discourse did it. And am too lazy to find out.
Still you have to admire the ember devs. It's a breakneck pace in js framework world. They are doing pretty good job so far of balancing between innovation and backwards compatibility. Certainly better than google is doing with angular.
-
You mean this isn't the testing server?
If by 'this' you mean 'us,' not any more. At least not in the first instance...
-
Are we staging then? Because this sure doesn't seem like production quality to me.
Filed Under: INB4 That's because it isn't production quality!
-
Are we staging then? Because this sure doesn't seem like production quality to me.
Manual beta, as opposed to daily alpha which is what we were before.
Basically when I get an announcement of another beta on my own instance, I update this one.
As a result while we still get bugs, the rate of change of them has been reduced.
-
I have no idea if this is the right Topic / Thread, but it is the best result I got searching the forum with "Discourse WTF".
Nor do I know if anybody has reported this before.
But if you click "n Comments" on the Front Page Article Teaser. The time you do it becomes the time of the last comment.
This happens if you are logged in or not, and with or without a "clean" Browser. Which suggests to me it is a Server Side Issue.
-
But if you click "n Comments" on the Front Page Article Teaser. The time you do it becomes the time of the last comment.
This happens if you are logged in or not, and with or without a "clean" Browser. Which suggests to me it is a Server Side Issue.
That's the biggest problem, and not the links actually not working at all?
-
It is when you see that a comment "has" been made but the Article cannot be found, and you've been wanting to post (see minor rants), and you can't "start" Comments. This small WTF just rubs salt into the wound that is TRWFT as you so accurately pointed out.
-
But if you click "n Comments" on the Front Page Article Teaser. The time you do it becomes the time of the last comment.
This happens if you are logged in or not, and with or without a "clean" Browser. Which suggests to me it is a Server Side Issue.
It's not really a Discourse issue. It's an issue with the main site.
-
... also a JavaScript library has a rendering engine that isn't just "the DOM, duh".
I called it years ago, soon websites will be one big <canvas> with a large pile of Javascript behind.
-
I called it years ago, soon websites will be one big <canvas> with a large pile of Javascript behind.
Then we can write an HTML rendering engine for that!
-
... also a JavaScript library has a rendering engine that isn't just "the DOM, duh".
That's crazy. It would run far too fast, use not nearly enough memory, and everything would work the same as other sites. There's no novelty or innovation there at all.
-
We are running htmlbars which made a lot of our templates farm or readable cause bind-attr is dead.
Glimmer will open the door to server side rendering and is meant to speed up rendering a lot. eager to measure the impact.
-
We are running htmlbars which made a lot of our templates farm or readable cause bind-attr is dead.
Has that landed? I'm still using
bind-attr
at 1.11, no deprecation notices so far.Glimmer will open the door to server side rendering and is meant to speed up rendering a lot. eager to measure the impact.
How are you gonna do it on rails backend? Adding node.js to the mix?
-
-
You should consider actually... writing code. Instead of just Googling up yet more and more buggy open source shit.
-
why would they reinvent the wheel when they can find a 7-sided one already made for them out of wood that almost doesn't quite break when bearing a load?
-
Turns out I write code
You can read through my 145 commits in the last month to confirm I am not
making that up
-
I think you can junk it if you are on html bars my guess would be it was
left for compatabilityWe already ship node in our image, server side rendering though is wayyyy
out in our plans
-
Right; the and the end-result is Discourse. Yay. 8 seconds on average to see my notifications! You can't type a line beginning with "5." without your text being mutilated! Such a quality, quality product.
Maybe I'm wrong; maybe the problem is you write TOO MUCH code.
-
You may know him as your friendly neighborhood @waffles. Or the maker of a media library for Windows Media Center (and, by Extender, Xbox 360) that doesn't suck. Or Valued Associate #00008. Or, essentially, someone who actually cares.
-
We already ship node in our image, server side rendering though is wayyyy
out in our plansWhat's the explanation for this?
...and then the actual post served up has the correct case.
-
I reported it on meta we refactored @mention validation so it works in batches but this slipped