mkopinsky

And even that is limited to sharing data for a single user between requests. It's hard to accidentally share data between users.

It's optional for the caller, but not for the callee. I think the controversy centers around two things:

a) Specific to this feature: For library maintainers, this means that argument names are now part of the public API, whether I like it or not, and renaming a parameter from $orderBy to $sortBy is now technically a breaking change. Yeah, you can put something in the readme saying "Heads up: I don't support named arguments and intend to rename arguments in semver-minor releases", but should you need to do that?

b) General to all new PHP features: PHP is a great language, with lots of crap code written in it. Will this feature result in people writing better or worse code? Just because something is optional doesn't mean it's a good idea, if it will result in the overall code quality of the ecosystem to get worse. Some people think that named arguments will make it too easy to create monster functions with too many parameters.

I personally support (aka am DELIGHTED by) named arguments, but I'm sympathetic to the concerns of library maintainers and I don't see a better way around it than a remark in the readme (at least until/unless they introduce e.g. a @@NoNamedArguments annotation in PHP 8.1). And I think that the benefits of named arguments far surpass the risk that they encourage people to create methods with too many arguments. But I can see both arguments.

They've moved over everything to Hacklang, which is a derivative of PHP.

The forum post at https://forums.wyzecam.com/t/updated-12-29-19-data-leak-12-2... has all the details from the company's perspective. The rest seems like scare-mongering to me.

It's one thing for them not to know what is owed. But surely they know what's already been paid? No amount of errors on a W-2 or 1099 or whatever will make me eligible to receive a refund of taxes I never paid.

I've now had two long-term jobs at large employers, both hospital systems, neither made me sign an IP agreement of any sort. On the university side there absolutely are provisions with faculty in terms of IP ownership. But for hospital employees, it just isn't a consideration. They're not in the IP business, they're in healthcare.

I'm typically a heavy terminal user. Git is my exception. a) the UI of git cli is just so terrible that I'd rather fill my brain with more important things, and b) for viewing what's changed, `git diff` just doesn't cut it relative to a GUI.

Sourcetree is my go to git client, but if I couldn't use sourcetree I'd be OK with pretty much any git GUI. But git CLI is reserved for particularly tricky things that GUIs just can't handle well. (And I need to look up the specific flags or commands every single time.)

If a private entity is issued a cert saying "Government Entity", is that a "tiny discrepancy"? https://twitter.com/SectigoHQ/status/1171808269528109058

I know for a fact that at least one of those certs was replaced with a DV cert - once the team in question had to replace it, they realized there was no point in replacing it with an EV since the browsers are removing the EV UI anyway.[0] I'd bet that a meaningful proportion of the certs in question are similarly being replaced with DV.

[0] https://www.isc.upenn.edu/alerts-outages/planned-weblogin-ss...

Or as another approach:

    <!-- inventory.html.twig: -->
    <div
        id="app"
        data-inventory="{{ inventory | json_encode }}"
        >
    </div>

    // main.js
    new Vue({
        template: '<App :inventory="inventory"/>',
        components: {App},

        data() {
            return {
                inventory: null
            }
        },
    
        beforeMount: function () {
            this.inventory = JSON.parse(this.$el.attributes['data-inventory'].value);
        }
    }).$mount('#app');

No, going to a doctor's appointment isn't what an ambulance is for. The comment specifically said "non-urgent". But when patients miss appointments because they can't get there or afford $20 for an Uber, the health system loses a lot more than $20, so it's worth it financially for them to partner with Uber/Lyft to get patients to appointments.

The one thing I've experienced on this front that was clunky was integration between netlify and self-hosted Gitlab. If y'all could come up for a solution for that (which is prettier than "manual" deploy using webhook), I'd love both of your companies even more than I already do.

That's a good reason not to donate to the red cross. There are other organizations out there with extremely high efficiency ratios and noble missions, and you shouldn't let one highly publicized rotten apple poison the rest.

University of Pennsylvania | Philadelphia, PA | ONSITE | https://www.waytohealth.org/

Way to Health is a patient engagement and research platform which has been used to power over 100 research studies and clinical programs improving the health of our patients. As just one example, the Heart Safe Motherhood program uses our platform to text postpartum mothers about their blood pressure for 10 days, allowing us to catch mothers at risk for preeclampsia long before they would otherwise show up in an ambulance.

As we scale from research to clinical and commercial use, the Software Developers on our team play a critical role in extending and supporting the platform - designing and building new features to enable novel patient engagement strategies, improving the user interface for our patients and providers, and troubleshooting issues affecting our users.

