1,260 karma · joined November 2, 2009
But I remember the times when that blog didn't look like a webdesign internship project in progress. And there were interesting comments…
I agree that StackOverflow is at fault here, but enabling JS is not a binary choice — "allow all JS on this site" vs "block all JS on this site" are not your only options.
Tools like uMatrix allow me to control JS coming from different domains on different domains independently. For example, on SO I have enabled JS from Stack Exchange and related domains, but not from Google or other snoopers.
[0]: https://www.reddit.com/r/privacy/comments/bpr6xs/if_you_choo...
> [I]n 2018, 32 percent of the surveyed 1,500 Filipinos trusted vaccines. In the 2015 iteration of the poll, 93 percent of the respondents said they trusted vaccines.
> Health Secretary Francisco Duque III attributes the lowered trust on the government's immunization drive due to the Dengvaxia controversy.
---
I also saw someone on Twitter questioning if that decline in trust was related to the Philippines' continued obsession with social media [1].
[0]: https://en.wikipedia.org/wiki/2019_Philippines_measles_outbr...
[1]: https://news.abs-cbn.com/focus/01/31/19/filipinos-still-worl...
All the developers in the world combined can not solve a legal problem. You can't implement technologies like Widevine without a license, and if they simply won't give you one [0], you're dead in the water.
[0]: https://blog.samuelmaddock.com/posts/google-widevine-blocked...
[0]: https://www.reddit.com/r/programming/comments/ar1qj1/x/egl52...
I wholly agree that this would not help, but for the sake of completeness, I want to point out that <input autocomplete=""> [0] is designed to solve this, by decoupling input field names from their intent.
But Chrome is playing dumb about it [1]. And of course, the spambots will just adapt to parse the autocomplete info…
[0]: https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes...
[1]: https://www.reddit.com/r/programming/comments/ar1qj1/chromiu...
Someone who needs to clone your repository (e.g. you're a dependency for their project) cares.
Someone tired of using an inactive repo and trying to get an overview of healthy forks cares.
Someone whose project uses GitHub for more than just a raw git repo (e.g. issues, wiki, releases with precompiled/crossplatform binaries) cares.
Someone searching for answers who encounters a link to some GitHub gist cares.
† Stylish is a … special case [0]. But see also hypothes.is or any other extension that relies on a "user-created content store".
[0] https://robertheaton.com/2018/07/02/stylish-browser-extensio...
Google Chrome has defaulted to disabling extensions in incognito mode as long as I can remember:
> Allow in incognito [ ]
> Warning: Google Chrome cannot prevent extensions from recording your browsing history. To disable this extension in incognito mode, unselect this option.
[0]: https://github.com/doctrine/collections
[1]: https://github.com/schmittjoh/php-option
ES6 has Map and Array, which are perfectly sufficient and distinguishable from each other. PHP core only has array() which tries to do everything. You can use array() to build a collection or an associative array and you cannot force it to only behave as one of those. Even Zend's PHP certification contains questions about what happens if you try to push a value into an array that uses associative keys. This is a joke.
I prefer React over Angular as well, but interactivity was not on my list of goals. I want a template syntax that combines valid markup, escaping by default, and TSX-style typechecking. Basically, I want XHP [0]. There is no other template engine for PHP that validates "values passed into this template" against "values used in this template" like TSX can, and no engine that ensures you're generating valid XML/HTML markup. I certainly agree that this is far less important than powerful types, but hey, one can dream :)
- expressive type system with generics, union types, literal types, basically TypeScript. I can say "this function returns a string" or "this function returns an array", but not "this function returns an array of strings".
- specialized collection/hashmap data structures with good support across third-party libraries. Having one array() structure acting as both a sequence and an associative array at the same time is awful.
- a templating solution similar to JSX. I am spoiled by TypeScript's ability to typecheck my HTML views along with other code.
PHP has its tentacles all over the web: WordPress and Drupal are immensely popular for simplistic sites and short-lived promotionals, Magento and WooCommerce attract many e-commerce users, and Symfony/Laravel handle the custom stuff. I've worked with all of these and have the scars to show for it.
All popular projects have swarms of consultants offering advice, prebuilt additions, and custom development. (E.g. WordPress plugins and themes are everywhere.) This is also a significant factor for the penny-pinching customer — from their point of view, they avoid vendor lock-in and expensive development this way. (Spoiler: it rarely works out, in the end. "Tower of Babylon" and "shallow learning curve" mix in very exciting ways.) So there are masses of people who know the basics of PHP and call themselves "PHP developers". In my opinion, just a fraction of them actually deserves that title.
The current datepickers on the desktop are "consistent in the same browser across many sites". There is no native solution for "consistent in the same site across browsers", which makes a lot of designers and PHBs upset, doesn't always fit the overall look of the site, and makes it harder for developers because each browser brings its own quirks with formatting, localization, validation, etc.
There's always a way to enhance your processes, monitor more indicators, etc. or otherwise improve your security.