2,372 karma · joined March 12, 2010
I find running on battery, lots of things are throttled or disabled. CPU is slower for example. That's probably a good reason for why not.
That was a good social bookmarking site. I wonder if anything similar exists now?
Are we allowed to say that now?
- their instructions
- your instructions
But you only see your instructions.
The appeal of this project is that it uses CoW (copy on write), so in theory it should be fast to copy as it only maintains writes.
But careful the app developer that abuses this position, for they will more likely be the app I remove from my phone.
And now we have the opposite situation with those who have had the most boosters and now more likely to catch the new variant that is out.
This was used in the war to estimate the number of German tanks based on the sequential IDs
https://en.wikipedia.org/wiki/German_tank_problem
So just for business intelligence you don't want to leak your IDs.
And yeah, I know everyone loves to hate on the syntax and approach of frameworks like React, Vue, Svelte, and Angular. But guess what? They've been widely adopted and proven effective in real-world scenarios. They provide a familiar syntax and conventions that make collaboration and code maintenance easier. Instead of completely dismissing these frameworks, let's focus on improving them while staying open to new ideas.
I get it, some folks prefer alternatives like XAML/Silverlight/WPF or Android with Jetpack Compose. And hey, those technologies may have their advantages too. But before we jump ship, let's carefully evaluate the pros and cons of each option. Consider community support, learning curve, performance, and scalability.
At the end of the day, there's no one-size-fits-all solution in web development. We need to understand our project requirements and make informed choices. Let's keep learning and adapting to new technologies while respecting the merits of existing solutions.
What about frameworks like htmx though?
While they may not be as widely known as React or Angular, they offer a different approach to building dynamic web applications. htmx focuses on enhancing server-rendered HTML with minimal JavaScript, allowing for a more progressive enhancement approach.
By leveraging existing HTML and server-side logic, htmx can provide a simpler and more lightweight solution for certain use cases. It's definitely worth exploring and considering htmx as an alternative when evaluating framework options.
However, it's important to note that the adoption and community support for htmx might not be as extensive as some of the more mainstream frameworks. This can impact factors such as available resources, documentation, and community-driven improvements.
Ultimately, it all comes down to understanding the specific needs and goals of your project. Consider the trade-offs involved, evaluate the resources and community support available, and make an informed decision based on what aligns best with your requirements.
It does help I guess if you eat so much sugar and fibre helps mop it up and digest it slowly. But the solution isn't to eat more fibre, it's to eat less or no sugar.
A body can survive without glucose and burn fat for energy instead.
You get people to do a postal vote, and they show you what they are voting for and you pay them, take away the ballot and post it yourself (or threaten them and do the same thing)
> This gets better - Razor's crack is fine, the reason both Midnight Club 2 and Manhunt crashed when these cracks were in use was the fact that Steam DRM included a .bind section that was code not marked as code - thus tripping Data Execution Prevention
How would one account for a fixed cost then? Do you say ok it's a fixed cost, and you get 6months base on our estimate (but if the 6months has finished the contract ends, and isn't that just a time based project). Or do you tell the client no changes after the initial requirements (which doesn't sound flexible and you end up building something the client doesn't want)?