This position requires strong technical ability to design and build web applications and APIs, clear communication with team members and users to deeply understand user needs, and creativity to solve issues and meet requirements while paying off rather than accruing technical debt.

Bachelors degree and minimum 3 years experience in web development required. We use mostly PHP/Symfony and Vue.js so experience in either of those is a plus, but we will consider candidates with experience in other backend or frontend frameworks. An interest in medicine, research, and/or patient engagement is always great - we are an excited and engaged team who loves what we do and the impact that we can make.

Email me at [my HN username]@waytohealth.org with your resume or any questions - I'm happy to chat. Application is at http://w2h.us/devjob

University of Pennsylvania | Philadelphia, PA | ONSITE | https://www.waytohealth.org/

Way to Health is a patient engagement and research platform which has been used to power over 100 research studies and clinical programs improving the health of our patients. As just one example, the Heart Safe Motherhood program uses our platform to text postpartum mothers about their blood pressure for 10 days, allowing us to catch mothers at risk for preeclampsia long before they would otherwise show up in an ambulance.

As we scale from research to clinical and commercial use, the Software Developers on our team play a critical role in extending and supporting the platform - designing and building new features to enable novel patient engagement strategies, improving the user interface for our patients and providers, and troubleshooting issues affecting our users.

This position requires strong technical ability to design and build web applications and APIs, clear communication with team members and users to deeply understand user needs, and creativity to solve issues and meet requirements while paying off rather than accruing technical debt.

Bachelors degree and minimum 3 years experience in web development required. We use mostly PHP and Vue.js so experience in either of those is a plus, but we will consider candidates with experience in other backend or frontend frameworks. An interest in medicine, research, and/or patient engagement is always great - we are an excited and engaged team who loves what we do and the impact that we can make.

Email me at [my HN username]@waytohealth.org with your resume or any questions - I'm happy to chat.

How can you make domain renewals be monthly or quarterly?

One thing that amazes me about the modern PHP ecosystem is that when it comes to distributable PHP packages, there is only one package manager (composer) and one central package repo (packagist).

When it comes to binaries it's still a bit of a mess (homebrew? pecl? yum?) but the native PHP code story is clearer than any other language ecosystem I've seen.

The difference with composer is that in most cases you're getting the exact version from github, including the full .git directory. No minification, no "the tarball doesn't match the source". And most composer packages have 0-5 dependencies, whereas most npm packages seem to have 10-20.

But too-many-dependencies is a problem there too.

His explanation is at https://www.colorado.gov/governor/sites/default/files/legisl...

UPenn has that. I took CIS 399 ("Special Topics in Computer Science") once as "Unix/Linux Skills" and once as a Python course. From googling I see that it's also been offered as "The Art of Recursion", "Open Source Software Development", and other titles. It is a half-credit course, i.e. half of a normal course.

A similar incident happened in 2001 (!) to TWA ("The Wrong Airport"):

http://edition.cnn.com/2001/TRAVEL/NEWS/03/15/wrong.airport/...

In the thread at http://www.airliners.net/forum/viewtopic.php?t=76657 the commenters list a few other instances of this happening.

Except that a lot of the time those user contributed notes are bad code that no one should ever be copy-pasting. I wish php.net had some sort of curation for those.

FYI if I visit the new subdomain over HTTPS I get a cert error.

How do you set cron to post to Slack?

Seconding the Manager Tools Podcast. There's also Manager Tools Basics, which is a highlight reel of sorts from the main podcast. Their approach can be a bit simplistic at times, but is immensely valuable.

Wow. That really makes you feel morally superior, doesn't it?

While in this case I was wrong, DNS poisoning is certainly not out of the realm of what Verizon will do, and when a site resolves properly on one ISP and not another, I don't think it's a "wild claim" to assume that it's the ISP's fault.

Unfortunately I can't get to the new site (without changing my DNS servers) because Verizon is resolving krebsonsecurity.com to loopback. Presumably doing it for (poor) DDOS mitigation, but this sort of censorship is ridiculous.

    $ nslookup krebsonsecurity.com 71.242.0.12
    Server:   71.242.0.12
    Address:  71.242.0.12#53
    
    Non-authoritative answer:
    Name: krebsonsecurity.com
    Address: 127.0.0.1

EDIT: I see downthread that this is a DNS propagation issue. Nevermind.

Where did he accuse anyone of that? All he asked for is a citation.

Earlier this year I needed to get something notarized. Went to the UPS store 3 blocks from my work, paid $5 per signature (=$10), walked out 5 minutes later. It's a hassle, but for a $500 transaction it really isn't such a big deal.