skysight-inc/HackerNews huggingface dataset:
> Unique Debugging

That caught my eye. How do you people debug C (on Linux) ? I'm tired of switching constantly between Sublime and GDB. I know there's a GDB plugin for Sublime but it's a pain to configure.

I need to edit my code AND set breaks in the same GUI window. There is DDD but it's old and odd looking. Tried Kate also but for some reason didn't like it.
Twitter is used by about 5% of online people. They're an obnoxious 5% but they're really not that big of a group. I mean, Microsoft has about 25% of online users. Facebook has bout 35% of online people and Google has almost 60% of online users. Twitter is tiny.
I'd rather enforce it at the repo then hope and pray everyone updates their global configs.

Easy enough to catch but you'll miss some. Literally no cost to adding it to repo config either
> Presumably if the location history data is stored on-device in a format accessible to the user

Except it won't be, because this is Google we're talking about. They'll find some bogus security or privacy reason to keep the data encrypted and inaccessible to end users except through their blessed app, and it will only be transferable through a "backup" feature that's explicitly designed to allow for provisioning new devices without, at any point, giving you actual access to your own data you "backed up".

Like it's with all the other stuff Google manages on Android now.
IDE-specific files aren't necessarily auto-generated. They might include project-specific configs (random examples that come to mind include linter configs, tab/space indent settings, C library include paths)
Everyone is free to pick a proverbial hill to die on.

Some focus on battles they are likely to win, others on battles they are bound to lose.
missed this in the readme. you can edit that in the user preferences file - https://github.com/sentient-engineering/jobber/blob/main/job...
Germany has a bleak economy currently , definitely not leap frogging anyone but definitely no scammers on young Germans finishing their diplomas.
Do you think these scammers are a healthy sign of the Chinese economy ?
Yeah, the article's point is also that you need both:

> The contents of the repo’s git ignore is for the project only files and folders. Developers can customise their own global git ignore with extra exclusions they need.

The two gitignores are for different purposes. The user-specific gitignore (~/.gitignore, or ~/.config/git/ignore) is tailored to the developer's specific workflow and preferred tools, so for example, a Vim user would have different rules from an Emacs or VSCode user.

The project-level gitignore(s) are for build products. For example, if the project's build scripts create a "build" directory for all the build products, "build/" would probably be in the project's .gitignore.

It doesn't make sense to put editor-specific stuff in the project's .gitignore because the editor or IDE a contributor chooses to use to develop the project is orthogonal to the code in the project.
I have used vo=gpu-next, actually. Still green/purple.

"I" shows: Primaries: bt.2020. Colormatrix: bt.2020-ncl. Levels: full. If that means anything.
Thanks! Yes I've read his stuff and basically all discourse online since ~2005 when I wrote my first web app version of Manabi. I was also heavily influenced by the Breaking into Japanese Literature book and similar ones which had translations of words and pages, sometimes additional explanations, for short stories from Akutagawa etc. (as I've included in the Rashomon EPUB in Manabi Reader)

I don't know how to contact Khaz sorry I've never talked w/ him. There's a subreddit dedicated to his approach r/ajatt so you might find leads there. I'd also check archive.org of course

If you try out my apps pls drop any feedback, easiest is Discord (chat or issue tracker) https://discord.gg/4aF9yuASzb Thanks - recently went full-time on this so looking to grow it quickly and have lots more on deck
In my Laravel projects, there are a few packages of much more niche/hobbyist origin without corporate backing, some haven’t been updated for a while, and others are perfectly fine and don’t need much maintenance.

Normally, packages are listed in my composer.json and stored in vendor/. For those packages, I created a separate folder called vendor_private/ which is part of my Git tree, put copies of these weird little packages in it, and set up my composer.json to consider that folder a repository.

