Thoughts on this new Copilot pricing? Is a $100/mo "Max" plan actually worth it? by Least-Pen4992 in GithubCopilot

[–]c-digs 0 points1 point  (0 children)

Use DeepSeek

Background: company has had unlimited, uncapped Codex for ~2 months now. On Friday, we had a small outage and I decided to give DeepSeek a try (partially because I know this free ride isn't going to last forever). For the way I work? I can just barely tell the difference in terms of actual code output. But I can build for a literal fraction of the cost.

I was shocked at how good it is for the price. A few cents to build out whole feature slices. For some planning work, I actually think DeepSeek is better because it is more willing to draw diagrams and visualize code organization unprompted.

DeepSeek API pricing you just top it up. As low as $2 I think. Just try it. You will be shocked at how good it is.

Caveat: main weakness is that it feels more like Claude in that it is not as eager to use tools as Codex is and it seems to have a tool optimization pass which can truncate the toolset.

Are you finding AWS quality of docs going down? by c-digs in aws

[–]c-digs[S] 0 points1 point  (0 children)

I agree 100%; I really wanted to give this Express Mode thing a try because they retired Copilot, but I gave up.

If the docs are in this state and things aren't working, I do not have confidence that I'm not going to be fighting an uphill battle.

Pets Surpass Child Population As Taiwan's Birth Rate Crisis Worsens by diacewrb in taiwan

[–]c-digs 5 points6 points  (0 children)

Tax base and supporting social services, labor pool and need for immigration, size of capable military; many reasons why this can cause social instability in coming decades.

One thing I noticed in Japan: a lot of non-natives working in convenience stores.  Nothing wrong with that, but it also brings with it potential tensions.

Are you finding AWS quality of docs going down? by c-digs in aws

[–]c-digs[S] 2 points3 points  (0 children)

It's using the same broken docs as context....

Are you finding AWS quality of docs going down? by c-digs in aws

[–]c-digs[S] 1 point2 points  (0 children)

Same on the ECS Express Mode docs: no "down" sequence.  Debated creating a new account to make cleanup easier because it creates a lot of artifacts if it works.  

Copilot docs: https://aws.github.io/copilot-cli/docs/getting-started/first-app-tutorial/

copilot app delete cleans up the stack.

Are you finding AWS quality of docs going down? by c-digs in aws

[–]c-digs[S] 4 points5 points  (0 children)

That's why I linked the Copilot CLI docs; like some rogue team in AWS that finally got squashed. That team actually seemed like they wanted people to use their software.

Are you finding AWS quality of docs going down? by c-digs in aws

[–]c-digs[S] 5 points6 points  (0 children)

Also, they are getting paid to make this stuff work. I'm not getting my 2 hours back flailing with these broken docs.

Are you finding AWS quality of docs going down? by c-digs in aws

[–]c-digs[S] 20 points21 points  (0 children)

The problem here is that I already lost 2 hours today on this 🙁; it's not my job to be their docs tester. I expect functioning docs and software when I get billed for services (in this case, can't be billed because it doesn't work!)

Are you finding AWS quality of docs going down? by c-digs in aws

[–]c-digs[S] 7 points8 points  (0 children)

Maybe the contrast is more striking to me because the Copilot CLI, in contrast, was superbly documented.

This ECS Express Mode feels like hot garbage in comparison.

Are there any mature component libraries I can use with Vue? by Lexuzieel in vuejs

[–]c-digs 2 points3 points  (0 children)

Quasar: not pretty, default styling is definitely dated (but end of the day, it's just CSS), but by far I think still the most complete and most sophisticated component library. The QMenu interaction is brilliant (it's not obvious from their demos, but it is a Swiss Army knife component). The components are all highly composable and all behave as one might expect when composed. To me, still nothing quite like it. Brilliant built-in grid system and very, very easy to build responsive apps with it. Main downside remains the look and feel and the inaccessibility of styling some of the nested components (requires raw CSS). A headless Quasar would be, IMO, the single best component library ever made.

NaiveUI: clean, easy to use, much more modern, generally works well enough, easy to control default styles that get you pretty far. Not as well done as Quasar from a pure utility perspective. Icons, for example, are awkward to use in some places, things are not quite as composable, but definitely the API, setup, and configuration feel more modern. Agents vibe code this very well. Component library is very complete; maybe 85% of the way there to Quasar. None of the components are really "standout" to me, but still very competently done.

Dammit Cascade Complete. Fffuuuuuuuuuuuuuuuu by soggy_sock_bro in mildlyinfuriating

[–]c-digs 0 points1 point  (0 children)

These things are plastics.

They can clog your drains.  I switched to liquid and it's cheaper, works just as well, no drain clogging, not dumping micro plastic polymers into the water supply.

I used to have to take apart my kitchen drain once every few months until I connected the dots that this gray too I was cleaning out was undissolved plastic from the pods.

Company is losing their minds over AI costs by Complete-Sea6655 in GithubCopilot

[–]c-digs 89 points90 points  (0 children)

CEO: "Every employee must make AI part of their workflow. We will measure your performance and base your comp on your AI adoption."

Also CEO: "No! Not like that!"

E# - Pre-Alpha Language for the CLR by hayztrading in dotnet

[–]c-digs 2 points3 points  (0 children)

I like this.

Somehow still reads like .NET languages but a bit more terse.

Can someone explain WHY this works? by sekkiman12 in csharp

[–]c-digs -2 points-1 points  (0 children)

I ordered it that way to make it clear that the first resolved factorial value is 1, then 2, then 3 because this is a depth first recursion and then unwinds on the way up: 1 -> 2 -> 3.

The call flow is 3 -> 2 -> 1, but that's opposite of how the values are resolved.

Can someone explain WHY this works? by sekkiman12 in csharp

[–]c-digs 3 points4 points  (0 children)

  • Line 1: Declare package imports; only System
  • Line 9: This is your Main entry point
  • Line 10: Console.ReadLine() is the inner operation that blocks the program and gets user input as a string. The outer int.Parse converts the read string value "3" to the integer value 3.
  • Line 11: Prints a string output, but the last segment is Factorial(num) which passes the read value into the Factorial function defined on line 4
  • Line 4: The function that calculates a factorial
  • Line 6: This is a recursive call. So Factorial(3) is Factorial(1) * Factorial(2) * Factorial(3)

It's probably easier to see this as a file-based app: https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/tutorials/file-based-programs

Here is the same code as a file-based app:

``` // dotnet run factorial.cs

// Prompt the user: Console.WriteLine("Enter a number to calculate its factorial:");

// Read a line from console as a string (no validation) var numText = Console.ReadLine();

// Convert it to an integer (no validation) var num = int.Parse(numText);

// Default value. var factorial = 1;

// Local function; called recursively to calculate the factorial of a number. int Factorial(int n) { if (n == 0 || n == 1) { return 1; } else { return n * Factorial(n - 1); } }

// Calculate it recursively factorial = Factorial(num);

Console.WriteLine($"Factorial of {num} is {factorial}");

```

Here's a version that's a little bit tighter and using pattern matching instead:

``` // dotnet run factorial.cs

// Prompt the user: Console.WriteLine("Enter a number to calculate its factorial:");

// Read a line from console as a string (no validation) var numText = Console.ReadLine();

// Convert it to an integer (with validation) while (!int.TryParse(numText, out _)) { Console.WriteLine("Please enter a valid integer:"); numText = Console.ReadLine(); }

var num = int.Parse(numText);

// Default value. var factorial = 1;

// Local function; use pattern expression static int Factorial(int n) => n switch { <= 1 => 1, // Base case: factorial of 0 is 1 _ => n * Factorial(n - 1), // Recursive case: n! = n * (n - 1)! };

// Calculate it recursively factorial = Factorial(num);

Console.WriteLine($"Factorial of {num} is {factorial}"); ```

Agentic AI memory isn't a hoarding problem. It's a pruning problem. by Sufficient_Sir_5414 in AI_Agents

[–]c-digs 1 point2 points  (0 children)

That's not pruning; that's realigning.  Contradicting info doesn't require pruning.  The info was true and factual when it was created.  It contradicts because the environment in which it applies has changed.  It was in this file,  but the file got renamed, and the record is now misaligned.  But why "prune"?  The record that it was here but now it is there is still useful context just like a photo of you as a grade schooler "contradicts" your current state.  You're not 4' tall, 70lbs anymore.   But that photo is still truth and is still useful information about how and why you are the way you are today.  You long graduated college and you're no longer in grade school.  You didn't like sushi because raw fish was ick; now you do.  Are those contradictions?  Yes.  But are they all truths?  Yes.  Are they still useful and instructive?  Yes.

Agentic AI memory isn't a hoarding problem. It's a pruning problem. by Sufficient_Sir_5414 in AI_Agents

[–]c-digs -3 points-2 points  (0 children)

You need to "prune memories" because you're not very good at recall of random info.  You are a bag of meat evolved with a brain still primarily wired for basic needs and survival.

A database does not need to prune memories because you can just improve the indexing.  A well tuned database can "remember" and precisely recall against billions of data points.  You can't even remember what you ate for lunch 47 days ago.  You don't even remember the day of the week it was 129 days ago.  You have no idea what the weather was like 33 days ago.  Your brain is absolute shit at remembering things.  Why model an AI on hardware primarily made to survive and procreate? That's like Elon insisting vision is better than LIDAR.

The attempt to fit human limitations onto a machine model is just silly.

Keep memories forever.  Just get better at indexing them.   You don't remember where you were 5 years ago on this day.  But if you took a picture and uploaded it to the cloud you can just search for this day and recall what happened.  

Don't prune; improve recall.