i use markdown because it's inherently limited to styling that is easy to represent. it's a good way to communicate the limitations of text-based content submission form.
if you tell somebody they can use HTML, they get frustrated when you tell them that tags other than anchor, bold, italic, list, heading, and paragraph aren't supported. but if you tell somebody they can use markdown, then they implicitly understand that the content they're submitting won't be rendered as green text on a purple background, and don't try to accomplish that.
Seems unlikely, migrating away from an entrenched codec like H264 isn't like a routine software update. It has widespread hardware support, and there's an enormous body of H264 video out there.
As fhn points out, there are now truly open video codecs available (open specification, royalty free, unencumbered by patent terms) that are able to compete with the patent-encumbered ones on technical merit. Seems curious that the patent-holders would want to hike prices in this way and validate the motivation behind the truly open codecs.
Also, the article mentions the licensing fees for H265 were also increased recently. It doesn't seem to give a figure, a quick web search turns up 25% [0] or perhaps 20% [1]. Perhaps I'm missing something obvious but I'm not clear on how the change in price relates to the patent dispute between Nokia and certain laptop manufacturers.
(It seems the H264 fee increase affects streaming providers only, whereas the H265 fee increase did not, as it affected laptop manufacturers.)
I waited until off peak hours to use Opus 4.6 to do some research. One prompt consumed 100% of my 5h limit and 15% of my weekly usage. Even off peak it's still insane. Opus didn't even manage to finish what it was doing.
>There aren't futures markets in RAM as far I know
sure there is. not formally, but if you hold a contract for x units of future production, you can sell that contract to somebody else who wants those units more than you do.
where do I find the paid option? I can not find that on their product page.
There are only two options I can see; one "Available at no charge" and another one "Coming soon - For organizations"
Can you upgrade in the IDE? It would be strange that Google has a performance problem for paid users while I do not experience any such issues at all with Claude and Codex.
ever worked in IT support? letting people customize their environment both increases the amount of support that users require, and increases the difficulty of providing that support.
a laptop in a stock configuration can be swapped out for a new one when it breaks. a laptop that has three years of accumulated customizations installed on it means that the employee wants their laptop back when it breaks, and they want it fixed ASAP.
when you're supporting a user who doesn't know how to type a URL into their web browser, it's a whole lot easier if you don't have to start that call with asking what web browser they're using.
It mattered in the sense that it provided valuable grist for the mill as they attempted to figure out if it could work as a Reels/TikTok alternative for companies to eventually deluge with ads.
But why not Bluetooth or NFC? I can’t imagine any way those could be annoyances, or even why websites would want them outside of some extremely specialized applications.
I'm personally a WebUSB, WebBT etc hater but I totally get why PWA developers want those features. For example, let's say you're manufacturing some sort of USB device and you need a way to flash drivers. The idea of being able to just make a webpage that can update your drivers is so appealing compared to having to ship apps on Windows, Mac, Linux, iOS and Android.
Similarly, if my bank website could do NFC tap-to-pay securely, that would be pretty cool. I can imagine lots of interesting opt-in uses for NFC in a webapp.
Arguments that these features are held back by Apple specifically in order to keep apps on the app store where they can control things and take 30% at least hold water, I think, even if that reasoning doesn't apply to Mozilla rejecting features.
> The idea of being able to just make a webpage that can update your drivers is so appealing compared to having to ship apps on Windows, Mac, Linux, iOS and Android.
I suspect like many here, at $work we use a shit-ton of Flexoptix SFPs.
Flexoptix are not a $megacorp, they are a (very) small German company.
They manage to ship cross-platform apps to flash the SFPs. So its really not that difficult.
I would think a web app would be more of a pain the the butt to maintain because you have to deal with CSS reactive UI etc.
For little utility apps where you don’t care to deviate from UI default appearance and behavior (and, as a user, it’s much better if you don’t anyway, though it’s very trendy to make UX worse by customizing everything) iOS and Android both are dead simple, very easy to write and maintain a utility app for either of them.
An enormous amount of the cost of developing a lot of native apps is customizing the appearance and behavior, to match some slide deck mockup or to make it “on-brand” or whatever. It’s better for the user, and way cheaper, if you just… don’t do that. Hell a lot of common UI elements are easier in native than web if you just don’t try to customize them a ton (data-backed tables and list views and such are sooooo nice)
I like WebUSB in Chrome to update my Meshtastic radios. I also like that I have to go out of my way to launch Chrome for that, and other websites can’t request permission to access local hardware in my normal browser.
Nonsense. Firefox on Android (and I'm sure everywhere else) allows endless redirects without prompting me about the redirect, sending me to sites I never wanted to go to.
And even then, where does one draw the line on "privacy"? Especially given that every other app on the user's phone is granted every permission under the sun and feeding on as much data as possible.
The core of the problem isn't supporting web bluetooth etc or not...the core of the problem is that dumbass humans will go "yes use all the permissions" because their hands are already shaking from tiktok withdrawal.
if you tell somebody they can use HTML, they get frustrated when you tell them that tags other than anchor, bold, italic, list, heading, and paragraph aren't supported. but if you tell somebody they can use markdown, then they implicitly understand that the content they're submitting won't be rendered as green text on a purple background, and don't try to accomplish that.
reply