And created such a boom of medicine that one can assert that the poorest among us should be entitled to it, and not have that assertion dismissed for being literally impossible.
It’s affordable relative to the definition of affordable given at the time. The entry level Model 3 currently sells for $38,630. That's $28,600 in 2016 dollars.
If you have a good argument, it will withstand the bare minimum of logical analysis, such as the factoring the consequences of inflation.
On a personal note I don’t find the CEO of most companies to be particularly interesting or important, and I include Tesla in that. Obsessing over personalities is the furthest from interesting as it gets for me.
If that's really the reason, that's the most idiotic reason possible. So he "earned" a couple of Roadsters by spamming his referral code, and it turns out his free cars might be a decade late, and maybe not as awesome as promised?
If your employer said they'd pay you half a million if you worked for them, and then you did and they didn't pay you, I doubt you'd be dismissing it so frivolously
Is it fraud if he paid $0 for non-existent roadsters? Referral credits are legal fictions, much like how Tesla Roadsters are physical fictions. Trading one fiction for another isn’t fraud, it’s cosplay.
>Is it fraud if he paid $0 for non-existent roadsters?
Is it fraud if you worked for a startup that promised you options, and then refused to honor/issue those said options? After all, because those options never existed, you also "paid $0 for non-existent [options]"?
> Leveraging an existing monetised readership for referral credits isn’t “work”.
> Is it fraud if he paid $0 for non-existent roadsters?
How do you think readership gets monetised in the first place? The biggest way is ads, which includes referrals.
Do you dismiss paid ad placement the same way you dismiss referrals? If not, what makes it different?
> Referral credits are legal fictions
A promise for $100 of stuff isn't exactly the same as a promise for $100, but it's close. Debt is a "legal fiction" but that doesn't mean it's not legitimate, or that you can pretend it doesn't exist.
It’s not that simple. For trains to be a complete solution you need walkable cities, and high density transport-oriented residential construction near stations.
This is almost diametrically opposite to parking-oriented cities and sprawling suburbia.
The best time for a city to invest in making their city walkable and public-transportation-able is decades ago. The second best time for a city to invest in making their city walkable and public-transportation-able is now.
Not everyone wants walkable. I'd much rather a remote first economy and cars. One of my hobbies is riding motorcycles on race tracks, I need a garage to store them, and a vehicle to tow them there. This is practically impossible in "walkable" cities.
Localities large and small have been moving towards higher density, walkable and transit oriented development for years now. It's happening, and it works.
Every time I attempt to read it, halfway through my brain flips into the mode that is normally reserved for when people start telling me that Ivermectin is a COVID remedy, or something equally farcical.
The comment you're replying to is not OK and I've replied to them to convey that. But the escalation and gudelines-breaking conduct in the thread began with you and was extreme. We need you to stop this style of commenting on HN and make an effort to observe the guidelines if you want to keep participating here. You've been warned before, and after enough warnings we have to ban accounts that keep commenting like this.
Please take a moment to remind yourself of the guidelines and make an effort to follow them in future.
Presumably if it knows it needs to perform multiple searches in order to gather information (e.g. searching for redundant implementations of an algorithm, plus calls to the codebase's canonical implementation) it should be able to run those searches in parallel grep calls.
LLMs are inherently single-threaded in how they ingest and produce info. So, as far as I can gather from the description, either it spawns sub-agents, or it has a tool dedicated for the job.
The web platform doesn’t need to move this fast. Google is, often unilaterally, pushing new features and declaring them standards. In my opinion, the web should not be changing so fast that a truly open source community project couldn’t keep up. I don’t like how the web has become reliant on the largesse of billion dollar corporations.
I recognise that this is a controversial take, but in my opinion what Google is doing is a variant of “embrace and extend”. Traditionally, this meant proprietary extensions (e.g. VBScript) but I think this a subtle variant with similar consequences.
I know it's fashionable to forcefully shove the same pet peeves about Chromium into any topic even loosely related, but here I'm talking about Safari webcompat fixes, bug fixes, and improvements having very long delays between being written and landing in customers' hands. I would make the same argument if Chrome never existed. Thank you for presenting the 10,001st reissue of this "controversial take".
The behaviour of entities that WebKit is ostensibly told to be compatible with isn't a "loosely related" topic, it's precisely on-point. It's certainly no less on-point than nebulous criticisms of Apple for assumed NIH syndrome or marketing priorities. You criticise Apple for not having a rapid release schedule; I am criticising the very notion of rapid release schedules (other than security patches).
How can you defend Safari rendering broken sites for long periods due to lack of frequent updates as a good thing?
The ever current adage of distortion field applies here.
Just like Safari not having webgpu was touted as a feature and now that it has support, webgpu suddenly turned into a feature. Apple can do no wrong to some. Whatever they do is a feature. And if they don't do, it's a feature too.
I agree that numerous companies inspire occasional weird reflexive defences from their most enthusiastic supporters. Thankfully, bad arguments have no transitive value.
Implying otherwise is itself a bad argument.
It is true that Safari sometimes lagged in ways that are legitimately open to criticism. There are instances where Safari had incomplete or broken feature implementations. But many claims of “broken sites” are really just evidence of lazy developers failing to test beyond Chrome or to implement graceful fallback. Relying on bleeding-edge Chromium features before they've been broadly adopted by browsers is, IMHO, a infatuation with novelty over durability. It's also, IMHO, a callous disregard for the open web platform in favour of The Chrome Platform. Web developers are free to do whatever they like, but it's misleading to blame browsers for the bad choices and/or laziness of some web developers.
> But many claims of “broken sites” are really just evidence of lazy developers failing to test beyond Chrome or to implement graceful fallback.
Correct. People test Chrome first and often only. That'll never change because people are lazy and you have a humongously long tail of websites with varying levels of giving a shit and no central authority that can enforce any standards. Even if another browser takes other, they'll only test that one.
The solution is formal tests and the wpt.fyi project. It gives a path to perfectly compatible implementations of agreed-upon standards, and a future where *the only* differences between browsers will be deliberate (e.g. WebMIDI). Brilliant.
That's why I wish the gap between Safari TP's wpt.fyi score and Safari stable's score was shorter. Simple!
Because such bugs were predominantly associated with then-new platform features.
As a web developer myself, I appreciate the frustration with Safari's flexbox bugs of a decade ago and viewport bugs more recently. I also remember being endlessly frustrated by Chrome bugs too, like maddening scroll anchoring behaviours, subpixel rounding inconsistencies, and position:fixed bugs which were broken for so long than the bugs became the de-facto standard which other browsers had to implement. All browsers have bugs. To suggest that Safari was uniquely bad is to view history with Chrome-tinted glasses.
You are assuming that Safari didn’t fix bugs for a long time because it “ships slowly.” Maybe some bugs are just complicated and take time to fix. It took Google years to fix the bugs I mentioned earlier (and many others) despite having the largest budget of any browser project and a VERY rapid release cadence.
No a lot of them are pretty straightforward, this is why I’m upset. I’m talking about, like, “SVGs with this feature don’t render correctly due to an oversight in size calculation” not “can you please implement WebGPU in the next release cycle”.
> How can you defend Safari rendering broken sites for long periods due to lack of frequent updates as a good thing?
That hasn't been true for a few years now.
Even now, when a site breaks in Safari, more often than not, it's because that particular site is using a Chrome-only feature that hasn't shipped in Safari or Firefox yet. These developers need to be reminded that progressive enhancement is a thing.
There are web developers who only test their sites on Chrome, which makes no sense, given mobile Safari has around 50% marketshare in the US [1] and about 21% globally [2].
> Just like Safari not having webgpu was touted as a feature and now that it has support, webgpu suddenly turned into a feature.
I must have missed this one, but anyone paying attention would have noticed WebGPU had been available in Safari (behind a flag) long before it became official; it was always on track to becoming a real feature.
"Google learned from Microsoft’s mistakes and follows a novel embrace, extend, and extinguish strategy by breaking the web and stomping on the bits. Who cares if it breaks as long as we go forward." https://www.quirksmode.org/blog/archives/2021/08/breaking_th...
VBScript is a word I hadn't heard in quite a while! Brings back memories of editing 5k line .asp files to find an if statement and then a 1000 lines of html and such. Sadly, I dont' think web development is actual better 20+ years later, just different...
The web platform on your device needs to be locked to a specific version because the OS stopped being updated. Once the OS stops being updated, you're supposed to buy a new device.
You shouldn't be allowed to use an old device with an updated browser, especially not a browser from a 3rd party, because that doesn't help Apple sell more iPads.
reply