satyanash
What terminal / agentic workflows spawn the demonstrated dialogue boxes that require the User to click/reject the action? Aren't most such flows actually inline UIs? And finally, if the core issue is that these confirmation boxes are tied to the terminal that triggered them, which does not autofocus, what's the point of said "big arrow" that is also lurking behind without focus?
If the said "big arrow" automatically gains focus, isn't the real fix here to just make the dialogue boxes themselves gain focus automatically? Both are similarly disruptive anyway.
Either they aren't evil in which case they're being demonized, or they're already evil in which case demonization is redundant.
Keeping aside the motives of people, what is clear is that scale effects of AI cannot be ignored. An AI "learning" millions of pieces of content in a short span is not the same as humans spending time, effort and energy to replicate someone's style. You can argue that its 'neural nets' in both cases, but the massive scale is what separates the two.
A village is not a large family, a city is not a large village, ... and all that.
This is advice I've never seen or received. It's always been the latter, exit early, etc. Languages like Swift even encode this into a feature, a la if guards.
All this, for literally nought
missed opportunity to call it "final final"
Omission of trailing part changes the meaning and makes it clickbaity.
The fact that an "L8" at Google ranks above an OSS maintainer of a super-popular library "L5" is incredibly interesting. How are these levels determined? Doesn't this represent a conflict of interest between the FOSS library and Google's own motivations? The maintainer having to pick between a great paycheck or control of the library (with the impending possibility of Google forking).
All metrics are wrong, some metrics are useful. Finding the useful one and then recognising when it ceases to become useful is the hard problem.
Snowflake removes Spark Pushdown support in favour of Snowpark
In [PR#572](https://github.com/snowflakedb/spark-snowflake/pull/572), Snowflake has removed this feature in their spark connector without any real explanation.
This of course comes at the cost of not being able to support non-free parts of the web standard such as DRM.
> 0-1.fb.me
> 0-7.fb.me
> ...
This lists a bunch of subdomains, ideally only the second-level domain names that can be owned by FB should be listed. Because anything under that is obviously FB.IIRC git does _not_ ship diffs. It copies whole files even for the tiniest change. The compression layer handles the de-duping, which is a different layer.
2038 is 15 years away right now; this article was published 15 years before 2000.
YAGNI is not a principle. It is a contextual thumb rule. A codification of expert intuition. Exceptions to thumb rules are quite the norm. Conflating thumb rules with principles is a sign of sloppy thinking. Often engineers will misuse terminology thinking that it "doesn't matter". But it does. Think twice before claiming that something is a principle. The words you use highly influence your thought process[0].
> Perhaps the only language I've used which translates well both for terse REPLs and lengthier scripts is LISP.
Why not just use a lisp then?
Try out Ruby: so many Python syntax decisions make no sense after you see the Ruby way.
But it is not surprising given that large parts of film-making are now supported by software, which has a tendency to direct the evolution of terminology and concepts.
After a cursory glance at the model, it starts with a fairly generic set of primitives: Task, Asset, Participant, Context and Relationship. It then creates further instances based on this idea.
I'm sure other industries could also benefit from collaborative modelling of their problem domains like this.
taking your own argument into account, using "popular alternatives" is probably not the right criteria here.
Telegram is not E2E by default, so the name shouldn't even appear in any list of recommendations.
hehe, +1
leaning into it harder means understanding it better, the internals, why it works and why it does things the way it does.
Now only if our phones were lisp machines.