Surprisingly, Coriolis at extreme ranges (like 5000 feet) can be relevant enough to be corrected for, but how much and in what direction depends which way you're shooting and where on the planet you are. There's a fun calculator here: https://codingace.net/physics/coriolis_effect_shooting.html
Enterprise customers don’t get those plans, at the enterprise level you have to pay by the API rate… so people don’t have limited use, but you’re also not getting the heavily discounted rate the “normal” plans are at.
I’d disagree wrt “modify”. There are all sorts of tools for modifying LLM weights (ie to remove refusals, remove layers or experts, merge models, finetune, and more) and a quick glance at huggingface or civit will show those in very active use.
I don’t think the hardware requirements are relevant. If a research lab publishes the code their particle collider runs under the GPL, that doesn’t make it not OSS even though they’re the only ones on the planet with the hardware to run it.
I feel like I have a different $20 plan than everyone else. I have no problem hitting my 5 hour and weekly limits. Don’t get me wrong, it’s a great deal compared to API pricing, but it’s a far cry from “unlimited”.
> There needs to be a time when you are completely undisturbed and disconnected. If you are disturbed by work you will think about work while you answer and maybe even after that. That's not good.
IMO this is not a universal truth - I’m sure some people need that level of disconnection, but I don't find I'm one of them. I generally like my job, and don't find that forcing myself to disconnect does me any particular mental good. But other people report needing that separation, and that's fine! I don't think there needs to be a one-size-fits-all answer here.
I think my POV on this is a bit different than what others are expressing… I don’t mind answering the occasional email while on vacation, but I view it as a fair trade - as long as the company doesn’t mind me handling the occasional personal obligation during work hours I don’t mind handling the occasional work obligation during personal hours. If the company wants to be strict about clock in/out hours or taking PTO for every 30 minute errand or the work trends in a way that routinely exceeds 40 hours per week total then I’ll stop doing work “off the clock”, but so long as they’re willing to be reasonable I’m willing to be reasonable.
Is there anything to read on how the economics of an orbital datacenter make any sense? Because I don't really see how blasting a server into space solves any of the typical issues associated with datacentres beyond easier access to solar.
That’s how I use it. I might be working on two or three features at a time (iterating, iterating, iterating…), but they’re all scoped and of user value; I don’t feel that I’m just off chasing rabbits.
But I’m also one of those people for whom the “fun” was always solving human problems rather than solving computer problems. I can see how if you are in the latter category AI has already sucked out a lot of joy and how rapidly project switching could be the least-unfun option.
A library with a bunch of different providers doesn’t solve the payment/billing problem (which is one of the main openrouter benefits). IMO being able to buy credits and not have them locked to one provider is worth the 5% to me.
They're different sizes, it's in the description and it's also described under "More info" > "Capacity (cl)". I'm not seeing the "What is the capacity..." button you mentioned.
I love that even something as well-trodden as a kettle design can still be refined further. My main skepticism is whether this works well when the kettle isn't close to full - the image of it pouring implies a nearly-full kettle, but does the angle become awkward when it's closer to empty? Hard to know without actually holding one.
While web accessibility is important and something we should be investing in, I do feel that the vendors of accessibility tools are somewhat to blame here in how friggin difficult it is to actually make something accessible. Quirks and features are wildly inconsistent across tools, and feature uptake is much slower than it should be. For example, creating an accessible dialog shouldn’t be a multi-page essay to explain, it should just be “use the <dialog> element.” - but the a11y tools are so inconsistent that you can’t just do the standards compliant thing. And don’t get me started on roving tabindex techniques (for things like data tables), which are at best an ugly hack that the entire industry has collectively decided “eh, it’s good enough”.
Even what's described in the article basically boils down to "You can label things, but not generic things (for some reason?), unless that generic thing is a <section> or has a popover attr in which case it magically works." And this isn't even one of the "hard" accessibility things!
It looks like in iMessage for business, the phone’s user’s outbound messages show as dark grey (as opposed to normal iMessage and SMS/RCS which show outbound messages as blue and green respectively). I assume this is supposed to communicate that you’re talking to a different sort of entity, not a normal person on a phone.
Personally I don’t see why you’d care. My business isn’t trying to pretend to be a normal person using a phone, so why would it matter?
> It is only spectacular because of the free tiers
The thesis under discussion is "most people hate AI", not "most people will pay for AI". People who hate AI won't sign up to use the tools if they're free or paid QED AI service signups regardless of paid status are useful datapoints for "how many people don't hate AI".
I’ve said this before on HN, but there are two things that make me optimistic that we won’t see a big rug pull where price-to-capability ratio skyrockets relative to today:
* People keep finding ways of cramming more intelligence into smaller models, meaning that a given hardware spec delivers more model capability over time. I remember not that long ago when cutting edge 70B parameter models could kinda-sorta-sometimes write code that worked. Versus today, when Qwen 27BA3B (1/23 of the active parameters!) is actually *fun* to vibe code with in a good harness. It’s not opus smart, but the point is you don’t need a trillion parameters to do useful things.
* Hardware will continue to improve and supply will catch up to demand, meaning that a dollar will deliver more hardware spec over time. Right now the industry is massively supply constrained, but I don’t see any reason that has to continue forever. Every vendor knows that memory quality and memory bandwidth and the new metrics of note, and I expect to start seeing products that reflect that in a few years.
I hope that one day we’ll look back on the current model of “accessing AI through provider APIs” the same way we now look back on “everyone connecting to the company mainframe.”