1. I have a Voodoo 2 paired with an S3 Virge/DX, the Voodoo 2 output level is lower. On a CRT I always have to make the image brighter when running a 3DFX game. Additionally, the V-Sync pulse is not the same as the Virge/DX and the Voodoo 2 image is shifted up.
2. I have a Voodoo Rush which is the maligned hybrid model of 2D and 3D chipsets on a single card. It still uses the internal switching though. On this card the voltage issues are the opposite, the 2D output is significantly dimmer than the 3D which makes the 3D game clip badly when running something until the image is adjusted again.
These problems are voltage level issues with the signal, not gamma. Adjusting gamma will not change the black or white voltage level of the signal. But a lower voltage signal may seem brighter as gamma is raised and the dynamic range is compressed.
> we were so enthralled by the absolute performance of 3DFX that the color fidelity didn’t get as much attention as it should have.
I would say it's more likely that they just didn't notice and the varying outputs from different 3DFX cards, with different GENDAC's, on differently calibrated CRTs just made it a total mess to try and and dial in something as imperceptible as a gamma level. Also keep in mind that around 1995-1996 adjusting the brightness of a CRT was as easy as twisting a few knobs on the front of it.
Edit: see comments re founders
But there is one place where sRGB is truly linear, and that is signal voltage for a CRT display. 50% of sRGB truly means 50% of signal voltage (between the minimum and maximum voltages).
No, they’re not. They find it really annoying that apps ask them for overbroad permissions
This is the unsolved problem. Neither the platforms nor app developers are aligned on solving it between themselves, much less aligned with user interests. My pet peeves:
- Apps requesting way broader or more general access for reasons that are unexplained, whether due to innocent oversight or actual malice.
- Platforms aggressively segregating access into broad categories (to reduce user fatigue), which compounds the problem of broad requests, and then preventing users from being able to override those.
- Platform giving special bypasses to their "valued partners", and refusing to inform the users or give means to disable this access (or grant to apps of their choice).
Now wrt. platforms, I get the arguments and I'm sympathetic, even though most of them don't apply to majority of customers. The end result is still the same: users don't get to offer informed consent, and have little to no control where it actually matters.
MacOS is also used by power users, though. The kind of people who were drawn to it being a user-friendly UNIX and then stayed. I think it's reasonable for them to ask for a more granular permission system that actually supports their usecases.
Could you report this: https://github.com/ankitects/anki
----
For historical reasons, the Android app requests "All files access", if not using the Play Store variant. I'm working to fix this.
We don't need it. The replacement API is 300x slower on some phones[1] and is infeasible to use.[0] It should be possible to use AnkiDroid in a "public" folder, but it no longer needs to be the norm. Times have changed
[0] https://news.ycombinator.com/item?id=43987745
[1] just tested: 966ms for a file delete on my Pixel 9 Pro vs 3ms
However users are very happy with it.
> developers will continue to feel like they need to request these expansive permissions
And users will continue to seek alternatives, or risk denying said permission.
I don't use any apps that require this permission, and would never use any app that required this permission without an extremely good explanation of why it was needed.
Until that happens, no.
> Allow the developer to specify the common location(s) that they need access to.
Why not just back up: How does the developer know the location. What's common about it?
I'm so not sure they need access to anything yet.
I use Spotify, Slack, Zoom, and WhatsApp: All of them have asked for it, but they all seem to work fine if I deny them access to full-disk access. So I am confident your issue is a non-issue for me and millions of people like me.
I don't have any apps that need this, so I do not want you to blow past this so quickly with the prior that just because you are a developer who has a use case that requires this, it is still my computer and you don't get any time on it while you're asking for this.
> Readonly access. Allow an app to read your files but prevent writes or deletes
Again: Absolutely not. There are no files I want your app to have access to without an explanation.
> Allow for negative access (i.e. allow labels or tags on directories to mark them as sensitive and prevent access by default - browsers could do this for their cookie stores, `~/.ssh` could ship with it as a default, etc.)
I know Linux works this way, and it only ever works for stuff that the integrator ships (i.e. on Red Hat, they are called seLinux labels), so it's not something that independent publishers have ever done, and to my knowledge, despite it being so easy, not one independent developer has ever used them in the way you say, despite such a thing being possible for more than 25 years.
> Apple needs to learn to talk to (and listen to) developers.
That sounds like your opinion. I think developers need to explain better what they actually want and why.
You have what you ask for on other platforms, so I think if your ideas were so right you would have simply ignored Apple, so I think Apple doesn't need to do shit for you, and you have some explaining to do.
It's also critical to recognise that data exfiltration is just as serious a risk as data manipulation. Read-only access doesn't prevent data theft, and time-limited access can't undo it.
- Allow the developer to specify the common location(s) that they need access to. Rather than having to have the user select the folder they want to grant access to, have the developer say "this app uses data in these 5 folders, do you want to grant that access" - so much clearer, and useful in cases where an app has to integrate with other apps through the filesystem. - Readonly access. Allow an app to read your files but prevent writes or deletes. - Time limited access. Allow some kind of access and allow the user to auto-expire it rather than having to remember it exists. - Allow for negative access (i.e. allow labels or tags on directories to mark them as sensitive and prevent access by default - browsers could do this for their cookie stores, `~/.ssh` could ship with it as a default, etc.)
Apple could have used this opportunity to think through the question of "why do developers ask for filesystem access, and how can we allow legitimate usage through well scoped access controls", but instead they built a bad API that will (I would guess) not actually allow developers to be more judicious or achieve any of the user-safety benefits.
Apple needs to learn to talk to (and listen to) developers.
I counted 44* applications on my mac that ask for FDA. I've only granted it to 8. The other apps work just fine without it. (Some apps that ask for full disk access: Anki, a flashcard app and Soulver, a calculator app – cmon now)
This change is less about bureaucracy and more requiring developers to be more clear why it needs the permissions it does.
*edit: originally said 56
Even one of these accounts being compromised would be a massive security incident that would potentially put millions of people's data at risk.
It doesn't cost them anything but a "whoops" post when they fuck up, so the incentive is misaligned (as you noted under repercussions).
The cost is externalised onto everyone else not them so it's not going to change.
In this case optimizely should have had better systems to spot a release like this (internal cool downs, check and balances, phased rolouts, automatic security checks). And sites that have massive user bases (cnn, bbc, etc..) have zero excuse to not have the same.
I would go so far as to say those sites should not be serving from vendors but should be vendoring their own scripts that they also are passing through security audits and serving them selves with cool downs.
How do these companies not have better dedication to protecting their users is beyond me.
I hope folks are re-evaluating that now.
> Your origin can be clean while your visitors are robbed — the compromise sits in the tag layer.
They were able to join a handful of retailer affiliate programs and were probably clearing tens of millions a year in affiliate commissions with no overhead. Then they sold it to WhaleShark Media (funded by Google Ventures among others) and IPO’d it in 2016, cashing in a second time.
Honestly one of the most impressive bootstrap stories you’ll ever find.
> The first letter of every four-letter group exactly matches Python’s random.Random(2026).choice(string.ascii_uppercase) repeated 125 times
import random, string; rng = random.Random(2026); print("".join(rng.choice(string.ascii_uppercase) for _ in range(125)))
1. Search for "temporary email", there are zillions of these. Some services detect that they are special temporary emails, many don't. They have tons of domains, always creating new ones, then you can get a random email on that domain. Many of them even let you log back in later if you save off the password.
2. Use duck duck go - Lots of folks must be using ddg to create a new email that hides their underlying email, even my non technical spouse uses it. Most sites accept this today, even reddit.
3. catch all domains. If you have your own domain, you can set it up so <anything>@your_domain.com will go to you. With the latest "advance" from the modern world's anonymization destroying stuff, you have to figure out how to setup dkim and dmarc etc.
I think we'll all be polluting our account/pw software with thousands of these. A huge hunk of junk.
Yeah, if he wants to? If he finds value in that? Why wouldn't he?
It's his voluntary, willful choice. Seems like he was fine doing it for decades.
And sounds like after 20+ years, the site's usefulness had come to an end, and maybe the time investment wasn't worth it either. This did happen within a shadow of that big php vuln.
There's more to life and building things than monetary success. If you struggle with this concept, I suppose there's not much more of a conversation to be had here.
DXXR KAKD QMDZ QJPV UQSG DWRM HXCO TGVL TLWE RHIP
NJPA ZKNZ SCVP RJWD XRFT YRMH YUJI PEBD YOOS YNVE
SLGB OEJM HYIV AMMW TMWE CYFI DLGD JWBT DWCJ OAWA
AUZO VKCK PZXN VNJA KXCH GCHT MEZS IERW LCMH LZQE
ZSNJ MIKN XLEG QIEW UBES CWBQ XFAS KZWY CKKA RCNK
RMPO JGBI JQZB OGFD EVDY UNID WMQB WNMS SAAQ JUGV
AUIH WKRK LADI LCMH OCSF NGBW CYNM MATG SOKF RCPH
PIDY DTYA NXWZ QBMW ZOUG YSSM TJTM PLXV MEDB QHPK
IBWR NDHS SJIP PALV QFMQ QKKE ZSZA AWNK SLNS HZWV
YRMJ ESQT BSSA WMRA QEGP VPUJ DPQU WLDH TJJN NYAC
PJHS EWKL PJUA HNWW DLDG UNID WMQB OVTC VCKH PXMX
WSSK RAEU IUGH RKLB MHJY VOJE JFUT RGDF ZHHX UPCS
QMRD WOJM PYJB ZHHX MXIFNothing you said counters the comment you were replying to.
Paying $100/mo (or less) for a dedicated instance was probably more than adequate for something as simple as BugMeNot.
> When your entire userbase actively go out of their way to not pay for something it isn't a harbinger of success.
Success is more than monetary. And Bugmenot made the internet a little better for a lot of people.
Oh, and ironically enough, the owner of BugMeNot went on to be extremely successful, largely in part due to BugMeNot's free, open model.
Support for these types of projects doesn’t cost anything other than the sweat of the author.
The idea that web sites are big and expensive is false. I think the internet is better with more hobby projects where some kind stranger pays the $100/year to keep it running.
When I first used it years and years ago, it was great. But in the last five years not a single login worked. This kind of thing can't really last.
I needed it today when I stumbled on yet another "create a free account to read this article" page and noticed they had closed. Checking the Wikipedia talk page and Reddit it seemed they had closed today.
Most of the logins were actually bugmenot@mailinator.com, with password bugmenot.
There's a limit of course, it's higher the more you make. The stuff in that page is typically overpriced by 3-5x but since its free, it's fine. In theory you buy meat and fruit and regional delicacies but lately there's lots of stuff including electronics and whatnot. There are some truly bizarre things too, especially if you sort by price and select the most expensive ones, my favorites are the 10m yen tier I'm going off my memory but I just can't forget these:
- A custom statue of yourself
- A sauna to install in your backyard
- A whole frozen cow
- A local celebrity from that town records whatever you want for a ringtone
1. You can contribute to rural areas in return for a tax credit, effectively allowing you to redirect a portion of your taxes to another town.
2. The most important quirk of the system is that you can choose any towns to contribute to. There is no requirement of previous residence or whatever. In fact, most people contribute to towns with which they have no personal connection.
3. This ended up causing tax competition among local governments. Quite a few towns started advertising expensive "gifts" to contributers ("Give us your taxes and we'll send you some goodies"). It went so far that some towns got banned from the hometwon tax system.
It was introduced with good intension, but resulted in a very inefficient tax system.
With AI powered project cleanup it will be hard to land back into a phase like this. Feels like everything lands in sort of a safe median now. Mercifully my 8 year old son came home with an absolutely awful looking PowerPoint slide deck printed off the other day. And we made a terrible HTML site with random pokemon gifs and Marquee elements. Gotta keep the flame of creativity lit for as long as I can. Haha.
Thanks, Andreas Rumpf, for sticking with it for all these years: This seems like a great opportunity for me to get back into nim.
<button class="nav-btn" onclick="navigateToPage('index.html')">Home</button>
...
// Navigation functionality
function navigateToPage(filename) {
window.location.href = filename;
}
What shockingly poor code. Just disgraceful.This is bad for accessibility, bad for compatibility, and serves no purpose at all.
The CO2 vendors are really helped by it being invisible, aren't they? Nobody's going to pay to clean that up.
There was considerable pushback from the 60+ crowd and NIMBY types just like there is for everything new and different, but we got three permitted and are waiting on them to begin construction.
The thing that got me was there was a lot of people that just made whatever argument they could to try and stop it. All kinds of arguments that people either didn't understand or didn't really believe in. They just knew they hated solar. I really couldn't wrap my head around it.
From my perspective. It's a net good for our ranchers. We're mostly small family ranches, 200 head or less and the lease paid by the solar company helps these folks meet the bottom line. Beef prices won't stay up forever so it's a good time to diversify.
Either way it does not explain the concrete issues of recording in log. If you have a strong title like "Stop doing X" you better have some damn good arguments if you think you can tell other people what to do.
Without a functioning intuition, discovering the causes to initiate recovery effort in a high-stress, unfamiliar situation with catastrophic dimensions could be significantly hampered.
They are valid questions and of particular interest in the age of AI. Productive, highly specialized skills could degrade faster than one imagine once we start rely too much on external helps.
“Ready? 10 seconds to power on server alpha-romero-one-o-four!”
“Load—at five percent, check! All systems stable!”
This is one of those beautiful engineer understatements. Rotational speed is fundamentally linked to voltage by the motor velocity constant: https://en.wikipedia.org/wiki/Motor_constants
Although it's fundamental for all motors, the actual constant is arbitrary for each motor. Voltage is still proportional to change in field is proportional to speed; at zero voltage you have zero speed.
A large dead AC load has its own speed- zero. It's connecting the engine without a clutch, but the engine makes hundreds of megawatts. The 6' wide generator wants to go from 3600 RPM to a standstill in a few inches. A full speed rotor can have up to 5 gigajoules of rotational inertia; over a ton of TNT.
On a live grid you've got a synchronoscope: https://youtu.be/LVozbX9Mn1c?si=RhRPIkuTVxh4Wseq&t=181
Which is great, because connecting it backwards would cause a slow motion explosion. On a dead grid the only thing saving you is the resistance in the wires; it would be LOUD if you connected to it and you would very likely increase the ventilation through the walls of the plant.
Before Linux took over the server market in 2000, Windows server was the dominant player in mid-market (enterprise market has IBM mainframes too). But you would have be old enough to remember that decades ago.
We had to practice load pickup on a normal start at the pier often, but we likely practiced a full SCRAM to back online (including a FULL load shutdown) more.
Having predefined lists of what gets brought up at various points helps a ton, but it's still not an easy or simple operation.
The electricity industry has this notion they call a black start, where they bring the grid online from zero. It's a very difficult operation because you can't start a generator straight into an offline grid otherwise it gets hit with full demand and can't keep frequency in the right range, which can damage equipment. So they have to start by disconnecting all the loads and then bringing load blocks back in sequence, trying to roughly balance available generation with the size of the next block. In practice black starts are extremely rare, but they can happen after a cascading failure in which something causes some generating stations to trip, redirecting load onto the remaining stations which can't handle it causing them to trip in turn. The entire grid can collapse in just 60 seconds or so once that kind of runaway failure starts.
This kind of outage is very analogous to a black start. A few servers get into trouble - maybe they're in a crash loop or maybe their caches are cold - the load balancers shift traffic onto the remainder which then can't handle the load either and so the failure cascades. Once a service is in this state sometimes the only remedy is to disconnect all load, bring the servers back to stability, then bring load blocks back online in small chunks, making sure to never hit anything with the full load immediately to ensure any caches or JIT compilers have time to warm up.
It's the sort of thing that requires a bit of preparation because naive ways of doing it like just randomly dropping 90% of requests will yield a broken service for everyone. Ideally your LB can drop traffic by modulus of the session cookie or similar, so users are let back in atomically.
Black starting a service is obviously quite hard to practice, but is probably something that sufficiently well resourced SRE teams should try once a quarter or so on a test cluster. I used to be an SRE at Google and although we regularly started up new clusters and moved traffic around between them, actually starting an isolated service instance entirely from scratch was never something we practiced. I remember in a few cases teams discovered devs had introduced circular dependencies by accident, i.e. starting service X required service X to already exist, or it depended on service Y that in turn depended on X. Sometimes you can only find these things by practicing.
I was very aware of the ambiguity in the title re. geometry of molecules vs geometry of kinetics though, and I was trying to be a bit cheeky :) ! Maybe I took it too far
A lot of modern spam policing is just protectionism of a duopoly masking as security theatre.
> Every sending IP must have a reverse DNS entry pointing to a fully qualified domain name (FQDN). That hostname must, in turn, resolve back to the same sending IP address. This is known as forward-confirmed reverse DNS (FCrDNS). An IP with missing or mismatched reverse DNS is treated as suspicious and is one of the most common reasons for an IP to be considered for listing.
I self-host an email server behind my ISPs connection, and so I do not own the IP address that I send mail from, therefore I can't satisfy the reverse DNS requirement.
We've allowed them to grow this way by preferring convenience.
DRY doesn't mean don't repeat a similar looking block of code, it means try to structure your code so that each element of the design has a single representation.
There's no shortcut to good design where no thinking is required, much as a lot of people seem to wish there were.
Security should be enforced outside the harness with a sandbox. You can define what's allowed and what's not in one place and have strong enforcement guarantees instead of ad-hoc permission requests every minute.
I follow him on X, and I never got that impression. He has always come across as a skeptic IMO. Often wondering what others know that he doesn't due to practices that he hasn't found useful. I think yesterday he posted something suggesting that he doesn't follow usage patterns posted by others because the models have advanced to the point where any perceived improvements are by model rather than these patterns. I generally agree with this, and try not to get attached to any way of working with these things.
As for the usage of OpenCode, I have kept it to a minimum. V1 memory usage got a bit wild. Not sure if V2 has greatly improved. I have signed up for their Go plan a few times for times when I get tight on my other subs.
Not that agreement proves anything but I am glad to know I was not the only one. Him, Boris, Theo (t3.gg or something) -- I look at their archetype and wonder if that is what you need for success and if indeed that is what you need, then perhaps I do not want success at all.
Their CEO spends all day on twitter talking about how much better he is than everyone. And how nobody can use agents like he can. Its quite obnoxious
Also just use CDP, way too many browser solutions for agents when chrome ships with the ability to control the browser at a low level.
If you want to wrap it in a jsonrpc api for mcp, this is like 4 hrs or a work for an llm, point them at a pkg thats uses CDP like go-rod.
Nobody is claiming multiple parallel failures. They are claiming one failure that impacted multiple organizations.
People were making memes about the GitHub unicorn a decade ago.
Also, I don't think it's that "AI code is inferior" but rather devs got sloppy and no longer review code. Not to say that everyone's lazy but me---a lot of systemic/environmental factors could be the reason.
All of them got laid off at the next layoff. That was before AI.
Basically, these guys: https://www.nytimes.com/2025/11/22/us/texas-men-haiti-island...
Chernobyl was caused by a guy flipping a switch, Challenger blew up because of a faulty O-ring, etc.
Not the things that are breaking, no. The FAA was doing ATC a decade ago. We had email and cloud servers a decade ago. We had bank websites a decade ago. The scale of those things today is perhaps larger than a decade ago, but not enormously larger; indeed, the increase in scale in those things is much smaller than the increase in computing power in the world from a decade ago. So these things should have gotten more reliable--but they haven't.
When banks started moving to computerized systems, maybe a bank would be unable to process something... but not multiple banks. I can't recall any "outages" that affected banks nationwide for any period of time. Walk into your local bank and find out they can't do something because their big system at the mothership is down? Perhaps.
Consolidation likely plays a part in this as well. I can't speak to the FAA/ATC systems 50 years ago, I have no recollection of what they were like then, but the only nationwide system I can think of around that era was Ma Bell. And I don't honestly recall any nationwide outages back then. Regional, sure. You might have a problem with part of the country getting calls if there was some kind of emergency... (e.g., everybody trying to call their grandmas in Kansas after reports of a tornado) but I don't remember there being any nation-wide problems like that.
We had to count on actual snow for snowdays. :-)
Roman citizen wondering why the aqueduct isn’t working kind of thing.
All hat, no cattle.
They are entirely wrong.
None of these outages, as far as we know, have a common cause. They just happened by coincidence inside the same news cycle.
Nor is there any evidence to blame them on AI, or tech layoffs, or hackers from Iran. It's more likely something boring and technical that doesn't fit into anyone's narrative.
Things like food, water, basic sanitary items, would be bartered for.
I told him it's just like how he keeps telling his patients to watch what they eat, drink and smoke less, and get some exercise, but they don't, and then they have a heart attack and wonder why.
Ugh. DownDetector's methodology is… not great.
Steam isn't down: https://downdetector.com/status/steam/
Amex isn't down: https://downdetector.com/status/americanexpress/
Visa isn't down: https://downdetector.com/status/visa/
AWS isn't down: https://downdetector.com/status/aws-amazon-web-services/
But each has a huge corresponding spike there.
- Physical branches closed or unresponsive.
- Online banking down.
This exact same thing happened in Europe with Revolut late last month. It was resolved in about 12 hours: https://www.revolut.com/blog/post/20octoutagetechnicalovervi...
In that case, it was a Google Cloud outage. Something similar (database outage) could be the culprit here.
Those speakers were there for diagnostics of various types. One of them was figuring out when a person picked up on the other end.
I think we could be a lot better at using human sound, visuals, and spatial navigation abilities in understanding software systems too, but I've never gotten around to implementing anything despite plenty of ideas.
My latest experiment is using tones and/or speech synthesis artifacts to get insight into LLM agent operation -- ongoing reasoning, tool call success/failure, etc. Still haven't really dialed it in (hah!) to be useful yet.
I had an FTTH provider with 100% of their network on natural gas standby generators. Went through a week long power outage without losing a single packet. You can support something like 100k households with well under 50kW of power. There are homes with larger generators than this. Docsis 4 would put you somewhere around half a megawatt.
I get that attitude, but coax connections are fragile in a way that fiber is not. Water infiltration, bad crimping jobs, unterminated ends in the neighbor's house all cause signal degradation that is extremely time and labor intensive to identify and fix.
Cable is an excellent solution for distributing broadcast analog radio signals over a private line cheaply and efficiently, but two-way digital signals over the same medium aren't as robust as their fiber-based counterpart.
ISP outages are one thing, but if you ever experience service degradation—and not a full outage, but tear-your-hair-out crap like "my internet goes down for 15 seconds once every 16 hours with no discernible pattern"—and it ends up being some particularly coax-flavored problem, you'll understand what I'm talking about.
If the goal truly is social progress, perhaps we should spend a little less energy hunting heretics and a little more effort showing empathy. It doesn't matter that the empathy isn't reciprocated. There's value in being the more likeable side to anyone watching from the sidelines.
It's not lost on me that our side often responds to hateful language with our own forms of hatred. Both sides are complicit in allowing these differences to calcify into the worst kind of political tribalism, but I think our side fails every time it turns a teachable moment into a "hateable moment".
Hate cannot drive out hate; only love can do that.
Then the QA started to go down or the devices wouldn’t ship on time. On top of that, Ryan’s politics were a big turnoff.
I would not buy another device from this company.
Man how long and often do I need to get my hopes up?
You can't tell me that the company having the patent is so bad in making it cheaper and better so that the mass market would kick in?
Or is there 0 mass market for things like that?
Or is it really that expensive to make them bigger?
Lets see who wins in a few years: The price going down or my wallet
I see no reason why any developer, other than someone writing something for the Windows platform specifically, should not be using Linux over Windows. MacOS has a ton of polish in so many places—but then there are all these little paper cuts that keep coming: funny little bugs that interrupt work or make you scratch your head. Peeking over the garden wall into Windows' garden only seems worse. Linux by comparison is awesome! I look forward to spending my day on my Linux desktop.
Seriously, if you do dev work, do yourself a favor and boot up—I dunno, maybe Fedora Silverblue—on a separate partition and force yourself to work on it for a day or two. Use an LLM to diagnose issues as they come up. (I had some serious stability issues; Claude suggested it was a memory issue; running memtest86 told me I had bad RAM—fixing that and all problems went away.) You'll find that your system is quieter and less distracting.
I still don't think Linux is for "average users"—even though most people probably only need a web browser. But if you have gone anywhere near a command line in your life, it will be worth the switch.
Most Chrome configs end up persisting full browser history and clickstreams inside a Google account.
If you use Debian and opt-in to popularity contest; it may collect and send similar info depending on how you installed these coding agents.
Moving from windows device to a phone/table because it collects names of coding agents would be a perfect example of out of the frying pan to the fire, given the choice of OS we have for those.
If those caveats are not a big deal(depends on the person) compared to the privacy issues, linux is still a better option.
I wish I could. I wish it could do everything well. But it just doesn't.
If all you do is web, then use your phone or a tablet. Windows isn't the right choice for that either.
> ... you could play many commercial Windows games well
But this is just not true.
Proton was the turning point where you went from specifically looking for Linux games to just assuming everything works.
I have to keep my gaming PC as Windows because I can't play Madden, EA FC, or PUBG on my Linux machines nor my Steam Deck (unless I install windows). They all require kernel level anti-cheats that are only supported on Windows.
You also can't play a ton of other very popular games (that I don't happen to play, but millions do) like Call of Duty, Fortnite, League of Legends, Battlefield, etc. Those games have millions of players.
And this is just for gaming. There are plenty of other bits of software that don't run on Linux, even with all of the amazing work that has gone into compatibility tools like WINE.
I am not saying that many people shouldn't explore moving to Linux from Windows, but I don't think it is helpful to say everyone can switch without at least mentioning any of the reasons people can't.
Yes, of course. The key to understanding it is that this is still less overhead than Windows adds.
Take your pick - Ubuntu, Fedora, someone else mentioned Mint. All fine choices, no wrong answers.
The biggest barrier is kernel anti cheat, so no Call of Duty, Battlefield, etc. Luckily my friends don't play those AAA multiplayer games, protondb is a good resource to check which games can't run due to their anti cheat.
The vast vast majority of single player games are 100% perfect on Linux. Multiplayer still has lots of hiccups.
ISAs are pretty complicated and reasoning about programs in that context is hard which is why we have high level languages.
> This distinction in terminology used to be a colloquially accepted notion, when we heard "CompCert is a formally verified compiler" or "seL4 is a formally verified microkernel" we assumed the authors did not verify vacuous or trivial properties, because the work of verification itself was held to a high standard that highly affected the reputation of the researcher.
CompCert has also had extensive empirical evaluation to vet the theorems. Famously the CSmith paper (https://users.cs.utah.edu/~regehr/papers/pldi11-preprint.pdf) has this rather choice quote:
> As of early 2011, the under-development version of CompCert is the only compiler we have tested for which Csmith cannot find wrong-code errors. This is not for lack of trying: we have devoted about six CPU-years to the task. The apparent unbreakability of CompCert supports a strong argument that developing compiler optimizations within a proof framework, where safety checks are explicit and machine-checked, has tangible benefits for compiler users.
At my work we've extended this to CPU millennia. I hasten to add this of course doesn't rule out the possibility of poorly formed assumptions in the semantics etc (it's empirical after all) but it helps to build evidence that we have the theorems and semantic design right. More generally differential testing of this sort offers a possible way forward to build evidence in favor of theorem statements beyond expert examination.
> Every discussion of formal verification must come with a list of caveats, a precise understanding of what is trusted, what is proven and what is not.
Anyone that seriously participates in this work practices this. The whole community. More importantly this is precisely the point of writing down a theorem so that we can closely examine the assumptions. To abuse the CompCert example yet further it's now entirely possible to draw the envelope of assumptions, which are many for a non-toy compiler: https://arxiv.org/html/2201.10280v2.
Last note, I like the kiki bouba diagram if only because it evinces the problematic "round cow" assumption and how that doesn't pan out for real software.
> Apps are ephemeral, but your files have a chance to last.
Edit: looked it up, it’s an AI note taking app from what I can tell.
This would not even be news if people weren't jumpy after last week's chaos.
I suspect it's a good example of media bandwagoning and availability cascade.
I hope folks are re-evaluating that now.
Thank you so much for building something that was obviously good enough to sustain the community for 12 years <3
Turns out, the reason people wanted to use it was because the API was stable and every slight step towards improvement was met with... resistance. I stopped maintaining it because the burnout from seeing what it could be and not seeing any path to get there was too much for me.
I'm extremely grateful to burntsushi for writing the datetime library rust deserves. Chrono is stable and is maintained (though semi-deprecated) by an extremely reliable rustacean -- you don't need to leave, but you'll probably be happier if you do.
I really appreciate when a project calmly acknowledges that it's not the right tool for every use case, and is not trying to be. That's professional engineering.
Especially in the AI-age, the crucial skill will be what NOT to implement.
The alternative is to keep a relatively small standard library, and a good package manager, to make it easier for people to iterate on API design in third party packages. Major version changes in a single library can have much less impact accross the ecosystem than standard library packages. Eventually you may get a de facto standard, and sometimes they are then later incorporated into the standard library.
This model isn't without its downsides; it can sometimes mean fragmentation when standardization would help, sometimes these de facto standard libraries can become important enough that they run into the same ecosystem fragmentation issues on major releases. But it allows for more flexibility.
The latter model is what the Rust project decided on for everything outside of the most fundamental time types. Dates and times and timezones are notoriously hard to model in code, and easy to create API designs that are full of footguns, so this is a place where that extra freedom to iterate was more important than standardizing on an API early on.
That iteration has led to a number of different libraries, including time, chrono, and now jiff, allowing for exploring the space of API design to really get it right rather than being stuck with what was available early on.
Woah now, let's not get too controversial.