rldjbpin
Joined 4 years ago
Joined 4 years ago
i'd understand using micro-usb on a $5 sbc, but now with themselves charging for accessories, especially on the rpi 5 with the $15 power supply, something's gotta give.
i appreciate the challenges with properly supporting a standard at a reasonable component cost. but in a sea of poorly designed usb-c, doing micro-usb otg for the new zero would be outright ridiculous if they go ahead with it.
the video out has similar grievances where a cheap usb-c dongle is better than adapting hdmi in niche, fragile ways. i hope the model a still allows using the bandwidth provided by the soc to still add ethernet and regular connectivity for those who would rather implement it themselves.
whether the focus is at commercial partners or still the foundation's core audience, i hope they stop nickel and diming on the simpler components going forward. tough times to make hardware as usual but i hope they keep on trucking with the releases.
for me just having a brushless motor and a remote was good enough lol. maybe smart home functionality nowadays perhaps.
also, all of this seems like crying wolf as usual, which won't help for when we finally get there. lowkey, following this noise is getting as horrible as getting all your news from linkedin posts.
meanwhile the downgrade to the 200 plan, while not as outrageous as github copilot, is just not good pr fwiw. the base number, i.e. what plus users get, is arbitrary as it is, so there was no need to break the appearance of "20x". using the efficiency excuse is not helping here lol. same as further segmentation of pro plans with ultrafast mode.
plug-in hybrid don't make sense to me based on the op's experience, but the regular hybrids (where you don't charge the battery) makes perfect sense today, more than ever arguably. same tech as f1 cars fwiw (not that this season they are being very favoured)
while not my cup of tea and not going to rewatch it, i see a repeat of a lot of the ways people react to "world-changing" topics.
or in other words, a lot of hand-waving since past few years is only going to be crying wolf when maybe we ever get there. perhaps before nuclear fusion or gta 6!
for all the promise, i would temper my expectations for a frontier model for coding or general purpose. but for niche use cases (document parsing, voice*, etc.) and as a platform to handle finetuned versions, etc. for small-ish pilots, i can see the value of partnering with them.
if the core model could be any open-weights solution out there, the moat dissolves really quickly.
Sadly, things are not quite as straightforward for non-Studio. For one, you need to be a paying customer to get access to the new feature. Moreover, a community-based solution [1], which previously worked for all users, have now artificial limitation in implementing automation for Free users.
Quite a shame really but maybe it will trickle down over time (like expanding export resolution support). Regardless, a much more open implementation than Adobe, who'd like you to pay for yet another chat window.
[1] https://github.com/samuelgursky/davinci-resolve-mcp#free-edi...
i wonder when the migration was started and whether it made sense to not migrate it to another framework instead.
clearly it will be a while before it would be a standard across the lineup (air is still fanless, perhaps to a fault), so allow someone to continue the old way without needing additional complexities with a touchscreen. perhaps allow to save by downgrading to a non-touch one?
regardless, oled panels tend to be a mixed bag in terms of text rendering. i wonder if they did a good job with theirs. having adaptive refresh would definitely help those on dark mode in terminal to eek out even more life out of their laptop.