Not the case universally. My son's school in south-central UK does everything via Google Docs or apps specially built for distance learning. If it weren't for Minecraft mods, he'd have no concept of the file system.
Well, in Google Docs you have something that looks a lot like a hierarchical filesystem (whether someone actually creates folders or not). The fact that it's not actually a filesystem as traditionally understood is sort of irrelevant. The average filesystem user didn't know about inodes, journaling, etc. either.
I'm pretty sure that in the EU (and the USA), even fictional CP is illegal. That is, even drawings or stories of CP are illegal, and certainly AI-generated images would fall under that banner.
Probably yes, although in some EU countries having CP is below the level of a criminal offence, with the circumstances being that the images are artificially created even the minimum of three months of jail might not be considered.
ESET started scanning SSL certificate chains for nodejs, which is a good feature. If you're using node without a full chain then it will block the requests. Unfortunately, they did so without warning, which broke our GitHub Actions Runner and our dev machines.
ESET deployed the change silently, breaking nodejs implementations and leaving people scrabbling around trying to add node to the SSL scan exception list.
Is it reasonable to expect some warning before a change like this?
I might be forced to choose a replacement. What's your goto brand of antivirus/botnet detection for server and workstation with centralised cloud management?
All of the above! Additionally... I think AI companies are trying to steer the conversation about safety so that when regulations do come in (and they will) that the legal culpability is with the user of the model, not the trainer of it. The business model doesn't work if you're liable for harm caused by your training process - especially if the harm is already covered by existing laws.
One example of that would be if your model was being used to spot criminals in video footage and it turns out that the bias of the model picks one socioeconomic group over another. Most western nations have laws protecting the public against that kind of abuse (albeit they're not applied fairly) and the fines are pretty steep.
Article is 3.5 years old, best put the year in the title, OP!
I think the definition of serverless is too narrow (AWS lambdas/ Azure functions) and that serverless is really "I want to build apps, not manage infrastructure". That's not the same thing as putting everything onto functions.
I have a monolith we're preparing to move onto a managed container system (prolly AWS AppRunner). I don't want to manage K8 if I can help it, our app doesn't need complex server architecture.
Personally, I think it's just the next layer of abstraction up. Some won't benefit from serverless in the same way some are better off with in-house tin. I know some that need custom chipsets in-house, so can't even buy a stock rack server! However, many many web apps don't really need the control and will probably use facets of serverless over time. But it is still a revolution for old people like me that just don't want to manage servers anymore!
AWS right now feels like the most lagging in serverless containers.
If you get a chance, try out the DX with Google Cloud Run or GKE AutoPilot. Building and shipping to GCR is fast enough that it feels like a local build-run worflow. Google Cloud Run jobs are also fantastic and you get a pretty hefty free monthly grant (~60h of compute).
Both Azure Container Apps and GCR are true scale to zero whereas AppRunner is not and always maintains a minimum monthly baseline cost (~$5-6).
AWS feels the most behind in terms of its serverless container workload experience (I use AWS every day professionally, but use GCP and Azure for side projects).
Trying to program the web front end like you do the API backend feels like an antipattern. I'm all for productivity but you eventually hit issues that cannot be resolved because the client/serverness of your solution has been abstracted away from you. Those of us with WebForms scars remember those days.
Like the article suggests right at the end, I want a C#-compile-to-wasm with new language structures for common web browser features such as shadow DOM. Perhaps also without the .NET core lump unless you really need it - and even then importing only the dependencies you need. I almost love Typescript but only because I spend my life wishing it was really C#.
Blazor looks cool but it's not quite native enough to client/server. I've been burnt by Silverlight and have a lots of ReactJS at work so the benefit isn't quite worth the cost and risk. I wonder if in a future role I might be tasked with a greenfield app for which it's a brilliant fit but I can't see that in any of the SME roles I've had so far.
