It's like DRM; on some level, the user is using computer how he is supposed to use it - interacting with memory and processor and the programs.
Of course nowadays DRMs are sort of baked-in, so I guess anti-cheats could be too?
573 karma · joined April 19, 2024
Of course nowadays DRMs are sort of baked-in, so I guess anti-cheats could be too?
everything is .net, azure, 365, now also copilot.
VSCode itself can deal with big text data being thrown at it, this will be some of the language server stuff
GNOME Web/Epiphany (same thing) seems to use WebKit and is officially supported
https://apps.gnome.org/Epiphany/
It seems there is no WebKit browser for Windows.
What if you log all POST requests for debugging purposes and forget to sanitize the logs.
What if you have XSS in your web app that sends the password to a third party.
What if your mobile phone app has a dependency that includes a keylogger.
The likelihood of this increases the more layers you have in your organization (for example, the log pipeline team assumes the logs are already sanitized; the login form team assumes the log team is sanitizing them; it all goes through some A/B testing team that just dumps all data to "data lake" somewhere unsafe; the FE team puts in random node.js dependencies as it's "just a frontend"; etc).
Passwords can leak from more places than just from the DB...
Thus there is basically nobody doing credit card processing and the companies that DO that are unreasonably big and basically a monopoly. (Everyone always complains about PayPal...)
no corp will use sourcehut. That's just outside of the possibility. And corps have the most money.
If you have a messy app, you have a messy organisation.
Structure of code often reflects structure of your company.
The code is often maze of layers because the company is a maze of sub-committees. Java/C# fits more neatly in there.
Although with Go, what can happen is that there is a maze of microservices. Maybe that's not that much better.
ok errors.As is a little stupid, I'll give you that. But that's all.
The more enterprisey software usually have lots of layers for organizational reasons, and go doesn't really fit there. So I don't think it will really be a hit in the enterprise.
yes there are orm solutions and DI frameworks and all that, but they always feel like they don't belong in the language.
(Also, java and .net and php are much older and have much bigger enterprisey ecosystem.)
I have seen go replacing the php stack though, and in some way the "original" python stack - but python now has ML.
At the time, the community seemed to have settled on dep - a different, more npm-like way of locking dependencies.
rsc said "nope this doesn't work" and made his own, better version. And there was some wailing and gnashing of teeth, but also a lot of rejoicing.
That makes me a bit sad that rsc is leaving.
On the other hand, I don't really like the recent iterator changes, so maybe it's all good.
Btw if you reading this rsc, thanks a lot for everything, go really changed my life (for the better).
That almost never happens in reality so it's not an issue.
For example, go has io.Reader which needs just `Read(p []byte) (n int, err error)`
Your issue is that you accidentally do Read with same signature, but it will mean something else, and the error it returns are different, so instead of EOF (as io reader should) it will return something else on end of file?
... it just doesn't happen in Go. You would need to go out of your way to break it. I guess it theoretically can happen.
Or maybe I just don't know Fx.
https://github.com/temporalio/temporal/blob/main/service/mat...
The issue we hit with Temporal - again and again - is that it's very under-documented, and it's something you install at the core of your business, yet it's really hard to understand what is going on, through all the layers and through the very obtuse documentation.
Maestro has... no documentation? OK Temporal wins by default.
(Please correct me if I'm wrong.)