66 karma · joined July 3, 2025
Even without wanting to attribute that to any malicious planned obsolescence, my impression is that the very small size of mini PCs makes it almost impossible for the manufacturer to ensure proper thermal management for keeping all components constantly at a temperature low enough for device longevity.
They cause each (remaining) shareholder's part of the profits to increase (relative and absolute), because there are fewer shareholders left. So it does very really increase the value of each share.
My guess is, they're gonna let Intel rot a little further while doing their best to pressure for Intel to split off their fab biz (as AMD had done back then), and then invest just in the fab.
but well, given that people understanding German are likely a minority here, I felt it was probably necessary to link to a version with subtitles so that it would be accessible to everyone here.
Anyways, here's the link to the vid without subtitles for those who understand German: https://www.youtube.com/watch?v=4lSBwF8ojVw
* For those who wouldn't know it: https://www.youtube.com/watch?v=TJYOkZz6Dck
I see what you did there ;)
Sent from my iMPC
The thing is: those "$100M+" of negative-margin ARR don't mean anything positive for Cursor, just like it didn't for Windsurf; quite to the contrary, it's just a measure of capital bleed with an unsustainable model in a negative margin death spiral: the more of that artificial ARR they make, the closer they get to bust.
For a description of the problem, see https://ethanding.substack.com/p/windsurf-gets-margin-called which was discussed here: https://news.ycombinator.com/item?id=44843801
…I struggle to comprehend how an odd quantization like 5 bit, that doesn't align well with 8 bit boundaries, would not slow things down for inference: given that on one hand the hardware doing the multiplications doesn't support vectors of 5 bit values but needs repacking to 8 bit before multiplication, and on the other hand the weights can't be bulk-repacked to 8 bit once and for all in advance (otherwise it wouldn't fit inside the RAM, besides in that case one would use a 8 bit quantization anyways)
it would require quite a lot of instructions per multiplication (way more than for 4 bit quantization where the alignment match simplifies things) to ad-hoc repack the 5 bit values to vectors of 8 bit. So i kinda wonder how much (percentage-wise) that would impact inference performance
> People grow them in very poor soil, and even in literal bags of compost
a bag of compost is pretty much the exact opposite of "very poor soil"; it's about the richest soil there is.
Consequently, pretty much all open source projects for cheapo china smartwatches apparently only support devices that are so old that you don't even find them anymore on aliexpress or other such shops.
I'd be interested to know for what currently easily available cheap (i.e. not in a much higher price category) china smart watches there is an open source alternative firmware that does not miss half of the features.
Too bad the hopes from the early Nokia adoption days got smashed by MS mole Elop and the later owners of Qt.
it's just the other way around: the pizzeria's duty is just to serve you a fresh pizza, but if you haven't finished eating it within 10 minutes, THEY can report YOU for violation and the pizza police comes for YOU. This ensures that customers don't hog the table (which is bad for business).
The fact that Intel managed to push their shitty market segmentation strategy of only even supporting ECC RAM on servers has rather nefarious and long-lasting consequences.
* https://en.wikipedia.org/wiki/Alternative_for_Germany
* https://en.wikipedia.org/wiki/Federal_Office_for_the_Protect...
It's interesting to see which prominent figures of tech and politics in the USA have publicly associated with the AfD.
be it things better done with a database, a word processor, a diagramming program, a label generator, a Form editor, a markup language, a web page, anything: they had all the tools at their disposal but no, no, they felt the odd compulsive need to do it with only Excel instead…
…often leading to problems down the line when the limitations of Excel for the use case (for which it wasn't made) would show more and more but they wasted already so much time and (needless) effort doing it in Excel that they would be even more reluctant to the possibility of switching to any more appropriate tool for the task.
That being said, I'd point out that the situation has been (and still is) unfortunately far from satisfying on the cross-platform and open-source side as well: GTK has also been a mess for quite long; Qt has - aside from the bloat - an increasingly repulsive licensing model for professional use (too bad the hopes from the early Nokia adoption days got smashed by MS mole Elop and the later owners of Qt), …
… and while there are some nice solutions for specific niches (e.g. Dear Imgui), the overall situation in general-purpose cross-platform native UI frameworks looks quite bleak and unsatisfying imho. There's a huge gaping opening for a permissive-licensed open-source cross-platform UI/Widgets framework that compiles to native, has a good set of widgets and gives access to Vulkan contexts for 3D rendering.
The thing is: that would require additional hardware though, whereas the relevant limiting criterion of the project presented in the article is obviously that it has to run with just the hardware provided by common mobile phones. Which is what makes the project interesting despite the comparatively lower precision.
That being said, while raw SVG suffers in that respect from the verbosity of the format (being XML-based and designed so as to be humanly readable and editable as text), it would be unfair to compare, for the purpose of HTTP transmission, the size of the raster format image (heavily compressed) with the size of the SVG file (uncompressed) as one would if it were for desktop use. SVG tends to lend itself very well to compressed transmission, even with high-performance compression algorithms like brotli (which is supported by all relevant browsers and lots of HTTP servers), and you can use pre-compressed files (e.g. for nginx with the module ngx_brotli) so that the server doesn't have to handle compression ad hoc.