In the philosophical sense, sure. But given the context of this conversation, the fact that you don’t have to pay to use GitHub projects is absolutely relevant to their success.
is your expectation that if you contribute to an open source project that you would get notified if your code is later modified?
if I was in your shoes, I would assume that once the feature is merged, the maintainers have final say and can modify or remove your code as they wish. An RFC for a breaking change would surely be nice but I wouldn’t expect any kind of notification if the change was some kind of minor update or enhancement.
People are using the term “metaframework” these days to describe things like Remix and Next that build on top of React as the view layer and provide many of the other bits you might need to get a fully-fledged web app up and running. Including but not limited to routing, performance optimizations for images and fonts, data fetching, SSR/static generation & regeneration
I’m the exact opposite of you. I like most of the touch screen controls, including the AC ones, but the number of taps it takes to open the glovebox always irritates me.
It’s been several years since I’ve used Jira so can’t give an honest head to head comparison, but my experience with Linear has been fantastic. Looks nice, has all the functionality I look for, enough customizability.
If you’re looking for something you can configure every little bit of for a very large team (like Jira) it may not meet your needs, but otherwise I highly recommend.
That price is squarely in the realm of other popular similar products like Squarespace. Most likely not targeted at people who have the skills and time to figure out how to self-host.
That’s fair. My issue with the mixin approach is that then your app code can hit the database from anywhere you have access to the model object, which makes testing your own code in isolation much more difficult
I don’t use Clojure but based on a quick search, EDN is extensible so you can serialize things like datetimes and UUIDs with type information rather than as plain strings
The problem is that coverage of typing in third party libraries is not that high yet, so it’s not really possible to enforce typing in a thorough manner.
I’m not the person that suggested handwriting object methods. As I’ve said, I agree with the point you’re making, I’m not arguing with you, or for any specific ORM design.
I don’t see what the nuance is you’re getting at with the mixin vs object method argument though. They both have the same issues around testability and violation of SRP.
The quote is about the shift to mirrorless vs DSLR, and the article seems to misinterpret that to support the conclusion that phone cameras are killing photography. They even throw in a random comment about film photography in the last paragraph.
Canon is still making cameras, and Sony is having more success than ever with the mirrorless transition. Changing the label doesn’t mean that photography is dying.
There’s not a perfect solution yet (I want someone to release preview DBs) but I currently use Supabase since they provide a regular Postgres instance with a connection pooler out of the box.
Many/most ORMs (the ones that follow the ActiveRecord pattern) do this as well though. I prefer to avoid mixing concerns and use datamapper-based ORMs myself, but what GP wrote is fundamentally not that different than what a lot of ORMs do.
I definitely agree that there’s less magic going on with a traditional style deployment, but I think you’re strawmanning Next a bit with this comment. Not everyone uses graphql, and a vanilla Next API route is similar in complexity to a vanilla node http server.
For a basic CRUD app, especially for a solo dev, the monitoring story on Vercel is sufficient and it’s hard to say that their single repo push to deploy setup is more complex than the traditional alternatives.
Counter argument: if they’re paying designers, why would they not pay for the tools that enable them to be most productive? Figma is a small cost, relatively. Asking them to use a tool that’s worse is like hiring a developer and refusing to pay for a Jetbrains subscription, the tool is worth way more than the pennies saved.