Works like a charm. My big important packages are still upstream. I can customize the little ones as needed to fit better, or have better code, and not worry about them going unmaintained. It’s also way quicker than copying the files individually out of the package and into the right places (along with updating Namespaces, configuration, etc.) Once in a while, I’ll go back and see if anything worthwhile has changed upstream - and so far, it never has.
There is a cap implied. The only reasonable reason to hold the property is for evidence. Once the statue of limitation runs out, or the appeals process is exhausted, there is no reasonable reason to hold the property anymore.
This seems like a terrible idea.. imagine framework A that has a throwaway folder called ".blah"—now imagine framework B that has a very important configuration folder called ".blah"—so at best this would only cover IDE and OS stuff. But that stuff ends up being like what, 10 lines at most?
I've recently realized that one can effectively cross-ventilate studio apartment by adding to their mail slots a PC-fan filtered by small HEPA-filter (to remover outdoor odors) combined with a window-attached ventilator pulling air to outdoors, possibly with a normal fan in the middle of the studio. Feel free to Kickstart this.
Why not? It's caching the state of the model after the cached prefix, so that inference workload doesn't need to be run again.
I'm not sure about that. We had a new hire once add a ton of .DS_Store files because we forgot to ignore it at the repo level and they didn't have a global ignore set up. I don't see the point of committing files that have no purpose in the repo, especially these ones, that could change between users age potentially polluting the diffs. We added it to the ignore list and removed the files
So it had debt. How will they finance the rebuilding?
Using a user gitignore file works if you’re responsible for your development environment. This does not work for other developers who are not responsible for their development environment.

The first place to catch errant build files and artifacts from entering the repo database is the .gitignore file. The second place to catch them is the PR. The .gitignore prevents repetitive file adds from entering the PR.

What I don’t want to see in an enterprise environment is someone checking in a 100MB binary file that gets checked into dev because the team was busy and approved a PR hastily. What would be helpful is a git hook that checks the mime type of a file and decide if it should even by a type of file that should be checked into a project.
Thank you for the detailed feedback, I really appreciate you taking the time and effort.

Yes the title is a little bit controversial
Life and death of Java asynchronous network programming
I'm "that guy" that questions everything, leaving no stone un-turned and no assumption unquestioned. I came to this point after being told that saying "no, here's why" all the time made me "difficult to work with".

New lesson learned: They don't like you questioning everything and being super thorough either. And no matter how politely[1] you say it, they think you're difficult to work with too. The decision to rewrite, or do something a certain way was made by someone that is "in the decision room", and they'll play along with you for a while, but you best eventually acquiesce to the way they want it done.

Being a bit more meta about it: I'd say the real problem is that the tech field has ridiculous levels of "flat hierarchy". In this case it means that simultaneous everyone and no one has a say in any one particular decision. And even if there is a title for whatever responsibility or area you are to have final say in, there is always the room for suggestion and criticism, which means you have to "consider it". Thus opening the flood gates of all this non-sense.

[1]. I don't even know the word to use here. Politely doesn't do it justice to how much I have to bend over backwards to be considerate, calm, and appreciative of everyone.
You actually can cache the "output" of a transformer on the prefix by caching what happens in the attention layer for that text string (specifically the "K" and "V" tensors). Since the attention layer is a big part of the compute cost of the transformer, this does cut down FLOPs dramatically.
I've tried it a few times, and each time there's been something missing that was too irritating to live without - stuff like git integration, or extensions that I use a lot. It's nice, but I don't really notice the speed much once the application is open and running, and so I just ended up back at vscode every time.
Vlog: One year of hut life (feat. Atlas singing) [video]
not sure I agree with the article or not, just wanted to state there's a third option: you can define your ignore rules per project but not necessarily share the, by putting the ignore rules in:

.git/info/exclude
Jetbrains' .DotSettings file is a specific example. It contains things like project specific dictionaries for the IDE's spell checker.
The transformer only looks backwards, so if the first part of the sequence (the prompt) doesn't change, you don't need to rerun it again on that part, just on the part after it that changed. For use cases with large prompts relative to the output size (e.g. lots of examples in the prompt), this can significantly speed up the workload.
Neovim has felt frustrating. I still sort of manage a Neovim configuration, but have been gradually moving to Zed as well. (Similar reasons overall.)

I think everyone has their own personal list of gripes and wants for a text editor. Here's some issues that I think many people will immediately be struck by:

- Zed does not yet support EditorConfig. https://github.com/zed-industries/zed/issues/8534

- Zed does not yet support auto-detecting indentation in the current file. https://github.com/zed-industries/zed/issues/4681

- Zed does not yet support configuring indentation in the current file. (edit: clarified wording) https://github.com/zed-industries/zed/issues/4867

- The core editing experience is still less polished than Monaco. Example: Selecting a block of spaces and striking "delete" may lead to an uneven number of characters being deleted. It seems to interact poorly with indentation.

- No settings UI (yet?).

As a Linux (and specifically NixOS) user, there's also a few other problems that I would love to have solved:

- Zed can't be configured to not auto-update, which can simply never work on immutable distros or e.g. inside of Flatpak. It just tries and fails, wasting bandwidth. https://github.com/zed-industries/zed/issues/9224

