You have three features, A, B, and C. They are core features. Two of the features break. How do you prioritize which feature gets fixed first? With telemetry its obvious, without it, you're guessing.
Also, gh cli is not about git, its about the github api. In theory the app has its own user agent and of course their LB is tracking all http requests, so not anonymous ever.
It's not, you can literally do everything this tool does with Git, and 80% of the features could be replaced with commands in your shell rc file also using vanilla git.
This tool was described perfectly the other day. JJ is the Dvorak of Git. Most people could careless about Dvorak layout, 99.8% of people use qwerty just fine. Those 0.02% though, they're loud, and they want everyone to know how great the reinvention of bread is.
Nearly every package manager does this. You would never get work done if you had to inspect every package. Services like renovate and dependabot do this lifting at no cost to the js developer, and probably do it better.
I've been watching a series on YT that is specifically about rural towns in Texas that are being abandoned or on the brink of total collapse. Much of it has to do with highways and routing around these communities decades ago. I don't know if a datacenter is the answer, but it has to be better then what looks like a post apocalyptic America.
Reviving Radiator Springs with a datacenter! The plot of Cars 4.
Those small towns are often positioned such that even if you plopped a billion dollar datacenter on top of them, it wouldn't change much, as even with second and third order effects it's adding 100-200 total population.
Sounds more difficult then modern web frameworks. We've all done this for little projects, but anything with users or development teams, your method is DOA.
I disagree, most webapps, like 99.9% I would say, are just forms, links, and pages. Meaning, they can be done with 0 reactivity and that is the most simple and straightforward way to do it.
Less code is basically always better, so if you can skip the huge amounts of JS and orchestration required by modern web frameworks, then it will be easy. People are out here using React to render static pages. It's very overkill.
Eh, there’s tradeoffs. They’re real. But I’ve done plenty of this on teams back in the day before all these frameworks and it can absolutely work. It may even be easier now with JS modules.
I'm retired now, but if I were looking for a job I'd try to find a company not using Atlassian products. In theory you're not supposed to use them as a (micro-) management tool, but companies like to do just that.
I’ve written on this. Jira is a code smell. The only people I’ve ever known who liked it were the people I don’t want to deal with. It’s a dream tool for someone who wants to make a career out of looking busy and inventing process, and a nightmare to everyone else. Its presence in an org tells me, in italic capitals, that this is going to hurt.
Consumers dont care about OSS, most people dont feel enslaved, and the only market share they'll dent is Android/Google. If we're getting more android slop, I'll pass.
reply