ChatGPT vs DeepSeek

Ja interesē lietot AI fikcijas rakstīšanā, tad DeepSeek ir ievērojami labāks:

write dialogue between browser privacy enjoyer and cookie defender.

DeepSeek domu gājiens:

Okay, the user wants a dialogue between a browser privacy enjoyer and a cookie defender. Let me start by understanding both perspectives. The privacy advocate would focus on tracking, data collection, and consent issues, while the cookie defender might argue for personalization, convenience, and the necessity of cookies for website functionality.

I need to make sure the dialogue covers key points from both sides. The privacy person might mention GDPR, consent fatigue, and invasive tracking. The cookie defender could counter with examples like shopping carts, tailored content, and the idea that not all cookies are bad. I should also include some common ground at the end to show both sides have valid points.

I should keep the conversation natural, not too technical, but still touch on important terms like third-party cookies, ad revenue, and maybe even browser settings. Let me structure the dialogue so each character responds to the other’s points, creating a balanced debate. Maybe start with the privacy person blocking cookies, then the defender explaining their necessity. They can argue back and forth, each addressing the other’s concerns, and end with a mutual understanding that there’s a middle ground.

DeepSeek R1 rezultāts:

Browser Privacy Enjoyer (BPE): clicks “Reject All” on a cookie consent banner Ah, another day, another website trying to slurp up my data. Why do they even need 27 third-party cookies just to show me a blog post?

Cookie Defender (CD): leans over You know, cookies aren’t all evil. Some of them actually make the internet… work? Like, remember your login so you don’t have to type “password123” 50 times a day.

BPE: narrows eyes Sure, session cookies are fine. But 99% of these are tracking cookies—follow-you-around-the-web, sell-your-habits-to-advertisers nonsense. GDPR made them ask for consent, but they still guilt-trip you into clicking “Accept All” with that tiny “Reject” link.

CD: Fair point on the dark patterns. But without some tracking, how do small sites fund themselves? Personalized ads keep content free. You want every news site to be paywalled?

BPE: I’d rather pay with money than with my privacy. Plus, browsers already block third-party cookies by default now. The tide’s turning—people are sick of being surveilled for a “better ad experience.”

CD: crosses arms Okay, but what about convenience? Your favorite streaming service uses cookies to remember where you paused a show. Your shopping cart doesn’t vanish if you click away. You’re throwing the baby out with the bathwater!

BPE: First-party cookies? Fine, I’ll allow those. But scripts from data brokers and ad networks? Nope. Privacy tools block those, and guess what—the internet still works. Shocking, right?

CD: sighs Not everyone’s a tech wizard tweaking uBlock filters. Most folks just want things to function. And “legitimate interest” cookies do things like prevent fraud…

BPE: …which is 1% of the problem. The other 99% is profit-driven surveillance. Look, I get it—data fuels the modern web. But the scales tipped too far. Consent should be meaningful, not a pop-up hellscape.

CD: pauses Okay, I’ll admit: the current system’s messy. But demonizing all cookies feels… reductive. Maybe there’s a middle ground? Better regulation, clearer opt-outs?

BPE: nods Now that I can toast to. Keep first-party cookies for functionality, nuke the creepy trackers, and make “Reject All” the default. Deal?

CD: Deal. But you’re still gonna have to manually re-add items to your cart if you clear cookies every 5 minutes.

BPE: grins A small price to pay for salvation.

CD: mutters …says the person who’s never worked in e-commerce.

BPE: already typing “how to disable cookies entirely in CSS”

ChatGPT o1 rezultāts:

Privacy Enjoyer: I’m telling you, all these browser cookies are just mini surveillance trackers. They store our every move!

Cookie Defender: Well, that’s an exaggeration. Cookies can actually improve your web experience—remembering login states, saving cart items, personalizing content. They’re useful tools.

Privacy Enjoyer: Useful? That’s a slippery slope. If websites save my preferences, that also means they know my behaviors. And if they know them, they can exploit them.

Cookie Defender: Exploit is a harsh word. Companies rely on cookies to understand user behaviors—yes, that means more targeted ads, but it also means faster page loads and relevant recommendations. It’s not all doom and gloom.

Privacy Enjoyer: So I’m supposed to willingly hand over my data for convenience? That’s too big a price. I’d rather log in manually every time than have my actions tracked.

