Haven’t coded in 15 years. Just vibe coded and deployed a full React app over spring break from a Mac Mini. No laptop, IDE or terminal. Just me and my trusty Claude Dispatch.
We live in crazy times!
https://t.co/9jvg15UKVP
(it’s an MVP, be kind)
and fuck every investor, founder, and executive in silicon valley that quietly (or not) goes along with it just to promote their own capitalistic goals
I cannot wait until the White House changes hands and all of you ghouls switch back from "you're a traitor unless you bootlick so hard your tongue goes numb" to "the government asking any questions about my offshore fentanyl casino is vile tyranny and I will throw myself in the San Francisco Bay in protest", like werewolves at the last ray of the setting moon.
this christmas, i am humbly asking for your help to support dr. hankinson's research.
if not with $, i would be just as grateful for a repost or a like on this thread.
100% of your donation goes directly to funding the research efforts of Hankinson Lab: https://t.co/z8DcECGXGS
Apple is expected to sell about 90 million AirPods this year.
That would generate more than $20 billion in revenue for the company.
These were some of the headlines when the AirPods were first unveiled 8 years ago.
If you bent the knee to this asshole, and started furiously inventing reasons to defend him from his critics, there will be a moral stain on that part of your personal history for the rest of your life.
We've been evaluating a number of C++ successor languages for @ladybirdbrowser, and the one best suited to our needs appears to be @SwiftLang 🪶
Over the last few months, I've asked a bunch of folks to pick some little part of our project and try rewriting it in the different languages we were evaluating. The feedback was very clear: everyone preferred Swift!
Why do we like Swift?
First off, Swift has both memory & data race safety (as of v6). It's also a modern language with solid ergonomics.
Something that matters to us a lot is OO. Web specs & browser internals tend to be highly object-oriented, and life is easier when you can model specs closely in your code. Swift has first-class OO support, in many ways even nicer than C++.
The Swift team is also investing heavily in C++ interop, which means there's a real path to incremental adoption, not just gigantic rewrites.
Strong ties to Apple?
Swift has historically been strongly tied to Apple and their platforms, but in the last year, there's been a push for "swiftlang" to become more independent. (It's now in a separate GitHub org, no longer in "apple", for example).
Support for non-Apple platforms is also improving, as is the support for other, LSP-based development environments.
What happens next?
We aren't able to start using it just yet, as the current release of Swift ships with a version of Clang that's too old to grok our existing C++ codebase. But when Swift 6 comes out of beta this fall, we will begin using it!
No language is perfect, and there are a lot of things here that we don't know yet. I'm not aware of anyone doing browser engine stuff in Swift before, so we'll probably end up with feedback for the Swift team as well.
I'm super excited about this! We must steer Ladybird towards memory safety, and the first step is selecting a successor language that we can begin adopting very soon. 🤓🐞
@ajhodls I've seen multiple VCs say this, post hoc ergo procter hoc. Are companies doing well bec they send frequent updates or are they sending frequent updates bec they are doing well?