ferdowsi

In what way do Javascript heavy SPAs reduce supply chain attacks vs a no-JS solution?

I think that there's something to be said about how a successful business that grows outside of the Bay Area hegemony can be an important source of community growth, and an acquisition can dramatically undercut that. It's great there is a one-time cashout but something important is lost in the process.

I don't understand. How can a decentralized currency be unilaterally shut down?

Cloudflare is down 71% in that same period. Zoom is down 60%. Speculative pandemic tech darlings are no longer darlings and are being hammered across the board.

It's going to be a rough time for anyone who had high hopes for their equity compensation.

Americans are exempted from a great amount of capital gains as well.

The Register fulfills its role as a beacon of misleading tech sharebait.

Congratulations to everyone who thought this through and implemented it. I'll go so far as to say that Project Loom makes Java a more desirable web programming language to me than any language that has colored asynchronousity, like Rust, C#, Python, etc. Async/await is one of the worst design patterns to emerge in the last few years and I'm glad that the tech world is coming to its senses.

Kotlin coroutines are colored and infect your whole codebase. Virtual threads do not.

After the 2017 tax reform bill, itemizing deductions is not cost effective for the vast majority of Americans.

The market will react at the next earnings report, not now. And only if customers start to bail.

Node has a more robust standard library than Rust, which forces devs to download third party libraries to compute a regular expression or generate a SHA-256.

For now Node is a richer target due to its popularity but the same issues will hit any language ecosystem that suffer the same flaws should they become popular.

Academia trying to "Make Haskell Happen" is a clear indication of how disconnected it is from the practice of software engineering. Haskell is not going to happen.

That's on the home screen, not displayed over content.

That company that hires 10 engineers to create a bespoke orchestration system will inevitably end up re-inventing a buggy, poorly specified implementation of Kubernetes.

Kubernetes gives a standardized set of abstractions and concepts that means hiring and development is easier, not harder.

Oddly representative of the prevailing Ruby attitude to prefer saving two characters over something absolutely explicit and informative like `.call`

Not just that, but I don't understand why users would be so eager to kill type safety in their applications. If i'm understanding, these injection methods are totally type-unsafe and construction errors are deferred until runtime?

https://pkg.go.dev/go.uber.org/fx#Provide

Technical discussions are far more ideologically driven than we give them credit for. Witness the hype cycles and evangelism machines around certain technologies, programming languages, etc. They're often barely rooted in technical merit.

Github has been rewriting performance-critical components in Go for a while now.

https://github.blog/2020-05-20-three-bugs-in-the-go-mysql-dr...

> Although GitHub.com is still a Rails monolith, over the past few years we’ve begun the process of extracting critical functionality from our main application, by rewriting some of the code in Go—mostly addressing the pieces that need to run faster and more reliably than what we can accomplish with Ruby.

I don't think it's coming back. The big players who started with Ruby during the peak of its 2008~ hype curve are having serious scaling pains and are looking to other more performant languages as a way out. Engineers at these companies are going to be taking these lessons elsewhere.

This isnt even mentioning the compelling environmental arguments against a computationally taxing dynamic language like Ruby, which is going to be louder in the next few years.

IRC usage stats are freely available. It was never popular.

https://netsplit.de/networks/top10.php?year=2006

IRC was never widely popular outside of a gamer/geek niche. At its peak, QuakeNet never broke 250,000 "users", many of which were bots.

Comcast is a pretty big deal.

Funny that this would be used in defense of Stallman, a zealot who built his whole public personality on supposed "speaking truth to power". He literally called Microsoft "the Great Satan."

The default Go server supports HTTP/2.

https://pkg.go.dev/net/http

> Starting with Go 1.6, the http package has transparent support for the HTTP/2 protocol when using HTTPS.

Seems pretty clear that Facebook is putting this statement out because they're sweating their big stock slide and looking to staunch the bleeding whereever possible. If they were in a stronger position they would be sticking to attempting to strong-arm the EU.

The opposite end of OOP is the functional purist world where "color = blue when hovering over button" becomes 10 levels of boilerplate indirection in order to update global state and receive changes using actions/reducers/containers/memoizers. It's just substituting one type of needless, brittle complexity for another.

The blog post is misconstruing things; WebAuthn is not totally backwards compatible with U2F. Specifically, WebAuthn doesn't support the U2F trusted facets functionality, which allowed for a U2F credential to be used on a cross-origin basis. https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fid...

GoFundMe is a facilitator for fundraising efforts. If someone wanted to start a far-right crowdfunding site they could without involving digital gold.

FB has been making their API increasingly useless for a decade now. They don't want you building integrations, they want you in their walled garden using their tools.

> If you don't want to discuss "taste" questions, then just don't, it doesn't matter what option you pick. If it is an important question, then you should debate it.

I'm personally glad to see Python development come to the same conclusion enforced by Go's opinionated tooling.

That is: style questions are almost always unimportant to producing value, but teams still waste excessive time on them because of the engineering tendency to bikeshed triviata.