4 ms·
I enjoy writing JS, so no, I won't stop.
by vertline3 8y ago
I enjoy writing JS, so no, I won't stop.
- raxxorrax 8y agoSeriously. The hate for JS is strong, but I don't really see why. Use typescript if you want, but I don't really see the issue. There are funny things related to implicit type conversion and some rules produce funny and unintuitive outcomes. These conversion can be very handy on the other sides. "Math.min() > Math.max()" and they are damn right that this is true!
- tobr 8y agoDespite personally enjoying JavaScript, I can see why someone might heavily dislike it. Like the fact that it is/has long been the only choice, and that so many of the problems with the modern web have come about through JS.
- spdionis 8y ago> Seriously. The hate for PHP is strong, but I don't really see why. > Just use PHP 7! There are funny things related to implicit type conversion and some rules produce funny and unintuitive outcomes. These conversion can be very handy on the other sides. > "PHP_INT_MIN < PHP_INT_MAX" and they are damn right that this is true! Feeling the perception difference?
- Klathmon 8y agoI always felt the same about PHP. It gets a lot of shit because some of the oldest parts have some weird function names or parameter order, but outside of that it's a fantastic language, especially if you stick with php ~5.5 and newer. It's fast, it has a nice package system, and the pepole behind the language are making it better, faster, and more feature complete every day, with standards bodies which includes the biggest players in the space. IMO languages like Go could learn a thing or 2 from PHP about how to stop worrying about the "best possible choice" and just start giving the language the tools that developers can use to solve real problems.
- akatechis 8y agoThe difference is that JS has to be backwards compatible in order to not break 50% of the internet. With PHP, it is theoretically possible to make a major version upgrade that fixes most if not all the issues without worrying about breaking backwards, since upgrading is opt-in.
- Klathmon 8y agoUpgrading was opt-in with python as well, and look at where breaking changes got them... A decade in and there's still a massive rift in the python community over 2 vs 3. PHP is backwards compatible almost to a fault, but that doesn't mean you can't use new libraries or frameworks that hide those warts away from you, and that's a MUCH better choice in my opinion than making a significant percentage of the internet incompatible with the latest PHP so that your function arguments for a handful of old function calls can all look the same...
- anchpop 8y ago"massive rift" is a bit of an exaggeration. Most Python libraries have Python 3 versions and it's not at all uncommon to see libraries that don't have support for Python 2 (see Django)
- Klathmon 8y agoI don't think it is. Sure, it's not like they are 2 different languages, but it's something that all python developers will have to keep in mind when using libraries. Not to mention the headache of having both installed on many systems (what does `python` give me?), and there are still many things that don't have python3 versions still (node-gyp is the one that still bites me every day). It's not the end of the world, and it is getting better every day, but having to spend the better part of a decade dealing with multiple "main" versions of a language is not something that I want any other languages I use repeating. And if that means needing to lookup if the function is urlencode or url_encode, well i'm happy to pay the price.
- 8y ago
- deleted 8y ago[deleted]
- jrs95 8y agoYou might enjoy writing it, but does anyone else enjoy reading it? ;)