| ▲ | computerex an hour ago | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
So your argument is that the 38T of tokens used in the last 7 days is by moron programmers or people doing "inauthentic" tasks? You think the person who made this post is also an idiot? Do you realize how incredibly delusional/self-centered you sound? | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | doctorpangloss an hour ago | parent [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
do YOU know anyone gainfully employed in programming who is using dsv4.1 to do work? what kind of work is it? why don't you ask them if it is good? in the market, where you cannot fake or hide stuff very easily: the outsource customer services and cheating sectors have been the most disrupted. Cheating company Chegg lost 99% of its market value. CS it remains to be seen - https://www.reuters.com/technology/teleperformance-shares-pl... - certainly perceived to be disrupted, but they are not dead yet. in my personal usage: dsv4 is generally pretty buggy. for example, if you give it a needle-in-the-haystack simple copying problem, it catastrophically fails to find needles if they happen to be positioned at index 250k tokens out of 1m. it can also be triggered to spew all sorts of garbage when DSpark is enabled during ordinary long-context coding, such as spewing weird DSML tool call errors after a normally parsed tool call error. i don't know why you have to attack me personally, i think you're a bright and otherwise nice person and you understand the thrust of my POV. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||