PHP 7.0 not dead, UNREJOICE_REAL!
-
Oh yeah baby! Let's see what fresh batch of insanity we'll find in this one! Prepare the popcorn!
Also, apparently:
It’s almost a non-issue now that PHP 7 can not only have the pile-of-poop emoji as a variable name, but also reliably use it as a string internally. The Register
Suck it, Swift!
-
..... i need more caffeine... or possibly less
i read that title as: "PHP 7.0 released, REJUICE!"
-
-
mysqli_real_escape_string_honest_this_time_we_mean_it
-
-
@flabdablet said:
mysqli_real_escape_string_honest_this_time_we_mean_it
FTFY
mysqli_real_escape_string_no__this_time_we_mean_it
-
mysqli_real_escape_string_honest_this_time_we_mean_it
Fortunately, I think all
mysql_
andmysqli_
crap is now officially GONE.Thank fuck.
-
What, they force PDO now?
Cue incoming drama!
-
Don't worry, this still exists:
So everyone will just switch to sticking strings into that, because
PDO::prepare
is too hard.
-
Yay! Workaround found…
-
Fortunately, I think all mysql_ and mysqli_ crap is now officially GONE.
Thank fuck.
I thought only
mysql_
was gone?
-
This is a pretty good video to get you up to speed, for those who are interested. Now that I am a PHP coder again, I have to follow this shit.
-
They give raw access to the AST now? I can only imagine what maniacs will write with that in mind...
-
AST access for extensions is neat, means it's possible to write static code analysis tools without rolling your own AST parser/builder like PHPMD did.
Only
mysql_
is gone, both MySQLi and PDO are still around but both have prepared statements etc meaning there's no huge gaping functionality holes left.
-
-
Only mysql_ is gone, both MySQLi and PDO are still around but both have prepared statements etc meaning there's no huge gaping functionality holes left.
But people will still code as if the functionality holes remain. You know they will. Oh well, maybe the analysers that are written can pick up on cases where the SQL is a not a constant and COMPLAIN in those cases. There will be a few cases where they get it wrong (variable column names, etc.) but they'll be the tiny minority.
-
Give people an option to do it wrong, and they will do it wrong. Remove the option to do things wrong and you cause endless grief to people who hit that one damned edge case where they need to do something apparently wrong, but it's the only way to actually do it properly. The good old double-edged sword.
That said, both PHP as a language and people who use it have a long history of doing it wrong because they don't know better...
-
PHP,
@Arantor, @cartman82: I suddenly feel much more sorry for you. PHP is apparently like Discourse: The gift that keeps on misgivings. (Although they actually improved it from what it was before, so I guess it's still marginally better than Discourse.)
-
No compassion for poor old me...
-
No compassion for poor old me...
Oh, I'm so sorry, I didn't realize! You poor soul.
(Also: good job Discourse! I can highlight-quote part of the post, but not the whole post. Intuitive!
)
-
NO_REPRO.
-
NO_REPRO.
Well, that's discoursistency for ya.
Wait...
/me tests something.Try doing it by triple clicking.
-
-
Selects too much of the post.
Well, now the nature of the problem is known. Guess it's going from NO_REPRO to… CLOSED_WON'T_FIX?
-
Well, now the nature of the problem is known.
Well when you get that close to the reply button it's outside of the div for the cooked post.
CLOSED_WON'T_FIX?
I ain't fixing any Discobugs.
-
Well, this is the proof that Discourse is the ultimate WTF - even a topic about PHP managed to devolve into the greater WTF that is Discourse...
I am now tempted to write an article. I think I'd call it... "Discourse, a fractal of bad design". Has a ring to it, don't you think?
I am brillant!
-
"Discourse, a
fractal of bad designsteaming pile of donkey shit"even a topic about PHP managed to devolve into the greater WTF that is Discourse...
I'm not sure Dischorse could be worse even if it was written in PHP.
-
-
Fighting talk, but probably true. Discourse-PHP would be as bad as Discourse because for once PHP isn't the problem.
-
-
PHP,
You had me at variable variables. Whoever uses those deserves to get stung.
I still think the ternary operator's left associativity is worse.
-
(Also: good job Discourse! I can highlight-quote part of the post, but not the whole post. Intuitive! )
Discoursistency notwithstanding, why would you want to do that? Just press the quote button without anything selected.
-
Discoursistency notwithstanding, why would you want to do that? Just press the quote button without anything selected.
He doesn't want full and is too lazy to delete it?
-
Maybe he's using a touchpad, which is different?
Anyway... is this the point where I start complaining about people Discoursing in my thread?
-
He doesn't want full and is too lazy to delete it?
Then why select the whole post?Anyway... is this the point where I start complaining about people Discoursing in my thread?
I'm surprised you haven't already.
-
even a topic about PHP managed to devolve into the greater WTF that is Discourse...
You know what hasn't been mentioned in a while? @blakeyrat's second law, that's what.
-
And now the thread is complete!
We can as well close it, we already did everything else we can.
Except certain types of flamewars, but I'll flag those for offtopic mercilessly.
-
-
I feel it would have been better for all involved to make that a syntax error.
If “that” was referring to PHP, then yes.
-
-
@Dreikin said:
(Also: good job Discourse! I can highlight-quote part of the post, but not the whole post. Intuitive! )
Discoursistency notwithstanding, why would you want to do that? Just press the quote button without anything selected.
Convenience. Just select line -> hit quote reply, which is approximately the same method as when I want only a part of a post (unless I need to deal with special formatting).
-
why would you want to do that? Just press the quote button without anything selected.
Maybe I am an idiot, but I have no idea what this means. I don't see any option to quote a post unless some of it is selected. I even tried clicking the reply button and then clicking the quote button in the empty editor, but nothing happened.
-
i think you need to degaus your monitor there.... that's some blurry ass text you posted there....
-
Improved performance: PHP 7 is up to twice as fast as PHP 5.6
Why is this what is being compared, instead of php 6.x? Is it like Windows 9?
-
Why is this what is being compared, instead of php 6.x? Is it like Windows 9?
PHP 6 was a "Unicode all the things!" initiative that fell through, AFAIK. So yeah, they just buried it in shame and moved on to 7.
-
@Zecc said:
why would you want to do that? Just press the quote button without anything selected.
Maybe I am an idiot, but I have no idea what this means. I don't see any option to quote a post unless some of it is selected. I even tried clicking the reply button and then clicking the quote button in the empty editor, but nothing happened.
Hit the regular reply, not the second one you get when you highlight text. Then click the quote button in the editor, and you'll get the full text of the post.
-
Hit the regular reply, not the second one you get when you highlight text. Then click the quote button in the editor, and you'll get the full text of the post.
Discoverable
-
@Lorne_Kates said:
@FrostCat said:
Hit the regular reply, not the second one you get when you highlight text. Then click the quote button in the editor, and you'll get the full text of the post.
Discoverable
Hell, I only know how to do it because someone else told me.
-
Arantor, a PHP enthusiast that tries to rid the world of badly written PHP one file at a time. These are his stories.
?
-
Hit the regular reply, not the second one you get when you highlight text.
Works for me either way, as long as there's no selection when I press the quote button in the toolbar.(Of course in the latter case you'll get two quotes)