Fork Android. Isn't that the only long-term way forward? Create a coalition with e/OS and LineageOS. Better start building something lasting now than waiting.
Even if this battle is won by law, they're going to continue to make maintaining spinoffs increasingly difficult. Pressure law makers to make sure not only duopoly apps are supported for e-governance software. Banking should follow.
In Google's eyes, open source was good for Android adoption. Now it's a nuisance at best.
Unless you can commit to fully support the full independently of Google, for ever, I am not sure just forking Android is a good idea.
The main point of Android right now are the apps that exist for it, the rest of it (graphics system, driver architecture, even system updates) is mediocre to shit level.
I think a much better option is to take mobile or even desktop Linux distro and make sure it has robust upstream support for the mobile hardware you care of. At the same time, work on Android emulation layer like Waydroid, to work as good as possible.
This way you have a long term sustainable hardware support model (sharing the effort with all other Linux distro communities) while still supporting the Android apps people care about.
This has been successfully by Valve for Windows games and apps on top of a regular Linux distro. And Jolla does the same for Android apps on Linux devices.
I wouldn't say "nuked" is the right word in this case. Considering how /e/OS's founder has attacked GrapheneOS, we wouldn't want to work with him, would we?
I'm not sure why you'd think we have issues with LineageOS.
I dont think theres ill will between LineageOS and GrapheneOS. They are just focusing on different areas (strict security guarantees vs wide device compatibility).
eOS markets itself as secure while being insecure and their CEO personally attacks GrapheneOS and GOS users (he said that only pedos and spies need good security) regularly. They also dont contribute back to generic AOSP development while GOS and LOS do.
Yeah, wow. I hadn’t realised that the prices had gone up that much on hard disks as well. A pair of Synology 4TBs I bought for 2500SEK 18 months ago are now 3400SEK each from the same vendor.
There are still okay deals to be made in the used market. I can find slightly used 4TB drives for about 80 euros a piece, or 8TB for 120. Obviously no warranty, but if the drive has lasted a year or two, there's a good chance it will last many years more.
Worse than that, sellers on Amazon all seem to be scams now[1], and my trusted local supplier (who has genuine parts) is only selling one hard disk per customer. Good luck populating a NAS.
I have 6x unused 6TB SAS drives I bought for $50 each in 2024. I assume they are $150 each now. I can't afford cold storage right now so I rely on raidz2 and can replace drives as they die.. But they have 2 years and no SMART errors.
> replaces JPEGs on the front-end of WordPress for browsers that support them.
Ouch. Pretty much every browser supports AVIF now which means everyone gets transcoded images worse than JPEGs one uploaded. For JPEG XL that process is lossless...
Note that the ability to repack a JPEG as-is in a JPEG-XL container gives you a 20% filesize reduction due to the more efficient container, but none of the encoding advancements of JPEG-XL.
Recompressing is not great, but many people might be happy with a file that is less than half the size even if they lost a bit of fidelity. Not everyone has original source material to work with after all.
It's broken in the exact same way in the last version of Vivaldi that works on Windows <10.
From a quick look at the second horizontal strip that starts "what is this?", and without wasting time doing too much digging, it appears to be ultimately caused by using a grid layout for a heading followed by a few paragraphs, all of which fill the available (constrained) width, which amounts to one of the absolute simplest layouts possible in CSS - block. Last time I saw something similar, albeit with flexbox not grid, it was from a junior developer who appeared to have only learned flexbox and nothing else.
As a quick semi-fix, just disabling grid-template-columns on .base-layout is enough to fix almost everything except the constrained width.
Sounds like that older Vivaldi version does not support CSS nesting. I looked into it. I'm assuming you are using Vivaldi 5.6 which uses Chromium 108, native CSS nesting became supported in Chromium 112.
It uses CSS Grid to create a centered, width-constrained content area while allowing individual elements to break out of it or span the full viewport width. This provides a flexible, consistent layout without the need for additional wrapper elements in the HTML.
CSS nesting has had full browser support for more than 3 years now, I recommend updating. I'll also add fallback for older browsers, but the Grid layout itself isn't the issue.
Yes, that's right. I thought I'd try it in that older browser that I still happen to have installed, as the user above didn't immediately let us know what that mobile browser was. It may or may not help by at least giving you a browser version you can use to test. As I mentioned somewhere else, it makes sense to use some sort of older browser as a proxy for older browsers in general, when testing.
Developers are always looking for new ways to do what we've always done, often using more technically complicated ways to recreate the simplest things. It's fun from the puzzle-solving point of view, but your choice of earliest browsers you want to support depends on your user base.
I built https://purecss.com (not pure-css.github.io), maybe you'd find the site helpful? Currently it's 77 CSS patterns and another ~20 coming in the next few weeks. Each have a demo and the code underneath. Check it out and let me know if there's something you can think of that you'd like to see there. Happy CSS'ing!
Yea, exactly and thanks! I love making CSS things that were previously only possible with JavaScript. Carouses, accordions, toggle switches, etc. I love how powerful CSS has become over the last few years!
Yes it is a pain. But the whole thing is like two pages, so I^H my LLM just reads it. I used to read it. It was ok readable (and I'm not very good at CSS).
Considering the insane memory price surge it's going to take years (or an eternity) before most people will consider upspecing their machines to run local over paying $20 per month to have the honor to loan a slice of Altman's hardware.
The only hope we have is the AI bubble bursting, but that will undoubtedly come with its own set of macroeconomic surprises.
The ~$1T/y AI capex isn't remotely sustainable. Memory fab capacity will go up, AI datacenter provisioning will go down, prices will become reasonable.
What is it with fabs where there is just no competition springing up outside the existing memory cartels? Is the knowledge of how to build and run a fab strictly controlled by these companies? Is all qualified talent just immediately poached and put behind NDA and noncompetes? It just makes no sense. Capitalism would suggest these conditions with so much unstable equilibrium in this market would see increase in supply to take advantage of the pricing. The fact that this isn't playing out as such suggests there are some very powerful thumbs on the scale of this "free" market.
It takes about a decade to bring one up and during EVERY wave of a booming memory demand supply crunch there has been a subsequent round of major bankruptcies from suppliers who decided to scale and had no demand when they finally got online.
Supply is not elastic and responds very much slower than demand. There's no conspiracy or corruption needed for this result.
The conspiracy is real, it's even been proven in court, but as things stand, it's also necessary because of the factors you describe. Investors will not touch the DRAM market with a 10-foot pole, so it has had to rely on self-funding. While there have been state subsidies too, price fixing has proven to be the most effective way to survive the extreme volatility and fund the massive capex necessary for each generational leap. They have gotten a bit more sophisticated about it since the court case 20 years ago, but as far as I can tell, it's basically the same as it's ever been. The lack of effective competition is a function of the market itself, not any tilted scales. If anything, tilting the scales on purpose with greater state involvement is the only way to change the dynamics, but few states have the capacity and competence to carry that out effectively.
Micron's stock price did go way up, after they stopped selling DRAM to the consumer market. It has been flat for several months though.
For comparison, SK Hynix stock is flat YoY and Samsung's stock did go up this year, but has come back down a bit (they're also much more diversified). Those are the only other companies outside of China that actually make DRAM at scale. There's also CXMT, which is making inroads, but its stock is not traded on any open markets, and the company is heavily backed by the Chinese government.
I'd say I'm rather well-versed in this topic but I have a really hard time following what you're saying. Could you attempt rephrasing?
MFT is a sensor size and lens mount, not a raw file format. Panasonic and Olympus (among others) have made cameras using this standard, but use different raw file formats.
Even if this battle is won by law, they're going to continue to make maintaining spinoffs increasingly difficult. Pressure law makers to make sure not only duopoly apps are supported for e-governance software. Banking should follow.
In Google's eyes, open source was good for Android adoption. Now it's a nuisance at best.
reply