411–420 of 434 posts
Earlier quoted context omitted.
> There’s always going to be a market for well designed UX Given the past 3 years, I will never understand how people can be so confident making statements like this
If you are implying that AI models can do 'well designed UX', I would really love to learn the way of doing it.
Earlier quoted context omitted.
"Pathology"
it's objectively a pathological use of CSS because it circumvents the C (cascade)
It's ironic because standard software development practices advocate isolation.
[1] - https://www.statista.com/statistics/1118859/mobile-apple-ios...
Earlier quoted context omitted.
If you are implying that AI models can do 'well designed UX', I would really love to learn the way of doing it.
That's not how I'm reading it. More like, given the past 3 years development, why wouldn't AI be able to do that in the not-so-distant future?
Earlier quoted context omitted.
From a security perspective I greatly prefer a client-server approach: you have an unsafe frontend where you care about ergonomy and aesthetics, and a backend which provides an API which handles the security. Two different worlds and often two different kinds of developpers
I think we actually don't disagree there, but we have a different understanding of the term "server-side". Anything related to security must happen on the server since safety measures in scripts running client-side can be defeated.
Having a separate backed and frontend allows for separation of duties: the client is responsible for the user-facing content and the backend deals exclusively with data flows. This allows to have several independent clients, machine to machine connections etc.
Whatever arrives to the server is untrusted, and the API (or other interfaces) only verify raw data (a JSON for instance) and there are excellent (backend) frameworks for that.
Mixing the visual content with the data is possible (Django does that for instance) but from a security perspective less efficient (again - separation of duties). It also requires to possible double the work to have an independent API.
In other words, if you separate the two you do not care about security on the front at all, and the one who builds the back can focus on their expertise.
Earlier quoted context omitted.
Right, and as a consequence lots of very important software (orders of magnitude more important than tailwind) does not have full-time employees. Good for them if they can manage it, but it's a gravy train.
Given how hard it is to build any form of financially sustainable model around an open source project I think we should actively celebrate anyone who manages to build a model that works, not dismiss it as a "gravy train".
What will Shopify gain from this deal? Why everyone is buying dev tools. Earlier Anthropic bought BunJs. Can anyone explain the business model here?
What will Shopify gain from this deal? Why everyone is buying dev tools. Earlier Anthropic bought BunJs. Can anyone explain the business model here?