emn13

5 ms·

1.
by emn13 4mo ago
Note that the uploader apparently still retains control over labeling in most cases; uploaders that intentionally misrepresent AI-generated content might not be discouraged by this. Whether youtube will (and can) ban accounts that do that m
2.
The Impossible Prompt(teodordyakov.github.io)
3 points by emn13 10mo ago|1 comments
3.
by emn13 10mo ago
Create an image that displays two seven-pointed stars, two eight-pointed stars, and two nine-pointed stars. All stars are connected to each other, except for the ones with the same number of strands. The lines connecting the stars must NOT
4.
by emn13 11mo ago
I think it's not at all a marshmellow test; quite the opposite - docs used to be written way, way in advance of their consumption. The problem that implies is twofold. Firstly, and less significantly, it's just not a great retu
5.
by emn13 11mo ago
Yep. Still, I think it's a pretty decent benchmark in the sense that it's fairly short, quite repeatable, does have a quite a few subtest, and it's horribly different from the nebulous concept that is "typical workloads
6.
by emn13 11mo ago
It's not trash - it's quite nice for its niche. It's just not very scalable with cores, so it's best interpreted as a benchmark of lightly threaded workloads - like lots of typical consumer workloads are (gaming, web br
7.
by emn13 11mo ago
I mean, reliably tracking ownership and therefore knowing that e.g. an aliased write must complete before a read is surely helpful? It won't prevent all races, but it might help avoid mistakes in a few of em. And concurrency is such a
8.
by emn13 1y ago
There's also the alternative of announcing this breakage publicly to electron beforehand; and the alternative of having a hack and publicly announcing it will be removed in a year. There's even the alternative of just announcing t
9.
by emn13 1y ago
Put it this way: if I were in charge of a major OS, and I having one of the major app frameworks used on my OS tested on for my annual upgrade, I'd feel pretty embarrassed, even if there's a figleaf excuse why it's not my fau
10.
by emn13 1y ago
Hyper amusing, thanks for sharing! Doesn't really improve the analogy, but fun quirk of history :-D.
11.
by emn13 1y ago
So on the one hand we have a product which isn't even remotely designed for the use case (hamsters), and during normal use shows obvious behaviour (cooking) that should imply risk to said hamsters. On the other side, we have a product
12.
by emn13 1y ago
The author's examples of rough edges are however no better when hosted on vercel. The architecture seems... overly clever, leading to all kinds of issues. I'm sure commercial incentives would lead issues that affect paying (hosted
13.
by emn13 1y ago
If you care about absolute accuracy, I'm skeptical you want floats at all. I'm sure it depends on the use case. Whether it's the standards fault or the languages fault for following the standard in terms of preventing auto-ve
14.
by emn13 1y ago
I get the feeling that the real problem here are the IEEE specs themselves. They include a huge bunch of restrictions that each individually aren't relevant to something like 99.9% of floating point code, and probably even in aggregat
15.
by emn13 1y ago
Yeah, before required properties/fields, C#'s nullability story was quite weak, it's a pretty critical part of making the annotations cover enough of a codebase to really matter. (technically constructors could have done what
16.
by emn13 1y ago
I love building libraries, so having the chance to talk about the gotchas with things like this is a fun chance to reflect on what is and is not possible with the tools we have. I guess my favorite "feature" in C# is how willing t
17.
by emn13 1y ago
"Recovered" sounds so binary. I think it's pretty usuable now, but there is scarring. The solution would have been much nicer had it been around from day one; especially surrounding generics and constraints. It's not _en
18.
by emn13 1y ago
While I'm most familiar with C#, and haven't used Ruby professionally for almost a decade now, I think we'd be better off looking at typescript, for at least 3 reasons, probably more. 1. Flowsensitivity: It's a sure thin
19.
by emn13 1y ago
Of course they had a choice: they could have stuck with google maps for longer, and they probably also could have invested more in data and UI beforehand. They could have launched a submarine non-apple-branded product to test the waters. T
20.
by emn13 1y ago
While some of what you say is an interesting thought experiment, I think the second half of this argument has, as you'd put it, a low symbolic coherence and low plausibility. Recognizing the relevance of coherence and plausibility does
21.
by emn13 1y ago
Perhaps the solutions(s) needs to be less focusing on output quality, and more on having a solid process for dealing with errors. Think undo, containers, git, CRDTs or whatever rather than zero tolerance for errors. That probably also mean
22.
by emn13 1y ago
Is the advantage over an enum not kind of small? We're seeing bugs here because people tried to do the right thing but the tooling has absolutely no way of helping anybody to do that. Simply preventing accidental mistakes would preven
23.
by emn13 2y ago
While a humorous response by Milton and an interesting debating point, the argument he makes is pretty weak because it almost inevitably reduces to complete lawlessness, doesn't really define which government "granted" monopo
24.
by emn13 2y ago
I'm curious what you base that on. For instance, we've never really allowed literally cutthoat competition, nor things like fraud and we've generally not allowed misrepresentation. Governments intervene heavily and always h
25.
by emn13 2y ago
One race-to-the-bottom phenomenon that (to me at least) appears to aggravate the impact of "corporate greed" is the social loop that goes as follows: 1. company decides to push the boundaries of the socially acceptable when it c
26.
by emn13 2y ago
Outright monopolistic pricing is also "the market rate". Frankly, virtually any price somebody is willing to pay is almost by definition "the market rate". It's a meaningless defense for an artificially high price.
27.
by emn13 2y ago
Certainly helped!
28.
by emn13 2y ago
The article lists 2: firstly, simply that ML models are now feasible at a scale they weren't only a few years ago. Secondly, compute power is now better enough that it can now simulate more realistic environments which enables sim-bas
29.
by emn13 2y ago
Presumably the author really is missing a driver; I doubt he'd have missed being able to install without it. If he really does need such a driver; then the exact name of it or the details of Dell's BIOS options and whether they h
30.
by emn13 2y ago
If you're literally using it just once, why not stick it in a local variable instead? You're still getting the advantage of naming the concept that it represents, without eroding code locality. However, the example is a slightly

More ›