187 karma · joined August 20, 2014
I don't understand, why would other models not be able to support any, or some, or even a particular single one of these? I don't even see most of these as relevant to the model itself, but rather the harness/agentic framework around it. You could argue these require a base degree of model competence for following instructions, tool calling, etc, but these things are assumed for any SOTA model today, we are well past this. Almost all of these things, if not all, are already available in other CLI + IDE-based agentic coding tools.
I wanted to try this out, so I opened Windsurf for the first time in ages and clicked the "Upgrade Available" button, which sent me to: https://windsurf.com/editor/update-linux
Did you install using apt or apt-get? If so...
1. Update package lists
sudo apt-get update
2. Upgrade Windsurf
sudo apt-get upgrade windsurf
Whle `apt-get upgrade windsurf` will technically upgrade Windsurf, instructing users to run a command that will attempt to upgrade all packages on their system is nuts when the command is provided in a context that strongly implies it will only upgrade Windsurf and has no warnings or footnotes to the contrary. Good thing I didn't ask Windsurf's agent to ugprade itself for me, I guess.EDIT - I don't want to detract from the topic at hand, however - after upgrading (with `sudo apt-get install --only-upgrade windsurf` :)) and playing around a bit, the Codemaps feature indeed seems very nifty and worth checking out. Good job!
This is effectively a strawman argument.
We are not discussing their principles that pertain to whom should be allowed to own guns, nor is that question even relevant to the heart of this topic. We are discussing the core, underlying principle that has been used as the primary justification for WHY people should have a constitutionally-protected right to own mechanized, efficient killing machines. You of course already know: the rhetoric (for literal centuries) has been that the preservation of our system of democracy from hostile internal actors requires a citizenry that has the means to effectively fight back.
Without a noble-sounding pretense of existential importance for 2A defenders to shield themselves with, things start to look a lot more like weighing "guns are fun, plus think about hunters" vs "we should reduce our yearly slaughter rate for schoolchildren to match those of other 1st world countries" and choosing the former. So, when people see what they believe to be the increasingly-obvious beginnings of authoritarian overreach in this country, and at the same time seeing most of the 2A crowd saying absolutely nothing about it, it looks like a genuinely remarkable, thoroughly nauseating display of hypocrisy and selfishness.
> But as a 2A supporter I don't feel any obligation to rage against ICE assembling a social media team. These seem to be completely disconnected concepts.
Dishonest framing aside ("assembling a social media team", like how drug cartels simply assemble a team of chemists, semantics be damned!) and with full context considered, I assume you are stating here that you see no problem with the current actions of this administration, both ICE-related and not, and have caught no whiffs of authoritarian overreach. Otherwise, social media monitoring and tracking teams within an organization that does not have the rules, oversight, requirements, or legal vulnerability of existing (previously) non-partisan agencies with similar teams, would be extremely concerning.
Though after writing this out, I'm not even clear on how much of this is a matter of opinion versus a matter of awareness and understanding of current events. One needs to only look at the events of the last 7 days to find egregious evidence of authoritarian movement, things that would've sent recent Democratic presidents into political exile and impeachment. I just learned that my neighbors and I are enemies of the US last Tuesday - literally, verbatim, "enemies from within" with no additional qualification beyond living in a blue city - for example.
Code with publicly-known weaknesses poses exponentially more danger than code with unknown weaknesses.
It's like telling sysadmins to not waste time installing security patches because there are likely still vulnerabilities in the application. Great way to get n-day'd into a ransomware payment.
It is true that he doesn’t care if people are unhappy or uncomfortable, it’s true he doesn’t care about optics, it is true that he has a set of things he wants to get done, and it’s true the first two points influence his approach to achieving the latter. However the question - the only question that matters - still remains: is this approach the most effective course of action to choose? Maybe it’s not reasonable to assert with complete confidence that it isn’t, but it is certainly unreasonable to assert that it is.
Or generally, since you say this did not deviate from your expectations, what are the past events that influenced your baseline expectation for conduct on the geopolitical stage?
> As an aspiring engineer
I’ve got some good news for you.
As far as the term 0day, I don’t think there’s much debate or contrarian opinions to be had. The only room for argument I see is between defining it as an unreleased vulnerability unknown to the vendor versus a vulnerability known to the vendor but not yet patched, basically what this article defines a 1day as.
Either way, it comes down to nitpicking nuances of definitions of commonly-used terms. I don’t think there’s much meaningful discussion to be had.