When its not optional to publish email only, the proposed solution is pretty reasonable imo.
When its not optional to publish email only, the proposed solution is pretty reasonable imo.
Does it actually improve the pairing experience? I am skeptical it will make any difference.
You can definitely ‘chat’ with copilot, like other llms as well as the inline editor auto complete.
I have been able to live with everything else, but this is the one that kills me every time.
Yeah. That post has over 900 comments, which is rare even for an Ars article. Mostly negative sentiment, which I get.
The OP discusses exactly a solution to the anyone setting up an instance to capture the data, because the users home instance federates their votes anonymously.
There maybe flaws in it, not that’s exactly what it aims to solve.
This is the main thing preventing me, and probably a good amount of other folks, from using alternative roms. If I can get all the apps I need to run, then I can’t use the rom, even if I would prefer it.
Not seeing it on f-droid yet.
I do not like this prediction, because it seems like a plausible reality. Which would be awful.
It’s a balance, but too many people don’t even flag it to management because they’re lazy and they write shit and ship it to get it off their own plate.
Now, if management says ship it anyway it’s a balance of you as a developer making sure they understand they’re throwing this technical debt on the credit card and it may (probably) need to be paid off later. If you fail to articulate the interest that’ll be due later then you didn’t do enough or management is bad.
You shouldt work unpaid to fix it, but sometimes you should just do it right even if it takes longer because it’s how it should be done.
I have done it as my main job and I echo your sentiment. It’s inevitable that sometimes you have to meet a deadline or get something more important working first, but if you write bad code because you are lazy or unwilling to read the docs to do it right, shame shame shame.
It’s a never ending onslaught of beginner questions and experienced folks with domain knowledge burn out. I’m sure it’s good when it’s new and fresh and everyone is exited to participate, but that wears out. It’s why things went away from mailing lists, or why mailing lists started getting archived, so they could be searched.
I guess with most things it comes in cycles, and we’re at the on demand answers cycle right now.
Ephemeral discord servers are awful because they don’t scale and they can only ever help the lowest common denominator of questions/issues. We need something else, but it has yet to present itself as a solution.
Regarding obsolete models, that’s only partially true. There’s loads of content that are effectively “finished” and won’t be changing, and will grow obsolete at a fairly slow pace. Meaning they’ll be useful in the models once trained for years.
Obviously new technology and similar ideas/content that didn’t exist when the model was created won’t be there, but the amount that changes and or is new is relatively small each year compared to all the historical content.
Nah. They will cross licence with the other big players effectively closing the market to anyone they don’t bless.
How’d that work out for them? Answer? Not well. History repeats itself, so here we go!
To them it’s a feature, not a bug.
I’m sure there are projects covering those areas written in JavaScript.
This is fantastic. Been waiting for this for years.
Had to jump into the Web app to see if it was really there, and it was and worked just like they said it would.
Should is the key word here. You pay a lawyer to find out, which probably isn’t worth it.