- Zed can't re-use all already-installed language servers yet, so some language servers can't be used on platforms where the auto-download feature can not work. https://github.com/zed-industries/zed/issues/4978

- Zed doesn't really integrate well with direnv. VSCode is in the same boat, but Vim is not. https://github.com/zed-industries/zed/issues/4977

Overall Zed has been very nice. It definitely feels like it's still pre 1.0, but it is a very strong pre 1.0 to me. I am a bit weary on the focus on collaboration and AI features so soon, but I do realize that people actually like these features, so hopefully it's not a sign that the core editing experience is going to be neglected.
Missing benefit: Libraries are a way to distribute and share the costs of labor, resulting in a more efficient ecosystem.

This doesn't apply to micro-libraries, but it looks like that cost/benefit list is intended to cover libraries in general.
>Sometimes vagueness is a necessary lubricant to get enough agreement on something, but I take your point.

Seems to me that a vague law is simply an invalid law. The rule of law requires the clear knowledge of what exactly is illegal, if that isn't clear then its simply a prospective law that doesn't meet the basic requires to be law.
This looks like a great task queue, I'm a massive proponent of "Postgres is all you need" [0] and doubling down on it with my project that takes it to the extreme.

What I would love is a Postgres task queue that does multi-step pipelines, with fan out and accumulation. In my view a structured relational database is a particularly good backend for that as it inherently can model the structure. Is that something you have considered exploring?

The one thing with listen/notify that I find lacking is the max payload size of 8k, it somewhat limits its capability without having to start saving stuff to tables. What I would really like is a streaming table, with a schema and all the rich type support... maybe one day.

0: https://www.amazingcto.com/postgres-for-everything/
Autoregressive models can't just resume so they have to re-parse the entire prompt again for each execution.

By caching them they resume from where it left off from before thereby completely bypassing all that computation.

For large contexts this could save a ton of compute!

I think this feature and structured outputs are some of the biggest inventions in LLMs this year.
First time hearing of Orkut, what was it?
The account creation process is free and takes just a few seconds. If you use Google to log in, you can access Raven immediately. For email sign-ups, you’ll receive a login link right away and it's just an extra click.

Nevertheless, I understand your point. We agree that having the option to try the app without creating an account would be ideal, and it's in our roadmap.
Once they're committed into the repository, they're no longer ignored, so what's the problem? The IDE files being listed in a hypothetical developer's global .gitignore do no harm in this case.
Pretty common. This sort of mistrust is one reason people oppose red flag laws that require seizure (before even being tried, and without the protections of the criminal system).

On a side note, how did they find the money? Or was this an expensive lesson in why not to consent to a search?
not sure what you mean by this, can you explain more?
Committing stuff to the repo means work for other people (namely the reviewers).

And to find the answer to “why is it a problem that there's a .sublimetext line in the .gitignore” then ask yourself the question “why is it a problem if there's a .sublimetext file committed to the repository”. Why even bothering to add it to the .gitignore when you can just commit the file?

Why do you think the second scenario is an issue and not the first?
The mergers often also end up making the respective products worse, and reducing competition.
What‘s an example for „latest functionality“ or „best practices“ that should or could possibly change for a function like leftPad and that would not automatically happen by virtue of being in the code base (such as formatting)?
I'm not taking an absolute position either way -- the devil is in the details -- but here's my steelman for the opposing view:

When you put something in the standard library, it's harder to take it out, meaning that you're committing development resources to support the implementation. Furthermore things change: protocols and formats rise and fall in popularity and programming style evolves as the language changes (e.g. callbacks vs. promises in JS).
Therefore the stdlib becomes where libraries go to die, and you'll always have a set of third party libraries that are "pseudo-standard", like NumPy in Python.

Having a minimal stdlib lets you "free-market" the decision, letting the community effects take care of what is considered standard in the ecosystem, and lets you optimize its minimal surface, like what happened with C.
> and i don't think there's anything wrong with it.

except all the legal ways you can't fire someone. Sexism, Racism, Ageism, and maybe Sexual Orientation (may not be Federal) are the big 4 reasons why this can't simply be a social contract. And there's more subtle but not illegal ways you can screw yourself over like Promissary Estoppel, because you can't just hire someone and fire them the first week "for whatever reason" and think that's not open for abuse.

>when you say "click-or-be-fired" it seems shocking. rephrase it into "agree to our new terms going forward, or we will not renew". i have zero problem with that if that was the situation that was originally agreed to.

"I have altered the terms, pray I do not alter it further".

