Right, but those capabilities are available to you as well. Granted the remediation effort will take longer but...you're going to do that for any existing issues _anyway_ right?
I understand why this is a tempting thing to do in a "STOP THE PRESSES" manner where you take a breather and fix any existing issues that snuck through. I don't yet understand why when you reach steady-state, you wouldn't rely on the same tooling in a proactive manner to prevent issues from being shipped.
And if you say "yeah, that's obv the plan," well then I don't understand what going closed-source _now_ actually accomplishes with the horses already out of the barn.
The mental model I had of this was actually on the paragraph or page level, rather than words like the post demos. I think it'd be really interesting if you're reading a take on a concept in one book and you can immediately fan-out and either read different ways of presenting the same information/argument, or counters to it.
Listen I'm not a crazy huge fan of a lot of new tech, but this is pretty transformational. When reading the first article [1] I was struck by the fact that it granted so much new freedom to your "social identity" on the internet. The comparison to hosting providers was incredible, because imagine you building a website and posting your thoughts there or starting a business there...and then immediately being shut down and all your data lost because of some arbitrary change of policy at your "host".
Everyone always talks about how your Google account being tied to logins is scary because you can get arbitrarily locked out. This protocol makes something like functionally impossible since /you/ control your data.
Hey, I'm an engineering manager at Join. We build collaboration tools for huge construction projects: think stadiums, hospitals, research facilities, etc. Our customers (GCs) love us and their customers (owners) love us so we're getting cool network effects out of that.
I'm looking for a senior/staff Golang/DB developer who has a bunch of tools in their belt, knows their tradeoffs, and /wants/ to share their knowledge with midlevels and help them avoid some of the scars you've accumulated over the years. :)
“Modern ESM” is a moving target. There’s always some new functionality that’s being added to the APIs that devs inevitably want to use. From his article, ‘structuredClone’ is a good example of something that everyone’s lusting over but isn’t quiiite there yet.
There are also still browser quirks etc for some of the newer stuff, and Safari tends to be a laggard, which cuts you off from iOS traffic.
I really like that line, "advice is a form of nostalgia." I think I already have internalized it a bit but I'm gonna try and be more mindful of that when I give advice!
This is true, but there's also a murkier middle option. I used to work for a company that made a lot of money from its software patents but I was in a division that worked heavily in open-source code. We were forbidden to contribute to the high-value patented code because it was impossible to know whether we were "tainted" by knowledge of GPL code.
Yes but it's a touch difficult to keep living expenses below $0, which most people in the developed - let alone developing - world would need to do on their salaries to save the extra $80k/year.
I understand why this is a tempting thing to do in a "STOP THE PRESSES" manner where you take a breather and fix any existing issues that snuck through. I don't yet understand why when you reach steady-state, you wouldn't rely on the same tooling in a proactive manner to prevent issues from being shipped.
And if you say "yeah, that's obv the plan," well then I don't understand what going closed-source _now_ actually accomplishes with the horses already out of the barn.