> What's the point of having a status page if it lies ?
Status pages are basically marketing crap right now. The same thing happened with Azure where it took at least 45 minutes to show any change. They can't be trusted.
It's actually the opposite. Calculating an asteroid impact is much easier because it primarily involves basic Newtonian physics. In contrast, the climate is a chaotic system, making long-term predictions far more complex.
I don't know how it's opposite. There's some complex guesstimating on where an asteroid will hit. We roughly know its size. We roughly know its composition. We roughly know its speed. We can give a +/- range where the impact area will be. That's not any different than how hurricane spaghetti models do.
The difference is knowing the size, speed and composition of a hurtling rock tells you where it's going to go, where as knowing the size, speed, and composition of a hurricane does not tell you where the hurricane will go. Complexity isn't a problem, the issue with weather prediction is that it's chaotic - extremely small changes to starting conditions cause large changes to the end result.
I believe the description as a "wall" is not completely correct. Yes, it's a wall as a unpassable obstacle, but the description they gave when walking into it seems more like a field "can't turn around just walk backwards".
The field was just dense enough to stop people from continuing moving forward similar to molasses.
The gripe I have though is that it is incredibly hard (if not impossible) to create a dense powerful e-field without it arcing over.
To be powerful you need an incredibly high voltage, to be dense you need the positive (holes, as they say) and negative charges to be close to each other.
If you could get 5MV between two plates that are a foot apart, that e-field would be insane an probably could do all manner of sci-fi. But it would flash over and equalize in a picosecond. Even if you had some kind of god tier power supply supply that could support a constant 5MV, you would just end up with a dense wad of plasma vaporizing everything.
Dunno. The breakdown voltage of vacuum is enormous. There might be several unknown parameters at play here which would increase the breakdown voltage of the air.
It might be but an urban legend, but the phenomenon sounds way too fun to not look into it (or to stop spreading it should it turn out as false, kinda like Santa)
This is the same impression I got, precisely because of this description. If it's the effect of a field, it would seem that by the point you notice it blocking your forward progress, you're already rather deep in it.
Makes me think of magnets, too - when you have two strong magnets oriented so they repel each other, and try to get them closer, the effect is very strongly non-linear and, unless you're intentionally pushing the magnets together with significant force, can feel like it turns on almost instantly.
When red tape makes drug development and testing impossible, as it did here, the system has ceased to benefit humanity and is causing nothing but stagnation and long-term suffering (by virtue of holding back potentially life-improving or life-saving treatments.)
Enabling medical progress is far more important in the long term for our species (and to reduce suffering) than adding the umpteenth killswitch/safeguard for an ostensibly safe medicine.
But FDA regulators have no incentive in the positive direction, only in the negative direction. The more drugs they deny, the less likely they can be blamed if something goes wrong; the more requirements they add, the more secure their careers - humanity's medical progress be damned.
It is unfortunate that the only way to get through the regulatory process is copious $ - but it does work. If this project were better funded, it would likely have gotten through.
There is an entire political party representing something like half the population of the US dedicated to shrinking the regulatory apparatus, including the FDA. That doesn't sound like career security to me.
This project might have helped me when I needed to implement a console app that might or not start a web server.
Asp.net is very overbearing (even using minimal APIs) when you want to use other Microsoft utilities like DI, logging or config since it wants to be the main entry of the application.
Never found an easy way to use the host feature with a optional web application where they both shared the DI. Note that this is more a problem with the generic host than asp.net itself.
It is actually possible, to seperate those things, but it's tricky.
Our current product can run in several modes, one with a web ui and api and one without. If running without there is no trace of the ASP.NET Core Pipeline ( and Kestrel is also not running )
We're using ASP.NET Core Minimal APIS for both API and UI (if configured to run in that mode )
If I understand the problem, just move all your DI registrations to a shared extension method:
public static ConfigurationExtensions{
public static AddMyApp(this IServiceCollection services){
services.AddScoped<IFooService,FooService>();
}
}
//In console app:
var consoleBuilder = Host.CreateApplicationBuilder(args);
consoleBuilder.Services.AddMyApp();
...
//pseudocode - in real world you'd put this in another class or method called by the commandline code:
if(webHostCommandLineSwitch){
var webBuilder = WebApplication.CreateBuilder(args);
webBuilder.Services.AddMyApp();
...
}
He already did it with a 1km diameter ball (https://what-if.xkcd.com/12/) and the destruction was terrifying. Please keep him away from these other bigger water balls.
> Some coworkers seem to be having better success but I definitely get the sense they are reading and editing the results carefully.
Yes, you need to consider the AI as if it were a junior programmer that sometimes makes mistakes. I use it for boring work that can be quickly checked. For example, the other day I asked for a 'give me next workday' algorithm based on the code structure I had, and it worked fine.
If it's that straightforward I'd rather just write it. Like I said it hasn't been an overall time saver with the extra scrutiny I need to put it through. I'll try again in six months.
Also idk kinda tangent but you brought it up. I don't feel like my junior devs make easily found algorithmic mistakes like that. They're more likely to misjudge the scope of the problem or not be aware of a technical consideration or known solution. For that kind of work I'd rather... mentor a junior dev through it so they have the experience.
That's what I've been saying: AI is just a tool that can't yet replace programmers—maybe one day.
I use it for the boring work like generating comments, basic algorithms, API endpoints, and naming stuff. Even with the need to double-check the output, it still takes a load off my brain.
A nice example of Hegelian Dialectic (if we're being XIX) or Robinson Resolution (if we're being XX), involving public defecation being a crime, occurred recently in Catalunya:
Thesis: the guy pooping is a traditional element of the nativity scene
Antithesis: government sponsored nativities shouldn't depict crime
Synthesis: keep the guy, but add a police officer, writing the guy a ticket
> I wonder if they added the anti-crime as PR excuse.
Having now done a bit more research than I care to admit to, this book, particularly the page 14 sample, suggests nuance rather than pretext, particularly that reduction of public urination was a secondary benefit that became a primary benefit after public lighting:
Status pages are basically marketing crap right now. The same thing happened with Azure where it took at least 45 minutes to show any change. They can't be trusted.