Cookie Defender: You can always use settings to limit cookie storage—like blocking third-party cookies. But first-party cookies, especially from the sites you trust, often give you a more seamless experience.

Privacy Enjoyer: I’m all for convenience, but I’d prefer real privacy. The trade-off isn’t worth it if it leads to being targeted at every corner of the internet.

Cookie Defender: True, excessive tracking can be intrusive. But responsible use of cookies is about balancing privacy with a smooth user experience. Not all cookies are evil, you know.

Privacy Enjoyer: Maybe. But to me, the best cookie is the one that doesn’t even exist—unless it’s homemade chocolate chip.

Cookie Defender: (Laughs) Fair enough. Just remember that the digital kind can sweeten your online experience—if handled responsibly.

Privacy Enjoyer: I’ll keep my guard up. No offense, but I like my digital cookie jar close to empty.

Cookie Defender: Understood. Just know there’s always a middle path: adopt privacy tools, adjust your browser settings, and keep a balanced stance. No need to go to extremes.

Privacy Enjoyer: I’ll try. But I’m still clearing my history and cookies before I shut this laptop off.

Cookie Defender: And that’s your right—privacy for the win! Keep fighting the good fight, but remember it’s not always us versus them. Sometimes, it’s about finding the right recipe.

(They exchange a friendly nod of respect—before heading off to their respective sides of the web.)

1 Like

Uzreiz nepievērsu uzmanību. Toč, mazākie modeļi ir balstīti uz llama vai qwen2.

Es pārgāju pie Codeium, kad viņi vēl piedāvāja par 10$ bezlimita promtus. Tas šķita galvas tiesu izdevīgāks variants, lai gan tagad tur sāk parādīties pieprasījumu daudzuma ierobežojumi un cenas kāpums. Pricing | Windsurf Editor and Codeium extensions Man vēl šie prasa 10$ mēnesī.

Salīdzinājumā ar Github Copilot tur lielais pluss bija, ka vari izvēlēties starp dažādiem modeļiem un tu neesi ierobežots tikai ar kodēšanas jautājumiem.

1 Like

Every time we let AI solve a problem we could’ve solved ourselves, we’re trading long-term understanding for short-term productivity. We’re optimizing for today’s commit at the cost of tomorrow’s ability.

Goddamn that’s so well said!

Thankfully, I’ve never used AI for programming, and only a couple times for anything at all.

1 Like

Principā tu to pašu vari teikt par StackOverflow koda aklu kopēšanu. Nekas super jauns pēc idejas nav. Ieejas barjera tik ir kļuvusi vēl zemāka.

2 Likes

Es neredzu mīnusus, tehnoloğijām ar laiku japaliek vienkaršākam. Tas tapēc, lai cilvēki izmantojot tehnoloğijas nepaliktu pa robotiem. Hyperfixation is real amongst IT tā nevajdzētu būt godīgi sakot… alot IT people are like this:


Should i tell why its bad? Nah life isnt about one thing…

1 Like

@Arnissan es ar patestēju chatgpt un deepseek. abiem to pašu uzdevu, interesanti, ka deepseek ir izsmeļošāks, more human-like ar atbildēm, bet nu jau arī serveris karās, jo pārāk daudzi lieto reizē ;D

2 Likes

Atbild aij " Nē nu jā, nu pašlaik man tā grūti pateikt, zini es padomāšu un vēlāk padošu ziņu. Tu tik atgādini"

3 Likes

Es copilot tikai IDE autocomplete lietoju, parasti nepromtēju. Nezinu vai citi modeļi piedāvā ko tādā pašā līmenī vai labāku tieši autocomplete ziņā. Būs jāpainteresējas. Promptēju primāri ChatGPT o1 arī programmēšanas jautājumos, jo cik zinu, tad reasoning modeļi caur IDE ir pieejami tikai caur API, kur jāmaksā par tokeniem.

Agrāk eksperimentējot ar GPT4 API tas sanāca visai dārgi, un jaunie reasoning modeļi ir vēl dārgāki. R1, iespējams, tagad ir gana lēts arī API lietošanā, bet pēc mana ātrā testa rezultātiem ChatGPT o1 ir spēcīgāks par DeepSeek Unity dziņa programmēšanas jautājumos.

