Right. Because compute power and/or a physics based model is the limiting factor for accurately predicting when a seismic event happens. Training on historic data is hardly the problem that need's solving.
It's the leading indicators that are actually measurable that are missing. You know the ones that allow for evacuations and other protective measures.
I saw beta screenshots of what used to be the toolbar (e.g. in Finder) and immediately disabled auto-update on my Mac. Seeing how many bugs have also been introduced (not just visual glitches) pretty much reaffirmed me in my decision.
However the downside is I can't try some new app releases like Daft Music[1] because it has become to burdensome to maintain two different designs. Especially in SwiftUI.
Trust me 1-Star-Drive-By Reviews by "customers" without any merit are just as bad for businesses.
So, congrats. You've basically discovered that online review systems suck. Look at app stores. Look at Amazon product reviews. It's all being gamed and manipulated and abused. Google obviously won't moderate any of this because there's no substantial business value.
I'm of the opinion that this is bad design because it makes it very hard to reason about the consequences when refactoring a large codebase. It's kind of like reactive global variables. There are legitimate reasons when to use them. But not as a general design principle.
That being said: If you're dead set on this paradigm you can implement this easily yourself. Create a bootstrapping function that modifies a prototype or class in order to provide functions to register signals and slots and use them wherever you need them.
If you use TypeScript you could even use Decorators (e.g. "@Signal" or "@Slot") which are just higher order functions to have some syntactic sugar like the QT macros.
> The irony is that, since you are splitting the problem in a way that requires synchronization between cores, you are actually introducing more work to be executed in the same CPU-time budget. So you are spending more time on overhead due to synchronization, which does the opposite of what you probably hoped for — it makes your code even slower, not faster.
That is certainly not universally true for every scenario and if you need to sync state between cpu cores very often then your tasks simply don't lend themselves to parallelization. That doesn't mean that multi-threading is inheritely the wrong design choice. Of course it will always be a trade-off between performance gains and the code complexity of your job control.
John has reiterated multiple times on his podcast that he doesn't want to deal with thousands of support requests when making his apps open source and free. All his apps are personal itches he scratched and he sells them not to make a profit but to make the barrier of entry high enough to make user feedback manageable.
For what it's worth: they do honor the robots.txt file. I had the same problem with a client's CMS and denying all AI crawler user agents did the trick.
It's clear they've all gone mad. The traffic spiked 400% overnight and made the CMS unresponsive a few times a day.
> AI Agent RequirementsDescriptionSemantic MarkupUse of HTML5 semantic elements to define web page structureConsistent CodingConsistent use of coding practices throughout the web pageWeb StandardsAdherence to established web standards and best practices
Right. Let’s ask AI how to make websites easier to navigate. Because that’s the top priority on the internet.
That's an interesting stack choice. A desktop client that uses Django as a backend. I kept wondering how this is rendered client side. TIL about NW.js.
What are you talking about? DB Infrago is a subsidiary of DB and is as such governed by the board. The fact that they are separate entities has purely corporate legal reasons.
Being able to apply algorightms and implemnent data structures isn't what makes you a good programmer. Writing maintainable code for yourself and your team members, documenting important bits and helping out others is what produces actual value.
Well my school did trips to the local library so that everyone could acquire their paper card for borrowing books. The process of borrowing and the different sections in the library were explained by the librarian and at least in my mind that helped a great deal to seek out books on my own.
It's the leading indicators that are actually measurable that are missing. You know the ones that allow for evacuations and other protective measures.