Because monitors aren't simple. There are dozens of axes along which they can be scaled.
They have resolution (1080p FHD, 1440p QHD, 4K, 5K, 6K, 8K), aspect ratio (16:9, 8:5, 4:3, 3:2, 21:9, 32:9), refresh rate (60 Hz, 75 Hz, 120 Hz, 144 Hz, 165 Hz, 240 Hz, 360 Hz, 480 Hz, 1 kHz, and of course adaptive refresh rate tech including G-Sync), colour quality (depth and accuracy), contrast ratios for HDR, panel technology (LCD-TN, LCD-IPS, LCD-VA, OLED, QD-OLED, WOLED, and now RGB stripe OLED), backlight technology (CCFL, edge-lit LED, miniLED, microLED), connectivity (HDMI/DP, USB-B, USB-C, DP alt mode, Thunderbolt, 3.5 mm, and KVMs).
It's very hard to stuff all this information in one neat model number.
On the consumer's part it makes sense to understand these features and what is necessary for one's use case, filter monitors by said features, and note down the model numbers that satisfy the requirements.
Simplifying their offerings for the sake of the model number doesn't make any sense. Simplifying their offerings for other reasons might make sense, but the companies themselves would be the best judge of whether or not it makes sense for them.
I feel like they do it deliberately, so that you can’t easily research their products and find if they are out of date. They can sell you a monitor from 2012 as if it’s brand new, because you have no idea what it is.
>Most avg consumers don't even know what Claude is[..]
Vibe coding is very early and pretty expensive, but computers and the internet are always in an exponential curve, a curve much steeper than the rest of the economy. Give it 3 years, and you will be amazed.
Not everyone will be vibe coding. In every social circle of 10 people, 1 person will be good at that, and will develop programs for his/her friends.
>Most vibed apps suck in unpredictable ways.
Yes of course, it would be infinitely preferable for normal people to learn proper computer science, algorithms etc. We agree on that.
* They haven’t said the source isn’t available to them, just that the closed nature of the ANE means they can’t use it in OSS.
* They’ve repeated constantly that it can’t do backprop and isn’t useful for most MLX use cases.
And really, ANE isn’t even that interesting for MLX really; it’s a limited resource power efficient inference engine for smallish edge models. If you want to use it you can use the Apple APIs, which while limited are generally “shaped” like what you’d want to do anyway. Almost every “biggish” CPU has one of these now and Apple don’t want to give away the specifics of theirs (even though it’s been pretty thoroughly RE’d by real REs and re-summarized by Claude, like this article).
I'm not op but I don't think op meant to shame, I understand the construction "tell me you're... without telling me" as a way to highlight that something is unexpected to people who haven't done something, that is that something is particularly unintuitive without some special experience.
> It's insane that the source code of ANE is not available even to the MLX team
no it's not insane - it's completely mundane policy. that's my point - that you're calling something out as insane with exactly zero experience (which is the actually insane thing...).
on that line of argument, nobody would have ever called out the emperor for not wearing any clothes, civilians would not go to peace protests, and nobody would ever improve things by looking at something from another angle.
This is a completely asinine take - you're not observing the emperor with no clothes here - you're completely outside the kingdom hypothesizing that the emperor has no clothes. To wit: you don't actually know the the ANE "source" isn't available to MLX. Hint: it probably is but there's just red tape involved.
actually, it really is not neccesarily a 'hardware company' thing. ive been in 'hardware companies' where the rtl was just as available for viewing as the rest of the firmware/software.
in big hardware companies, things start getting siloed, but that probably has more to do with big companies (seemingly invariably) operating as a union of fiefdoms (dunbar-number-ification?)
> The biggest downside of Racket is that you can't build up your environment incrementally the way you can with Common Lisp/Sly. When you change anything in your source you reload REPL state from scratch.
I think no Lisp is a "true" Lisp if it doesn't provide two critical components of the Lisp experience:
- Live Images
- REPL-driven development
That's why Clojure/Racket and even Scheme are Lisp-y but not a true Lisp. The only true Lisp languages I've found are CL and Janet.
Is this not ultimately a late-binding issue? Maybe I'm missing something, but I've absolutely been able to incrementally build up an environment without resetting using nrepl and Clojure
Once again, it's a tech that Google created but never turned into a product. AFAIK in their demo last year, Google showed a special version of Gemini that used diffusion. They were so excited about it (on the stage) and I thought that's what they'd use in Google search and Gmail.
I don't think that's what this issue is talking about. I have the Max $200/mo plan and have noticed starting yesterday that my quota drains much much faster, to the point I'm about to use the $50 credit Anthropic gave away to everyone.
reply