Cilvēki tāpat pēc 8-12 mēneši neatcerās, ko pie velna paši rakstījuši. Ja tavs rakstītais kods un AI kods ir vienlīdzīgi lasāmi, es neesmu drošs ka kaut kas tiek zaudēts. Un ja kāds AI kodu nesaprot, to nevajadzētu lietot.

Līdzīgi arī varētu rakstīt par grāmatvežiem, kalkulatoriem un viņu matemātikas spējām.

Jā, DeepSpeek nav tik ļoti sanitizēts, kā ChatGPT. Šķietami mazāka apsēstība ar amerikāņu politkorektumu, kas to padara lietojamāku prozas ģenerēšanā.

Bet zini, kas ir creepy? ;D
Paprasīju, vai Taivāna ir independent democratic country :skull:

3 Likes

Tas gan, jā. Viņiem ir jācenzē un jāatbalsta CCP propaganda, vai arī jāmirst cietumā un/vai zem orgānu tirgotāju skalpeļiem. The joys of living under authoritarian governments.

1 Like

sarēcos:

3 Likes

Ai.

3 Likes
1 Like

WTF? Es atceros kodu, kuru rakstīju un lasīju pirms 15 gadiem.

3 Likes

Varbūt atkarīgs no jomas vai arī tev vienkārši labas dabas dotas smadzenes. Nevienā projektā man kods neatkārtojas, tagad iet 3 projekti paralēli, katram citas prasības, citādāka implemetācija, arī no Unity dziņa versijas daudz kas mainās, kādi packages ir pieejami, utt. Man vajag laiku, lai ielektu kodā no gada un vairāk atpakaļ. Bet nu man arī ir slikta ilgtermiņa atmiņa, kaut kas ar ADHD un trauksmi saistīts.

1 Like

Es domāju, ka manā gadījumā no jomas tas nav atkarīgs.

Man ar ilgtermiņa atmiņu būtisku problēmu nav, man ir tikai ļoti agresīvs garbage collector :smiley:
If I don’t need it, I tend to forget it WAYYY too quickly. Except then it turns out I did actually need it… :sweat_smile:

Q: is it normal to forget code you’ve written a year ago?

ChatGPT o1:

Yes, it’s completely normal. Once you’re no longer actively working with a particular chunk of code, it’s easy to forget the details. The important thing is that you left enough clues (descriptive names, comments, documentation) so you can quickly recall or figure out what it’s doing when you revisit it. Having well-structured, self-documenting code and good commit messages also makes it a lot easier to jump back into a project even after a long time away.

DeepSeek R1:

Yes, it’s completely normal to forget code you wrote a year ago, especially if you haven’t revisited or maintained it regularly. Here’s why:

1. Memory and Use It or Lose It

Human memory naturally fades details over time unless they’re actively reinforced. If you haven’t worked with that codebase in a while, the specifics (like syntax, structure, or edge cases) become harder to recall. This is a universal aspect of how our brains prioritize information.

2. Complexity and Context

Code often reflects context (e.g., project requirements, deadlines, or team decisions) that might no longer be top-of-mind. Complex logic or poorly documented systems are especially easy to forget because they require mental effort to reconstruct.

3. Constant Learning

Developers learn new tools, languages, and patterns over time. Your brain prioritizes current knowledge, which can overshadow older work. This is a sign of growth, not incompetence!

4. Focus on Problem-Solving Over Memorization

Coding isn’t about memorizing every line—it’s about understanding how to solve problems. Even if you forget specifics, the core skills (debugging, architecture design, etc.) remain and can help you relearn the code quickly.


How to Mitigate This (Without Panicking):

  • Documentation: Write clear comments, READMEs, or architecture diagrams. Future-you will thank past-you.
  • Code Reviews: Discussing code with others (or even your past self via notes) reinforces understanding.
  • Revisit Old Projects: Periodically skim old code to refresh your memory and improve it with new insights.
  • Version Control: Use tools like Git with meaningful commit messages to track changes and reasoning over time.

Bottom Line: Forgetting code is natural and happens to everyone—even senior developers. It doesn’t reflect your skill level. What matters is your ability to relearn and adapt, which is a core part of being a programmer. :blush:

+1000 social credit

2 Likes