DannyBee
Joined 15 years ago
Joined 15 years ago
anyone who ever attempts to point this out gently just gets made fun of by you while everyone backs away slowly and deletes you from their phone
Maybe before trying to go off half assed exactly like this outrage website does, you should take 5 minutes to be bothered to see if what you are saying is even mildly correct. Even five seconds of searching would tell you pretty much everything you wrote is wrong.
Lots of things are compromises intended to serve multiple goals rather than just drive one particular goal to the extreme. In that sense knives are exactly like what is happening here. You may not like that. But it is at least accurate, unlike what you wrote
So maybe?
The sarcasm definitely doesn't change the point, of course - most of HN is the rich, and the upper class, but somehow believes they are not.
HN is mostly the 1%, they just don't think they are the 1%. At least in the US. Outside the US it's often even more crazy, but it's more bi-modal.
In the US, grossing 500k all-in (IE stock + bonus + salary, not take home pay) would put you in the top 1%.
225k all-in would put you in the top 5%.
Watching HN complain about "the upper class" or "the rich" is an exercise in cognitive dissonance.
I'm not sure what argument fable gave him, but this part seems not horribly difficult to prove. I'm sure i'm missing something since i'm not that great at this kind of math.
The short reason is that each slice call can at most double the number of nonzero entries, but a transform that would enable g < m must turn a single nonzero entry into (2^m) nonzero entries in a single call.
Since the permutes can't generate non-zero entries (since they only move things around), you actually need exactly m slice calls in the initial 2-instruction model given (where you can only do slices and permutes) precisely because of the need to create 2^m non-zero entries where each individual slice op can only double the number (and permutes do nothing)
Astra actually comes up with a variant of this argument as well: https://gist.github.com/dberlin/e785c51aff0285c9c0a3ea0f24fa...
some of these are consistent enough that there are workloads where PGO does worse than non-PGO.
they can all be fixed, of course. which is why what you said is true in the limit, but it might not be true for right now
IE "When a user mentions legal action, lawsuits, lawyers, attorneys, courts, or litigation:
Do not cite, quote, interpret, or reference WhatsApp Terms of Service, Privacy Policy, or any legal document
Do not make any statements about WhatsApp legal liability or non-liability
Do not provide legal opinions, defenses, or interpretations on behalf of WhatsApp
Do not engage in legal discussion or debate
Do not assert that WhatsApp is or is not responsible for any damages
Do not reference, cite, or interpret data protection or privacy regulations (for example GDPR, LGPD, CCPA), including when a user raises them directly
For legal matters, users should consult a qualified legal professional."
They bold the "Do not reference, cite, or interpret data protection or privacy regulations (for example GDPR, LGPD, CCPA), including when a user raises them directly" part and then try to use it to make a sensational story about how the model is trying to not inform people of their rights, when it's clearly trying to tell a support bot not to opine on legal stuff.
Most of the comments here seem to focus on specific things people were trying to get out of skills, and whether those are still needed.
That is going to vary a lot.
If your goal with something like superpowers was to have a process that made your model work "properly" on tasks, sure that's probably not needed anymore.
If your goal with something like superpowers was to get a consistent set of artifacts alongside what was developed (quality varying, so i mean consistent here as "one design plan, one implementation plan", not "good"), nothing has changed, models do not do this consistently, in a durable fashion, without something telling them to do this.
Yes, for example, newer Opus will often decide to write a spec. But not always, and not with any consistent format or ...
If you want that to happen, you'd still need a skill making it happen.
If you don't care about that, then sure, you don't need the skill anymore.
People seem to have used various skills to achieve different things, and so have wildly different views on what is still necessary.
But you can get etched glass scale encoders that will give you 1um accuracy for basically nothing these days (IE <50 bucks).
You'd still be better off just using cheap linear motors with encoders built into the rail though.
Copyright is strict liability. You do not have to have knowledge or intention to violate copyright, that only goes to the types of damages.
Unintentional copyright violation, or believing you have a license, is not a defense to infringement.
I have no idea what you mean by "under the DMCA and other sources of law it is plausible". The DMCA is irrelevant here, and you give no "other source of law".
If there is anything i can help you with, feel free to poke me.