If it’s 3 days it’s something like 15 minutes, if it’s 3 weeks, that takes a couple hours lol. Seems like there’s some sanity to the estimates after all when you think about it, it’s just the scale it gets wrong due to estimating human time.
From a practical perspective this makes perfect sense to me. But we do know the photons travelled over a period of time, right? Where those photons came from, ‘now’ is something else. Though it doesn’t matter practically, those events did occur in the past, before they were a part of our now. Or am I missing something?
No, actually, the photons did not travel over a period of time. Photons travel at C, and thus experience no time in their reference frame.
As for _our_ reference frame, I've explained in other comments but a debate has developed between those few who do understand because they've studied physics, and those who think that their intuition is more correct than Einstein. I decline to elaborate further, HN comments are not long enough to cover it all. In short: you are in fact missing something but that is fine, everybody is. Einstein himself stated that in his day maybe three people on the planet understood, and he was uncertain if he was among those three.
You've got some nerve to come in here with self-admittedly barely-understood BS from a pop science book and pretend it's other people's fault for being uneducated when they challenge you.
Quality of the information from the pop-sci book not withstanding, I've also taken physics courses on the subject. Albeit twenty years ago.
But go ahead, you win the internet argument. When I thought this was a discussion, and I could potentially learn something or help somebody understand, I was happy to participate. But I have no interest in an argument consisting of insults and accusations and no exchange of information. You win, congratulations.
I was on the Ultra for 18 months or so and came away from it feeling like a much less powerful and capable Garmin is much nicer as a daily watch. I found myself wanting to find reasons/excuses to justify the Ultra. Ultimately I couldn't, and it wasn't worth its cost, charging schedule, and lack of battery life.
I can see why others like them (they want WatchOS and Apple-specific capabilities). That stuff is useful, but not often enough for me to care.
Really, the watch was a regular reminder of how functional life was before the watch existed, if that makes sense. It's a genuine marvel, and yet... I got by (and get by) great without it.
I think a large percentage of your problem might be that you bought the most expensive model. Was the Ultra really the one to get?
It’s the thickest and heaviest, for one thing.
There’s a decent argument for the SE as the best Apple Watch for most people because it’s cheap and it does most of the things that regular people want out of a smartwatch.
As I recall, I went with it because it supported the best dive features. I used it for that quite a bit for a while, but eventually realized my basic cheap dive watch worked fine, could take a beating, and was actually better rated for deeper dives. Having physical buttons is a huge advantage over the Ultra. The dial was never enough to get the control I wanted, even if the UI only required it.
> Providing ready-made UI components and templates has never been a million-dollar business, nor should it be.
But what if people were already selling them, and tailwind showed up, did it better, and people went directly to them to buy what they were offering?
Why shouldn't that exist?
The folks over at Tailwind offered curated, hand-built components that were readily adapted and tuned to your own needs. They did an excellent job making it so you could pick and choose what you wanted, then theme all of it from your tailwind settings with ease. It was excellent.
Sure, similar things existed for less or at no cost. I was content to pay for this, though. It made my work meaningfully simpler at times. It paid for itself.
> Tailwind's business model existed due to a massive inefficiency in the frontend industry not being able to come to terms with CSS or native components.
I don't agree. The pain it addressed on my team was more so that very few people I worked with understood CSS, but tailwind was easy enough for them to work with (particularly in a React context). It was a useful tool in a context where a lot of the people didn't fully understand the tool. They could just pick and choose components and they'd slot into the app well enough. It addressed real pain there.
They surfed a wave for sure, but I think it was mostly that a non-trivial number of people working on the frontend don't understand HTML and CSS very well. That's not their fault at all.
> The folks over at Tailwind offered curated, hand-built components that were readily adapted and tuned to your own needs. They did an excellent job making it so you could pick and choose what you wanted, then theme all of it from your tailwind settings with ease. It was excellent.
They also offered an Open Source CSS framework with the explicit goal of making it easier for you to style your own components. There was always some tension between "make abstraction layer whose adoption depends on users finding it easier to make your own components with than vanilla CSS, which is not unusually hard" and "sell pre-made components". Particularly when there's an abundance of alternative FOSS components/libraries out there[1] in vanilla CSS or even full blown CMS templates for people not wedded to the idea that Tailwind makes things easy for them. Much easier to sell templates or even "premium components" when your USP is integrating them with a backend them rather than merely providing the layer of syntactic sugar supposed to make component styling easy...
They also happened to have the misfortune of designing it in a way which is particularly easy for AI which doesn't have to tradeoff time spent making design decisions and figuring out how to achieve those from the docs vs dollars spent buying components to minimally tweak.
[1]tbf, I always thought the Tailwind creators' designs were more tasteful than the average CSS mixin library even though I didn't think the same about the syntax...
> There was always some tension between "make abstraction layer whose adoption depends on users finding it easier to make your own components with than vanilla CSS, which is not unusually hard" and "sell pre-made components"
We wouldn't need doctors if we had a box you could walk into that cured all ailments.
We won't need software engineers once you can crudely specify requirements and have a machine turn them into rigid requirements with a solid data model, flexibility to extend, infrastructure to run, and monitoring and recovery to maintain reliability.
I doubt anything besides AI could ever become omniscient. Not that AI has a particularly high chance at it, but I can't imagine anything else even coming remotely close.
if you mean this in a reductionist way for humans, i dont think most of us think we’re omniscient
my point more broadly is that if you have an incomplete spec, any entity implementing it either needs to be omniscient or make assumptions about the intended behaviour of the system. if constraints or invariants aren't part of the spec it might be difficult or outright impossible to make the right assumptions.
so while LLMs might be writing all of the code in the future, someone will still need to create the spec + verify it. and often the spec is not really possible to know until implementation begins...
ive been using astra on a project that isn't even that complex in the grand scheme of things, and it still fails to make the right assumptions. of course i could just give it a full complete spec right?! except i didn't know what the right assumptions were either until implementation anyways. so to some extent they were unknowable to me, and thus unknowable to the llm no matter how powerful.
I do think in the future humans will probably write very little code themselves, but the work will be all about specification + verification and that means system design, which is the stuff I care about anyways. maybe I won't develop rsi when I get older :)
im not swe by trade, in fact I would love it if what you said was true because I could consolidate various kinds of businesses into one holistic infrastructure and demolish all the competitors.
I do want safer vehicles and I do see a path to get there with this technology.
What I don't want is companies training their technologies with legitimate risk to the public, with a clear pathway to profiting off of this risk and public data, with no benefit to the public _unless_ they happen to succeed, and to some degree, unless you can afford their products. Something feels off about that.
Of course, everyone benefits if vehicles are safer, but it does feel like there is an extractive factor regardless. These companies benefit from public resources, are wholly enabled by public resources, but are trying to create a situation in which the technologies they create are more or less required to be used in order to utilize the public resource. Does that make sense? I suppose it's inferred, but, I don't think it's unreasonable to believe any car manufacturer with a working FSD technology would LOVE to have that technology mandated to be on every new vehicle. Imagine leasing that to every manufacturer who didn't develop it themselves so they could continue to sell in the USA.
On one hand, safer vehicles are a MUST because we allow an absurd number of people to die due to unsafe driving every day. On the other hand, I don't feel right about private companies benefiting so much from roads the public built, while training their technology with some degree of risk imposed on the public, and with no clear desire in these companies to give back. They tend to pay paltry sums in taxes, if any. Rivian was at a net loss of over 4 billion for 2024. I understand they're trying to build something that requires massive capital, but, I also understand that these companies are experts at operating at a loss for prolonged periods of time. Amazon is a stellar example.
This definitely cuts both ways, but I'm not sure exactly where I stand. I need more information to decide, but I'm confident that there is some degree of exploitation of public data and resources here. I'm not trying to imply Tesla, Waymo, or Rivian are the only ones guilty of this either. The tragedy of the commons is a well-known phrase because it's such a typical phenomenon. I'm also not suggesting that there's a simple solution. There can't be because the fragmentation of the polities in which these companies operate and train their technology within.
> Considering the amount of ads they handle that seems... reasonable?
Why reasonable? Don't these ads pass through pre-publication review, and Meta makes money off of it? Any number above zero is a serious problem. If they can't run an ad business that doesn't publish and profit off of CSAM, they shouldn't run it.
I don't think we should distinguish between 'fake' and real CSAM based on if kids are hurt; this ad machine shouldn't be able to publish it, regardless. The moral question of if it's real or kids were directly harmed seems separate to me.
I recall YouTube was hijacked to show multi-hour ads during the pandemic. These are imperfect systems that can be abused at any scale.
They identified them after the fact and appear to have disclosed that. This is what they needed to do to be able to be held accountable and to do better detecting them in the future.
I block ads and ad services at the device and network level and don't use any Meta services (outside of facebookresearch models), so while I'm fortunate not to have been able to be served any of these, it's also kind of unfortunate that I'm in a relatively rare category to know to report them and how.
Without more context it’s hard to say whether 332 is reasonable, but I interpreted “reasonable” as in there will always be some amount of harmful content uncaught by automated systems.
In my mind there are two components of this that are in direct tension though, regardless of numbers:
1. Humans having to review ad content is legitimately traumatizing and awful
2. Automated systems can miss obviously harmful content, which should never be allowed
To me this means we probably shouldn't permit these systems to scale as they do, because the company profits from harms to its own workers and/or ad viewers. I worry that we've normalized a business that shouldn't exist in its current form, but it prints so much cash that no one is willing to stop it.
Not OP but my guess is that they're already using bad AI images for their kebab business, and OP wants them to use better AI for their images (so they may actually lose fewer customers because the AI imagery isn't so awful)
Yeah, important to note that the way the label is used has deviated from its historic meaning. Colloquially it’s something like “someone who rejects new technology” with variable reasons as to why, but historically there’s more nuance and it’s grounded in rejection of technology which worsens working conditions, detracts from craft, and disrupts cottage industry/workers rights/wages/etc. They made more sense than the label presently suggests they did. I suppose you could think of them as activists protecting their crafts and trade privileges that were being undermined by specific machines and their owners
reply