simonhamp

CoW doesn't require reinstall of dependencies as they're part of the same directory tree, so should be immediately accessible (I've been using this way for a couple months now and it works fine)

The application running (port config) problem is an issue for frameworks and build tools to figure out around the shift towards multiple live working copies at once

The tools that facilitate this will win imo

I use Laravel Herd along with Polyscope (made by the same company). Together they enable CoW clones with their own dev domains - it's zero setup and works super well for my use-case

I can see a simpler version of the same thing being very neat dev experience across many stacks

This is a guest post from Saurav Pathak, CPO at Bagisto, the open-source Laravel eCommerce platform. Bagisto's mobile admin, NativeBagisto, is built with NativePHP and available on the Play Store.

This article has not been sponsored or paid for.

Fascinating! Thanks for sharing

NativePHP

No snark. Genuinely happy. This is progress

React kid discovers the web

Thanks! Fixed

NativePHP & Bifrost

https://nativephp.com

https://bifrost.nativephp.com

A two-man team, we're enabling PHP developers to get into mobile app development as easily as possible - no need to learn new languages, no new skills, just a few commands and away you go.

NativePHP is the library. Bifrost is the build and release service, getting apps into the stores faster than anything else.

This month we're planning to release the first fully open source version of the Mobile package.

How's it going?

We've sold over 2,000 licenses since May. We built Bifrost over the summer and it already has almost 300 monthly subscribers.

We just gave away another 1,000 licenses to the African PHP community.

Or perhaps surgically appended into your palm or something...

Love to see it. Glad to see PHP getting more support here

Awesome! It worked! Thanks so much.

Looking forward to being listed and considered for funding :)

Sure, but that's not how it's demonstrated in the docs...

I've updated it, but that also doesn't work AND fails validation because:

"projects[0].repositoryUrl.url and `projects[0].repositoryUrl.wellKnown` hostnames do not match"

I am trying to submit my funding.json, it validates when I check the validator, but fails when I submit with the error: "too many lines in the .well-known list"

I have 1 line in my .well-known lists

Here's my funding.json:

https://nativephp.com/funding.json

Can someone help me figure out what I'm doing wrong?

Absolutely. And at the height of a global employment crisis, this is diabolical, people taking advantage of many earnest folks

But worse: LinkedIn being aware of it and doing nothing to stop it

It appears that they're vacuuming up applicant data by posting jobs as if they're from a certain Page (brand) but in reality they're not affiliated with that brand at all.

Who knows where this data is ending up

tl;dr: it's as much on the attendees who _are_ present to move things along. Take some initiative!

This article just comes across as completely ignorant of what might be going on in another person's life. Many comments here also lean towards this being about managers who demand things don't start until they're present.

This is just wrong.

In reality, any group of sufficiently smart and empowered people who have managed to get themselves together in a room should be organised enough to start without waiting on a particular individual.

If that individual then acts out because they missed some stuff, yep they're a dick. But they're not a dick just for being late or even being consistently late.

Looks really good and keen to try it out! One thing I've been itching for for ages is a way to name spaces... if I could put a label at the top of each column, I'd be all over this!

And yet Conway's Law still holds up surprisingly well

One way or another, your app reflects the org chart. So either you force the split because of your architectural choice or it happens because of your org structure

One way or another it will happen

Yeh... and if you've got iOS and Android covered, then web is a different thing. Doesn't need to be an SPA, can still use those same APIs if that makes sense for your app

Sure. But we're talking about needing the same API for two separate clients...

That infers building both and I'm questioning why you would build both if they're identical. Just build one and get your users to use it

If you're building an SPA that's identical to a native app, I think someone in the exec team is making poor decisions

Either make a web app or a native app... don't do both

Yeh I've seen some of those as SPAs... ouch

Honestly, I'd rather not be presented with an empty grid of spinners tbh

I think you can get something useful on first render and then dynamically update from there (either with polling, SSE or WebSockets) all without the added complexity of an SPA

You're absolutely correct. Thanks

Because they were entirely different applications. It was an API platform for a suite of applications

There was almost zero crossover in functionality

You can get offline support without an SPA. Of course, that may mean replicating some of your back-end behaviour in JavaScript, but that doesn't necessitate building an SPA, or the whole app in JS.

Please do share which crappy SPAs you're thinking of

Thanks for the feedback. I will try to make this clearer in the article.

While I state later that true decoupling isn't technically possible, it really only makes sense (to me) to attempt it when you've got larger teams split down these lines.

It really comes down to where you want to create the split: in code or on the org chart?

If you've created the split in one place, it will of necessity happen in the other.

If you can avoid the split altogether, then an SPA probably doesn't ever make sense.

Secondly, if you can’t build a system that actually decouples the frontend and the backend, that’s a “you” problem, not a technology problem.

You're right it's not a tech problem... it's a logistical impossibility. It is impossible to decouple a web frontend from its backend.

I'm a freelance consultant and a human person. I advise companies, especially early-stage startups, on this stuff.

I'm writing about what I see, which is hundreds of hours being wasted on triaging bugs, meetings trying to align small teams, and decision-makers simply following trends.

You still don't need an SPA for this

I don't think this has anything to do with design tbh. You have developers who are comfortable with HTML/CSS/JS and those who prefer to stay clear of it.

A lot of those HTML/CSS/JS folks happen to also really enjoy (and are great at) PHP/Ruby/Python etc - not so unicorn-y