These aren't even labor laws. This can be extortion or retaliation. Neither of which are exactly squeaky clean. Or it could be a simply breaking of contract (e.g. your contract says WFH and now they want to force RTO you). If there's no protection nor reparation on the employer side for breaking a contract they can remake at anytime, it may as well be handcuffs instead.
All devices with the name Game Boy have some level of temporal smearing. It’s just that the newer devices’ display lag might not be perceived by everyone.
Not a very popular position among Apple users because everything must come only from the App Store for some reason

Because "security" is a great marketing point and they've bought into that completely, thinking that trusting Apple and having it control your life is a good thing.
'We need to define our future': Little Tokyo evolves and survives
Listened to this yesterday. Super enjoyable. Made the point that electricity in the future will be consumed much closer geographically to where it is generated than today - and so we probably don’t need huge interconnects - but much less close in time (because batteries).
> For MySQL, for smaller deployments, I've found Galera to really be a handy HA system to get going:

Well, at least if you don't value your data.

(https://aphyr.com/posts/327-jepsen-mariadb-galera-cluster; Galera failed Jepsen testing in 2015 and the bug is still open with a 2022 mention of basically “we have experimental support [for actually providing the data consistency we promise], but it's not clear if it's worth it because it will be very slow”)
Ignoring .env files globally could prevent some mistakes.. :D
I am suggesting we separate project specific and developer specific git ignores - I don't think you read the article
Congress has no reason to care. They certainly aren't subjected to any of the shady tactics. Most of their constituents aren't either. Just the edge cases, but nobody cares unless they find themselves in it.
Hadn't seen magentic before this comment, super cool! Would love to do a comparison blog post -- I'll reach out about this separately :)

re: scope:

I think anything one layer above the base provider API is definitely in scope. A lot of these APIs are autogenerated (e.g. stainless), so I see a lot of value in building language-specific tools (starting with Python, likely JS/TS next) to improve developer experience at this single step up layer (e.g. tools, structured outputs, state across calls, streaming, etc.).

I care deeply about cutting the amount of time people have to spend on things that ultimately aren't the value adding aspects of their work (like maintaining an internal tool), and I think the (coming soon) future of AI-native applications will need this more than ever. Essentially anything that could be considered boiler-plate or unnecessary repeated code is something I want to improve without removing/reducing control and transparency -- I want to build useful abstractions that aren't obstructions.

I also thing it's important to do this through a provider-agnostic interface given how frequently a new "king" pops up.

re: long-term vision:

more support for various providers/models + tools and agentic flows are definitely top of mind here, but to be honest I'm not fully certain what this AI-native future looks like, so I'm keeping an open mind about where to direct efforts. I'm hopeful usage and feedback from building in the open will help further guide this process.
Object Pascal, Memory Safety, the US Whitehouse and Future Programming
The History of Windows 2000
Thanks for taking the time to write the article! We need more people sharing their good ideas like this.
How would they know? Are they monitoring your code writing?
Let's hope that people who resort to clickbait titles never complain about dark patterns in software, because what they do is analogous, they're tricking me to their advantage.
Sure it is, no one is arguing against that. The process includes a constant check against the Constitution and its core values and whenever a conflict is found the law or act is just nullified.

See the Italian constitutional court as an example
https://en.wikipedia.org/wiki/Orkut
I think part of Russia and Iran making moves right now is that, like the Dutch, they're seeing the window of opportunity for selling fossil fuel closing, and they're settling long-term grievances while the rest of the world still needs their resources and can't isolate them like North Korea.
Or you could have taught them how to add the ignore file on their computer so they won't be making the same mistake in any other repo or other projects…

And you could have used the opportunity to teach them about using a version control altogether and how it they aren't supposed to just throw git commit -am "fix stuff" at every problem!

The fact that they committed the .DS_store files shows there's a much deeper problem with how this employee works that something you can work around with a .gitignore file. Now the problem has just been hidden under the rug.
So glad someone’s here saying it. I am absolutely dreading tomorrow morning now with the thought our manager has also read this article.
Heh and I was able to do some of that work in service of the dumb but fun test of Internet vs Pigeon data transfer speeds.
I have a system prompt of around 100k which includes a couple of internal schema definitions. Having this cached could be super useful to us.
yes as an open source maintainer, this is a difficult decision I need to make for each project. On one hand, I want to do the right thing, but on the other, the initial convenience does come into play - but this can come back to bite us later when people play the green square game on the git ignore file in the GitHub repo
> it doesn't sit well with bizdev or project managers

To be fair, it makes everything twice as expensive. Managers are always going to reflexively push back against that, even if the new feature covers that cost and more.