200$ ThinkPad...? The current best sellers on Amazon US are two 180$ brand new laptops.
Intel Celeron N4020, 4Gb ram, 64 GB storage, 1366x768.
This is what the average computer user is using to try to run your apps and websites. And remember - a cheap laptop bought today is going to be in use for at least five years.
The only things I recognize on that are the CPU brand name (there have been times the Celeron has been good bang for the buck), the RAM, and the storage (I guess and the resolution).
To me, all of those seem woefully underpowered, but $180 is $180...
> Is there some sort of tool that can be expressed as an MCP and but not as an API or CLI command?
... most standard desktop software? How do you interact with Blender, Unity3D, Ableton Live, Photoshop, DaVinci Resolve, ... when they don't provide any API or programmatic CLI and don't want to open random network ports but will be absolutely fine with opening a tightly controlled local channel through a fd / pipe like MCP uses ?
Heh, nodejs uses V8 which shares legacy with WebKit's JavaScript core, itself being forked from KDE's KJS. Fun to think that eventually, some KDE code spiritually made its way to the windows start menu
Similarly, I've been doing It development for pretty much the entirety of my career. When I see the struggles to make remotely useable apps in other frameworks I'm very happy I chose this path
For me, native means "I can integrate a platform widget in the middle of it". For instance, with Qt, GTK or wxwidgets it's entirely possible to integrate a Win32 / Cocoa / X11 component right in the middle of your app (and it's super important for instance for things such as integrating audio plugins, where the plugin only gives you a HWND or NSView and you have to draw your application Chrome around it, have it follow resizes, etc.)
It's pretty much impossible to embed properly without edge cases in GPU-based renderers as far as I know, if you want layering of widgets (for instance a platform widget in-between two flutter widgets in z-order)
I'd expect a cause is that most camera makers are Japanese, and it's not uncommon in Japan to uppercase words written in Latin alphabet for aesthetic reasons
Perhaps the combination of that and the old .raw filename extensions on old filesystem implementations where everything appears uppercase (since camera firmware is slower to catch up, this persisted for years even though contemporary OS already had no such limitation) made it stick.
so basically this thread confirms that we're all getting worse color that we can actually see because I guess of some terrible lab measurement that got carried over like gospel? (0.0021 here, on a semi-cheap acer IPS screen)
> At its core this formula gives you a single number: how far apart two colours look. 0.0 means identical, 100.0 means you're comparing black and white. The magic number to remember is the "Just Noticeable Difference" (JND). For dE00, JND is around 2.0. Below that, people struggle to tell two colours apart. Below 1.0, basically no one can. So anything under 2.0 is "close enough" and anything under 1.0 is "you're kidding yourself."
OpenBSD is g̶e̶t̶t̶i̶n̶g̶ ̶a̶l̶o̶n̶g̶ ̶f̶i̶n̶e̶ ̶w̶i̶t̶h̶o̶u̶t̶ ̶c̶o̶m̶p̶a̶n̶i̶e̶s̶ ̶l̶i̶k̶e̶ ̶N̶v̶i̶d̶i̶a̶ unuseable for any professional video-related work
This is what the average computer user is using to try to run your apps and websites. And remember - a cheap laptop bought today is going to be in use for at least five years.
reply