I think this is really honest and the reason we see this big divide. On the one hand people that never enjoyed coding but enjoy to see their ideas realized are celebrating. But the group of people who enjoyed coding in itself and never saw it just as a means to a result feel cheated.
I think a lot of the polarization you seen online is revolving around this difference in character.
I am of two minds about this really. because I've certainly enjoyed the puzzle and the journey in the past. But I also enjoy to get to see ideas I've had for a while but never had the time for, realize quickly.
I also don't think its just a distinction between enjoying the journey or the destination, but I think its enjoying a very specific type of journey, e.g. slow methodical etc.
Whereas people with a different temperament find the speed and the ease of experimentation and the sometimes surprising results more appealing.
I think it's just replacing what a a good Library or Bookstore would have given you in previous times: cross reading many different books, without having to commit and pay upfront. The assumption that I'm going to pay for a book upfront without being able to leaf through it from front to back is preposterous.
This is only sometimes true. Cases like opening hours and daily batch processing rely on local time. Persisting the values in UTC mean best case you are wrong half of the year and worst case all of it.
6am in my time zone is two different times in UTC. Right now it is 14:00 UTC. But when DST starts it will be 13:00. So what UTC value do you insert into your database for the opening time of the coffee shop? And how do you convert?
Yes, you can store additional information to decipher the meaning of a UTC time but why? Storing locale is good because sometimes you need to know where something is, such as when converting the local time to another zone. But you should avoid creating dependencies between these values because it makes using them individually harder.
The coffee shop opens at 6am. That is an unambiguous fact. The coffee shop is in Seattle, WA. That is another unambiguous fact.
If the time is in UTC then you need to know the date the time was set or store a dtc flag and then build some logic to convert. You can just feed local time+locale into any datetime library and get whatever you need.
UTC is great for a lot of things. Such as recording when something happened. But local time has a place as well.
Iagree, Seems like it's a bad study design. Unfortunately this will not be discussed in these types of articles. and at the end people only remember the headlines.
I wonder how much of these "restrictive" licenses are just attempts at whitewashing, virtue signalling and generally trying to cover their own asses. If someone wants to use publicly available weights in an illegal way, there is no way a license is going to stop them, just as much as the existing laws won't stop them. That being said I agree with the overall sentiment that breaking the division of powers and putting creation and enforcement of laws regarding model usage is outside of the scope of a model provider.
Has it been established that these even are licenses? A license provides authorization to do something that one would otherwise be prohibited from doing, but that assumes that copyright (or some sui generis right) covers model weights. Most of the findings/rulings I've seen talked about have been on the topics of inferred outputs and applications mixing them with human-authored elements, not about the model weights themselves.
