Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kimixa
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
91.
▲
by
kimixa
8mo ago
And profiting from it, though less directly than "$ for illegal images". Even if it wasn't behind a paywall (which it mostly is) driving more traffic for more ads for more income is still profiting from illegal imagery.
92.
▲
by
kimixa
8mo ago
Yup - I've related it to working with Juniors, often smart and have good understandings and "book knowledge" of many of the languages and tools involved, but you often have to step back and correct things regularly - normally
93.
▲
by
kimixa
8mo ago
He does (or at least a good proportion) if you want to use as precedent for delivering on these promises, though. Especially for the larger more extreme statements and not just buying himself into an existing business.
94.
▲
by
kimixa
9mo ago
Considering Microsoft's significant (and vocal) investment in LLMs, I fear the current state of Windows 11 is related to a team trying to do exactly that.
95.
▲
by
kimixa
9mo ago
That guy's style guide seems to conflict with the Cambridge editorial services guidelines - though that is for books rather than papers: > Spaced en rules (or ‘en dashes’) must be used for parenthetical dashes. Hyphens or em rules
96.
▲
by
kimixa
9mo ago
The Oxford style guide page 18 https://www.ox.ac.uk/public-affairs/style-guide > m-dash (—) > Do not use; use an n-dash instead. > n-dash (–) > Use in a pair in place of round brackets or commas, surrounded
97.
▲
by
kimixa
9mo ago
In British English you'd be wrong for using an em-dash in those places, with most grammar recommendations being for an en-dash, often with spaces. It's be just as wrong as using an apostrophe instead of a comma. Grammar is often w
98.
▲
by
kimixa
9mo ago
As a brit I'd say we tend to use "en-dashes", slightly shorter versions - so more similar to a hyphen and so often typed like that - with spaces either side. I never saw em-dashes—the longer version with no space—outside of p
99.
▲
by
kimixa
9mo ago
True, you can increase bit width to guarantee never hit those issues, but right now saturating arithmetic on types that pretty commonly hit those values is the standard. Guaranteeing it would be a significant performance drop and/or me
100.
▲
by
kimixa
9mo ago
Fixed point arithmetic isn't truly associative unless they have infinite precision. The second you hit a limit or saturate/clamp a value the result very much depends on order of operations.
101.
▲
by
kimixa
9mo ago
I worked on an extremely niche project revolving around an old DOS game. Code I worked on is often pretty much the only reference for some things. It's trivially easy to get claude to scrape that and regurgitate it under any requested
102.
▲
by
kimixa
9mo ago
I mean technically there's nothing they can do that SMM couldn't - introduced in a revision of the 386. It's code running with system permissions invisible to the "parent" user code and OS. You're already prett
103.
▲
by
kimixa
9mo ago
Yup, it's their right, as it's their right to crank their seat back. Both are available, and expected. I see some take issue with people doing them at all, but I don't really mind much. Might be related to being 180cm or so -
104.
▲
by
kimixa
9mo ago
I think the issue is that people limited compute time as a proxy for difficulty. In that case you'll hit issues on any device that performs significantly differently from that which it was tuned in. Though I am slightly amused by peopl
105.
▲
by
kimixa
9mo ago
That happened to me when I had an ipad in a standing case and the seat in front cranked back - trapping then pinging the tablet across me and by neighbour's lap. Though the ipad itself wasn't damaged, a couple of glasses didn'
106.
▲
by
kimixa
9mo ago
I feel to be consistent the output of that model will also be under that same open license. I can see this being extremely limiting in training data, as only "compatible" licensed data would be possible to package together to tr
107.
▲
by
kimixa
9mo ago
The psychology behind "creating it for the sake of creating it" can also be significantly changed by seeing someone then take it and monetize it without so much as a "thank you". It's come up quite often even before
108.
▲
by
kimixa
9mo ago
Let be honest, you'd only bother trawling if you already had significant suspicion.
109.
▲
by
kimixa
9mo ago
The output of AIs that is "churned out" wouldn't exist without templates like this being used as an input to the training. But that isn't "Copyright Infringement", according to the AI companies.
110.
▲
by
kimixa
9mo ago
Add in presumably ignoring the license of the scraped documents.
111.
▲
by
kimixa
10mo ago
Zen1 was further behind in ST perf than Intel is today in it's desktop offerings. They really exploited their strength in MT and price, and showed that the market was already chafing under Intel's reluctance to go beyond 4 cores o
112.
▲
by
kimixa
10mo ago
I kinda agree. We've been told for years it's a "massive productivity multiplier", and not just an iterative improvement. So you expect to see the results of that. The AAA games being released faster, of higher quality,
113.
▲
by
kimixa
10mo ago
Not in RE, maybe, but directly viewing source isn't RE either.
114.
▲
by
kimixa
10mo ago
It seems they're pretty directly admitting to referring to the LGPL library while implementing theirs under a different license. I wonder if they'll have no issues with people directly reading their code while happening to imple
115.
▲
by
kimixa
10mo ago
You could argue that microcode emulation is what they do now.
116.
▲
by
kimixa
10mo ago
If you can realistically notice and reason out a bug within ~45 seconds of seeing the diff, then they are really shallow "dumb" bugs. The sort that even a junior would be expected to avoid. And I wonder how many other massive is
117.
▲
by
kimixa
10mo ago
It's very much nvidia specific, not just using CUDA but the backing nvidia-specific management libraries. Though I don't think there's anything particularly device-specific they're measuring, they're using the priva
118.
▲
by
kimixa
10mo ago
Arguably most MP3s are limited lower than 48k, depending on the implementation. Like LAME uses a low pass filter unless you explicitly disable it, even on the "insane" preset it cuts off about 20khz. But I can still understand why
119.
▲
by
kimixa
10mo ago
> MP3s don't (really) support higher than 48 kHz sample rates Neither does the human ear. While there may benefits for intermediate representations during mastering/modification, for playback higher frequencies can only ever ma
120.
▲
by
kimixa
10mo ago
"Can't complain"
More ›