I recall C++ OOP being the new hotness when I started out and C was always contrasted as the old & busted example. Kind of the "Everything-as-an-object will simplify everything" phase. Windows MFC was the new way, then STL.
Java WORA write once, run anywhere was definitely a thing when it came out. Java Applets came out of the woodwork and were the WASM of their day. Even Cisco ran Java for their router UI for a while, which was painful.
More recently, HN went through a period about 10 years ago where every other article ended in " ... written in Go".
The mantra may not have rhymed with "rewrite X in Y" but the spirit was there.
In the circles where I hang out I think community opinion is that go is _fine_, but python has faster iteration speed for experiments, and rust has better correctness and performance for production, so there's less excitement around it
It does seem like a highly antagonistic way of working or perhaps I'm just naive.
If your only goal is to maintain a performance lead on your peers, you either need to gain and keep an advantage or find ways to actively make your coworkers disadvantaged (or both). And if you're already doing 1) then 2) isn't a far stretch.
> would you like to work on a team full of people like you?
If their team is already like this, what choice do they have? It's a prisoners dilemma where everyone else is defecting and I'm the sole cooperator.
IMO the onus for solving this is on the business owner, either through establishing a knowledge sharing culture or more comprehensive performance evaluation that rewards these innovations.
Not without my knowledge or your knowledge sure. But I'd bet there's significant percentage of the population who is tired of thinking about permission popups and just hit yes yes YES to get the App started. Especially if it forces retries before going forward.
I think they're counting on these popups wearing people out.
After GDPR made these incessant annoying cookie popups mandatory, I just robotically click any button to dismiss it as fast as possible. Some website could probably write "Give root access" in that box and I'd probably click it without thinking.
As has been said before, sites that don't use unnecessary cookies don't need to have a cookie banner. Having the banner is often just malicious compliance (or for a non-compliant one banner, maliciously non-compliant).
This is the 1st link posted in /r/unitedairlines anytime someone mentions "starlink". One use-case better covered by https://unitedstarlinktracker.com/ is the upfront log that shows a quick swath of airports that might receive and depart starlink equipped planes. I can CTRL-F -> "RDU" and know immediately my chance of checking this out (not much).
Would it be hard to produce a pie chart showing top 10 airports with most starlink planes arriving/departing?
Maybe the opponents consider it a foot in the door; a wedge that can be expanded gradually to include lower tiers at lower percentages AKA the beginning of a WA State Income Tax. There are not few 400k households in Seattle.
The majority of states have one so it's not that big a deal, but it'll be less often said "I'm going to turn down this higher SF offer for Seattle b/c of lower COL...".
I'm not sure where the next refuge will be. Austin? Memphis?
Java WORA write once, run anywhere was definitely a thing when it came out. Java Applets came out of the woodwork and were the WASM of their day. Even Cisco ran Java for their router UI for a while, which was painful.
More recently, HN went through a period about 10 years ago where every other article ended in " ... written in Go".
The mantra may not have rhymed with "rewrite X in Y" but the spirit was there.