I am using duckduckgo for a decade. But especially, I am using Firefox Saved searches a lot. I type mdn in the bar, and it searches in the Mozilla developer network. osm is openstreetmap, so is stackoverflow, w is Wikipedia, yt is YouTube... I often know on which website I will find the info anyway, so I use less a generic search
I used Kagi for several months, I guess I'd at least recommend trying it out.
I stopped using it, though, and I can't honestly say I've missed it. It was nice not having sponsored results, I guess, but overall it didn't feel like a transformative experience.
To take this a step further. I want a phone that is small (doesn't have to be tiny, just iPhone SE 2020 or smaller, please), has a replaceable battery, has an unlocked bootloader, has a headphone jack, and costs $400 or less.
It doesn't need to have a cutting-edge processor or tons of RAM and storage space or a 120hz screen or razor-thin bezels or a studio-worthy camera, yet somehow all these things are prioritized on the market over a basic, reliable phone.
I guarantee you that, given your requirements, this will never be a product that you can buy.
Hardware projects live and die on scale. The engineering and tooling costs are a similar order of magnitude whether you make 1000 phones or 1,000,000. If you can guarantee that you have an accessible market for a million devices, then you're starting to get into the region of scale where this would be an OK idea.
Mind you, that's a million users who are cool with all the design tradeoffs you had to make to ingress protection, software performance with modern android, and form factor in order to get your desirable characteristic.
The Punkt MP02 is at roughly the price point and "niche-ness" as the product you describe here, and that sold for almost $400. They could afford to build in about the same amount of functionality as a Nokia brick of yore (but with 4G radios!) for that price.
Have you looked at Motorola? I'm not sure they have all of those features, but me and you think similarly and when I did research, I ended up choosing their $130 phone for my contractors.
But I main the $900 pixel.
They are so similar its weird, but Motorola was slow with snapchat and the keyboard some time.
Filtering for GP's requirements on GSMArena.com, I only see a handful of recent phones. Some of them do have an unlockable bootloader, but all of those are made by GPL violators, so you won't get the source code necessary to really make use of that unlocked status.
EDIT: I forgot to check the "removable battery" checkbox; with it you get zero matching phones. Maybe you should've checked that before assuming GP just can't search.
Not to end on such a negative note, foregoing a maimum height and the removable battery, Sony's Xperia 5 and 10 fit the rest of the requirements and are very good phones. Hard to find for sale in the last few years, though.
Wouldn't work very well as a phone though. The networks a 2012 phone support no longer exist. 2G and 3G are both fully shut down where I live. Even if you specifically got a 4G phone from 2012 it might not support VoLTE, so you'd be unable to make calls.
As a wifi internet device it would work but I'm not sure that's what OP is going for.
it is very difficult to find good (as in "good condition") battery for a 5+ old gadget. even if you find original one - it could be expired and DoA. but more often you get "compatibles" which die in 3-6 months.
The rule of good fast cheap still applies the same as always, but business leaders consistently choose to ignore this reality and insist upon fast and cheap without acknowledging that it will come at the cost of good.
What's worse, is that these decisions are usually made on a short-term, quarterly basis. They never consider that slowing down today might save us time and money in the long-term. Better code means less bugs and faster bug-fixes. LLMs only exacerbate the business leader's worst tendencies.
I respectfully disagree. If you compare the western designs in the article to the Japanese ones, the western designs have these giant banners and images that insist on themselves. Those are the ones that are shouting. It's like the Japanese pages are presenting information and the western pages are trying to be highway ad banners.
You cannot remove the toil without removing the creative work.
Just like how, in writing a story, a writer must also toil over each sentence, and should this be an emdash or a comma? and should I break the paragraph here or there? All this minutia is just as important to the final product as grand ideas and architecture are.
If you don't care about those little details, then fine. But you sacrifice some authorship of the program when you outsource those things to an agent. (And I would say, you sacrifice some quality as well).
Quote: "Toil is the kind of work tied to running a production service that tends to be manual, repetitive, automatable, tactical, devoid of enduring value, and that scales linearly as a service grows."
Variations of this definition are widely used.
If we map that onto your writing example, "toil" would be related to tasks like getting the work published, not the writing process itself.
With this definition of toil, you can certainly remove the toil without removing the creative work.
You can remove a lot of toil from the writing process without taking away a writer's ability to do line edits. There's a lot of outlining, organization, bookkeeping and continuity work AI automates in the early draft/structural editing process.
Most writers can't even get a first draft of anything done, and labor under the mistaken assumption that a first draft is just a few minor edits away from being the final book. The reality is that a first draft might be 10% of the total time of the book, and you will do many rounds of rereading and major structural revision, then several rounds of line editing. AI is bad at line editing (though it's ok at finding things to nitpick), so even if your first draft and rough structural changes are 100% AI, you have basically a 0% chance of getting published unless you completely re-write it as part of the editing process.
It all depends on how you split the difference. I wouldn't call the emdash vs comma problem toil. It's fine-grained and there are technical aspects to the decision, but it's also fundamentally part of the output.
The problem pointed out in the article seems a little silly. We're adding an entire language feature because someone wanted an optional bool class? Why not just create a uint8_t with three values: OPTIONAL_BOOL_FASLE, OPTIONAL_BOOL_TRUE, OPTIONAL_BOOL_UNDEFINED?
Doing so takes the same space as a bool, and could be wrapped in a class if desired to provide a nicer interface.
I would think it would have to work the same in both since otherwise C code using that behavior would not compile in C++, right?
I am not a C++ expert, but I'm surprised to hear that it is considered UB to access the other member since as far as I can tell a union is just a chunk of memory that can be interpreted differently depending on which union member you access?
So, if you had a union { bool b, char c }, and you set b = false, then I would think that accessing c would predictably give you a value of '\0'.
Granted, you probably shouldn't go around accessing an inactive union member like that, but when people say it's UB they make it sound like it's impossible to guarantee what data will be inside that byte, and it seems to me like that isn't true.
The language is the problem, and WG21 hates fixing the language. The really bone headed stuff like "UB? in my Lexer?" got through as a language change and Barry has also had some success with "just fix it" language changes, that's what happened so that C++ can attempt what Rust's MaybeUninit<T> does, but mostly WG21 will take weird new intrinsics in the standard library, as here, over just fixing the programming language.
Barry even explains, the transmutation is outlawed during compile time in C++. They could remove this prohibition but they did not.
Notice that e.g. Rust doesn't prohibit compile time transmutation, the provided core::mem::transmute literally does this operation, and it's const. The result is - as with similar situations in C++ - that if at compile time that's a 2 the compilation fails, 2 is not a boolean. You don't need all this bother because Rust's type system is better so Option<bool> already does have the same size as bool, but that's beside the point.
The whole problem only arises because accessing the union member as a character is allowed at runtime, but disallowed in constexpr. If that restriction were relaxed to be the same in both cases, the entire motivating problem would disappear...
Except there are literally people on this thread saying that this is proof that code quality doesn't matter and that we all need to "wake up". It's the same as the people saying that spec driven development is the way of the future and that engineers should be focusing on the spec and not even looking at the code.
If you use LLMs and you do care about code quality, then great. But remember that the term vibe coding as it was coined originally meant blindly accepting coding agent suggestions without even reviewing the diffs.
Many of the people aggressively pushing AI use in code are doing so because they care more about delivery products quickly then they do about the software's performance, security, and long-term maintainability. This is why many of us are pushing back against the technology.
> Will human generated art still be as respected/valuable?
I would hope that humans would always value human generated art, but these days it seems that many businessmen and AI bros do not. Perhaps they are not human.
Don't be ridiculous, talking about "partisan fear". They have taken away documented, American citizens without due process.
When armed men can take you out of your home or your car and whisk you away without a judicial warrant and without due process, it is very reasonable to be afraid.
It’s really not. Define taken away. They’ve absolutely detained some citizens, then let them go.
And again, not defending what they are doing, they are awful,but you are probably more likely to be hit by lightning than you are to have any of your family planning go wrong because of them if you are a full citizen. (If you are undocumented here right now, yeah, totally.)
Hysterical people think they are being rational and stuff like this is exactly what they say.
> They’ve absolutely detained some citizens, then let them go.
That is taken away.
Someone in my network - a US citizen - was detained, taken to a city 3 hours away, and held for 10 days before being released. Was quite a while before her family knew where she was.
If you're an American who is visibly Hispanic, it's not at all hysterical. If you're in one of those cities, you do have to worry whether you'll return home when you leave your house.
> you are probably more likely to be hit by lightning
I get that you're trying to rationalize this scenario, but this line is completely false. If there was a nation-wide wave of aviation terrorism, it would not be appropriate to say that you're "more likely to be hit by lightning" than risk your life in a plane. The situation has changed, and they're not being hysterical for observing the trends and adjusting accordingly.
Lightning has a relatively static chance of hitting you. The likelihood of feds accidentally executing you in your hometown is on the rise, and we don't know when it will stop climbing.
Do you really think you have a holographic sign floating above you that tells them you are a citizen? How are you sure you are above suspicion to be an undocumented immigrant? Could you prove you aren't if some goons decided to pick you off the street right now or next time you go for a walk?
All this is about expanding the reach and normalizing abuse of the power of law enforcement, just like back then after 9/11.
It's like Germany in the 1930s again when Jews were required to wear a yellow star on their clothes, but the other way round.
reply